Win7 64 BSOD

Hello all,

I installed win7 pro 64 about 2 months ago and get random BSOD about once a week. I'm new at looking at the minidump files but installed windb and from what I can tell it is for different reasons (I could be reading the files completely wrong). I ran memtest86 for 6 passes last night and found nothing. I have posted the minidump files if anybody could help.

Oh, my system specs are:
Core 2 Duo E6750
ASUS P5N-E MB
XFX 8800 GTS
4 (1 gig) Corsair 800
Creative Xtremegamer sound card
1 320 gig WD 7200 SATA HD (boot)
2 500 gig WD 7200 SATA HD running RAID 0 (my documents)

Again, any help would be greatly appreciated and all of my drivers are up to date.

vikingking50 said:

Hello all,

I installed win7 pro 64 about 2 months ago and get random BSOD about once a week. I'm new at looking at the minidump files but installed windb and from what I can tell it is for different reasons (I could be reading the files completely wrong). I ran memtest86 for 6 passes last night and found nothing. I have posted the minidump files if anybody could help.

Oh, my system specs are:
Core 2 Duo E6750
ASUS P5N-E MB
XFX 8800 GTS
4 (1 gig) Corsair 800
Creative Xtremegamer sound card
1 320 gig WD 7200 SATA HD (boot)
2 500 gig WD 7200 SATA HD running RAID 0 (my documents)

Again, any help would be greatly appreciated and all of my drivers are up to date.

Viking Hi and welcome

With so many different probable causes my first guess would be hardware. That being said there is one thing we can do to force your computer to fail. Its called driver verifier. It will make you blue screen. I have snipped Johns instructions for its use. Be sure to back up. Be sure to have a win 7 dvd

I also assume most of your crashes are from the raid. If you are overclocking or have adjust voltages reset them back to default

Ken J+

Code:

