Solved Random Black Screen/Crash - I have a minidump + SF.zip!

ajthemacboy · Sep 20, 2014

Hey everyone. I recently built my first custom PC. Here is a link to the build on PCPartPicker:
AMD FX-6300, Sapphire Radeon R9 270, Corsair 300R - Ordered build updated - ajthemacboy's Saved Part List - PCPartPicker

Since then I have had random black screen issues. At one point I reinstalled the OS, and they still occur. You may notice the R9 270 needs a 450W power supply at the least.

At first look you would think this is the problem, but it's not. Before the R9 270 I had an EVGA 750 Ti, which only uses like 60 watts of power or something, as well as a CM430W power supply, and the black screen issues still occurred.

First I returned the power supply for a CS450M, black screen still occurred. Then I returned the 750Ti for an r9 270, and the issue still occurs.

If it's not the graphics card, power supply, or OS, what should I do?

The last three times the black screen has happened, there was no minidump. It happened two times yesterday (Friday) and once today.

The info I got from SF Diagnostic tool is attached. The minidump blames NTOSKRNL.EXE, but I have no clue what this is or how to fix it.

Thanks in advance for your help.

usasma · Sep 21, 2014

MSI Afterburner and Riva Tuner (along with EVGA Precision) are known to cause BSOD's in some Windows systems (it's driver is usually RTCore64.sys). Please un-install them immediately!

If you're overclocking, please stop the overclock while we're troubleshooting. Feel free to resume the overclock once the system has been stabilized.

