Windows 7 Windows 7 64 bit BSOD: Possibly after Driver Installation from Windows Update!


Honorable Member
Jun 12, 2013
On 05/06 after installing (thru Windows Update) the AMD SATA Contoller , the AMD - Other hardware - Storage Controller - AMD SATA Contoller & IE 10 for Windows 7 for x64 based systems, the problems BSOD began. As Critical Evens (2) I got : Windows Stopped working & Shutdown Unexpectedly. The problem continued on the 06/06 with the following listings under Critical Evens: Windows Stopped Working & Shutdown Unexpectedly and on the 11th (11/06) I had another BSOD with Windows Shutdown Unexpectedly listed as critical events. I'm uploading the Errors, the Reliability Report .XML as well the mini dump files to my sky PUBLIC FOLDER drive:!105
I do have also uploaded a file W7F_12-06-2013, as per forum instructions. Someone pointed at the 0xF4 and 0x7A errors, and said that the BSOD are hardware related (hardware fault). If I right both the errors are referring to: a hardware device, its driver, or related software might have caused this error". I could be right, but I also could be wrong; the errors appeared after the driver installation. Now something worth to mention is that the system was idling both times! Didn't play games or run apps! And if I m right the incidents (BSOD) happened when the PC was unattended (probably/possibly it entered the sleep mode). To start from checking my hardware it would be a long task, as I have 2 HDD and an SSD (where Windows 7 resides). I would appreciate your suggestions and input. v/r


  • W7F_12-06-2013.rar
    896.1 KB · Views: 449
Nice post! Lot's of good info included - just what we need to get started.

BSOD's are caused by 3 things - in this order of likelyhood:
1) 3rd party drivers (90% or more)
2) Hardware (less than 10%)
3) Windows drivers (less than 1%)

BSOD's can be due to a simple issue with 1 driver/piece of hardware - or they can be related to several different things on your system and not be triggered until a specific set of circumstances is encountered. For example a fault in the system lies undiscovered until a Windows Update activates the software/driver function that addresses the area of the fault - at that point a BSOD may occur - even though the system has been problem free.

STOP 0x7F and STOP 0x7A errors can be hardware, so I suggest that you try these free diagnostics as you have time: Hardware Diagnostics

There are enough signs here that I have to wonder about this installation. Should this be a pirated copy of Windows, please be aware that we may not be able to fix it (as the hacks that were done to activate it will cause the OS to behave differently than we expect it to). If that's the case, our efforts to help may just waste your time. Secondly, the forum rules prohibit assisting with pirated software - so the topic would be closed if that is the case.