010710-24710-01.dmp    1/7/2010 8:54:02 PM        0x00000119    00000000`07000000    fffffa80`074bb010    fffffa80`045a0700    fffffa80`045a1be0    watchdog.sys    watchdog.sys+122f                    
111309-20030-01.dmp    11/13/2009 7:59:00 PM    ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY    0x000000fc    fffff960`0035536c    f18b5653`5151ec8b    fffff880`047c4a00    00000000`00000002    win32k.sys    win32k.sys+28536c                    
112909-25194-01.dmp    11/29/2009 8:25:12 PM    CRITICAL_OBJECT_TERMINATION    0x000000f4    00000000`00000003    fffffa80`07151b30    fffffa80`07151e10    fffff800`02dda240    ntoskrnl.exe    ntoskrnl.exe+71f00                    
110909-21918-01.dmp    11/9/2009 7:48:52 PM    DRIVER_IRQL_NOT_LESS_OR_EQUAL    0x000000d1    00000000`00000000    00000000`00000006    00000000`00000000    fffff880`0412e144    dxgmms1.sys    dxgmms1.sys+8144                    
111409-19812-01.dmp    11/14/2009 5:55:24 PM    DRIVER_IRQL_NOT_LESS_OR_EQUAL    0x000000d1    00000000`00000001    00000000`00000002    00000000`00000001    fffff880`03e4a408    USBPORT.SYS    USBPORT.SYS+2d408                    
120709-22557-01.dmp    12/7/2009 8:51:46 PM    DRIVER_IRQL_NOT_LESS_OR_EQUAL    0x000000d1    fffff87f`f12d3dcb    00000000`00000002    00000000`00000008    fffff87f`f12d3dcb    ntoskrnl.exe    ntoskrnl.exe+71f00                    
120909-23353-01.dmp    12/9/2009 10:02:54 PM    DRIVER_IRQL_NOT_LESS_OR_EQUAL    0x000000d1    00000000`00000000    00000000`00000006    00000000`00000001    fffff880`04c140bf    nvlddmkm.sys    nvlddmkm.sys+16d0bf                    
010410-24102-01.dmp    1/4/2010 9:35:42 AM    IRQL_NOT_LESS_OR_EQUAL    0x0000000a    fffff680`0035bb78    00000000`00000000    00000000`00000000    fffff800`02a93918    ntoskrnl.exe    ntoskrnl.exe+71f00                    
111509-20654-01.dmp    11/15/2009 11:29:36 AM    PAGE_FAULT_IN_NONPAGED_AREA    0x00000050    fffff960`002a0088    00000000`00000000    fffff960`001fa50b    00000000`00000000    win32k.sys    win32k.sys+2a0088                    
120409-24055-01.dmp    12/4/2009 2:44:24 PM    PAGE_FAULT_IN_NONPAGED_AREA    0x00000050    fffff900`f38d0ff8    00000000`00000001    fffff960`000e837a    00000000`00000002    nvlddmkm.sys    nvlddmkm.sys+63a94                    
010310-25568-01.dmp    1/3/2010 12:19:26 PM    SYSTEM_SERVICE_EXCEPTION    0x0000003b    00000000`c0000005    fffff960`000bff42    fffff880`029f59f0    00000000`00000000    win32k.sys    win32k.sys+3ff42                    
111709-20124-01.dmp    11/17/2009 9:56:24 AM    SYSTEM_SERVICE_EXCEPTION    0x0000003b    00000000`c0000005    fffff960`001038be    fffff880`046b8ef0    00000000`00000000    nvlddmkm.sys    nvlddmkm.sys+56534                    
112109-22292-01.dmp    11/21/2009 1:13:14 PM    SYSTEM_SERVICE_EXCEPTION    0x0000003b    00000000`c0000005    fffff880`0503e260    fffff880`07bf8e50    00000000`00000000    nvlddmkm.sys    nvlddmkm.sys+615260                    
121109-23712-01.dmp    12/11/2009 5:47:06 PM    SYSTEM_SERVICE_EXCEPTION    0x0000003b    00000000`c0000005    fffff960`0016830c    fffff880`038beac0    00000000`00000000    win32k.sys    win32k.sys+9830c                    
121209-22838-01.dmp    12/12/2009 10:18:44 AM    SYSTEM_SERVICE_EXCEPTION    0x0000003b    00000000`c0000005    fffff960`0014ecc0    fffff880`06be3d50    00000000`00000000    win32k.sys    win32k.sys+becc0                    
121309-23244-01.dmp    12/13/2009 11:18:50 AM    SYSTEM_SERVICE_EXCEPTION    0x0000003b    00000000`c0000005    fffff880`061aae7a    fffff880`06b5fd40    00000000`00000000    aswMonFlt.sys    aswMonFlt.sys+7e7a                    
121809-22776-01.dmp    12/18/2009 2:46:28 PM    SYSTEM_SERVICE_EXCEPTION    0x0000003b    00000000`c0000005    fffff960`0007f409    fffff880`0611ff50    00000000`00000000    win32k.sys    win32k.sys+1f409                    
122009-22776-01.dmp    12/20/2009 2:55:40 PM    SYSTEM_SERVICE_EXCEPTION    0x0000003b    00000000`c0000005    fffff800`02ad114c    fffff880`02e78130    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+71f00                    
122509-22510-01.dmp    12/25/2009 2:31:26 PM    SYSTEM_SERVICE_EXCEPTION    0x0000003b    00000000`c0000005    fffff880`0441a3ca    fffff880`07049da0    00000000`00000000    ks.sys    ks.sys+1a3ca                    
122609-24008-01.dmp    12/26/2009 2:11:16 PM    SYSTEM_SERVICE_EXCEPTION    0x0000003b    00000000`c0000005    fffff960`0014b321    fffff880`06d23fc0    00000000`00000000    win32k.sys    win32k.sys+cb321                    
121009-23244-01.dmp    12/10/2009 11:14:28 PM    UNEXPECTED_KERNEL_MODE_TRAP    0x0000007f    00000000`00000008    00000000`80050031    00000000`000006f8    fffff800`02a9ee6e    ntoskrnl.exe    ntoskrnl.exe+71f00

[code]

Code:

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.

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.

More info on this at this link: http://support.microsoft.com/?kbid=244617&sd=RMVP

Thanks for the information. I will give that a try this afternoon. As far as RAID is concerned my only hesitation with blaming it is that my computer didn't blue screen on vista, just since I did a clean install of win7 64. Also, how likely is driver verify to toast my OS?

Thanks zigzag3143! I ran the verifier and it blue screened on me before my comp got into windows, so I went in safe mode and disabled the verifier and retrieved the following dump file. I'm not quite sure what to do from here so any suggestions would be great!

vikingking50 said:

Thanks for the information. I will give that a try this afternoon. As far as RAID is concerned my only hesitation with blaming it is that my computer didn't blue screen on vista, just since I did a clean install of win7 64. Also, how likely is driver verify to toast my OS?

Win 7 doesnt like RAID's. How likely depends on how bad the problem is. Backup just in case


Ken J+

I am also getting BSOD's about once a week, sometimes once a day.

Any help would be greatly appreciated!

I have saved and attached the NFO file. I am also going through and updating my drivers on that list (nvidia network driver, creative sound driver, and I'm going to flash the MB).