BSOD at random times. System_Service_Exception and atikmdag.sys.

tycischke · 15 Oct 2014

I have run our of ideas to fix this. I have a HDD and an SSD. I boot windows from my SSD. I have done a clean install of windows, ran a full scan with Microsoft Security Essentials. Reinstalled my video driver multiple times. Made sure I am only running one audio driver. And I still get these errors at random times. The blue screen either says System_service_exception, or atikmdag.sys. They are completely random seeming. Could be watching a video, could be playing a game, or could even have nothing up.

I hope that I'm posting correctly, I have attached the zip file that the posting instructions thread told me to.
I appreciate any help and insight I can get.

Arc · 16 Oct 2014

Hi tycischke.

The zip you uploaded does not contain any crash dump.

Follow it: Dump Files - Configure Windows to Create on BSOD
Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.

Now wait for another BSOD. When it occurred, search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. See if the crash dump is recorded or not (hopefully it will be recorded).Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Dont run any disc cleanup tool before you upload another zip.

tycischke · 16 Oct 2014

I followed your instructions, Arc. I got a blue screen that said "dxgmm1.sys". I also made sure there was a .dmp in the minidump folder.

Arc · 17 Oct 2014

Try any older version of the display driver other than 14.9 WHQL.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Also plan to update the BIOS to Version 3602 from Motherboard - P8P67 PRO (REV 3.1) - ASUS

tycischke · 22 Oct 2014

I have updated my bios and am still getting blue screens. I attached a new log collector file.
Also, I ran the video stress test. It ran for about 7 minutes and then my computer crashed, there were no screen artifacts and the max temp that my gpu got to was 76 degrees Celsius.

Arc · 22 Oct 2014

Code:

BugCheck 3B, {c0000005, fffff80002edc79d, fffff880045b7fe0, 0}

Probably caused by : Unknown_Image ( nt!KiSignalSynchronizationObject+17d )

Followup: MachineOwner
---------

We are not getting any info from the crash dump. But generally a stop 0x3B causes due to 3 reasons. Let us check them.

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If it does not show any error, enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

Tip

If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

tycischke · 27 Oct 2014

I ran the ram test with no errors, it ran for 8 cycles. When I have the verifier on, after a while my screen will freeze and have a bunch of lines running horizontally, but it doesn't go to a blue screen, I just have to restart it. I installed the 14.8 video drivers and the same problems are happening. The log is taken right after a restart mentioned above.

Arc · 28 Oct 2014

Code:

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner
---------

Another different BSOD with unknown cause.

Code:

BUCKET_ID:  INVALID_KERNEL_CONTEXT

FAILURE_BUCKET_ID:  INVALID_KERNEL_CONTEXT

Crash dumps are not being helpful here.

I would suggest you to do a test. Observe if the BSODs are occuring or not, if you disconnect the logitech headset.

tycischke · 29 Oct 2014

So i unplugged the headset and I haven't had a crash in two days. I never did like the driver for it. It's a logitech g35. When I installed the driver it made it so a few of my usb plugs stopped working. Do you think it is just a problem with the driver or the hardware itself? I would like to be able to still use that headset. Also, I really appreciate all the help you've given me.

Arc · 30 Oct 2014

tycischke said:

So i unplugged the headset and I haven't had a crash in two days. I never did like the driver for it. It's a logitech g35. When I installed the driver it made it so a few of my usb plugs stopped working. Do you think it is just a problem with the driver or the hardware itself? I would like to be able to still use that headset. Also, I really appreciate all the help you've given me.

Difficult to say from my part. Specially when the crash dumps are totally silent.

But you may determine it by trial and error. Make it sure that the latest listed driver is installed for the device. G35 Surround Sound Headset - Logitech Support

If the issue occurs with multiple versions of the driver, then it is not a driver caused issue.