cpudrv64.sys is blamed in one of the memory dumps (and it dates from 2009) Please uninstall the program associated with it (I believe it's related to a program named "Can I Run It?" - Driver Reference Table - cpudrv64.sys )

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.

NOTE: these symptoms were from the previous release of OverDrive. The new release uses the same driver name, but is dated from 4 November 2013.

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.

Click to expand...

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.

The other 3 memory dumps are STOP 0x124 errors:
They are usually caused by one of these things:
- borked (broken) hardware (several different procedures used to isolate the problem device)
- BIOS issues (check for updates at the motherboard manufacturer's website)
- overclocking/overheating - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
- missing Windows Updates
- compatibility issues (3rd party hardware/drivers), older systems, or even pirated systems
- low-level driver problems
- or even malware (scanned for when we ask for hardware diagnostics from Initial Hardware Diagnostics or Hardware Diagnostics ).

You can get a head start on the hardware diagnostics if you'd like - they are located here: Hardware Diagnostics

Also, monitor your system's temperatures with this free tool: HWMonitor CPUID - System & hardware benchmark, monitoring, reporting

Normally temps shouldn't exceed:
CPU - 60ºC
GPU - 80ºC
HDD and other components - 40ºC

Analysis:
The following is for informational purposes only.

Code:

[font=lucida console]**************************Thu Sep 18 10:43:01.567 2014 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\091814-25125-02.dmp]
Windows 8 Kernel Version 9600 MP (6 procs) Free x64
Built by: [B]9600[/B].17238.amd64fre.winblue_gdr.140723-2018
System Uptime:[B]0 days 0:04:17.299[/B]
Probably caused by :[B]AuthenticAMD[/B]
BugCheck [B]124, {0, ffffe000481eb028, b0800000, 40151}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000124]WHEA_UNCORRECTABLE_ERROR (124)[/url]
Arguments: 
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffe000481eb028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b0800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000040151, Low order 32-bits of the MCi_STATUS value.
BUGCHECK_STR:  0x124_AuthenticAMD
PROCESS_NAME:  cpuocct64.exe
FAILURE_BUCKET_ID: [B]0x124_AuthenticAMD_PROCESSOR_CACHE[/B]
  BIOS Version                  V22.0
  BIOS Release Date             05/29/2014
  Manufacturer                  MSI
  Product Name                  MS-7693
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Sep 18 10:24:34.190 2014 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\091814-25125-01.dmp]
Windows 8 Kernel Version 9600 MP (6 procs) Free x64
Built by: [B]9600[/B].17238.amd64fre.winblue_gdr.140723-2018
System Uptime:[B]0 days 0:05:28.922[/B]
Probably caused by :[B]AuthenticAMD[/B]
BugCheck [B]124, {0, ffffe000a6cc8028, b0800000, 40151}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000124]WHEA_UNCORRECTABLE_ERROR (124)[/url]
Arguments: 
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffe000a6cc8028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b0800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000040151, Low order 32-bits of the MCi_STATUS value.
BUGCHECK_STR:  0x124_AuthenticAMD
PROCESS_NAME:  cpuocct64.exe
FAILURE_BUCKET_ID: [B]0x124_AuthenticAMD_PROCESSOR_CACHE[/B]
  BIOS Version                  V22.0
  BIOS Release Date             05/29/2014
  Manufacturer                  MSI
  Product Name                  MS-7693
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Sep 17 11:03:18.886 2014 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\091714-33937-01.dmp]
Windows 8 Kernel Version 9600 MP (6 procs) Free x64
Built by: [B]9600[/B].17238.amd64fre.winblue_gdr.140723-2018
System Uptime:[B]0 days 0:27:58.630[/B]
*** WARNING: Unable to verify timestamp for cpudrv64.sys
*** ERROR: Module load completed but symbols could not be loaded for cpudrv64.sys
Probably caused by :[B]cpudrv64.sys ( cpudrv64+1912 )[/B]
BugCheck [B]3B, {c0000096, fffff800ecaf4912, ffffd0015c297c70, 0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000003B]SYSTEM_SERVICE_EXCEPTION (3b)[/url]
Arguments: 
Arg1: 00000000c0000096, Exception code that caused the bugcheck
Arg2: fffff800ecaf4912, Address of the instruction which caused the bugcheck
Arg3: ffffd0015c297c70, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  inteldriver.ex
FAILURE_BUCKET_ID: [B]0x3B_cpudrv64+1912[/B]
  BIOS Version                  V22.0
  BIOS Release Date             05/29/2014
  Manufacturer                  MSI
  Product Name                  MS-7693
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Sep 17 08:53:02.835 2014 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\091714-40515-01.dmp]
Windows 8 Kernel Version 9600 MP (6 procs) Free x64
Built by: [B]9600[/B].17085.amd64fre.winblue_gdr.140330-1035
System Uptime:[B]0 days 0:01:13.582[/B]
Probably caused by :[B]AuthenticAMD[/B]
BugCheck [B]124, {0, ffffe00133abd028, b0800000, 40151}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000124]WHEA_UNCORRECTABLE_ERROR (124)[/url]
Arguments: 
Arg1: 0000000000000000, Machine Check Exception
Arg2: ffffe00133abd028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b0800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000040151, Low order 32-bits of the MCi_STATUS value.
BUGCHECK_STR:  0x124_AuthenticAMD
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID: [B]0x124_AuthenticAMD_PROCESSOR_CACHE[/B]
  BIOS Version                  V22.0
  BIOS Release Date             05/29/2014
  Manufacturer                  MSI
  Product Name                  MS-7693
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/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 Sep 18 10:43:01.567 2014 (UTC - 4:00)**************************
GEARAspiWDM.sys      Thu May  3 15:56:17 2012 (4FA2E2E1)
[COLOR=RED][B]NTIOLib_X64.sys      Sun Nov 18 23:32:58 2012 (50A9B67A)[/B][/COLOR]
speedfan.sys         Sat Dec 29 15:59:35 2012 (50DF59B7)
[COLOR=RED][B]RTCore64.sys         Mon Mar 11 01:32:06 2013 (513D6C56)[/B][/COLOR]
netr28x.sys          Thu Jul 11 05:27:41 2013 (51DE7A8D)
[DEL]dump_storahci.sys    Thu Aug 22 07:40:39 2013 (5215F8B7)
[/DEL]RTKVHD64.sys         Tue Nov 19 09:32:08 2013 (528B7668)
NuidFltr.sys         Thu Dec 12 08:16:25 2013 (52A9B729)
dc3d.sys             Thu Dec 12 08:16:35 2013 (52A9B733)
[COLOR=RED][B]AODDriver2.sys       Tue Feb 11 06:06:52 2014 (52FA044C)[/B][/COLOR]
usbfilter.sys        Mon Feb 17 01:23:43 2014 (5301AAEF)
AMDACPKSL.SYS        Tue Mar 11 19:49:44 2014 (531FA118)
AtihdWB6.sys         Tue Mar 11 19:50:02 2014 (531FA12A)
e22w8x64.sys         Wed Mar 26 11:58:37 2014 (5332F92D)
bwcW8x64.sys         Thu Apr 10 11:40:24 2014 (5346BB68)
xhcdrv.sys           Thu May 29 06:25:26 2014 (53870B16)
ViaHub3.sys          Thu May 29 06:25:32 2014 (53870B1C)
cpuz137_x64.sys      Mon Aug 11 09:27:34 2014 (53E8C4C6)
atikmpag.sys         Mon Aug 11 21:33:58 2014 (53E96F06)
atikmdag.sys         Mon Aug 11 22:37:53 2014 (53E97E01)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Sep 18 10:24:34.190 2014 (UTC - 4:00)**************************
NTIOLib_X64.sys      Tue Nov 20 03:11:26 2012 (50AB3B2E)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Sep 17 11:03:18.886 2014 (UTC - 4:00)**************************
[COLOR=RED][B]cpudrv64.sys         Tue Aug 11 12:39:13 2009 (4A819EB1)[/B][/COLOR]
atikmpag.sys         Fri Jul  4 21:26:52 2014 (53B7545C)
atikmdag.sys         Fri Jul  4 21:39:13 2014 (53B75741)
[/font]

