BSOD Problem

RiesP · Jan 2, 2013

Ever since I put together my PC I've been having randoom reboot/BSOD issues. At first I though it was video card related. Especially since a driver update solved my problems for a while. The last few days however it has BSODed several times again. I'm not sure what it is related to. My memory as well as my SSD seem to be fine. Any help would be appreciated.

Kind regards

usasma · Jan 3, 2013

We've seen a number of BSOD issues with SSD's. Here's the information that I've compiled so far:

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!!!)
- Update the motherboard controllers drivers to the latest available version from the controller manufacturer (NOT the mobo manufacturer unless you can't find any on the controller manufacturer's website)
- 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
29 May 2012 - The frequency of BSOD's with SSD's seems to have been decreasing over the last several months. It may be approaching time to re-evaluate my stand on their suitability for use in production systems.
10 Nov 2012 - I'm seeing an upswing in SSD errors - but most appear due to older storage controller drivers. I strongly suggest NOT using storage controller drivers that don't date from 2012 (if none are available, don't connect an SSD to that controller)

Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Win7 systems (mostly due to the sptd.sys driver, although I have seen dtsoftbus01.sys blamed on several occasions). I strongly suspect that this hold true for Win8 systems also.

Please un-install the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): ~~[DEL] DuplexSecure - FAQ [/DEL]~~ Link broken as of 21 Jul 2012
New link (15 Aug 2012): DuplexSecure - Downloads (pick the appropriate version for your system and select "Un-install" when you run it).
Alternate link: Disc-Tools.com
Manual procedure here: Registry and SPTD problems | DAEMON Pro Help

I figure that the 14 Dec and earlier memory dumps are a separate problem - and that you fixed them by updating your video drivers. Is that correct?

Also, did you deliberately crash your computer on Dec 9? You have what looks to be a user generated memory dump (0xDEADDEAD) from that date.

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

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.

Please also remove the Western Digital software. It's drivers date from 2008 and are known to cause BSOD's.

Ensure that your Logitech WingMan drivers are the latest, Win8 compatible version.
Ensure that your wired networking device drivers are the latest, Win8 compatible version also.

Analysis:
The following is for informational purposes only.

Code:

[font=lucida console]**************************Wed Jan  2 13:51:12.090 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\010213-7644-01.dmp]
Windows 8 Kernel Version 9200 MP (6 procs) Free x64
Built by: [B]9200[/B].16461.amd64fre.win8_gdr.121119-1606
System Uptime:[B]0 days 7:49:01.769[/B]
*** ERROR: Module load completed but symbols could not be loaded for HDAudBus.sys
Probably caused by :[B]HDAudBus.sys ( HDAudBus+1678 )[/B]
BugCheck [B]133, {0, 283, 282, 0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000133]DPC_WATCHDOG_VIOLATION (133)[/url]
Arguments: 
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
    component can usually be identified with a stack trace.
Arg2: 0000000000000283, The DPC time count (in ticks).
Arg3: 0000000000000282, The DPC time allotment (in ticks).
Arg4: 0000000000000000
BUGCHECK_STR:  0x133
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME: [B]MsMpEng.exe[/B]
FAILURE_BUCKET_ID: [B]0x133_DPC_HDAudBus+1678[/B]
  BIOS Version                  P1.60
  BIOS Release Date             10/12/2012
  Manufacturer                  To Be Filled By O.E.M.
  Product Name                  To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Jan  1 08:25:22.889 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\010113-7706-01.dmp]
Windows 8 Kernel Version 9200 MP (6 procs) Free x64
Built by: [B]9200[/B].16461.amd64fre.win8_gdr.121119-1606
System Uptime:[B]11 days 3:28:58.168[/B]
Probably caused by :[B]win32k.sys ( win32k!memcpy+240 )[/B]
BugCheck [B]133, {1, 784, 0, 0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000133]DPC_WATCHDOG_VIOLATION (133)[/url]
Arguments: 
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
    DISPATCH_LEVEL or above. The offending component can usually be
    identified with a stack trace.
