Windows 7: BSoD playing Everquest

Kailihn · 03 Jun 2012

I gave it one more try and OCCT is currently running...an hour left on the 2 hour test.
Once that completes I will run the SeaTools diagnostic.

usasma · 03 Jun 2012

Device Manager should show a number of unknown drives.
Right click on each one and uninstall it, then reboot.
Check to ensure that they aren't there any more (they're usually your media card reader)

9 memory dumps
8 different BSOD error codes
5 different causes blamed

This is most likely a hardware error. They (hardware errors) are usually caused by one of these things:
- borked (broken) hardware (several different procedures used to isolate the problem device)
- overclocking - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
- compatibility issues
- low-level driver problems
- or even malware (scanned for when we ask for hardware diagnostics from Initial Hardware Diagnostics or Hardware Diagnostics ).

AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Windows 7 systems.

Quote:

Please uninstall all AMD/ATI video stuff from Control Panel...Programs...Uninstall a program
Then, download and install a fresh copy of the ATI drivers from Global Provider of Innovative Graphics, Processors and Media Solutions | AMD (in the upper right corner of the page)
Use this procedure to install the DRIVER ONLY: ATI video cards - DRIVER ONLY installation procedure

If the device (AODDriver or AODDriver4.01) remains a problem, open Device Manager, select the "View" item.
Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
Locate the AODDriver entry, right click on it and select "Uninstall". Reboot for changes to take affect.

Sometimes the driver remains and continues to cause BSOD's. If this is the case for you, post back and we'll give further instructions for safely removing it.

If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.

If that doesn't fix the issues, then continue with the hardware diagnostics.

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs

- Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html
- Info on how to troubleshoot BSOD's (DRAFT): http://www.carrona.org/userbsod.html
- How I do it: http://www.carrona.org/howidoit.html

3RD PARTY DRIVERS PRESENT IN THE DUMP FILES

Code:


amdxata.sys        Fri Feb 05 21:03:57 2010 (4B6CCE0D)
amdsata.sys        Fri Feb 05 21:03:55 2010 (4B6CCE0B)
MpFilter.sys       Fri Mar 09 06:05:26 2012 (4F59E3F6)
AtiPcie64.sys      Wed Mar 10 09:33:45 2010 (4B97ADC9)
atikmpag.sys       Mon Oct 24 00:40:06 2011 (4EA4EC26)
Rt64win7.sys       Fri Feb 03 08:00:02 2012 (4F2BDA52)
usbfilter.sys      Wed Dec 14 02:44:02 2011 (4EE853C2)
netr28x.sys        Fri Feb 03 08:57:13 2012 (4F2BE7B9)
amdiox64.sys       Thu Feb 18 10:17:53 2010 (4B7D5A21)
AtihdW76.sys       Thu Feb 23 07:30:12 2012 (4F463154)
atikmdag.sys       Mon Oct 24 01:12:50 2011 (4EA4F3D2)
RTKVHD64.sys       Tue Jun 08 05:08:08 2010 (4C0E0878)
Sftvollh.sys       Fri Sep 30 12:42:46 2011 (4E85F186)
rikvm_C6F09094.sys Tue Jun 29 08:17:18 2010 (4C29E44E)
Sftfslh.sys        Fri Sep 30 12:43:06 2011 (4E85F19A)
Sftplaylh.sys      Fri Sep 30 12:43:05 2011 (4E85F199)
Sftredirlh.sys     Fri Sep 30 12:43:14 2011 (4E85F1A2)
psi_mf.sys         Wed Sep 01 03:53:14 2010 (4C7E066A)
cpuz135_x64.sys    Wed Sep 21 04:23:41 2011 (4E799F0D)
atikmpag.sys       Thu Apr 05 21:10:44 2012 (4F7E4294)
AODDriver2.sys     Tue Mar 06 04:55:00 2012 (4F55DEF4)
cpuz135_x64.sys    Tue Nov 09 08:33:36 2010 (4CD94DB0)
atikmdag.sys       Thu Apr 05 21:48:25 2012 (4F7E4B69)
netr28x.sys        Fri Dec 18 07:32:14 2009 (4B2B764E)

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\060312-14149-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Sun Jun  3 13:47:58.113 2012 (UTC - 4:00)
System Uptime: 0 days 0:03:11.284
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2
Bugcheck code 0000007F
Arguments 00000000`00000008 00000000`80050031 00000000`000006f8 fffff800`02ce1050
BiosVersion = 6.02
BiosReleaseDate = 07/21/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\060312-14851-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Sun Jun  3 13:44:02.210 2012 (UTC - 4:00)
System Uptime: 0 days 0:15:42.381
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+49331 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x18
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID:  X64_0x18_OVER_DEREFERENCE_nt!_??_::FNODOBFM::_string_+49331
Bugcheck code 00000018
Arguments 00000000`00000000 fffffa80`09fa5d20 00000000`00000002 ffffffff`ffffffff
BiosVersion = 6.02
BiosReleaseDate = 07/21/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\060312-17737-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Sun Jun  3 13:27:28.707 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:08.611
Probably caused by : ntkrnlmp.exe ( nt!ExpSystemErrorHandler2+5ff )
BUGCHECK_STR:  0xc0000221
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xc0000221_nt!ExpSystemErrorHandler2+5ff
Bugcheck code C0000221
Arguments fffff8a0`00092900 00000000`00000000 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\060312-15537-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Sun Jun  3 13:19:59.940 2012 (UTC - 4:00)
System Uptime: 0 days 1:08:45.751
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_SEGMENT::SafeUnlockPages+31 )
BUGCHECK_STR:  0x4E_9a
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  firefox.exe
FAILURE_BUCKET_ID:  X64_0x4E_9a_dxgmms1!VIDMM_SEGMENT::SafeUnlockPages+31
Bugcheck code 0000004E
Arguments 00000000`0000009a 00000000`001fa206 00000000`00000000 00000000`00000000
BiosVersion = 6.02
BiosReleaseDate = 07/21/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\060312-15100-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Sun Jun  3 12:03:45.499 2012 (UTC - 4:00)
System Uptime: 0 days 0:03:29.670
Probably caused by : ntkrnlmp.exe ( nt!KiTryUnwaitThread+28 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  linpack_xeon64
FAILURE_BUCKET_ID:  X64_0xA_nt!KiTryUnwaitThread+28
Bugcheck code 0000000A
Arguments 00000000`00000040 00000000`00000002 00000000`00000001 fffff800`02ced688
BiosVersion = 6.02
BiosReleaseDate = 07/21/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\060312-20373-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Sun Jun  3 11:44:38.193 2012 (UTC - 4:00)
System Uptime: 0 days 0:17:09.364
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+45a45 )
BUGCHECK_STR:  0x1a_41287
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  CPUStabTest.ex
FAILURE_BUCKET_ID:  X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+45a45
Bugcheck code 0000001A
Arguments 00000000`00041287 00000000`00000080 00000000`00000000 00000000`00000000
BiosVersion = 6.02
BiosReleaseDate = 07/21/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\060312-15459-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Sun Jun  3 11:14:44.382 2012 (UTC - 4:00)
System Uptime: 0 days 0:15:11.193
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+cbb )
BUGCHECK_STR:  0x19_3
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+cbb
Bugcheck code 00000019
Arguments 00000000`00000003 fffff8a0`09197010 fffff8a0`09197010 fffffa80`0699d020
BiosVersion = 6.02
BiosReleaseDate = 07/21/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\060212-17487-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Sat Jun  2 21:06:24.074 2012 (UTC - 4:00)
System Uptime: 0 days 4:32:51.884
Probably caused by : Ntfs.sys ( Ntfs! ?? ::FNODOBFM::`string'+2b49 )
PROCESS_NAME:  eqgame.exe
BUGCHECK_STR:  0x24
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
FAILURE_BUCKET_ID:  X64_0x24_Ntfs!_??_::FNODOBFM::_string_+2b49
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`04142e98 fffff880`041426f0 fffff800`02dbb007
BiosVersion = 6.02
BiosReleaseDate = 07/21/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\053112-22245-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Thu May 31 21:03:29.252 2012 (UTC - 4:00)
System Uptime: 0 days 0:10:07.423
Probably caused by : win32k.sys ( win32k!SetWakeBit+f8 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  msseces.exe
FAILURE_BUCKET_ID:  X64_0xA_win32k!SetWakeBit+f8
Bugcheck code 0000000A
Arguments 00000000`00000019 00000000`00000002 00000000`00000001 fffff800`02cd4a10
BiosVersion = 6.02
BiosReleaseDate = 07/21/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Kailihn · 03 Jun 2012

I removed all the unknown drives in Device Manager.

I completed the OCCT, VMT and SeaGate Tools (which I found very easy to use btw) tests and all passed with no errors.

Malware scans the other day came back negative and I ran Housecall again just now with no threats found.

I don't over clock and I've Uninstalled AoDDriver4.1 yet again. It's worse than a weed. Is there anything else I can do to stamp it out for good?

I have no idea what artifacts are, but the Artifact Locator came up with 69233 GDI Artifacts with 0 for all other types.

I think I've covered all the hardware diagnostics on your page but still have no clear indicator as to what the problem is. No overclocking and no new hardware installed leaves me with low level drivers or something broken. So how do we go about isolating any broken hardware?

usasma · 04 Jun 2012

How to stamp out AoDDriver4.1 - buy an nVidia video card :0)

Are you still getting BSOD's? If not, then I suspect it was the AoDDriver.
But wait and see if you get any more.
If you do, we'll use the dump files to ensure that there are no more compatibility issues or low-level drivers causing problems (anything dated 2009 or earlier is included in this - with antivirus and video drivers being the absolute latest available).

Kailihn · 04 Jun 2012

OK...by the time I finished the diagnostics it was time for bed so there was no gaming for me. Tonight I will take it for a test drive and see if I crash before I go out replacing my video card

I don't understand though, how this same set of hardware and software was stable for a year and then suddenly went into meltdown. I'm guessing that driver updates and the like might be the culprit?

usasma · 04 Jun 2012

Well, it depends on what caused it.

Generally I break problems down into these 3 categories:
- 3rd party driver/software problems
- hardware problems
- Windows problems

Now a computer is like a car - it's just not going to run forever without maintenance and parts (hardware and software) replacement. Things wear out, things get corrupted, things need to be updated/repaired.

FYI - it's my opinion that updates aren't to blame - rather it's the stuff that isn't updated that interferes with the new updates and causes the problems.

Good luck!

Kailihn · 08 Jun 2012

I've been able to play my game twice (both for atleast an hour) now without crashing.
I'd like to see if it will run for a few hours straight without crashing before I mark this as resolved....but I am hopeful!

I apologize for the delay, but work has kept me too busy to use my computer in a way that would cause a problem. With the weekend here, I should be able to sneak in some play time. I will post here once I give it a good testing and if all goes well, my problem should be solved.

usasma · 08 Jun 2012

I know the problem. I've got RAM problems and I don't have the time to work on them.
Good luck!

Windows 7: BSoD playing Everquest

BSoD playing Everquest problems?