BSoD playing Everquest

Kailihn · May 26, 2012

Running Windows 7 Home Premium 64 bit which came preinstalled on my HP machine.
I recently used their recovery discs to restore it to factory settings but that didn't help.
This machine is about 18 months old and I have never overclocked it or replaced any of the original hardware.
Windows 7 Home Premium
AMD Phenom II x6 1045T 2.7 GHz
Foxconn 2AB1 DVT mobo
ATI Radeon Hd 5570
8 gigs RAM

Prior to resetting the software I was getting several different BSoD messages:
Driver IRQL not less or equal
Bad pool header
Bad pool caller
A device driver attempting to corrupt the system has been caught with an error code of 0x000000c4 indicating a file sftplaylh.sys

After restoring to factory settings my first attempt playing Everquest was error free for 3 hours. Today I crashed within 5-10 minutes with a Reference by pointer error.

I have run Memtest 86 and Windows own Memory Diagnostics multiple times with no errors.
I downloaded and ran Secunia's PSI program as well based on posts here to update my software.

Attached are the zipped system health report and the Windows NT6 folder as per the BSoD post instructions.

If you need any more information I will do my best to provide it, this is definitely a learn as I go experience

Thank you in advance!

usasma · May 26, 2012

Only 1 memory dump in the uploaded reports. If using a disk cleaner, please stop until we're finished troubleshooting.

SP1 isn't installed, please do the following:

Installing Windows 7 Service Pack 1
1. Visit the PC manufacturer's website and update ALL drivers. DO NOT use Windows Update or the "Update drivers" function of Device Manager.
2. Check Device Manager for any unknown/disabled devices - if there are unknown/disabled devices, fix them with the latest drivers from the device manufacturer's website (not the PC Manufacturer)
3. Visit Windows Update and get all updates (may take repeated visits)
4. Visit Windows Update and get Service Pack 1 (usually under Important Updates). Read these notes for installing SP1: Steps to follow before you install Windows 7 SP1 and Windows Server 2008 R2 SP1 from the Microsoft Download Center
5. Visit Windows Update and get any other available updates. May take repeated visits, but keep it up until you get several "Windows is updated" results.
If you're having difficulties with installing a Service Pack, please use the SURTool from this link: What is the System Update Readiness Tool?
Also, check out this troubleshooting link from Microsoft: Troubleshoot problems installing Service Pack 1 (SP1) for Windows 7 and Windows Server 2008 R2

I have had limited success in installing updates/Service Packs when using a "clean boot". I suspect that I'm just bypassing the problem - and that it can come back to bite me in the butt later on.

There's nothing certain about what I've seen in the reports, so let's hit the most common problem areas first (I'll suggest some tests later on that should give us more info).

Update Norton Internet Security to the latest available version. If you don't want to do that, then uninstall it and install a free antivirus for testing purposes (list here: Free AntiVirus )

Update your ATI video drivers to the latest version available from Global Provider of Innovative Graphics, Processors and Media Solutions | AMD

Update wireless network drivers. Yours date from 2009.

usbfilter.sys dates from 2009 - it's likely to be a part of the AMD chipset drivers. Please download and install the latest version from Global Provider of Innovative Graphics, Processors and Media Solutions | AMD

If this doesn't fix the BSOD's, please run Driver Verifier according to these instructions: Driver Verifier Settings

You can also start with the free hardware tests on this page as time allows. I don't suspect a hardware problem, but you can never be too sure! 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:

[font=lucida console]
amdsata.sys             Fri Feb 05 21:03:55 2010 (4B6CCE0B)
amdxata.sys             Fri Feb 05 21:03:57 2010 (4B6CCE0D)
SYMDS64.SYS             Tue Dec 07 19:16:58 2010 (4CFECE7A)
SYMEFA64.SYS            Sun Mar 13 23:20:58 2011 (4D7D899A)
AtiPcie64.sys           Wed Mar 10 09:33:45 2010 (4B97ADC9)
SYMNETS.SYS             Tue Apr 19 18:33:31 2011 (4DAE0DBB)
SYMEVENT64x86.SYS       Thu Mar 24 19:02:36 2011 (4D8BCD8C)
Ironx64.SYS             Fri Nov 12 18:06:50 2010 (4CDDC88A)
SRTSPX64.SYS            Tue Mar 29 22:46:18 2011 (4D92997A)
netr28x.sys             Fri Dec 18 07:32:14 2009 (4B2B764E)
eeCtrl64.sys            Fri Jan 20 18:39:48 2012 (4F19FB44)
EraserUtilRebootDrv.sys Fri Jan 20 18:39:49 2012 (4F19FB45)
atikmpag.sys            Mon May 17 17:30:26 2010 (4BF1B572)
BHDrvx64.sys            Tue Mar 13 16:02:37 2012 (4F5FA7DD)
Rt64win7.sys            Fri Feb 03 08:00:02 2012 (4F2BDA52)
atikmdag.sys            Mon May 17 17:56:09 2010 (4BF1BB79)
usbfilter.sys           Tue Dec 22 03:26:22 2009 (4B3082AE)
AtiHdmi.sys             Thu Apr 08 03:42:30 2010 (4BBD88E6)
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)
ENG64.SYS               Wed Apr 25 05:29:25 2012 (4F97C3F5)
SRTSP64.SYS             Tue Mar 29 22:46:12 2011 (4D929974)
psi_mf.sys              Wed Sep 01 03:53:14 2010 (4C7E066A)
IDSvia64.sys            Fri Mar 09 16:57:02 2012 (4F5A7CAE)
EX64.SYS                Wed Apr 25 05:27:28 2012 (4F97C380)
[/font]

Code:

[font=lucida console]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052612-34710-01.dmp]
Built by: 7600.16988.amd64fre.win7_gdr.120401-1505
Debug session time: Sat May 26 10:49:46.719 2012 (UTC - 4:00)
System Uptime: 0 days 13:03:06.062
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+45e3a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x18
PROCESS_NAME:  HPAdvisor.exe
FAILURE_BUCKET_ID:  X64_0x18_CORRUPT_REF_COUNT_nt!_??_::FNODOBFM::_string_+45e3a
Bugcheck code 00000018
Arguments fffffa80`06a18570 fffffa80`0b552a60 00000000`00000001 00000000`00000001
BiosVersion = 6.02
BiosReleaseDate = 07/21/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

Kailihn · May 28, 2012

Still crashing

SP1 was not visible to me until I installed the SUR tool, so that was a big help.

I updated Norton Internet Security, installed Service Pack 1, updated video drivers from the link and ran a Driver Autodetect from their site which gave me a new set of AMD drivers which I hope covered the usbfilter.sys file.

I am not sure how to update my wireless driver and I am not currently using wireless for my internet connection.

Once I did the aforementioned updates, I crashed about 10 minutes into my game so I turned on the Driver Verifier as per the instructions and tried the game again this evening. Memory Management and PNF List Corrupt errors provided some more dump files to look at.

I will try some of the hardware diagnostics tomorrow evening and see if that comes up with anything.

View attachment 214076

Thank you for your time

Michelle

usasma · May 29, 2012

If you're using a disk cleaning program, please stop while we're troubleshooting.

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 Win7 systems.

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 http://www.ati.com (in the upper right corner of the page)
- Select the "Custom" installation option and don't let it install AMD OverDrive or the VISION Engine Control Center (if present)
Then use the ATI uninstall manager to uninstall the Catalyst Control Center (CCC). This is a separate issue and isn't required for the AMD OverDrive removal.

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.

AMD chipset drivers still date from 2009 - please ensure that you have updated them. If you've done it, please include a link to the place that you downloaded them from.

As for the networking driver - if you're not using wireless, simply uninstall the software and remove the device (or disable it in the BIOS).

Don't forget to turn off Driver Verifier by using the "Delete existing settings" in the first screen>
This may end up being a hardware problem - so we have to address all of the older drivers in order to be sure of that.

