New build blue screens, don't know where to start!

[theianhatton]

Hello all,

I am having quite a few problems with my new build (see specs below).

It started shortly after my first install of Windows 7 64-bit. I encountered frequent and random blue screens, (PAGE_FAULT_IN_NON_PAGED_AREA and IRQL_NOT_LESS_OR_EQUAL mainly). I changed a couple of settings in my BIOS:

DRAM voltage to 1.5 instead of AUTO.
Performance enhance to STANDARD instead of TURBO.

I was then able to run my computer for a solid 10 hours without a single problem (all tasks, including web browsing, watching videos and installing and using Adobe and iTunes software), but this morning I switched it on only to be greeted by a blue screen before my Windows log-in. As it stands now, 9 times out of 10 I can't make it into Windows but when I can, I'm only there for about 3 minutes before another blue screen gets me. For the record, all drivers are up to date and my motherboard is successfully flashed to the latest version.

The blue screens seem to always point to ntoskrnl.exe as the culprit and I'm more certain that the problem is a hardware one rather than a driver conflict as it seems to happen whether I have just Windows 7 installed or a bunch of other programs.

I'm wondering if I have incorrect settings in my BIOS for memory and other voltages. I also checked my motherboards Qualified Vendor List for memory support and noticed my RAM isn't on there; could this be a glaringly obvious problem I overlooked? I really don't know what I'm doing when it comes to things like this so any help would be greatly appreciated.

P.S. I will upload any dumps if I can get back into Windows and copy them to my USB.

Many thanks,

Ian

Intel Core i5 750
Gigabyte GA-P55M-UD2
Corsair 4GB (2x2GB) XMS3, DDR3 PC3-10666 (1333)
1TB Samsung SHD103SJ Spinpoint F3
Samsung 500GB HD501LJ Spinpoint T1
ATI Radeon HD 4870 1GB PCI-E
Tagan 680W TG680-U3II
Windows 7 64-bit

[Dave86]

Strangely I've had the exact same issue of being able to use the computers for hours at a time without a blue screen then one just popping up out of the blue with that exact memory memory, albit on a P43 platform.

I solved it by setting ram voltages and timing manually in the BIOS and never saw a blue screen again.

That being said mine never escalated like yours did this morning, have you tried running Memtest86 to check your memory?

[theianhatton]

Hi Dave, thanks for taking a look. I am running memtest86+ right now, it has had 4 passes with no errors. May I ask what your successful BIOS settings are?

[vti_786]

have you checked if your bios settings have changed back to the original settings that was casuing the issue in the first place, you say you changed to manual volatge from auto for the ram,maybe it has reverted back to what it was?

have you tried another OS?

or the usual, use 1 stick of ram (although it has passed memtest)
use onboard GPU, basically use the bare minimum needed to get the pc running

[Dingo]

Go into your computer management in control panel and look at the event logs to see what information is there. The error you have quoted is normally associated with a corrupted boot.ini so you should try recovery console using the OS cd.

[theianhatton]

Hi folks, I've tried everything I can think of including manually setting timings for my RAM as per Corsair's recommendations, adjusting QPI/Vtt Voltages which I have been advised to do, uninstalling software, updating drivers, running HDD diagnostic tools and memtest86+ on the RAM in different slots. I have also been through about six complete re-installs of Windows.

Many of the blue screens I am receiving now point to memory corruption but memtest86+ is happily working away giving me no errors.

I am still thoroughly confused! The problems do seem worse after the system has been off overnight or for a long time. Is it just my motherboard not getting along with my RAM? I am tearing my hair out over this!

Cheers,

Ian

[samsunglol?]

Ian,

I am having your exact same issue and we seem to have new spinpoint F3 103SJ hard drives in common.

I've gone through almost all the same steps for troubleshooting as well. Manually set factory RAM timing, Running memtest for 24 hours straight, swapping PSUs, swapping RTM batteries, using the samsung util for testing, I even ran the computer for 7 days without shutdown and not a single bluescreen. Even tried different copies of Windows 7 x64 (ultimate and pro). But if I shutdown the computer over night, the next bootup will result in a totally corrupted copy of Windows.

Searching google to find someone with the same problem has been painful. Been working on this since March.

Over the last few days I have been finding more evidence that the hard drive is to blame. I have seen one reported issue in newegg reviews that mirrors ours and someone wrote a blog about very similar issues with a 103UJ. I unfortunately don't have another drive to test with but thats my next step. You should do the same if you can.

our specs other than the hard drive are completely different

ASRock M3A770DE mobo
Athlon II 240
OCZ 550w PSU fatality edition(it was on sale!)
2x2gb Gskill ripjaws (F3-12800CL9D-4GBRL)
Gigabyte 220GT
No name DVD writer
and of course the Samsung Spinpoint F3 SHD103SJ

Hi folks, I've tried everything I can think of including manually setting timings for my RAM as per Corsair's recommendations, adjusting QPI/Vtt Voltages which I have been advised to do, uninstalling software, updating drivers, running HDD diagnostic tools and memtest86+ on the RAM in different slots. I have also been through about six complete re-installs of Windows.

Many of the blue screens I am receiving now point to memory corruption but memtest86+ is happily working away giving me no errors.

I am still thoroughly confused! The problems do seem worse after the system has been off overnight or for a long time. Is it just my motherboard not getting along with my RAM? I am tearing my hair out over this!

Cheers,

Ian

[kalniel]

I am still thoroughly confused! The problems do seem worse after the system has been off overnight or for a long time. Is it just my motherboard not getting along with my RAM? I am tearing my hair out over this!

Possibly, also don't forget the memory controller is on the CPU, so that's part of the equation now as well.

[opel80uk]

I don't know if this is right, and there are certainly much better qualified people then me on this forum (and you are in the right place!), but when I made my new build I had a problem with my RAM settings, and was getting a blue screen. This was sorted when I changed the command rate down to 800MHz. I doubt this will be the problem for you, as these were settings I mucked around with beforehand, but when seeking help I was told to try putting in just one memory stick at a time and seeing if that made a difference.

Like I said, probably not that, but just an idea!

Good luck!

[theianhatton]

Thanks for the replies folks. I never did find a solution to my problems. Scan have accepted an RMA for my system and are going to test it for faults.