Arg2: 0000000000000784, The watchdog period.
Arg3: 0000000000000000
Arg4: 0000000000000000
BUGCHECK_STR:  0x133
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME: [B]chrome.exe[/B]
FAILURE_BUCKET_ID: [B]0x133_ISR_win32k!memcpy[/B]
  BIOS Version                  P1.60
  BIOS Release Date             10/12/2012
  Manufacturer                  To Be Filled By O.E.M.
  Product Name                  To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Dec 14 12:46:00.840 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\121412-5584-01.dmp]
Windows 8 Kernel Version 9200 MP (6 procs) Free x64
Built by: [B]9200[/B].16461.amd64fre.win8_gdr.121119-1606
System Uptime:[B]0 days 3:08:48.005[/B]
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by :[B]atikmdag.sys ( atikmdag+6f4dfb )[/B]
BugCheck [B]1000007E, {ffffffffc0000005, fffff88009b11dfb, fffff880009ba368, fffff880009b9ba0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x1000007E]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)[/url]
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88009b11dfb, The address that the exception occurred at
Arg3: fffff880009ba368, Exception Record Address
Arg4: fffff880009b9ba0, Context Record Address
PROCESS_NAME: [B]System[/B]
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  NULL_DEREFERENCE
FAILURE_BUCKET_ID: [B]AV_atikmdag+6f4dfb[/B]
  BIOS Version                  P1.60
  BIOS Release Date             10/12/2012
  Manufacturer                  To Be Filled By O.E.M.
  Product Name                  To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Dec  9 12:35:12.956 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\120912-5210-01.dmp]
Windows 8 Kernel Version 9200 MP (6 procs) Free x64
Built by: [B]9200[/B].16442.amd64fre.win8_gdr.121023-1503
System Uptime:[B]0 days 0:11:17.639[/B]
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by :[B]atikmdag.sys ( atikmdag+195151 )[/B]
BugCheck [B]1000007E, {ffffffffc0000005, fffff88006598151, fffff880081b5838, fffff880081b5070}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x1000007E]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)[/url]
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88006598151, The address that the exception occurred at
Arg3: fffff880081b5838, Exception Record Address
Arg4: fffff880081b5070, Context Record Address
PROCESS_NAME: [B]System[/B]
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
FAILURE_BUCKET_ID: [B]AV_atikmdag+195151[/B]
  BIOS Version                  P1.60
  BIOS Release Date             10/12/2012
  Manufacturer                  To Be Filled By O.E.M.
  Product Name                  To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Dec  9 12:11:26.693 2012 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\120912-5148-01.dmp]
Windows 8 Kernel Version 9200 MP (6 procs) Free x64
Built by: [B]9200[/B].16442.amd64fre.win8_gdr.121023-1503
System Uptime:[B]0 days 0:29:16.376[/B]
*** WARNING: Unable to verify timestamp for rspCrash64.sys
*** ERROR: Module load completed but symbols could not be loaded for rspCrash64.sys
Probably caused by :[B]rspCrash64.sys ( rspCrash64+108b )[/B]
BugCheck [B]DEADDEAD, {0, 0, 1896abdb, 3c2a58ed}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0xDEADDEAD]MANUALLY_INITIATED_CRASH1 (deaddead)[/url]
Arguments: 
Arg1: 0000000000000000
Arg2: 0000000000000000
Arg3: 000000001896abdb
Arg4: 000000003c2a58ed
BUGCHECK_STR:  0xDEADDEAD
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME: [B]WhoCrashedEx.e[/B]
FAILURE_BUCKET_ID: [B]0xDEADDEAD_rspCrash64+108b[/B]
  BIOS Version                  P1.60
  BIOS Release Date             10/12/2012
  Manufacturer                  To Be Filled By O.E.M.
  Product Name                  To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

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.

