My system keeps crashing!

[kimboviper]

i have tried everything, new mobo, fresh installs, memtest. Everything and nothing stops these BSOD from happening. It is really frustating.

I am running a:

Phenom X4 955
HD5770
Intel 40gb SSD
MSI 890gxm-g65 motherboard
Corsair XMS DDR3 1600mhz RAM

Please help!

 

[usasma]

There's only 2 of them - do you have any more?
When do they occur?

Try running Driver Verifier according to these directions:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Jun 14 17:03:45.056 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:14.882
BugCheck E3, {fffffa80054c2c70, fffffa80057d1060, 0, 2}
Probably caused by : win32k.sys ( win32k!CreateXlateObject+78f )
BUGCHECK_STR:  0xE3
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Jun 14 17:03:08.563 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:29.389
BugCheck 18, {0, fffffa8005bedf90, 2, ffffffffffffffff}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+46661 )
BUGCHECK_STR:  0x18
PROCESS_NAME:  WerFault.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
  
  
 
[/font]

 

[kimboviper]

this is a very random BSOD

over the past month i probably have 20+ BSOD's but i keep reinstalling windows 7. Maybe i should try XP.

 

[ttran]

keep re-installing window 7 without updating drivers will give u same results, I mean BSODs. Everytime your computers get BSOD, it will create minidump files. Please keep uploading them to forum. I used to think the same way as u do. I love window xp and when my computer with window 7 crashed, i thought of installing window xp. But I visited this forum, and I learnt that updating driver could help me to use window 7, which is great operating system.
Please don't give up, if u have more BSOD, please upload them

 

[kimboviper]

here are some more recent BSOD's

also they usually happen when i boot the system. usually i get a win explorer crash and then i get the BSOD. I am running Steam but i also run it on my thinkpad edge laptop and it never crashes!!

I am overclocking my desktop to 3.8ghz but it still occurs if i set back to the stock clock speed.


thanks in advance!

 

[CarlTR6]

You have five mini dumps with five different stop error codes. This usually indicates hardware problems. It will take me a few minutes to look at these.

STOP 0x00000018: REFERENCE_BY_POINTER

Usual causes: Device driver, kernel, hardware

BSOD Index


STOP 0x000000E3: RESOURCE_NOT_OWNED

Usual causes: Device driver

BSOD Index


STOP 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint with no debugger attached, Hardware incompatibility, Faulty system service, Memory, 3rd party remote control,

BSOD Index


STOP 0x0000003B: SYSTEM_SERVICE_EXCEPTION

Usual causes: System service, Device driver, graphics driver, ?memory

BSOD Index


STOP 0x00000024: NTFS_FILE_SYSTEM

Usual causes: Disk corruption, insufficient physical memory, Device driver, Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure

BSOD Index

 

[CarlTR6]

Here are the results of the mini dumps.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 18, {0, fffffa8005bedf90, 2, ffffffffffffffff}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+46661 )

Followup: MachineOwner

******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck E3, {fffffa80054c2c70, fffffa80057d1060, 0, 2}

Probably caused by : win32k.sys ( win32k!CreateXlateObject+78f )

Followup: MachineOwner

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, 100, fffff880031e8148, fffff880031e79a0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+448f7 )

Followup: MachineOwner

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002fe2121, fffff88004420160, 0}

Probably caused by : ntkrnlmp.exe ( nt!ObpCloseHandleTableEntry+51 )

Followup: MachineOwner

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff8800317e898, fffff8800317e0f0, fffff88001342dc1}

Probably caused by : Ntfs.sys ( Ntfs!TxfDeleteTxfFo+11 )

Followup: MachineOwner

Did you follow John's recommendation above to run Driver Verifier? If not, please do so and we will go from there.

 

[ttran]

Hi there
In one of the five parameter above indicated memory exception (ffffffffc0000005), so I would suggest download third party called memtesst86, burn it to cd and let it run for at least 7 passes

Bugcheck for that one:

BugCheck 1000007E, {ffffffffc0000005, 100, fffff880031e8148, fffff880031e79a0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::NNGAKEGL::`string'+448f7 )
Followup: MachineOwner
---------

Regard
T

 

[kimboviper]

i have already done memtest and driver verifier.

 

[kimboviper]

i already ran bluescreenview and it is always the same files that crash but i have researched those files and they are very vague to what is truly causing the crashes. this is so frustrating that i want to throw my desktop out the window!

 

[reventon]

It is almost certainly a Hardware issue, as you still have it after several Re-installs.

RAM - you have checked
Motherboard - You have replaced, so it should be fine. However the pattern of STOP codes I am seeing I have seen before with a faulty motherboard (my own).

A faulty CPU could also cause these errors that you are getting - is it easy for you to RMA it or swap it out with one you have spare?

Other than that, you could try swapping out your graphics card.

EDIT: Just thought of something; What PSU are you running?

Regards,
Reventon

 

[usasma]

This is a hardware problem.
The first step is to stop overclocking - then, if you get BSOD's we can troubleshoot them
If you don't get BSOD's after stopping the overclock - then the problem is the overclock.

Once the system is returned to stock settings, then try these free diagnostics:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Malware (read the details at the link)

If those tests pass (without overclocking) then try these free stress tests (without overclocking):

*****
Additional tests for certain specific circumstances:
Try this free video stress test: FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net

FurMark Setup:
- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit

Try this free stress test: Free Software - GIMPS

Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
This won't necessarily crash the system - but check the output in the test window for errors.
The Test selection box and the stress.txt file describes what components that the program stresses.

Let us know the results of the test (and don't go back to overclocking until we've finished troubleshooting your issues).

 

[kimboviper]

the CPU has been changed from 925 to a 955 phenom X4

the mobo has been changed from a GA-785gmt-ud2h to a MSI 890gxm-G65

the Ram has been tested with memtest and passed

there are no viruses or malware on the system

here is the latest minidump with alot more crashes. I am sick and tired of this system and am about to throw it out the window!!

 

[Jonathan_King]

I suspect graphics card. Did you follow all of usasma's advice above?

BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Jun 23 11:30:19.235 2010 (GMT+12)
System Uptime: 0 days 0:00:39.640
BugCheck 3B, {c0000005, fffff8000302aaab, fffff88009423020, 0}
Probably caused by : ntkrnlmp.exe ( nt!EtwpSendNoReplyReply+1b )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x3B
PROCESS_NAME:  WerFault.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Jun 23 11:29:15.997 2010 (GMT+12)
System Uptime: 0 days 0:01:13.792
BugCheck 44, {fffff98010ddaee0, 346, 0, 0}
Probably caused by : Npfs.SYS ( Npfs!NpFsdWrite+76 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x44
PROCESS_NAME:  MOM.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Jun 22 15:37:23.812 2010 (GMT+12)
System Uptime: 0 days 0:00:31.592
BugCheck 3B, {c0000005, fffff80002cdc4e0, fffff880091dae60, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceHandler+7c )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x3B
PROCESS_NAME:  WerFault.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Jun 22 15:36:28.526 2010 (GMT+12)
System Uptime: 0 days 0:00:41.305
BugCheck 3B, {c0000005, fffff80002f6acd0, fffff880090ebe90, 0}
Probably caused by : ntkrnlmp.exe ( nt!AlpcpFlushResourcesPort+44 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x3B
PROCESS_NAME:  iexplore.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Jun 22 15:35:24.250 2010 (GMT+12)
System Uptime: 0 days 0:00:33.655
BugCheck 44, {fffff9801098cc60, 346, 0, 0}
Probably caused by : CLASSPNP.SYS ( CLASSPNP!TransferPktComplete+1ce )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x44
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Jun 22 15:34:27.241 2010 (GMT+12)
System Uptime: 0 days 0:00:58.020
BugCheck 3B, {c0000005, fffff8000301faab, fffff88002856020, 0}
Probably caused by : ntkrnlmp.exe ( nt!EtwpSendNoReplyReply+1b )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x3B
PROCESS_NAME:  WerFault.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Jun 22 15:33:08.474 2010 (GMT+12)
System Uptime: 0 days 0:00:07.269
BugCheck 44, {fffff980026e0ea0, 346, 0, 0}
Probably caused by : ataport.SYS ( ataport!IdeCompleteScsiIrp+62 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x44
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Jun 19 13:39:13.741 2010 (GMT+12)
System Uptime: 0 days 1:45:54.536
BugCheck 4E, {9a, 1ab8b, 2, 0}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_SEGMENT::SafeUnlockPages+31 )
BUGCHECK_STR:  0x4E_9a
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  dwm.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/font]

 

[kimboviper]

i ran all the HW diagnostics and it passed without any BSOD's

 

[Jonathan_King]

See if you can change out your graphics card. If you can't find one to borrow, I suggest purchasing one from a store that will allow you to return it if it is not the cause.

PSU is another thing to consider. What brand and model is it?

You may consider borrowing one from another machine, or buying one like the graphics card.

 

[kimboviper]

PSU is a Antec Earthwatts 650w

I will try another GPU. I will try a 5870 at Frys.

thanks

 

[kimboviper]

i changed the video card to GTX465 and I get the same results!!!

im going to try a diff PSU.

 

[reventon]

Hi,

May I ask when did you change the card? Before or after the latest round of minidumps?

[FONT=lucida console]
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Jul  4 13:44:12.875 2010 (GMT+12)
System Uptime: [COLOR=Red]0 days 0:00[B]:[/B][B]10.717[/B][/COLOR]
BugCheck 3B, {[COLOR=Red][B]c0000005[/B][/COLOR], fffff88012569321, fffff880049d1cd0, 0}
Probably caused by : [COLOR=Red][B]nvlddmkm.sys[/B][/COLOR] ( nvlddmkm+69e321 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x3B
PROCESS_NAME:  csrss.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Jul  3 16:23:54.905 2010 (GMT+12)
System Uptime: 0 days 0:02:51.357
BugCheck 4E, {9a, 8fbba, 1, 0}
Probably caused by : [COLOR=Red][B]dxgmms1.sys[/B][/COLOR] ( dxgmms1!VIDMM_SEGMENT::SafeUnlockPages+31 )
BUGCHECK_STR:  0x4E_9a
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  dwm.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Jul  2 16:43:17.281 2010 (GMT+12)
System Uptime: [COLOR=Red]0 days 0:00:[B]11.122[/B][/COLOR]
BugCheck 3B, {[COLOR=Red][B]c0000005[/B][/COLOR], fffff88011fe68e1, fffff880049d9860, 0}
Probably caused by : [COLOR=Red][B]nvlddmkm.sys[/B][/COLOR] ( nvlddmkm+1178e1 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x3B
PROCESS_NAME:  csrss.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Jun 30 12:30:45.676 2010 (GMT+12)
System Uptime: [COLOR=Red]0 days 0:00:[B]08.502[/B][/COLOR]
BugCheck 1000007E, {ffffffff[COLOR=Red][B]c0000005[/B][/COLOR], fffff800033bb282, fffff880031a1a48, fffff880031a12a0}
Probably caused by : ntkrnlmp.exe ( nt!CmpDelayDerefKCBWorker+d6 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
[/FONT]

The above dumps are not all of the ones you have got since the last debug - you can find more below. These 4 however are the interesting ones; as on 3 of the above dumps the uptime was less than 15 seconds - this usually suggests a boot driver to be at fault and given both named the NVidia graphics driver it is pretty clear it is a graphics related issue.

However also note the c0000005 first parameter - means memory corruption. This can be caused by faulty hardware or poorly coded drivers.

System Uptime for latest 8 crashes:

[FONT=lucida console]
[COLOR=Red]0 days 0:00:10.717[/COLOR]
0 days 0:02:51.357
[COLOR=Red]0 days 0:00:07.363[/COLOR]
0 days 0:01:18.954
[COLOR=Red]0 days 0:00:11.122[/COLOR]
[COLOR=Red]0 days 0:00:08.502[/COLOR]
0 days 0:02:16.903
[COLOR=Red]0 days 0:00:07.363[/COLOR]
0 days 0:02:06.329
[/FONT]

I have seen BSODs with Corsair RAM that were solved by slightly upping the voltage in the BIOS - you tried that yet?

Regards,
Reventon

BUGCHECK SUMMARY

[FONT=lucida console]
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Jul  4 13:44:12.875 2010 (GMT+12)
System Uptime: 0 days 0:00:10.717
BugCheck 3B, {c0000005, fffff88012569321, fffff880049d1cd0, 0}
Probably caused by : nvlddmkm.sys ( nvlddmkm+69e321 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x3B
PROCESS_NAME:  csrss.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Jul  3 16:23:54.905 2010 (GMT+12)
System Uptime: 0 days 0:02:51.357
BugCheck 4E, {9a, 8fbba, 1, 0}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_SEGMENT::SafeUnlockPages+31 )
BUGCHECK_STR:  0x4E_9a
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  dwm.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Jul  3 16:18:40.521 2010 (GMT+12)
System Uptime: 0 days 0:00:07.363
BugCheck 44, {fffff98003862ea0, 346, 0, 0}
Probably caused by : ataport.SYS ( ataport!IdeCompleteScsiIrp+62 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x44
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Jul  2 16:45:03.502 2010 (GMT+12)
System Uptime: 0 days 0:01:18.954
BugCheck 44, {fffff9800fd82c60, 346, 0, 0}
Probably caused by : CLASSPNP.SYS ( CLASSPNP!TransferPktComplete+1ce )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x44
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Fri Jul  2 16:43:17.281 2010 (GMT+12)
System Uptime: 0 days 0:00:11.122
BugCheck 3B, {c0000005, fffff88011fe68e1, fffff880049d9860, 0}
Probably caused by : nvlddmkm.sys ( nvlddmkm+1178e1 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x3B
PROCESS_NAME:  csrss.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Wed Jun 30 12:30:45.676 2010 (GMT+12)
System Uptime: 0 days 0:00:08.502
BugCheck 1000007E, {ffffffffc0000005, fffff800033bb282, fffff880031a1a48, fffff880031a12a0}
Probably caused by : ntkrnlmp.exe ( nt!CmpDelayDerefKCBWorker+d6 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
BUGCHECK_STR:  0x7E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Jun 29 17:12:48.452 2010 (GMT+12)
System Uptime: 0 days 0:02:16.903
BugCheck A, {20000011d, 2, 1, fffff800030d8329}
Probably caused by : ntkrnlmp.exe ( nt!NtWaitForWorkViaWorkerFactory+318 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  svchost.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Tue Jun 29 17:10:05.521 2010 (GMT+12)
System Uptime: 0 days 0:00:07.363
BugCheck 44, {fffff98002608ea0, 346, 0, 0}
Probably caused by : ataport.SYS ( ataport!IdeCompleteScsiIrp+62 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x44
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Jun 27 18:23:13.534 2010 (GMT+12)
System Uptime: 0 days 0:02:06.329
BugCheck 44, {fffff98010cb0c60, 346, 0, 0}
Probably caused by : CLASSPNP.SYS ( CLASSPNP!TransferPktComplete+1ce )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x44
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
[/FONT]

 

[kimboviper]

i have tried to up the voltage for the ram. I tried a different and much better PSU...Corsair 650TX and it still crashes

maybe they are the Nvidia drivers because they are crashing at bootup or directly after bootup but the odd thing is that it works perfectly after a few bootups.

what can i do if they are the Nvidia drivers? try older more stable drivers? where can i find those?