I do not recommend using wireless USB network devices. Especially in Win7/Win8 systems.
These wireless USB devices have many issues with Win7(and I suspect with Win8) - using Vista drivers with them is almost sure to cause a BSOD.
Should you want to keep using these devices, be sure to have Win7/Win8 drivers - DO NOT use Vista drivers!!!
An installable wireless PCI/PCIe card that's plugged into your motherboard is much more robust, reliable, and powerful.

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 systems.
Please un-install all AMD/ATI video stuff from Control Panel...Programs...Un-install a program
Then, download (but DO NOT 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 - Sysnative Forums

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 "Un-install". 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.

Of the 3 memory dumps, one is corrupted and the other 2 refer to issues with a device (IOERR and
I suggest that you run the hard drive test from the above link for diagnostics ( Hardware Diagnostics )

Note in the drivers listed below that the USB 3.0 drivers are known to cause BSOD's - so they MUST be udpated.

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

AsIO.sys Mon Apr 6 03:21:08 2009 (49D9AD64)
Asus PCProbe Utility

AtiPcie.sys Tue May 5 11:00:22 2009 (4A005486)
ATI PCIE Driver for ATI PCIE chipset or [br] ATI PCI Express (3GIO) Filter[br]Found in my ATI video drivers (I have an Intel chipset)

nusb3hub.sys Thu Apr 22 21:34:35 2010 (4BD0F92B)
NEC Electronics USB 3.0 Host Controller Driver (previous BSOD issues with 2010 and earlier versions)

nusb3xhc.sys Thu Apr 22 21:34:36 2010 (4BD0F92C)
NEC Electronics USB 3.0 Host Controller Driver (previous BSOD issues with 2010 and earlier versions)

The following is for informational purposes only.
[FONT=lucida console]**************************Tue Jun 11 06:44:45.734 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\061113-13088-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 2:00:00.826[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+50080 )[/B]
BugCheck [B]7A, {20, ffffffffc000009d, fffffa800d3a0078, 0}[/B]
Arg1: 0000000000000020, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000009d, error status (normally i/o status code)
Arg3: fffffa800d3a0078, current process (virtual address for lock type 3, or PTE)
Arg4: 0000000000000000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
DISK_HARDWARE_ERROR: There was error with disk hardware
BUGCHECK_STR:  0x7a_c000009d
FAILURE_BUCKET_ID: [B]X64_0x7a_c000009d_nt!_??_::FNODOBFM::_string_+50080[/B]
  BIOS Version                  2001   
  BIOS Release Date             03/08/2011
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
**************************Wed Jun  5 17:21:55.816 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\060613-16848-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Built by: [B]7601[/B].18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime:[B]0 days 1:31:19.909[/B]
Probably caused by :[B]csrss.exe[/B]
BugCheck [B]F4, {3, fffffa800e321b30, fffffa800e321e10, fffff80002fe2350}[/B]
Arg1: 0000000000000003, Process
Arg2: fffffa800e321b30, Terminating object
Arg3: fffffa800e321e10, Process image file name
Arg4: fffff80002fe2350, Explanatory message (ascii)
PROCESS_NAME:  csrss.exe
  BIOS Version                  2001   
  BIOS Release Date             03/08/2011
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
**************************Sun Jan  1 00:00:00.000 1969 (UTC - 0:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\060513-12901-01.dmp]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
[FONT=lucida console]**************************Tue Jun 11 06:44:45.734 2013 (UTC - 4:00)**************************
[COLOR=RED][B]AsIO.sys                    Mon Apr  6 03:21:08 2009 (49D9AD64)[/B][/COLOR]
[COLOR=RED][B]AtiPcie.sys                 Tue May  5 11:00:22 2009 (4A005486)[/B][/COLOR]
ASACPI.sys                  Wed May 13 21:25:17 2009 (4A0B72FD)
SCDEmu.SYS                  Mon Jul 27 13:53:10 2009 (4A6DE986)
amdsata.sys                 Wed Oct  7 16:13:09 2009 (4ACCF655)
amdxata.sys                 Wed Oct  7 16:13:10 2009 (4ACCF656)
cmudaxp.sys                 Mon Oct 19 05:10:53 2009 (4ADC2D1D)
usbfilter.sys               Tue Dec 22 03:26:22 2009 (4B3082AE)
[COLOR=RED][B]nusb3hub.sys                Thu Apr 22 21:34:35 2010 (4BD0F92B)[/B][/COLOR]
[COLOR=RED][B]nusb3xhc.sys                Thu Apr 22 21:34:36 2010 (4BD0F92C)[/B][/COLOR]
speedfan.sys                Fri Mar 18 12:08:46 2011 (4D83838E)
athurx.sys                  Wed Apr 20 06:07:45 2011 (4DAEB071)
Rt64win7.sys                Fri Jun 10 02:33:15 2011 (4DF1BAAB)
SRTSPX64.SYS                Tue Nov 15 17:30:55 2011 (4EC2E81F)
[COLOR=RED][B]AODDriver2.sys              Thu Apr  5 05:23:37 2012 (4F7D6499)[/B][/COLOR]
GEARAspiWDM.sys             Thu May  3 15:56:17 2012 (4FA2E2E1)
Teefer.sys                  Tue Jul 17 08:58:52 2012 (5005618C)
SYMNETS.SYS                 Fri Jul 20 22:07:07 2012 (500A0ECB)
SYMDS64.SYS                 Mon Jul 23 18:58:38 2012 (500DD71E)
Ironx64.SYS                 Mon Jul 23 20:34:50 2012 (500DEDAA)
EraserUtilRebootDrv.sys     Tue Jul 31 19:36:50 2012 (50186C12)
eeCtrl64.sys                Tue Jul 31 19:36:51 2012 (50186C13)
ccSetx64.sys                Thu Aug 16 17:18:11 2012 (502D6393)
SYMEVENT64x86.SYS           Wed Aug 22 01:33:18 2012 (50346F1E)
IDSvia64.sys                Tue Aug 28 22:48:40 2012 (503D8308)
SYMEFA64.SYS                Wed Oct  3 15:00:06 2012 (506C8B36)
amd_sata.sys                Fri Oct 12 05:48:36 2012 (5077E774)
hiber_amd_sata.sys          Fri Oct 12 05:48:36 2012 (5077E774)
amd_xata.sys                Fri Oct 12 05:48:39 2012 (5077E777)
SRTSP64.SYS                 Thu Nov  1 16:16:15 2012 (5092D88F)
SysPlant.sys                Sat Nov  3 09:53:53 2012 (509521F1)
AtihdW76.sys                Tue Nov  6 16:41:51 2012 (5099841F)
atikmpag.sys                Wed Dec 19 14:32:55 2012 (50D21667)
atikmdag.sys                Wed Dec 19 15:38:55 2012 (50D225DF)
BHDrvx64.sys                Wed Apr 10 01:39:03 2013 (5164FAF7)
EX64.SYS                    Fri Apr 26 02:08:58 2013 (517A19FA)
ENG64.SYS                   Fri Apr 26 02:10:48 2013 (517A1A68)
Teefer.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
hiber_amd_sata.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
Last edited:
Hi Usasma, thanx 4 your quick reply. I'm currently at work and I can't do a lot with my 'home' windows pc right now. I'll follow your instructions methodically, step by step and I'll let you know. For the paragraph with the underscored section, I already took pics of it & I will upload them; my Windows 7, 64bit Professional (US Release/OEM) is 100% legit from N@3E##. I prefer not to diclose the name in pubic, for ad reasons. I say US Rel. because the European Rel. gives u the option to install the browser of choice! The Office 2007 Professional Enterprise is also legit (from the Home use program which my employer uses). The AV/FW is Symantec Endpoint Protection v. 12.1.2015.2015, which some blame that is is the cause of BSOD, is also legit from the same program listed above, this one I get it for nada; for the previous one I believe I paid some $15.
The Windows 7 product id # I removed it for the attachments I uploaded!
From your website & OCZs website, I also noticed that there is no utility to test my SSD (That's Windows 7 resides). The rest of the apps are instaled in my 1TB Seagate & I have also moved the ones that they wanted to reside on C, to the 1TB with the use of 'links'. I'll follow your instuctions and I will let u know, thanx again.

Unfortunately, there is no test for SSD's (AFAIK).
The only "test" is to replace it with a known good platter-based hard drive for test purposes.

You can test the Seagate and Western Digital drives with the Seagate SeaTools program.
Make sure that the firmware for the SSD is fully updated to the latest version
Also make sure that the storage controller drivers are also updated to the latest version. Any controller drivers earlier than mid-2012 are suspect.

If all that doesn't fix it, then we'll have to see about running a platter based hard drive instead of the SSD - to see if it's the SSD that's causing the problems.
This pics are uploaded so that u won't doubt the legitimacy of my os and software:razz:.
Didn't have time to follow your remedies thru the weekend, I have had another BSOD, today in the morning; unfortunately I cannot upload the file. I'll be starting with the 'remedies' u wrote from tonite and I will let u know. I don't know if it is important or not, the BSOD happens when the pc is unattended, left the pc for more than 10min (I believe I wrote u that before). The drivers in red that I need 2 remove, is it right to keep them (make a backup)?
Last edited:
DO NOT REMOVE DRIVERS - un-install the program that installed them.
Removing drivers can cause the system to become unbootable.

Don't key on the RED color, those are just for reference.
And, in the case of the ASACPI.sys driver - that one is a mistake on my part - DO NOT REMOVE it or it's program!

1) follow the procedure to remove AMD Overdrive that I posted - that'll take care of the AODDriver2.sys driver and most likely the AtiPcie.sys driver

2) Update your USB 3.0 drivers - that'll take care of the nusb3hub.sys and the nusb3xhc.sys drivers

3) Update the Asus programs associated with the AsIO.sys driver (Asus PCProbe/AISuite). If you can't find an update, un-install the program.
Last edited:
Hi again (john) Usasma,

