Help with random BSOD crashes

[thehun]

Hi,

my PC crashes randomly every couple of hours. I have attached the logs and report in echo.zip. Any help would be appreciated!

My memory dump looks like this:

Debugging Details:
------------------




READ_ADDRESS: 0000000000000017


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.


FAULTING_IP:
nt!PiDmCompareObjects+12
fffff802`85bfe83a 448b4218 mov r8d,dword ptr [rdx+18h]


EXCEPTION_PARAMETER2: 0000000000000017


BUGCHECK_STR: 0x1E_c0000005_R


DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT


PROCESS_NAME: TeamViewer.exe


CURRENT_IRQL: 0


TRAP_FRAME: fffff8800c92bb20 -- (.trap 0xfffff8800c92bb20)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000bb96d503 rbx=0000000000000000 rcx=fffff8800c92bd40
rdx=ffffffffffffffff rsi=0000000000000000 rdi=0000000000000000
rip=fffff80285bfe83a rsp=fffff8800c92bcb0 rbp=fffff80285adbdc0
r8=fffff8a0003d5700 r9=0000000000000000 r10=fffff8a009d84bc8
r11=000000000000006f r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz ac po cy
nt!PiDmCompareObjects+0x12:
fffff802`85bfe83a 448b4218 mov r8d,dword ptr [rdx+18h] ds:00000000`00000017=????????
Resetting default scope


LOCK_ADDRESS: fffff80285ade840 -- (!locks fffff80285ade840)


Resource @ nt!PnpRegistryDeviceResource (0xfffff80285ade840) Exclusively owned
Contention Count = 84
Threads: fffffa8007648080-01<*>
1 total locks, 1 locks currently held


PNP_TRIAGE:
Lock address : 0xfffff80285ade840
Thread Count : 1
Thread address: 0xfffffa8007648080
Thread wait : 0x3ded4


LAST_CONTROL_TRANSFER: from fffff802859e026d to fffff80285860440


STACK_TEXT:
fffff880`0c92b278 fffff802`859e026d : 00000000`0000001e ffffffff`c0000005 fffff802`85bfe83a 00000000`00000000 : nt!KeBugCheckEx
fffff880`0c92b280 fffff802`8585f842 : fffffa80`076439f0 00000000`00000017 fffff880`0c92bab0 fffff880`048c409e : nt! ?? ::FNODOBFM::`string'+0x148c3
fffff880`0c92b940 fffff802`8585dfba : 00000000`00000000 fffff8a0`003d56e0 00000000`00000000 fffff880`0c92bb20 : nt!KiExceptionDispatch+0xc2
fffff880`0c92bb20 fffff802`85bfe83a : 00000000`c0000002 fffff8a0`0b02f650 00000000`00000000 fffff802`85be465c : nt!KiPageFault+0x23a
fffff880`0c92bcb0 fffff802`858e7add : fffff8a0`00000200 fffff880`0c92bec8 fffff880`01020100 fffff8a0`09d84ac8 : nt!PiDmCompareObjects+0x12
fffff880`0c92bce0 fffff802`85c02717 : 00000000`00000000 00000000`00000000 00000000`00000120 fffff802`85adbe20 : nt!RtlLookupElementGenericTableAvl+0x2d
fffff880`0c92bd10 fffff802`85be45a2 : fffff8a0`09d84a02 fffff8a0`09d84ac0 fffff8a0`09d84ac0 00000000`00000000 : nt!PiDmLookupObject+0x5b
fffff880`0c92bdc0 fffff802`85bf9b67 : 00000000`00000000 fffff880`0c92be40 fffff880`0c92c070 00000000`00000017 : nt!PiDmGetObject+0x52
fffff880`0c92bdf0 fffff802`85beb75f : fffff802`85e8c950 fffff880`0c92bf00 00000000`00000000 00000000`00000017 : nt!PiControlGetDeviceInterfaceEnabled+0xaf
fffff880`0c92be60 fffff802`8585f453 : fffffa80`07648080 fffff880`0c92c070 fffff880`0c92c0b0 fffff880`0c92c070 : nt!NtPlugPlayControl+0xaf
fffff880`0c92beb0 fffff802`85864630 : fffff802`85bd77be fffff8a0`001fd9a0 00750073`00260031 fffff880`00000001 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0c92c048 fffff802`85bd77be : fffff8a0`001fd9a0 00750073`00260031 fffff880`00000001 fffff880`0c92c0b0 : nt!KiServiceLinkage
fffff880`0c92c050 fffff802`85bd7d4f : fffff880`0c92c370 fffff880`0c92c129 fffff8a0`00314201 00000000`00000001 : nt!PiPnpRtlGetDeviceInterfaceEnabled+0x36
fffff880`0c92c0a0 fffff802`85bd6ec1 : 00000000`00000000 00000000`00000000 fffff802`85bd6dc8 fffff880`0c92c288 : nt!PiPnpRtlInterfaceFilterCallback+0x78
fffff880`0c92c190 fffff802`85bd6dfc : 00000000`00000086 fffff8a0`001fdac0 00000000`00000000 00000000`00000000 : nt!PiDmCmObjectMatchCallback+0x26
fffff880`0c92c1c0 fffff802`85bd6bd8 : 00000000`000003b4 00000000`00000000 00000000`00000000 fffff802`85be45b6 : nt!PiDmGetObjectListCallback+0x34
fffff880`0c92c210 fffff802`85bd6d07 : fffff880`0c92c500 00000000`00000000 fffff880`0c92c2b0 fffff8a0`00483000 : nt!PiDmListEnumObjectsWithCallback+0x130
fffff880`0c92c260 fffff802`85bd6dc1 : fffff880`0c92c510 fffff8a0`0007d400 fffff880`0c92c510 00000000`00000003 : nt!PiDmGetObjectConstraintList+0xa7
fffff880`0c92c2d0 fffff802`85bd739a : fffff8a0`00483000 fffff802`858d3657 fffff6fc`50002418 fffff880`0c92c3b9 : nt!PiDmGetCmObjectConstraintListFromCache+0x55
fffff880`0c92c330 fffff802`85bd8efb : ffffffff`00000000 00000000`c0000002 00000000`20207050 00000000`00000000 : nt!PiPnpRtlGetFilteredDeviceInterfaceList+0xa2
fffff880`0c92c3d0 fffff802`85bd7686 : fffff880`0c92c6a0 fffff8a0`0007d400 fffff8a0`00483000 fffffa80`03c60680 : nt!PiPnpRtlCmActionCallback+0x1b7
fffff880`0c92c4b0 fffff802`85bd7a73 : 00000000`c0000225 fffff880`0c92c6d0 00000000`00000000 fffff880`0c92c6d0 : nt!CmGetMatchingFilteredDeviceInterfaceList+0xd6
fffff880`0c92c5d0 fffff802`85bd7f28 : 00000000`00000001 fffff880`0c92ca18 00000000`00000000 fffff880`0c92c818 : nt!IopGetDeviceInterfaces+0x283
fffff880`0c92c7a0 fffff802`85beb597 : 00000000`00000001 fffff802`85c3897c 00000000`00000250 fffff802`858a9181 : nt!PiCMGetDeviceInterfaceList+0xf8
fffff880`0c92c8a0 fffff802`85bec875 : d4003b1e`5987fc09 0000001f`00120089 00000000`00000000 00000000`00000003 : nt!PiCMHandleIoctl+0x187
fffff880`0c92c8e0 fffff802`85bec7b9 : fffff802`85bec754 fffffa80`03c51dc0 00000000`00000000 00000000`00000000 : nt!PiCMFastIoDeviceDispatch+0x55
fffff880`0c92c930 fffff802`85c3547a : 00000000`00000002 fffff802`858d9c9d 00000000`00000000 00000000`00000002 : nt!PiDaFastIoDispatch+0x65
fffff880`0c92c990 fffff802`85c4aa76 : 00000000`00000001 00000000`00000000 00000000`00000001 00000000`00000000 : nt!IopXxxControlFile+0x3d9
fffff880`0c92cb20 fffff802`8585f453 : 00000000`00000000 00000000`7f797000 fffff6fb`7dbed000 fffff6fb`7da00000 : nt!NtDeviceIoControlFile+0x56
fffff880`0c92cb90 00000000`77a92ad2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00c4efb8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77a92ad2




STACK_COMMAND: kb


FOLLOWUP_IP:
nt!PiDmCompareObjects+12
fffff802`85bfe83a 448b4218 mov r8d,dword ptr [rdx+18h]


