The page faults occur mostly while playing WoW. The other ones usually just happen at random times after I walk away from the comp.
I checked the RAM with memtest and it passed with 0 errors (though I only allowed it 1 pass).
Thanks for any info you can give.
Last edited by Doompa; 01 Jun 2010 at 10:30.
Update: I ran memtest through 5 passes and recieved zero errors.
Any help on analyzing the dump files would be appreciated.
Welcome to SF!
Please follow these directions for enabling Driver Verifier: Using Driver Verifier to identify issues with Drivers
Update these old drivers:How To Find Drivers:Code:wanatw64.sys Mon Apr 11 18:07:10 2005 ctac32k.sys Wed Jul 02 04:38:22 2008 gdrv.sys Sat Oct 13 03:22:00 2007- - The most common drivers are listed on this page: Driver Reference- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - Driver manufacturer links are on this page: Drivers and Downloads
Code:BugCheck 7F, {8, 80050031, 6f8, fffff800030075f4} Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 ) ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии BugCheck 50, {7ffe0324, 0, 7532ee15, 8} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+43057 ) ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии BugCheck 3B, {c0000005, fffff960003741d9, fffff88003ab9070, 0} Probably caused by : win32k.sys ( win32k!DestroyUMPDHeap+d ) ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии BugCheck 50, {fffff100123ab960, 1, fffff80002d99042, 7} Probably caused by : ntkrnlmp.exe ( nt!NtClearEvent+32 ) ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии BugCheck 1A, {41201, fffff680002d6940, eb3000800a87e847, fffffa8009413a90} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13bb2 ) ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
Thanks.
The gdrv.sys I guess is from Gigabyte's Dynamic Energy Save. I never used the program so I went and uninstalled it and changed the name of that driver.
From what I found the ctac32k.sys is from Creative. I have a creative x-fi fatal1ty but from what I've been reading, the file is for an Audigy card which confused me quite a bit. This was a clean install of Win 7 so there should not be any other card drivers on there (along with the fact that I've never had an audigy) but I assume it was put there for a reason.
The wanatw64.sys I could find very little information on but it appears to be related to AOL
Were one of these drivers causing the crashes? I figured it was RAM or my video card.
wanatw64.sys could also be your network adapter drivers.
Old drivers can have compatibility issues, and cause a BSOD. Whether or not those drivers caused your problem is unclear, but even if not, old drivers should still be updated.
My network adapter driver was dated from March of 2010.
I wish those dumps could have told me something about what was causing the problem. It doesn't happen too often but the page faults happen after playing World of Warcraft for a period of time so I figured it was the RAM or the vid card
The dmps point to a driver issue, most likely. Please enable driver verifier, and hopefully it will tell us which one.
Using Driver Verifier to identify issues with Drivers
Ok i enabled it and now the comp is on the Starting Windows screen and has been for awhile. I hear the comp loading stuff so is it verifying?
It will be verifying in the background.
Leave it for maybe 30 minutes, and reboot it if it hasn't moved on. Your system may be slow and crashy until you turn it off.
I had to do a system restore to get to windows but it seems to be working fine now.
I did the driver verification and got an immediate crash 2 times. The driver has to do with Spyware Doctor. I'm going to run the driver test without testing that driver to see if it is something else too.
Quote