I haven't done everything you said, but the 1st thing I did was to remove the USB3 driver and reinstall a newer (?) one from the ASUS website. See, I'm getting old and I keep forgetting, I ran partly the Mem test recommended, from my USB; I say partly because over here where I'm stationed it is hot (mainboard/cpu 123 degrees) with an ambient temperature of 86 degrees. I can't complain, I have seen 100 degrees when I lived in El Paso; but then again ac was lots cheaper to run.
Mem test didn't report any errors, my question is if the memory test crashes the system would I get an error log in the stick? Because if I would leave it to run the whole night, the only thing to tell me if the test is successful would be to see the computer running (the test) first thing in the morning; if the pc has crashed, then again I have to troubleshoot by removing/swapping the sticks etc.
The other thing I did as u recommend it, I checked the secondary drive with Sea tools and as I can't test the OCZ SSD, I risked it and I updated the firmware, to the latest. Since then I haven't had any blue screens! Hope this could be the solution to my problem; if not I'll go ahead and follow steps 1 & 2 of your post above. Thanks again

Michael (somewhere in the Med)
"The longest month of my life was the night I spent in El Paso" - attributed to Mark Twain/WC Fields/Kramer on the Seinfeld TV Show. I was stationed at Ft. Bliss in El Paso from 2000 through 2003 (hence my nick - U.S.A.S.M.A.).

If MemTest86+ crashes the system, then there won't be a report. It runs off a Linux kernel and runs in memory - so there's no place for it to store a report AFAIK. It's relatively rare for a system to crash when running MemTest86+ - and most of the errors will show up in the first pass (although the trickier problems need the 3+ passes and Prime95 in order to isolate other memory tests.

Good luck!
Top Bottom