Code:

[font=lucida console]**************************Wed Jan  2 13:51:12.090 2013 (UTC - 5:00)**************************
[COLOR=RED][B]wdcsam64.sys                Wed Apr 16 04:39:08 2008 (4805BB2C)[/B][/COLOR]
[COLOR=RED][B]WmVirHid.sys                Tue Apr 27 16:08:53 2010 (4BD74455)[/B][/COLOR]
[COLOR=RED][B]WmXlCore.sys                Tue Apr 27 16:09:26 2010 (4BD74476)[/B][/COLOR]
[COLOR=RED][B]WmHidLo.sys                 Tue Apr 27 16:09:36 2010 (4BD74480)[/B][/COLOR]
[COLOR=RED][B]WmFilter.sys                Tue Apr 27 16:10:19 2010 (4BD744AB)[/B][/COLOR]
[COLOR=RED][B]WmBEnum.sys                 Tue Apr 27 16:10:19 2010 (4BD744AB)[/B][/COLOR]
[COLOR=RED][B]Rt630x64.sys                Wed Oct 19 08:12:55 2011 (4E9EBEC7)[/B][/COLOR]
[COLOR=RED][B]dtsoftbus01.sys             Fri Jan 13 08:45:46 2012 (4F10358A)[/B][/COLOR]
[COLOR=RED][B]AODDriver2.sys              Thu Apr  5 05:23:37 2012 (4F7D6499)[/B][/COLOR]
usbfilter.sys               Tue Jun 19 07:07:40 2012 (4FE05D7C)
amd_sata.sys                Mon Jul 23 14:34:48 2012 (500D9948)
amd_xata.sys                Mon Jul 23 14:34:52 2012 (500D994C)
AtihdW86.sys                Tue Aug 21 22:26:37 2012 (5034435D)
atikmpag.sys                Sun Dec  2 02:13:21 2012 (50BAFF91)
atikmdag.sys                Sun Dec  2 03:21:53 2012 (50BB0FA1)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Jan  1 08:25:22.889 2013 (UTC - 5:00)**************************
L6TPortA64.sys              Mon Mar 26 15:39:35 2012 (4F70C5F7)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Dec  9 12:35:12.956 2012 (UTC - 5:00)**************************
atikmpag.sys                Thu Sep 27 21:12:52 2012 (5064F994)
atikmdag.sys                Thu Sep 27 22:14:57 2012 (50650821)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Dec  9 12:11:26.693 2012 (UTC - 5:00)**************************
rspCrash64.sys              Mon Nov  5 02:18:46 2012 (50976856)
[/font]

RiesP · Jan 3, 2013

Thank you for your helpful respons. Indeed, the previous crashes were, I believe, fixed with new video drivers. I uninstalled the WD software as well as Daemon Tools in an attempt to fix the issue. Sadly my pc froze again a few minutes ago. This time however it did not show the BSOD nor did it create a dump file. I'm not sure what's wrong but I will first look into the other steps you listed in your post.

usasma · Jan 3, 2013

