Random BSODs... 1e

[pchill]

I have been having random BSODs 3 or 4 times a week for months now. Most of them are 1e, but I have also had various other codes over the last few months.

Here are the steps I have performed to date:
1. Updated the drivers for what would appear to be likely culprits.... network card, ceton cable card reader, video card (Radeon HD 6850), Motherboard (Z68AP-D3)... etc.
2. Tried to run driver verifier. Unfortunately the only time it does anything is if I select all drivers and it gives me a wacked screen requiring a reboot in safe mode to turn it off.
3. I have updated the BIOS
4. Cycled Memtest83 8x's and no failures

I'm a bit at a loss here. I am attaching the .dmp file.

Any thoughts?

 

[x BlueRobot]

Please follow these instructions fully: http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html

 

[pchill]

I didn't see the instructions. I know that must be frustrating. Sorry about that.

 

[x BlueRobot]

[COLOR="Red"]BugCheck 3B[/COLOR], {[COLOR="SeaGreen"]c0000005[/COLOR], fffff80003eb5969, fffff8800d1ec890, 0}

Probably caused by : memory_corruption ( nt!MiRestoreTransitionPte+109 )

Usual causes:  System service, Device driver, graphics driver, memory

1: kd> [COLOR="SeaGreen"]!error c0000005[/COLOR]
Error code: (NTSTATUS) 0xc0000005 (3221225477) - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

memory_corruption doesn't necessary mean that a RAM module is faulty, it can also point to a object which corrupted the RAM at the time of the crash, for instance a corrupted driver or program. Paging files and the CPU caches can also be causes.

Follow these steps -

Test for any corrupted drivers, by running Driver Verifier for least 24 hours, stop the test if a BSOD occurs before this time frame. Driver Verifier will place stress on the drivers within your system, which will cause corrupted drivers to crash and hopefully be pinpointed.

• http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

   Information

More Help and Information with Driver Verifier - http://www.sevenforums.com/crash-lo...-driver-verifier-identify-issues-drivers.html

Memory:

• http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Run Memtest86+ for least 7-8 passes, and preferably overnight as it can take a while to fully complete.

Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

Test each RAM stick and every motherboard DIMM slot available.

:ar:Scan for any malware:

• http://www.sevenforums.com/tutorials/166445-windows-defender-offline.html
• Anti-rootkit utility TDSSKiller

:ar:Scan for any missing, modified or corrupted protected Windows files with:

• http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Upload .NFO file:

Start rb: > Type: msinfo32 > File, Save

 

[pchill]

BSOD From Verifier

I have run all these tests and here are the additional things I had done:

1. Since I couldn't get verifier to work without a freeze (no BSOD), I removed Catalyst Control Center.
2. BSODs have been much less frequent since then.
3. I finally got a BSOD with verifier on.

I have attached the SF file.

I have a Gigabyte AMD Radeon HD 6850 16GB Graphics Card.

Thoughts?

 

[x BlueRobot]

[COLOR="red"]BugCheck D5[/COLOR], {fffff9802bcc8fd0, 0, fffff880049a3f1e, 0}

*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys

Could not read faulting driver name
Probably caused by : [COLOR="Red"]atikmdag.sys[/COLOR] ( atikmdag+154f1e )

Usual causes:  Device driver

2: kd> [COLOR="SeaGreen"]lmvm atikmdag[/COLOR]
start             end                 module name
fffff880`0484f000 fffff880`0525d000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        [COLOR="red"]Wed Oct 12 20:56:42 2011[/COLOR] (4E95F0FA)
    CheckSum:         009C8B89
    ImageSize:        00A0E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Your graphics card driver is causing problems and is very outdated, please update the driver from here:

• AMD Driver Autodetect

1. Download Driver
2. Start rb: Type: Device Manager
3. Expand Display Adapters
4. Right-Click Driver Name, Uninstall
5. Reboot
6. Run Driver Sweeper
7. Reboot
8. Install Downloaded Driver

Driver Sweeper will scan for any left over files from the old driver, old driver files can cause conflicts with new driver installations. Create a System Restore point beforehand, in case any problems or issues arise.

Driver Sweeper:

• http://www.sevenforums.com/tutorials/83814-drivers-clean-left-over-files-after-uninstalling.html

What are the results of the other scans?

   Tip

Disable Driver Verifier

 

[pchill]

I passed all other tests.

I have done this, so we'll see where it goes.

Thank you very much for your guidance!!!!

 

[x BlueRobot]

Your welcome, leave the thread open for about a week, and post if the problem has been solved.

 

[pchill]

Intermittent BSOD, often with WMC Live TV

I have had continued BSODs. For a while, it would happen after I left my computer on, a couple of times per week. Now it happens when I have a lot going on on my computer.

I have done all of the standard procedures:
1. tested drivers
2. tested the RAM
3. Updated BIOS
4. Updated Video Drivers

I have attached my dump file

 

[x BlueRobot]

Hi again pchill,

[COLOR="Red"]BugCheck 3D[/COLOR], {fffff880009a8dc0, 0, 0, fffff80003e8b854}

Probably caused by : ntkrnlmp.exe ( nt!KiScanInterruptObjectList+64 )

0: kd> [COLOR="SeaGreen"]!irql [/COLOR]
Debugger saved IRQL for processor 0x0 -- [COLOR="Red"]5[/COLOR]

From what I can gather, a interrupt for an exception (error) was issued, but wasn't able to handled by the processor.

The interrupt most likely occurred from a physical device, the raw stack shows the video scheduler sending out interrupts, although an exception occurred before this, therefore it may be the video scheduler sending out mishandled interrupts or something else.

0: kd>[COLOR="SeaGreen"] lmvm atikmdag[/COLOR]
start             end                 module name
fffff880`04849000 fffff880`053bc000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        [COLOR="red"]Fri Mar 29 02:27:04 2013[/COLOR] (5154FBF8)
    CheckSum:         00B25604
    ImageSize:        00B73000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

WHQL
Release Date: April 24th 2013
Version: 13.4
In Device Manager: 12.104

Please update to the latest WHQL version using the same method as before:

• AMD Graphics Drivers & Software

Graphics Card:

• http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html

   Warning

Read all the steps within the hardware test tutorials very carefully, as stress tests is designed run components to their maximum capacity, in order to point out failing or faulty hardware components.

Use the following program to monitor your hardware temperatures during the stress test:

• GPU-Z Video card GPU Information Utility