BSODs on my new PC

Hi everyone,
Just 10 days ago I bought a new computer and already experience Blue screen errors. I ran lots of hardware testing programs such as Memtest86+, Intel Burn Test, Prime95, FurMark and none of them detected any errors. I have been having BSODs for a couple of days and reinstalled OS several times.
Today I reinstalled the Windows on my SATA drive instead of the SSD and also removed 2 sticks of my RAM ( 8gb) and already had a crash.

I read the BSOD posting instruction. However, at Step 3 when I run performance monitor clicking on "File" gives me just "Options" and "Exit" options. In there I can open Resource Monitor but there I got only "Save settings as" and its not an HTML file. I got Windows_NT6_BSOD_jcgriff2 folder though. Should I zip and post just it?

I was advised to use Whocrashed programme and the crash I had today with OS installed on my SATA and with 8gb RAM instead of 16 is here:

On Tue 14/06/2011 13:54:18 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0x00000000)
Bugcheck code: 0x50 (0xFFFFFA810BAAA29F, 0x0, 0xFFFFF880094F50E0, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: Unknown .
Google query: Unknown PAGE_FAULT_IN_NONPAGED_AREA

Previously when I had Windows on my SSD and all 4 sticks of RAM enabled the latest error was:

On Mon 13/06/2011 10:52:38 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0x00000000)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002EA05C0, 0xFFFFF8800A8AEEB0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: Unknown .
Google query: Unknown SYSTEM_SERVICE_EXCEPTION

I am really desperate now, can not find the cause of problems! I did Memtest86+ with 2 sticks of ram and again no errors. I have Windows 7 64bit home bought from retailer.
I posted the issue on other forums as well and some of recommendations were to set RAM voltage to 1.55v and to try to run my PC without VGA..
Any kind of help is truly appreciated.

ShortMeister said:

Hi everyone,
Just 10 days ago I bought a new computer and already experience Blue screen errors. I ran lots of hardware testing programs such as Memtest86+, Intel Burn Test, Prime95, FurMark and none of them detected any errors. I have been having BSODs for a couple of days and reinstalled OS several times.
Today I reinstalled the Windows on my SATA drive instead of the SSD and also removed 2 sticks of my RAM ( 8gb) and already had a crash.

I read the BSOD posting instruction, however at Step 3 when I run performance monitor clicking on "File" gives me just "Options" and "Exit" options. In there I can open Resource Monitor but there I got only "Save settings as" and its not an HTML file. I got Windows_NT6_BSOD_jcgriff2 folder though. Should I zip and post just it?

I was advised to use Whocrashed programme and the crash I had today with OS installed on my SATA and with 8gb RAM instead of 16 is here:

On Tue 14/06/2011 13:54:18 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0x00000000)
Bugcheck code: 0x50 (0xFFFFFA810BAAA29F, 0x0, 0xFFFFF880094F50E0, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: Unknown .
Google query: Unknown PAGE_FAULT_IN_NONPAGED_AREA

Previously when I had Windows on my SSD and all 4 sticks of RAM enabled the latest error was:

On Mon 13/06/2011 10:52:38 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0x00000000)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002EA05C0, 0xFFFFF8800A8AEEB0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: Unknown .
Google query: Unknown SYSTEM_SERVICE_EXCEPTION

I am really desperate now, can not find the cause of problems! I did Memtest86+ with 2 sticks of ram and again no errors. I have Windows 7 64bit home bought from retailer.
I posted the issue on other forums as well and some of recommendations were to set RAM voltage to 1.55v and to try to run my PC without VGA..
Any kind of help is truly appreciated.

Try this method.




To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.



To ensure minidumps are enabled:

Go to Start, in the Search Box type: sysdm.cpl, press Enter.
Under the Advanced tab, click on the Startup and Recovery Settings... button.
Ensure that Automatically restart is unchecked.
Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
OK your way out.
Reboot if changes have been made.

I already changed the way of logging the dump files which was "Kernel memory dump" on default to Small memory dumps , but it was after I had my last crash. I'll wait until the next one and post the results once I have it.