Fix the other things.
Then, should the freezing continue, post a new set of the data collection app ( https://www.eightforums.com/bsod-cr...e-screen-death-bsod-posting-instructions.html )

It's not unusual for this to happen. I'd guess that we get it (further problems) 10 to 20% of the time.

RiesP · Jan 3, 2013

I have attempted to fix the other things yet the problem persists. It has however not created any new dump files. I had my settings set to a 'Full Memory Dump' so I changed it to Kernel. Is this okay or is Small memory dump preferable? I am also running the Driver verifier. Will this cause problems or is this advisable? In any case I hope to have new memory dumps I can post when it freezes again.

usasma · Jan 3, 2013

Here's my suggestions for setting it: Set MiniDump

Driver Verifier won't cause any problems (but may slow your system down), but please let us know what settings you're using. At worst it'll cause the system to generate BSOD's - and we'll analyze them the same way that we do with others.

Memory dumps aren't necessary (but I like them! :0)
In general, we look at the MSINFO32 report and the different event viewer log files.
If possible, please also:
- open Event Viewer (eventvwr.msc)
- expand the Custom Views category (left click on the > next to the words "Custom Views")
- right click on Administrative Events
- select "Save all Events in Custom View as..."
- save the file as Admin.evtx
- zip up the file (right click on it, select "Send to", select "Compressed (zipped) folder")
- upload it with your next post (if it's too big, then upload it to a free file-hosting service and post a link here).

RiesP · Jan 3, 2013

I ran the driver verifier as specified on this page: Driver Verifier Settings. I think I've made a huge mess of things now though. For some reason I decided to redo the AMD/ATI driver step from your first post but this time with driversweeper. After running driversweeper I attempted to reboot my PC but to no avail. Since then it has been stuck in a loop of BSOD's on boot. I managed to start my pc in safe mode with network capabilities so I'm attaching but my dump files as well as the data from the event viewer. I fear I may have done some serious damage this time. After posting this I will also be running Memtest overnight to look for any clues. Any help will once again be greatly appreciated! Thanks in advance.

usasma · Jan 3, 2013

First, be sure that Driver Verifier is turned off. It looks to be turned off, but I'd like you to make sure.

Next, backup your data. This is in case the system "bricks up" and won't let you in to recover your data.
Next, this is a security issue. Try some of the free antivirus scans from here: Free Online AntiMalware Resources
Please note that I have not scrubbed this list for Win8 compatibility - but I can state that the bootable disks at the bottom will work even if the other scans don't.

2 sets of problems listed in the dump files, others in the other reports.
My first set of suggestions is designed to increase the stability of the system - not to fix the BSOD's.

Once they're done, then we can work on the BSOD's.

In Safe Mode, try updating your video drivers from the AMD/ATI website ( Global Provider of Innovative Graphics, Processors and Media Solutions | AMD )
If that doesn't work, try a installing after a clean boot: How to perform a clean boot to troubleshoot a problem in Windows Vista, Windows 7, or Windows 8

Remove any USB devices that are plugged into the system. Let us know the make and model of the system (or motherboard if it's a custom build) in order to see if there are any other USB devices present.

Then boot using the clean boot described above. Can you get into Windows and do things?
If so, first visit Windows Update and ensure that you have ALL available updates.

Then uninstall the Western Digital software (the drivers are still present in the dump files)
And uninstall the Logitech WingMan software as it's still present (you can reinstall it later, right now we're trying to stabilize the system.
And uninstall the Line6 Guitar stuff - quite a few errors in the Admin.evtx logfile

Then try to boot normally and see if that works. Once that is done, let us know and we'll move on from there.

Oh yes, please get rid of Driver Sweeper - I never did like that software!

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

wdcsam64.sys Wed Apr 16 04:39:08 2008 (4805BB2C)
Western Digital SCSI Arcitecture Model (SAM) WDM driver[br]2008 driver version has known BSOD issues in Win7
http://www.carrona.org/drivers/driver.php?id=wdcsam64.sys

WmXlCore.sys Tue Apr 27 16:09:26 2010 (4BD74476)
Logitech WingMan Translation Driver
http://www.carrona.org/drivers/driver.php?id=WmXlCore.sys

WmBEnum.sys Tue Apr 27 16:10:19 2010 (4BD744AB)
Logitech WingMan Virtual Bus Enumerator Driver
http://www.carrona.org/drivers/driver.php?id=WmBEnum.sys

Rt630x64.sys Wed Oct 19 08:12:55 2011 (4E9EBEC7)
Realtek PCI/PCIe Adapters
http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys

Analysis:
The following is for informational purposes only.

Code:

[font=lucida console]**************************Thu Jan  3 17:06:49.227 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\010313-3822-01.dmp]
Windows 8 Kernel Version 9200 MP (6 procs) Free x64
Built by: [B]9200[/B].16461.amd64fre.win8_gdr.121119-1606
System Uptime:[B]0 days 0:00:06.909[/B]
*** ERROR: Module load completed but symbols could not be loaded for USBXHCI.SYS
Probably caused by :[B]USBXHCI.SYS ( USBXHCI+3072d )[/B]
BugCheck [B]139, {2, fffff88005993750, fffff880059936a8, 0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000139]KERNEL_SECURITY_CHECK_FAILURE (139)[/url]
Arguments: 
Arg1: 0000000000000002, Stack cookie instrumentation code detected a stack-based
    buffer overrun.
Arg2: fffff88005993750, Address of the trap frame for the exception that caused the bugcheck
Arg3: fffff880059936a8, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved
BUGCHECK_STR:  0x139
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]0x139_2_USBXHCI+3072d[/B]
  BIOS Version                  P1.60
  BIOS Release Date             10/12/2012
  Manufacturer                  To Be Filled By O.E.M.
  Product Name                  To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jan  3 16:59:06.950 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\010313-5397-01.dmp]
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\010313-12994-01.dmp]
Windows 8 Kernel Version 9200 MP (6 procs) Free x64
Built by: [B]9200[/B].16461.amd64fre.win8_gdr.121119-1606
System Uptime:[B]0 days 0:00:07.631[/B]
*** ERROR: Module load completed but symbols could not be loaded for USBXHCI.SYS
Probably caused by :[B]USBXHCI.SYS ( USBXHCI+3072d )[/B]
BugCheck [B]139, {2, fffff88007fb2990, fffff88007fb28e8, 0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000139]KERNEL_SECURITY_CHECK_FAILURE (139)[/url]
Arguments: 
Arg1: 0000000000000002, Stack cookie instrumentation code detected a stack-based
    buffer overrun.