SYMBOL_STACK_INDEX: 4


· OS: Windows 8 x64
· What was original installed OS on system? Win 8 x64
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? Full retail
· Age of system (hardware): brand new
· Age of OS installation - have you re-installed the OS? no

· CPU: Celeron G1620
· Video Card: Sapphire Radeon 7950
· MotherBoard: Z77A-GD65
· Power Supply - brand & wattage (if laptop, skip this one): Corsair CX750 (750W)

· System Manufacturer : self built
· Exact model number (if laptop, check label on bottom): N/A

· Laptop or Desktop? Desktop

 

[Patrick]

Hi,

We have various bug checks:

KMODE_EXCEPTION_NOT_HANDLED (1e)

This indicates that a kernel-mode program generated an exception which the error handler did not catch.

SYSTEM_SERVICE_EXCEPTION (3b)

This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.

This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code.

STACK_TEXT:  
fffff880`0c0bbdc8 fffff880`0434161f : 00000000`00000000 fffffa80`00000002 fffffa80`03cd1ea0 00000000`00000001 : [COLOR=#ff0000][I][B]atikmdag[/B][/I][/COLOR]+0xed80
fffff880`0c0bbdd0 00000000`00000000 : fffffa80`00000002 fffffa80`03cd1ea0 00000000`00000001 000000ff`828b2000 : [COLOR=#ff0000][I][B]atikmdag[/B][/I][/COLOR]+0xb861f

^^ AMD/ATI video driver.

Unknown bugcheck code (144)

The BUGCODE_USB3_DRIVER bug check has a value of 0x00000144. This is the code used for all USB 3 bug checks.

BugCheck 144, {2, fffffa8004f63060, 1, 0}

^^ 1st parameter of the bug check is 2, therefore this indicates that a boot or paging device failed re-enumeration.

Unknown bugcheck code (a0000001)

This is an AMD/ATI only bug check. If you take a look at the call stack:

0: kd> kb
RetAddr           : Args to Child                                                           : Call Site
fffff880`046417ce : 00000000`a0000001 00000000`00000005 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
00000000`a0000001 : 00000000`00000005 00000000`00000000 00000000`00000000 00000000`00000000 : [COLOR=#ff0000][I][B]atikmdag[/B][/I][/COLOR]+0x277ce
00000000`00000005 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xa0000001
00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x5

You can see that the AMD/ATI video driver called directly into KeBugCheckEx as opposed to Windows performing its routine exception handling, fault tolerance checks, etc. This is generally a hardware problem only bug check, and rarely is it caused by software or even the driver itself.

----------------

1. Remove and replace avast! with Windows 8's built-in Windows Defender for temporary troubleshooting purposes:

avast! removal - avast! Uninstall Utility | Download aswClear for avast! Removal

Windows Defender (how to turn on after removal) - Windows Defender - Turn On or Off in Windows 8

2. Ensure you have the latest video card drivers. If you are already on the latest video card drivers, uninstall and install a version or a few versions behind the latest to ensure it's not a latest driver only issue. If you have already experimented with the latest video card driver and many previous versions, please give the beta driver for your card a try.

3. Run Memtest for NO LESS than ~8 passes (several hours):

Memtest86+:

Download Memtest86+ here:

Memtest86+ - Advanced Memory Diagnostic Tool

Which should I download?

You can either download the pre-compiled ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).

How Memtest works:

Memtest86 writes a series of test patterns to most memory addresses, reads back the data written, and compares it for errors.

The default pass does 9 different tests, varying in access patterns and test data. A tenth test, bit fade, is selectable from the menu. It writes all memory with zeroes, then sleeps for 90 minutes before checking to see if bits have changed (perhaps because of refresh problems). This is repeated with all ones for a total time of 3 hours per pass.

Many chipsets can report RAM speeds and timings via SPD (Serial Presence Detect) or EPP (Enhanced Performance Profiles), and some even support changing the expected memory speed. If the expected memory speed is overclocked, Memtest86 can test that memory performance is error-free with these faster settings.

Some hardware is able to report the "PAT status" (PAT: enabled or PAT: disabled). This is a reference to Intel Performance acceleration technology; there may be BIOS settings which affect this aspect of memory timing.

This information, if available to the program, can be displayed via a menu option.

Any other questions, they can most likely be answered by reading this great guide here:

FAQ : please read before posting

4. If Memtest passes, run chkdsk (paste log afterwards) and then Seatools:

Chkdsk:
There are various ways to run Chkdsk~

Method 1:

Start > Search bar > Type cmd (right click run as admin to execute Elevated CMD)

Elevated CMD should now be opened, type the following:

chkdsk x: /r

x implies your drive letter, so if your hard drive in question is letter c, it would be:

chkdsk c: /r

Restart system and let chkdsk run.

Method 2:


Open the "Computer" window
Right-click on the drive in question
Select the "Tools" tab
In the Error-checking area, click <Check Now>.

If you'd like to get a log file that contains the chkdsk results, do the following:

Press Windows Key + R and type powershell.exe in the run box

Paste the following command and press enter afterwards:

get-winevent -FilterHashTable @{logname="Application"; id="1001"}| ?{$_.providername –match "wininit"} | fl timecreated, message | out-file Desktop\CHKDSKResults.txt

This will output a .txt file on your Desktop containing the results of the chkdsk.

If chkdsk turns out okay, run Seatools -

SeaTools | Seagate

You can run it via Windows or DOS. Do note that the only difference is simply the environment you're running it in. In Windows, if you are having what you believe to be device driver related issues that may cause conflicts or false positive, it may be a wise decision to choose the most minimal testing environment (DOS).

Run all tests EXCEPT: Fix All, Long Generic, and anything Advanced.

5. What devices do you have connected via USB?

Regards,

Patrick