ajthemacboy · Sep 21, 2014

Hello, and thanks for your reply.
I uninstalled Afterburner and RivaTuna, but I do not know how to remove cpudrv64. I have never heard of 'Can I run it'. I see that near Cpudrv64 on the page you linked is Cpuz by CPUID, which I have now uninstalled.

I used to have OverDrive installed on my computer, but a few weeks ago I had to reinstall Windows because of an issue I was having. Windows was booting to the login screen with a flashing cursor and internet icon. I have not installed it since. I did however have GPU overdrive turned on in Catalyst. It is now disabled.

As for malware, I have scanned multiple times with no results.

I know overheating is a problem that can cause this. I read somewhere about using the stock CPU cooler to keep the motherboard heatsinks cool. Today I set this up. I plugged the stock cpu cooler cable into the SYSFAN1 plug, and moved the rear fan to another plug, and positioned the fan to cool the smaller heatsink on the motherboard (not the one that keeps the 'things' that supply power to the CPU cool). We will see if this helps.
However, my CPU and GPU temps usually stay cool, the CPU only gets to around 45 when under load, and 52~ when I stress tested.

Also, the computer has crashed 2 more times and still hasn't made another minidump. I made sure that the Windows Diagnostic Service was starting with windows. It was actually disabled. However, this still didn't make a minidump. All minidump settings are enabled, but it doesn't make one.

Questions:
Is cpudrv64 CPUID by CPUZ, and if it isn't how do I uninstall it?
Is there a way I can see a list of installed drivers to see if I have any of the bad ones you mentioned installed?
Is the OverDrive software included in Catalyst what you meant when you said OverDrive was bad?

ajthemacboy · Sep 21, 2014

I am going out of town until Tuesday, so I won't be able to help until then. I hope we can continue this then, and sorry for the inconvenience.

usasma · Sep 21, 2014

Thanks for the info on CPUDRV64.sys - I'll research it and add it to the DRT (Driver Reference Table)

I get an email once you respond to a post - so I'll get notified when you respond back - be it in a week, a month, or even a year!

The list of drivers that I provide is the 3rd party (nonWindows) drivers that were present on your system when the BSOD's happened. It's only those that were involved with the BSOD. There are plenty more on the system.
Also, I remove the Windows drivers from the display as we don't normally worry about them.

Most drivers are located in C:\Windows\System32\drivers - but some developers store them elsewhere (not a good practice IMO). Also, some developers don't mark their drivers with the .sys file extension, so there may be other drivers on the system that you can't locate by searching for *.sys In short, don't worry about searching for the bad one's - if they raise their ugly heads (in a BSOD), then we'll deal with them then.

Yes, OverDrive is included with the Catalyst Control Center. Getting rid of it is a pain, but it's needed in order to rule it out as a cause (it has a history of BSOD's in the past).

ajthemacboy · Sep 24, 2014

Alright, I'm back, and I've started to remove the drivers I can. I removed AMD FUEL, apparently I don't really need it, speedfan, iTunes (it has the gearaspiwdm.sys driver), and a couple others, but how do I remove drivers like usbfilter.sys or amdacpksl.sys, or do I even remove them?

Both have multiple locations, is it safe to just delete them all? USBFilter.sys has like 10 locations in the C:\AMD directory, and 2 in Windows/System32.

ViaHub3.sys is in C:\Windows\System32\drivers and C:\Windows\System32\DriverStore\FileRepository, am I going to loose usb functionality if I delete them?

Going to use DDU on the AMD Drivers in a minute and just install the driver without Catalyst.

usasma · Sep 24, 2014

DO NOT DELETE DRIVERS - IT CAN RENDER YOUR SYSTEM UNBOOTABLE!!!!!!

I never delete anything right away. I either rename it or move it to another location.
That way, if something goes wrong, I can just un-rename it or move it back from where it was.