Arg2: fffff88007fb2990, Address of the trap frame for the exception that caused the bugcheck
Arg3: fffff88007fb28e8, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved
BUGCHECK_STR:  0x139
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]0x139_2_USBXHCI+3072d[/B]
  BIOS Version                  P1.60
  BIOS Release Date             10/12/2012
  Manufacturer                  To Be Filled By O.E.M.
  Product Name                  To Be Filled By O.E.M.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jan  3 16:45:50.193 2013 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\010313-6801-01.dmp]
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\010313-5194-01.dmp]
Windows 8 Kernel Version 9200 MP (6 procs) Free x64
Built by: [B]9200[/B].16461.amd64fre.win8_gdr.121119-1606
System Uptime:[B]0 days 0:00:05.986[/B]
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by :[B]atikmpag.sys[/B]
BugCheck [B]C4, {62, fffffa8008ea7258, fffffa8008eb21c0, 1}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x000000C4]DRIVER_VERIFIER_DETECTED_VIOLATION (c4)[/url]
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Arguments: 
Arg1: 0000000000000062, A driver has forgotten to free its pool allocations prior to unloading.
Arg2: fffffa8008ea7258, name of the driver having the issue.
Arg3: fffffa8008eb21c0, verifier internal structure with driver information.
Arg4: 0000000000000001, total # of (paged+nonpaged) allocations that weren't freed.
    Type !verifier 3 drivername.sys for info on the allocations
    that were leaked that caused the bugcheck.