In the event that it is a hardware problem, we'll start with these free diagnostics: 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:

[font=lucida console]
amdsata.sys             Fri Feb 05 21:03:55 2010 (4B6CCE0B)
amdxata.sys             Fri Feb 05 21:03:57 2010 (4B6CCE0D)
SYMDS64.SYS             Mon May 16 18:15:03 2011 (4DD1A1E7)
SRTSPX64.SYS            Thu Mar 15 14:09:21 2012 (4F623051)
SYMEFA64.SYS            Tue Nov 22 19:49:28 2011 (4ECC4318)
ccSetx64.sys            Fri Nov 04 18:05:25 2011 (4EB461A5)
Ironx64.SYS             Mon Nov 14 21:00:53 2011 (4EC1C7D5)
AtiPcie64.sys           Wed Mar 10 09:33:45 2010 (4B97ADC9)
SYMNETS.SYS             Sat Nov 12 16:11:53 2011 (4EBEE119)
SYMEVENT64x86.SYS       Tue Nov 22 13:30:48 2011 (4ECBEA58)
IDSvia64.sys            Fri Mar 09 16:57:02 2012 (4F5A7CAE)
eeCtrl64.sys            Fri Jan 20 18:39:48 2012 (4F19FB44)
EraserUtilRebootDrv.sys Fri Jan 20 18:39:49 2012 (4F19FB45)
BHDrvx64.sys            Tue Mar 13 16:02:37 2012 (4F5FA7DD)
atikmpag.sys            Thu Apr 05 21:10:44 2012 (4F7E4294)
AtihdW76.sys            Thu Feb 23 07:30:12 2012 (4F463154)
netr28x.sys             Fri Dec 18 07:32:14 2009 (4B2B764E)
Rt64win7.sys            Fri Feb 03 08:00:02 2012 (4F2BDA52)
usbfilter.sys           Tue Dec 22 03:26:22 2009 (4B3082AE)
atikmdag.sys            Thu Apr 05 21:48:25 2012 (4F7E4B69)
amdiox64.sys            Thu Feb 18 10:17:53 2010 (4B7D5A21)
RTKVHD64.sys            Tue Jun 08 05:08:08 2010 (4C0E0878)
Sftvollh.sys            Fri Sep 30 12:42:46 2011 (4E85F186)
AODDriver2.sys          Tue Mar 06 04:55:00 2012 (4F55DEF4)
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)
SYMDS64.SYS             Tue Dec 07 19:16:58 2010 (4CFECE7A)
SYMEFA64.SYS            Sun Mar 13 23:20:58 2011 (4D7D899A)
AtiHdmi.sys             Thu Apr 08 03:42:30 2010 (4BBD88E6)
SYMNETS.SYS             Tue Apr 19 18:33:31 2011 (4DAE0DBB)
SYMEVENT64x86.SYS       Thu Mar 24 19:02:36 2011 (4D8BCD8C)
Ironx64.SYS             Fri Nov 12 18:06:50 2010 (4CDDC88A)
SRTSPX64.SYS            Tue Mar 29 22:46:18 2011 (4D92997A)
atikmpag.sys            Mon Oct 24 00:40:06 2011 (4EA4EC26)
atikmdag.sys            Mon Oct 24 01:12:50 2011 (4EA4F3D2)
SRTSP64.SYS             Tue Mar 29 22:46:12 2011 (4D929974)
ENG64.SYS               Wed Apr 25 05:29:25 2012 (4F97C3F5)
EX64.SYS                Wed Apr 25 05:27:28 2012 (4F97C380)
[/font]

Code:

[font=lucida console]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052812-23166-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Mon May 28 23:23:14.356 2012 (UTC - 4:00)
System Uptime: 0 days 0:01:03.527
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+16b66 )
BUGCHECK_STR:  0x4E_7
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  CCC.exe
FAILURE_BUCKET_ID:  X64_0x4E_7_VRF_nt!_??_::FNODOBFM::_string_+16b66
Bugcheck code 0000004E
Arguments 00000000`00000007 00000000`00220c00 00000000`00000001 00000000`00000000
BiosVersion = 6.02
BiosReleaseDate = 07/21/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052812-23103-01.dmp]
*** WARNING: Unable to verify timestamp for Unknown_Module_fffffa80`078c0760
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_fffffa80`078c0760
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Mon May 28 23:11:58.662 2012 (UTC - 4:00)
System Uptime: 0 days 0:02:06.473
*** WARNING: Unable to verify timestamp for Unknown_Module_fffffa80`078c0760
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_fffffa80`078c0760
*** WARNING: Unable to verify timestamp for Unknown_Module_fffffa80`078c0760
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_fffffa80`078c0760
Probably caused by : Unknown_Image ( Unknown_Module_fffffa80_078c0760+2b8ab70 )
BUGCHECK_STR:  0x1a_5003
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
Bugcheck code 0000001A
Arguments 00000000`00005003 fffff700`01080000 00000000`0000270f 00002711`00004c1e
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052712-37923-01.dmp]
Built by: 7600.16988.amd64fre.win7_gdr.120401-1505
Debug session time: Sun May 27 10:47:57.601 2012 (UTC - 4:00)
System Uptime: 0 days 7:42:29.568
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+1dd )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  TrustedInstall
FAILURE_BUCKET_ID:  X64_0x3B_nt!CmpKcbCacheLookup+1dd
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`02d55aed fffff880`0b934770 00000000`00000000
BiosVersion = 6.02
BiosReleaseDate = 07/21/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052712-38610-01.dmp]
Built by: 7600.16988.amd64fre.win7_gdr.120401-1505
Debug session time: Sun May 27 02:41:33.091 2012 (UTC - 4:00)
System Uptime: 0 days 6:51:11.023
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : atikmpag.sys ( atikmpag+7bb8 )
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_atikmpag.sys
Bugcheck code 00000116
Arguments fffffa80`0b95c4e0 fffff880`0a407bb8 00000000`00000000 00000000`00000002
BiosVersion = 6.02
BiosReleaseDate = 07/21/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

Kailihn · May 30, 2012

Update

I am not using a disk cleaning program and I wouldn't have a clue how to overclock a computer even if I were so inclined, which I am not. I do notice that I have many more crashes than I have dump files but I am uploading the latest ones I have. Is there something I can do to fix that?

I updated the AMD chipset drivers and repeatedly removed the AODDriver4.1. After rebooting to complete the removal it would be gone but twice now it has shown up again (currently it is not showing the driver in the Non Plug and Play list). I removed the Catalyst Control Center and the wireless network device.

Driver Verifier is turned off but I am still crashing in game with a variety of error messages, including 2 or 3 crashes that did not give an error message. I also had my first crash outside of game when I tried to update the system's performance rating.

I'm going to start the hardware tests now.

usasma · May 31, 2012

Here's a link to an article that explains how a dump file is generated: BSOD Crash Dump Generation
Generally there's not much to do. Most frequently the dumps don't show up because it's either outside of Windows ability to figure it out, or it's corrupted in such a way that Windows decides not to keep the information.

You're still having trouble with the AOD (AMD OverDrive), so here's my other suggestions:

If AODDriver2.sys is still present and the software/device isn't present and the driver isn't needed - then please do this:

- create a System Restore point.
- create a System Repair disc and ensure that it works. To do this, go to Start...All Programs...Maintenance...Create a System Repair Disc
- uninstall all ATI video stuff using Control Panel...Programs...Uninstall a program (this may make the next 3 steps unnecessary - if so, just continue on).

- check in services.msc to see if there is an AOD service. If there is, set it to "Disabled" for the startup type.
- then disable any startups that name AODDriver2.sys using Autoruns (free from here: Autoruns for Windows )
- rename AODDriver2.sys to AODDriver2.BAD (it's probably in C:\Windows\System32\drivers)

- reboot and see if that fixes the problem(s). Check in C:\Windows\System32\drivers to be sure that it stays renamed.
- install fresh video drivers using the procedure here: ATI video cards - DRIVER ONLY installation procedure
DO NOT install the full Catalyst Control Center package!!!

Just FYI - when we see a bunch of different errors with a bunch of different causes - it says to us that this is a hardware problem. BUT - there are many different things that simulate hardware issues, so we have to rule them out before deciding that it's an problem with the physical piece of hardware.

These 2 links explain (in more detail) how we go about doing this:
- Info on how to troubleshoot BSOD's (DRAFT): http://www.carrona.org/userbsod.html
- How I do it: http://www.carrona.org/howidoit.html

The AODDriver2.sys is still present - so try my suggestions above for removing traces of it.

Try this to help ensure that your Norton/Symantec protection isn't at fault:

Anti-Virus Removal:
Please do the following:
- download a free antivirus for testing purposes: Free AntiVirus
- uninstall the Norton from your system (you can reinstall it, if so desired, when we're done troubleshooting)
- remove any remnants of Norton using this free tool: http://us.norton.com/support/kb/web_view.jsp?wv_type=public_web&docurl=20080710133834EN
- IMMEDIATELY install and update the free antivirus, then check to ensure that the Windows Firewall is turned on.
- check to see if this fixes the BSOD's
NOTE: NEVER run more than 1 anti-virus, firewall, Internet Security/Security Center application at the same time.

The wireless network device driver (netr28x.sys) present. Please ensure that the software for it is uninstalled. Then I would suggest going into Device Manager, right clicking on the wireless device and selecting "Uninstall"

If that doesn't do it, then:
- set a System Restore point (you'll still have the System Repair disk from the previous operations).
- rename the netr28x.sys to netr28x.BAD
- ensure that any entry in Autoruns for netr28x.sys is disabled
- then reboot and ensure that the driver remains renamed.

If these 3 problems are cleared up and the system still BSOD's - then we presume that it's a problem with a piece of physical hardware. Then the hardware diagnostics become essential.

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:

[FONT=lucida console]
amdsata.sys             Fri Feb 05 21:03:55 2010 (4B6CCE0B)
Ironx64.SYS             Mon Nov 14 21:00:53 2011 (4EC1C7D5)
SYMEVENT64x86.SYS       Tue Nov 22 13:30:48 2011 (4ECBEA58)
amdxata.sys             Fri Feb 05 21:03:57 2010 (4B6CCE0D)
SYMDS64.SYS             Mon May 16 18:15:03 2011 (4DD1A1E7)
SYMEFA64.SYS            Tue Nov 22 19:49:28 2011 (4ECC4318)
ccSetx64.sys            Fri Nov 04 18:05:25 2011 (4EB461A5)
AtiPcie64.sys           Wed Mar 10 09:33:45 2010 (4B97ADC9)
EraserUtilRebootDrv.sys Fri Jan 20 18:39:49 2012 (4F19FB45)
IDSvia64.sys            Fri Mar 09 16:57:02 2012 (4F5A7CAE)
eeCtrl64.sys            Fri Jan 20 18:39:48 2012 (4F19FB44)
AODDriver2.sys          Tue Mar 06 04:55:00 2012 (4F55DEF4)
SYMNETS.SYS             Sat Nov 12 16:11:53 2011 (4EBEE119)
SRTSPX64.SYS            Thu Mar 15 14:09:21 2012 (4F623051)
atikmpag.sys            Thu Apr 05 21:10:44 2012 (4F7E4294)
BHDrvx64.sys            Tue Mar 13 16:02:37 2012 (4F5FA7DD)
usbfilter.sys           Wed Dec 14 02:44:02 2011 (4EE853C2)
netr28x.sys             Fri Dec 18 07:32:14 2009 (4B2B764E)
Rt64win7.sys            Fri Feb 03 08:00:02 2012 (4F2BDA52)
amdiox64.sys            Thu Feb 18 10:17:53 2010 (4B7D5A21)
atikmdag.sys            Thu Apr 05 21:48:25 2012 (4F7E4B69)
rikvm_C6F09094.sys      Tue Jun 29 08:17:18 2010 (4C29E44E)
AtihdW76.sys            Thu Feb 23 07:30:12 2012 (4F463154)
RTKVHD64.sys            Tue Jun 08 05:08:08 2010 (4C0E0878)
Sftvollh.sys            Fri Sep 30 12:42:46 2011 (4E85F186)
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)
SRTSP64.SYS             Thu Mar 15 14:09:13 2012 (4F623049)
ENG64.SYS               Wed Apr 25 05:29:25 2012 (4F97C3F5)
EX64.SYS                Wed Apr 25 05:27:28 2012 (4F97C380)
[/FONT]

Code:

[FONT=lucida console]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\053012-17799-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Wed May 30 22:03:08.109 2012 (UTC - 4:00)
System Uptime: 0 days 0:28:36.919
Probably caused by : win32k.sys ( win32k!SetWakeBit+f8 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID:  X64_0xA_win32k!SetWakeBit+f8
Bugcheck code 0000000A
Arguments 00000000`1586b572 00000000`00000002 00000000`00000000 fffff800`02c94889
BiosVersion = 6.02
BiosReleaseDate = 07/21/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\053012-17706-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Wed May 30 21:32:36.959 2012 (UTC - 4:00)
System Uptime: 0 days 0:07:50.130
Probably caused by : ntkrnlmp.exe ( nt!ExAcquireResourceSharedLite+4e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!ExAcquireResourceSharedLite+4e
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`02ce70fe fffff880`08bd8e80 00000000`00000000
BiosVersion = 6.02
BiosReleaseDate = 07/21/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\053012-16754-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Wed May 30 20:58:52.233 2012 (UTC - 4:00)
System Uptime: 0 days 0:07:02.404
Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+150 )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!MiReplenishPageSlist+150
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`02aa68e0 00000000`00000000 ffffffff`ffffffff
BiosVersion = 6.02
BiosReleaseDate = 07/21/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\053012-20404-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Wed May 30 20:50:54.440 2012 (UTC - 4:00)
System Uptime: 0 days 0:05:20.250
Probably caused by : ntkrnlmp.exe ( nt!PpmPerfRecordUtility+163 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  eqgame.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!PpmPerfRecordUtility+163
Bugcheck code 0000000A
Arguments 00000000`00000201 00000000`00000002 00000000`00000000 fffff800`02bba653
BiosVersion = 6.02
BiosReleaseDate = 07/21/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\053012-19390-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Wed May 30 20:42:38.880 2012 (UTC - 4:00)
System Uptime: 0 days 0:49:37.035
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+5235 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  ccSvcHst.exe
FAILURE_BUCKET_ID:  X64_0x3B_nt!_??_::FNODOBFM::_string_+5235
Bugcheck code 0000003B
Arguments 00000000`c0000094 fffff800`02ae52a9 fffff880`0b5c7b60 00000000`00000000
BiosVersion = 6.02
BiosReleaseDate = 07/21/2010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/FONT]

Kailihn · May 31, 2012

I uninstalled Norton's and opted for MS Security Essentials.
I chased my tail for a while until I figured out that my AOD file was in C:\Program Files\ATI Technologies\ATI.ACE\Fuel\amd64 and after running the Autoruns program and disabling 2 things I renamed it as a bad file and it stayed that way after restarting.

I did not have as much luck with the wireless network driver. Despite renaming the file and uninstalling the device, as soon as I restarted my computer it would just put it back again. I did finally find a driver for it from 2012 and I am crossing my fingers that will solve that problem.

I had one crash prior to completing the 3 tasks but due to the late hour will not be able to test it out in game. I checked out Furmark and did not experience any crashes - my computer maxed out at 87 degrees Celsius. I was unable to set it to log the temperatures as directed as that would cause the program to freeze.

I will set up Memtest86 to run overnight though and start working on more of the hardware tests. Tomorrow evening I'll put the 3 changes I just did to the test when I play the game.

usasma · Jun 1, 2012

More and more we find that driver files aren't being stored in their usual location (C:\Windows\System32\drivers) and that makes it more difficult. Thanks for letting us know the new path, I've included it in my canned speech.

As long as you got Furmark to run, and you observed it's max temp - all should be OK.

Looking forward to the rest of the results...

Kailihn · Jun 3, 2012

Hardware tests

After the last software fixes my system was pretty stable. In two days I only had 1 crash and was able to play my game for 3 hours straight at one point. Since I did have the one crash I couldn't post back that my issues were resolved and I started in on the hardware tests on your site.

I ran the memory tests with no errors two nights in a row. One night it was still running when I woke up, the next night I woke up to my regular desktop with nothing running...I wasn't sure what to make of that.

Furmark and Prime95 both ran with no errors though I did notice that cpu #5 did not complete tests as quickly as the other 5 processors.
I tried to run the hard drive fitness test and it wasn't seeing my HD so I skipped to the cpu stress tests. And that's when it all began to unravel.

I tried Hot CPU Lite (the free version) with the following results:

Hot CPU Tester Pro(Lite Edition) 4.4.1
Copyright © 1999-2003 7Byte Computers
Sunday, June 03, 2012 - 13:15:17
Diagnostic Report
---------------------------------------------
Test Started at: 08:54:52
Test Duration: 04:19:59
Physical Processors Available: 6
Logical Processors Available: 6
Multi-Processors System(SMP): Available
Hyper-Threading Technology: Not Available
CPU Name String: AMD Phenom(tm) II X6 1045T Processor
Speed: 2699MHz
Logical Processors Tested: CPU 0, CPU 1, CPU 2, CPU 3, CPU 4, CPU 5
Average CPU(s) Performance: 100.0%

Modules Results:
Complex Matrix: Finished without error
Calculating Pi: Finished without error
Sorting Algorithms: Finished without error
Prime Test: Finished without error
Fast Fourier Transforms:
Chipset:
L1 Cache:
L2 Cache:
Memory: Finished without error
HD: Finished without error
MMX: Finished without error
SSE:
SSE2/SSE3:
3DNow!:

LinX also ran with no errors but then I tried OCCT using the settings suggested to test overall CPU health. My system crashed prior to completion 2 or 3 times. It ran fine until about 80% of the way through the test.

I Googled CPU stress tests and found another one not listed on your page and maybe that was my big mistake. I found a lot of posts suggesting that S&M FPU was a good test to try and when it was loading I started crashing. Repeatedly.

I ran the BSoD app again so I could post the logs here before I caused more harm to my machine and crashed several times just trying to zip up the two files. This is definitely new and not improved as previously my system only crashed while playing Everquest.

usasma · Jun 3, 2012

Go to the Seagate website and download the Seatools test for Windows and try running that.

Gotta run right now, will post back later on (in a couple of hours)

Kailihn · Jun 3, 2012

Ooct

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 · Jun 3, 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 Win7 systems.

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:

[font=lucida console]
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)
[/font]

Code:

[font=lucida console]
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
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

Kailihn · Jun 3, 2012

Hardware

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 · Jun 4, 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 · Jun 4, 2012

Honeymoon period

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 :sarc:

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 · Jun 4, 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 · Jun 8, 2012

Update

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 · Jun 8, 2012

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

BSoD playing Everquest

New member

My Computer

Mr. Cranky Pants

My Computer

New member

My Computer

Mr. Cranky Pants

My Computer

New member

My Computer

Mr. Cranky Pants

My Computer

New member

My Computer

Mr. Cranky Pants

My Computer

New member

My Computer

Mr. Cranky Pants

My Computer

New member

My Computer

Mr. Cranky Pants

My Computer

New member

My Computer

Mr. Cranky Pants

My Computer

New member

My Computer

Mr. Cranky Pants

My Computer

New member

My Computer

Mr. Cranky Pants

My Computer