If you need to remove drivers manually, I'll provide specific directions that'll let you recover if they render your system unbootable. It's not needed right now tho'

If the system is still BSODing - please zip up and upload the contents of C:\Windows\Minidump. You may have to copy them to your Desktop in order to zip them up.

ajthemacboy · Sep 26, 2014

Ok, it's been about 2 days since I've had a crash, but I just had one. Again, there was no minidump.

This is the second or third time the computer has crashed exactly when I started playing a youtube video. I have disabled most of the drivers. Have any ideas why this could be?

Edit: Forgot to mention that uninstalling all amd and ati software other than the display drivers (no catalyst or any other software) seemed to result in 2 days of no crashing. Usually I can watch a youtube video just fine, but when loading one up after a while it crashes.

usasma · Sep 27, 2014

Let's take a look at this and see if it gives us any clues:

Please do the following:
- open Event Viewer (run eventvwr.msc from the "Run" dialog))
- 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).

While waiting for a reply, please monitor your temps with this free utility: HWMonitor CPUID - System & hardware benchmark, monitoring, reporting

I've seen a lot of video problems with older Asus G750's (not so much with the newer one's).
How old is yours? When was it purchased? What OS did it come with originally?

Try the free video stress tests from here: Hardware Diagnostics
Make sure that you blow out the vents with canned air (DO NOT USE a vacuum or an air compressor - it can damage your components). Then make sure you use the system on a hard surface (preferably with a laptop cooling pad).

ajthemacboy · Sep 27, 2014

Here is the administrative events view.

My laptop is from 2012, I've never had any problems with it. Here's another thing; I ran chkdsk, restarted the computer, and then the 'scanning and repairing drive' thing at login got stuck at 10%. I read this means that it's probably damaged. I didn't let it sit for a long time, should I?

I've also notice that crashes often happen in the middle of a file download. This makes me think it could be memory problems, but I've run several passes of memory diagnostics with no errors. I've googled about disk errors and black screens and it doesn't seem to be a related problem.

I've heard that if chkdsk gets stuck it usually fixes itself... after 24+. Do you think it would be a good idea to let it run that long? Is there another bootable utility that could do it faster? The utility you can use by right clicking the C: drive says that there are no errors on the disk, but I don't know how reliable that is.

usasma · Sep 28, 2014

Rerun chkdsk and let it run for a couple of hours. You shouldn't have to run it for 24+ hours.
This tests the file system on the hard drive - not the hard drive itself.
The right click on the C: drive thing is only predictive, it isn't an actual diagnosis.

Also, run a hard drive diagnostic - follow the suggestions here: Hard Drive Diagnostic Procedure

Black screens are difficult problems to troubleshoot. There are no simple answers for them.
First run these hardware diagnostics: Hardware Diagnostics

The uploaded Admin Log File shows a number of problems.
It shows problems with the system firmware - so please update the BIOS/UEFI from the manufacturer's website. Use the builtin Live Update utility if possible - it's safer than manually updating it.

It shows problems with AMD OverDrive, so please follow these suggestions:

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.

NOTE: these symptoms were from the previous release of OverDrive. The new release uses the same driver name, but is dated from 4 November 2013.

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.

Click to expand...

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.

Click to expand...

To address the rest of the problems we'll need a full set of reports. Even though you're not reporting BSOD's, please provide this information so we can provide a complete analysis (from the Pinned Topic at the top of the forum): http://www.eightforums.com/bsod-cra...e-screen-death-bsod-posting-instructions.html Please use Option 1 as it provides Event Viewer logs.

ajthemacboy · Oct 4, 2014

I ran ddu again and uninstalled all amd components in device manager and control panel. I haven't had a crash in a week.

Solution: Uninstalled all AMD software and only installed the graphics driver. I did this by deselecting everything else in the AMD driver installer.

So happy to finally have a working computer!

blueelvis · Oct 5, 2014

Glad to hear that the issue has been solved ^_^

Solved Random Black Screen/Crash - I have a minidump + SF.zip!

ajthemacboy

New Member

usasma

Mr. Cranky Pants

ajthemacboy

New Member

ajthemacboy

New Member

usasma

Mr. Cranky Pants

ajthemacboy

New Member

usasma

Mr. Cranky Pants

ajthemacboy

New Member

usasma

Mr. Cranky Pants

ajthemacboy

New Member

usasma

Mr. Cranky Pants

ajthemacboy

New Member

blueelvis

OMG Debugger!

Similar threads