BUGCHECK_STR:  0xc4_62
PROCESS_NAME: [B]System[/B]
FAILURE_BUCKET_ID: [B]0xc4_62_LEAKED_POOL_IMAGE_atikmpag.sys[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

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.

Code:

[font=lucida console]**************************Thu Jan  3 17:06:49.227 2013 (UTC - 5:00)**************************
[COLOR=RED][B]wdcsam64.sys                Wed Apr 16 04:39:08 2008 (4805BB2C)[/B][/COLOR]
[COLOR=RED][B]WmXlCore.sys                Tue Apr 27 16:09:26 2010 (4BD74476)[/B][/COLOR]
[COLOR=RED][B]WmBEnum.sys                 Tue Apr 27 16:10:19 2010 (4BD744AB)[/B][/COLOR]
[COLOR=RED][B]Rt630x64.sys                Wed Oct 19 08:12:55 2011 (4E9EBEC7)[/B][/COLOR]
usbfilter.sys               Tue Jun 19 07:07:40 2012 (4FE05D7C)
amd_sata.sys                Mon Jul 23 14:34:48 2012 (500D9948)
amd_xata.sys                Mon Jul 23 14:34:52 2012 (500D994C)
AtihdW86.sys                Tue Aug 21 22:26:37 2012 (5034435D)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jan  3 16:59:06.950 2013 (UTC - 5:00)**************************
[COLOR=RED][B]dtsoftbus01.sys             Fri Jan 13 08:45:46 2012 (4F10358A)[/B][/COLOR]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jan  3 16:45:50.193 2013 (UTC - 5:00)**************************
atikmpag.sys                Sun Dec  2 02:13:21 2012 (50BAFF91)
[/font]

RiesP · Jan 4, 2013

I have disabled driver verifier. The reason why the WD software is still in the dump files is because I had to use system recovery in order to get the pc to boot at all. I had removed them before, along with the other things mentioned in your first post. I have made backups of all my data so I will try to do as you suggested as soon as I get home later today. My motherboard is an Asrock AMD 970 Pro3 by the way. Thanks so much for your help!

usasma · Jan 4, 2013

I've seen problems in the past with XFast LAN, XFast USB - please don't use them. If installed, please uninstall them.

RiesP · Jan 4, 2013

I have made some progress! Despite the fact that I couldn't leave safemode I managed to activate Windows Installer and uninstall all the software and update all the drivers that you mentioned in your post while still in safemode. After that I attempted the clean reboot and it seemed to work. I then fixed the Video card driver issue and rebooted 'normal' windows. It took longer than usual but in the end it worked. Now I'm basically running Windows almost completely barebones, no USB devices except for my mouse and keyboard etc. However I had to reinstall AMD Catalyst software in order to fix the overscan/underscan issue (although I believe there is a fix for this I will try next). What is my next move? The fact that I retrieved Windows to some extent doesn't necessarily solve my previous issues. Should I run driver verifier again?

RiesP · Jan 4, 2013

I uninstalled the Catalyst software and then manually updated the video card driver only (as described in one of the previous posts) so now I don't have the Catalyst software anymore and I still fixed the over/underscan issue.

RiesP · Jan 5, 2013

I tried to do everything that has been said so far, including virus/malware checks, removing/updating drivers etc. Yet after a short period of 'stability' my system is freezing, rebooting and BSODing all the time again. For some reason though it has stopped creating dump files despite the fact that I have all the correct settings and I have been running driver verifier. I have checked my SSD and RAM with both the windows tests as well as Memtest but nothing has showed up. I'm completely lost. I added my event log because that's all I could do. How likely is it that the errors are actually hardware malfunctionings?

usasma · Jan 5, 2013

Due to the missing memory dump files and the errors in the event viewer log (unexplained shutdowns) - we have to assume that this is a hardware problem (if it was a driver/Windows problem we'd expect Windows to show some sign of it in the logs/memory dumps).

So, please run the free hardware diagnostics from here: Hardware Diagnostics
Let us know the results and we'll move on from there.

RiesP · Jan 6, 2013

I have run all the memory, cpu, ram and gpu test I found in your link. My pc's performance in these tests has been very confusing at best. All the memory tests turned out fine, as well as the CPU tests. At the same time, FurMark didn't give me any problems either. Having said that, AMD Overdrive's stability test has been a mixed bag. I've had both analyses of over an hour that didn't show any errors, as well as 2 test that were stopped because of a 'hardware failure'. It didn't specify what the failure was however. But still, FurMark, Intel Burn Test, Memtest, etc. were all fine.

Despite this my pc has had a few freeze and crash moments. I have replaced my XFX 7770 (which has known issues I think) with an older 5670 in an attempt to rule out the video card as being a problem. So far this setup has been stable but obviously it's too early to tell. Is there anything else I should or could do at the moment?

usasma · Jan 7, 2013

I would suggest running more of the CPU stress tests to see if you can isolate the "hardware error" that the AMD program found.

RiesP · Jan 8, 2013

My system had been stable after replacing the video card. Until a few minutes ago when it rebooted again. Even though I have set the settings to disable an automatic reboot. I'm lost again. I'm running more CPU diagnostics but I have no idea what to do now. Could it be the motherboard or the power supply? The reboots are so extremely random. There doesn't seem to be any link to any sort of load or specific task. Am I missing something very obvious maybe?

EDIT: After nearly 48 hours of constant stability it crashed again within 10 minutes after the first crash. On reboot I had a pc freeze when starting up Speedfan to look for possible elevated temperatures. This program froze while looking for the ISA Bus, which isn't used anymore I think? I will see if I can find any information regarding the reboots. Software wise both times I was running only IE and Spotify.

EDIT EDIT: I found this thread: [SOLVED] Computer restarts itself randomly (as if i pressed the restart button on the - Tech Support Forum
The symptoms described by the OP are very similar to mine. I will therefore attempt to follow the instructions and tips posted in this topic.

RiesP · Jan 12, 2013

I just want to ask for help one more time because my pc still isn't working as it should. Over the last few days I have done a large number of CPU/GPU/RAM/Mem tests as found in your hardware diagnostics page. My pc managed to pass all these tests after I replaced the video card. The previously shown message by AMD Overdrive about a hardware failure has disappeared. Still it is prone to random and unexpected crashes and reboots. It has been stable for 48 hours straight before crashing twice in one hour. During these crashes it doesn't make any dump files even though I have all the correct settings. Right now I'm thinking the motherboard is probably broken. Is this possible? Are these generally symptoms of a broken motherboard or is there anything else I should be looking at? Thanks in advance.

usasma · Jan 13, 2013

I didn't receive notification of your last post, so please excuse my not responding.

Yes it is possible that it's the motherboard - but, unfortunately there are no definitive motherboard diagnostics.
If you're not getting memory dumps, yet you've run (and passed) all the diagnostics - then we have to assume it's a hardware problem.

The tests that I recall seeing have tended to rule out your:
- hard drive
- memory
- graphics card
- PSU

The next step is to remove everything that you can from the system to see if any of that is the cause. Try this procedure here: Hardware Stripdown Troubleshooting

If you can't do this procedure, then it's your choice as what to replace. IMO I suspect the mobo - but this costs me nothing. But it'll cost you the price of a new motherboard and the time to replace it (and repair Windows). That's not a problem if I'm right - but if I'm wrong you'll do all this for nothing. As I said previously - it's your choice. Good luck!

RiesP · Jan 13, 2013

Once again thanks for all of your helpful comments and links! Using your link I will try to isolate the problem. Like you said, the mobo will be the most expensive and hardest thing to replace so I'll make sure I check every other piece of hardware again first. Let's hope I'll be able to fix it!

BSOD Problem

Member

My Computer

Mr. Cranky Pants

My Computer

Member

My Computer

Mr. Cranky Pants

My Computer

Member

My Computer

Mr. Cranky Pants

My Computer

Member

My Computer

Mr. Cranky Pants

My Computer

Member

My Computer

Mr. Cranky Pants

My Computer

Member

My Computer

Member

My Computer

Member

My Computer

Mr. Cranky Pants

My Computer

Member

My Computer

Mr. Cranky Pants

My Computer

Member

My Computer

Member

My Computer

Mr. Cranky Pants

My Computer

Member

My Computer