Random BSODs - Errors 0x00000101 and 0x0000007A

Ashkrall · 30 Jan 2012

My computer has crashed twice today, giving me error code 0x00000101. The first time was while watching Netflix, and the second time was while playing Minecraft. Additionally, I got an error code 0x0000007A (ataport.sys) while surfing the internet.

Perfmon and Dump files attached below. Thanks for the help.

usasma · 30 Jan 2012

Only 60 updates since SP1, most systems have 70 or more. Please visit Windows Update and get all available updates.

Your Linksys AE1000 is a USB wireless device. Win7 doesn't like these devices and with older drivers they are a known cause of BSOD's. Here's my rant on them:

I do not recommend using wireless USB devices. Especially in Win7 systems.
These wireless USB devices have many issues with Win7 - and 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 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.

We've been seeing BSOD issues with SSD's. Here's the info that I've compiled:

There's not a whole bunch available to test SSD's. The "easiest" test is to remove the SSD, install a platter-based hard drive, install Windows and test for stability that way.

Here's some suggestions:
- Update the SSD's firmware to the latest available version (VERY IMPORTANT!!!)
- Slow the memory (RAM) down to the next slower speed (I've only seen one person who claimed that this worked for them).
- Use any manufacturer's utilities that you may have. If you don't have any, then try this free one (I haven't used it myself): Crystal Dew World
- Update chipset and storage controller drivers to the latest available from the manufacturer of the device (not the manufacturer of the motherboard). Be sure to update ALL controllers on the motherboard!
....NOTE: Recently (Nov 2011) we had BSOD issues with the Marvell 91xx controller and an SSD. You may have to switch controllers also.-
Replace the SSD with a platter based hard drive and see if that stops the BSOD's. If it does, then it's likely that there's a problem with the SSD OR an incompatibility with your system.
It's my opinion that SSD's aren't reliable enough (with current hardware) to be used on a system that needs to work reliably. Until I see reliability I will not recommend, nor will I use, SSD's for critical applications.
06 Dec 2011 - This post tends to confirm issues with certain SSD chipsets and certain controllers - [SOLVED] cant find the cause of BSOD F4 - Tech Support Forum

FNet Turbo HDD USB Driver (FNETURPX.SYS)_dates from 2008. Please install an updated version or uninstall this program from your system.

This Creative audio driver (ctac32k.sys) dates from 2008. Please install an updated version or uninstall this program from your system.

Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs:
3RD PARTY DRIVERS PRESENT IN THE DUMP FILES
- Create a System Restore Point prior to doing any of this. DO NOT mess with the drivers themselves - leave the Windows\System32\drivers directory alone unless we specifically direct you to it!
- Please either update the older drivers from the device manufacturer's website - or uninstall them from your system. Reference links are included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Please feel free to post back about any drivers that you are having difficulty locating.
- Windows Update exceptions may be noted below for Windows drivers.

Code:


mvs91xx.sys       Fri Apr 08 06:50:11 2011 (4D9EE863)
mvxxmm.sys        Fri Apr 08 06:49:53 2011 (4D9EE851)
amdxata.sys       Fri Mar 19 12:18:18 2010 (4BA3A3CA)
WRkrn.sys         Fri Jan 13 16:28:48 2012 (4F10A210)
NDIS.SYS          Sat Nov 20 04:23:30 2010 (4CE79392)
FNETURPX.SYS      Fri Oct 03 22:27:02 2008 (48E6D476)
AsrAppCharger.sys Fri Jun 11 02:37:12 2010 (4C11D998)
nvstusb.sys       Sat Oct 15 01:54:19 2011 (4E99200B)
ae1000w7.sys      Fri Jan 15 03:15:48 2010 (4B502434)
EtronHub3.sys     Fri Jan 28 16:46:45 2011 (4D433945)
k57nd60a.sys      Mon Feb 14 23:19:05 2011 (4D59FEB9)
EtronXHCI.sys     Fri Jan 28 16:46:43 2011 (4D433943)
ctprxy2k.sys      Wed May 05 08:59:51 2010 (4BE16BC7)
igdkmd64.sys      Fri Oct 21 13:29:55 2011 (4EA1AC13)
HECIx64.sys       Tue Oct 19 19:33:43 2010 (4CBE2AD7)
ha20x2k.sys       Wed May 05 08:59:10 2010 (4BE16B9E)
emupia2k.sys      Wed May 05 08:57:27 2010 (4BE16B37)
CTHWIUT.SYS       Wed May 05 09:01:32 2010 (4BE16C2C)
CT20XUT.SYS       Wed May 05 09:01:28 2010 (4BE16C28)
FNETTBOH_305.SYS  Wed Nov 03 02:24:26 2010 (4CD1001A)
ctsfm2k.sys       Wed May 05 08:57:33 2010 (4BE16B3D)
ctac32k.sys       Wed Jul 02 04:38:22 2008 (486B3E7E)
CTEXFIFX.SYS      Wed May 05 09:01:21 2010 (4BE16C21)
nvhda64v.sys      Thu Jul 07 12:21:14 2011 (4E15DCFA)
ctoss2k.sys       Wed May 05 08:57:46 2010 (4BE16B4A)
nvlddmkm.sys      Sat Oct 15 02:07:55 2011 (4E99233B)
ctaud2k.sys       Wed May 05 08:59:48 2010 (4BE16BC4)

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\013012-12604-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Jan 30 09:15:34.776 2012 (UTC - 5:00)
System Uptime: 0 days 22:29:49.604
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000019 00000000`00000000 fffff880`009b3180 00000000`00000004
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\012912-12074-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Jan 29 10:43:36.132 2012 (UTC - 5:00)
System Uptime: 0 days 17:59:30.960
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000019 00000000`00000000 fffff880`03165180 00000000`00000002
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``