Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD mini dmp what does this mean? Thanks!

08 Jun 2010   #1

windows 7 pro 64 bit
 
 
BSOD mini dmp what does this mean? Thanks!

So basically I got the BSOD while doing lots of things on my PC. I have now managed to finally see what's in the dmp but I am unsure of what it means. Anyway most of it points to the memory I guess but I was wondering why the !ataport bit was in there - meaning another error? I am slightly confused as well as my system memory is underclocked! I took my 1066 RAM and brought it down to 800 mhz so that I could have it at 1:1 (400 x8) FSB on my overclocked CPU which is at 3.2 Ghz (qx6700). But I did not lower the stock voltage of 2.1v on the RAM (not sure if this is a problem). The other setting are at stock: 5-6-6-18. Now I have run the sfc/scannow in CMD which says system 32 in the path for some reason :S (not sure if I need to change that and check the system 64 bit path?). Anyway it passed that I need to do a long memtest but my ram did pass this not long ago so I am guessing this will not turn up anything but I will do it anyway. Anyway tell me what you think for now - I have my suspicions but I will see what you guys think first. Here's the DMP Thanks!:


Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\060510-36707-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c64000 PsLoadedModuleList = 0xfffff800`02ea1e50
Debug session time: Sat Jun 5 21:04:58.057 2010 (UTC + 1:00)
System Uptime: 0 days 8:01:57.914
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88000c784ac, fffff880031a15a8, fffff880031a0e10}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Followup: memory_corruption
---------

2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88000c784ac, The address that the exception occurred at
Arg3: fffff880031a15a8, Exception Record Address
Arg4: fffff880031a0e10, Context Record Address

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


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

FAULTING_IP:
ataport!IdePortDispatchPnp+0
fffff880`00c784ac 0000 add byte ptr [rax],al

EXCEPTION_RECORD: fffff880031a15a8 -- (.exr 0xfffff880031a15a8)
ExceptionAddress: fffff88000c784ac (ataport!IdePortDispatchPnp)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 000000000000001b
Attempt to write to address 000000000000001b

CONTEXT: fffff880031a0e10 -- (.cxr 0xfffff880031a0e10)
rax=000000000000001b rbx=fffffa8007277e10 rcx=fffffa8007b05050
rdx=fffffa8007277e10 rsi=fffffa8007b05050 rdi=fffffa8007ae7cb0
rip=fffff88000c784ac rsp=fffff880031a17e8 rbp=fffffa800a1ad800
r8=fffffa800775bc80 r9=000000000000001b r10=0000000000000000
r11=fffffa8007277fb8 r12=fffff80002dd3c80 r13=fffff880031a1880
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
ataport!IdePortDispatchPnp:
fffff880`00c784ac 0000 add byte ptr [rax],al ds:002b:00000000`0000001b=??
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

CURRENT_IRQL: 0

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

EXCEPTION_PARAMETER1: 0000000000000001

EXCEPTION_PARAMETER2: 000000000000001b

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f0c0e0
000000000000001b

FOLLOWUP_IP:
ataport!IdePortDispatchPnp+0
fffff880`00c784ac 0000 add byte ptr [rax],al

BUGCHECK_STR: 0x7E

DEFAULT_BUCKET_ID: CODE_CORRUPTION

LOCK_ADDRESS: fffff80002ed8400 -- (!locks fffff80002ed8400)

Resource @ nt!PiEngineLock (0xfffff80002ed8400) Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE:
Lock address : 0xfffff80002ed8400
Thread Count : 0
Thread address: 0x0000000000000000
Thread wait : 0x0

LAST_CONTROL_TRANSFER: from fffff8000309370e to fffff88000c784ac

STACK_TEXT:
fffff880`031a17e8 fffff800`0309370e : 00000000`00000000 00000000`00000000 fffffa80`0a1ad800 fffff880`02f64180 : ataport!IdePortDispatchPnp
fffff880`031a17f0 fffff800`03093a7a : 00000000`00000000 fffffa80`0a1ad800 fffff800`02dd3c80 00000000`00000000 : nt!PnpAsynchronousCall+0xce
fffff880`031a1830 fffff800`03095d67 : fffff800`02ed81c0 fffffa80`07aeb990 00000000`00000002 00000000`00000588 : nt!PnpQueryDeviceRelations+0xfa
fffff880`031a18f0 fffff800`030c195c : fffffa80`07aeb990 fffffa80`07ae001f fffffa80`07aeb990 00000000`00000002 : nt!PipEnumerateDevice+0x117
fffff880`031a1950 fffff800`030c1f68 : fffff800`02ed5d80 00000000`00000000 00000000`00000001 fffff800`02f42698 : nt!PipProcessDevNodeTree+0x21c
fffff880`031a1bc0 fffff800`02dd62f7 : 00000001`00000003 00000000`00000000 00000000`00000001 00000000`00000000 : nt!PiProcessReenumeration+0x98
fffff880`031a1c10 fffff800`02ce1861 : fffff800`02dd5fd0 fffff800`02fd1801 fffffa80`06d1cb00 00000000`00000000 : nt!PnpDeviceActionWorker+0x327
fffff880`031a1cb0 fffff800`02f79a86 : 36f3b363`331b3133 fffffa80`06d1cb60 00000000`00000080 fffffa80`06d08040 : nt!ExpWorkerThread+0x111
fffff880`031a1d40 fffff800`02cb2b06 : fffff880`02f64180 fffffa80`06d1cb60 fffff880`02f6efc0 3ae1bc22`33fbb975 : nt!PspSystemThreadStartup+0x5a
fffff880`031a1d80 00000000`00000000 : fffff880`031a2000 fffff880`0319c000 fffff880`031a1090 00000000`00000000 : nt!KxStartSystemThread+0x16


CHKIMG_EXTENSION: !chkimg -lo 50 -d !ataport
fffff88000c78000-fffff88000c78012 19 bytes - ataport!DeviceBuildCompatibleId+64
[ 8d 4c 24 30 ff 15 8e 82:00 00 26 00 00 00 00 00 ]
fffff88000c78014-fffff88000c7801b 8 bytes - ataport!DeviceBuildCompatibleId+78 (+0x14)
[ 02 8d 50 04 b9 01 00 00:00 00 00 00 11 f0 4d 0b ]
fffff88000c7801d-fffff88000c780bb 159 bytes - ataport!DeviceBuildCompatibleId+81 (+0x09)
[ 41 b8 49 64 65 50 66 89:00 00 00 00 00 26 00 00 ]
fffff88000c780bf-fffff88000c780cd 15 bytes - ataport!DeviceBuildHardwareId+1f (+0xa2)
[ 48 8b 05 3a a0 ff ff 48:00 00 00 26 00 00 00 00 ]
fffff88000c780d1-fffff88000c780d6 6 bytes - ataport!DeviceBuildHardwareId+31 (+0x12)
[ 48 8b e9 be 82 02:00 26 00 00 00 00 ]
fffff88000c780d8-fffff88000c780db 4 bytes - ataport!DeviceBuildHardwareId+38 (+0x07)
[ 00 bf 01 00:11 b0 4e 0b ]
fffff88000c780de-fffff88000c780fb 30 bytes - ataport!DeviceBuildHardwareId+3e (+0x06)
[ 48 8b d6 8b cf 41 b8 49:00 00 00 00 26 00 00 00 ]
fffff88000c780fe-fffff88000c7810e 17 bytes - ataport!DeviceBuildHardwareId+5e (+0x20)
[ 4c 8b c6 33 d2 48 8b c8:00 00 00 00 26 00 00 00 ]
fffff88000c78111-fffff88000c78136 38 bytes - ataport!DeviceBuildHardwareId+71 (+0x13)
[ 4c 8d 2d 78 85 ff ff 80:00 26 00 00 00 00 00 11 ]
fffff88000c78138-fffff88000c7813b 4 bytes - ataport!DeviceBuildHardwareId+98 (+0x27)
[ 00 b9 00 01:11 10 4f 0b ]
fffff88000c7813e-fffff88000c7817e 65 bytes - ataport!DeviceBuildHardwareId+9e (+0x06)
[ 66 85 48 0c 74 09 4c 8d:00 00 00 00 26 00 00 00 ]
fffff88000c78182-fffff88000c78186 5 bytes - ataport!DeviceBuildHardwareId+e2 (+0x44)
[ 2b c7 0f 84 9e:26 00 00 00 00 ]
fffff88000c78188-fffff88000c781cd 70 bytes - ataport!DeviceBuildHardwareId+e8 (+0x06)
[ 00 00 2b c7 74 62 2b c7:11 70 4f 0b 00 00 00 00 ]
fffff88000c781d1-fffff88000c781e2 18 bytes - ataport!DeviceBuildHardwareId+131 (+0x49)
[ 49 3b d7 75 03 48 2b cf:00 26 00 00 00 00 00 11 ]
fffff88000c781e6-fffff88000c781ec 7 bytes - ataport!DeviceBuildHardwareId+146 (+0x15)
[ 48 8d 4c 24 40 e9 98:00 00 11 c0 50 0b 00 ]
fffff88000c781f0-fffff88000c78216 39 bytes - ataport!DeviceBuildHardwareId+150 (+0x0a)
[ 48 8b d1 4c 8d 05 56 67:00 00 26 00 00 00 00 00 ]
fffff88000c78218-fffff88000c7821f 8 bytes - ataport!DeviceBuildHardwareId+178 (+0x28)
[ 00 41 b1 5f f2 ae b8 28:11 f0 50 0b 00 00 00 00 ]
fffff88000c78222-fffff88000c78224 3 bytes - ataport!DeviceBuildHardwareId+182 (+0x0a)
[ 00 e9 88:26 00 00 ]
fffff88000c78228-fffff88000c7822f 8 bytes - ataport!DeviceBuildHardwareId+188 (+0x06)
[ 48 8b d1 4c 8d 05 ee 66:11 00 51 0b 00 00 00 00 ]
fffff88000c78232-fffff88000c78245 20 bytes - ataport!DeviceBuildHardwareId+192 (+0x0a)
[ 48 8d 4c 24 40 e8 cc b0:26 00 00 00 00 00 11 10 ]
fffff88000c78248-fffff88000c7825b 20 bytes - ataport!DeviceBuildHardwareId+1a8 (+0x16)
[ 48 8d 4c 24 40 4d 8b ce:11 20 51 0b 00 00 00 00 ]
fffff88000c7825e-fffff88000c7828c 47 bytes - ataport!DeviceBuildHardwareId+1be (+0x16)
[ 48 83 c9 ff 33 c0 48 8d:00 00 00 00 26 00 00 00 ]
fffff88000c7828f-fffff88000c782a6 24 bytes - ataport!DeviceBuildHardwareId+1ef (+0x31)
[ 41 b1 5f e8 d1 ae fe ff:00 00 00 26 00 00 00 00 ]
fffff88000c782a8-fffff88000c782ac 5 bytes - ataport!DeviceBuildHardwareId+208 (+0x19)
[ 00 f2 ae b8 08:11 80 50 0b 00 ]
fffff88000c782b0-fffff88000c782b2 3 bytes - ataport!DeviceBuildHardwareId+210 (+0x08)
[ bf 01 00:00 00 26 ]
fffff88000c782b5-fffff88000c782f8 68 bytes - ataport!DeviceBuildHardwareId+215 (+0x05)
[ 48 f7 d1 48 2b cf 44 8d:00 00 00 11 70 50 0b 00 ]
fffff88000c782fa-fffff88000c78364 107 bytes - ataport!DeviceBuildHardwareId+25a (+0x45)
[ ff 15 98 7f ff ff eb 0b:50 0b 00 00 00 00 00 00 ]
fffff88000c78368-fffff88000c78395 46 bytes - ataport!DeviceBuildHardwareId+2c8 (+0x6e)
[ 44 8d 41 e8 41 83 fc 05:11 c0 4f 0b 00 00 00 00 ]
fffff88000c78398-fffff88000c783a5 14 bytes - ataport!DeviceBuildHardwareId+2f8 (+0x30)
[ 00 48 33 cc e8 ff 6b ff:11 80 51 0b 00 00 00 00 ]
fffff88000c783a8-fffff88000c783ce 39 bytes - ataport!DeviceBuildHardwareId+308 (+0x10)
[ 00 49 8b 5b 38 49 8b 6b:11 90 51 0b 00 00 00 00 ]
fffff88000c783d1-fffff88000c783d5 5 bytes - ataport!DllInitialize+9 (+0x29)
[ 48 83 a4 24 90:00 26 00 00 00 ]
fffff88000c783d8-fffff88000c783de 7 bytes - ataport!DllInitialize+10 (+0x07)
[ 00 00 48 8d 15 7f 65:11 c0 51 0b 00 00 00 ]
fffff88000c783e1-fffff88000c783f0 16 bytes - ataport!DllInitialize+19 (+0x09)
[ 48 8d 4c 24 30 ff 15 0c:00 26 00 00 00 00 00 11 ]
fffff88000c783f2-fffff88000c783f6 5 bytes - ataport!DllInitialize+2a (+0x11)
[ 48 83 64 24 60:26 00 00 00 00 ]
fffff88000c783f8-fffff88000c783fc 5 bytes - ataport!DllInitialize+30 (+0x06)
[ 48 83 64 24 68:11 e0 51 0b 00 ]
fffff88000c783fe-fffff88000c7840c 15 bytes - ataport!DllInitialize+36 (+0x06)
[ 48 8d 44 24 30 4c 8d 44:00 00 00 00 26 00 00 00 ]
fffff88000c78410-fffff88000c78413 4 bytes - ataport!DllInitialize+48 (+0x12)
[ ba 0f 00 0f:00 00 26 00 ]
fffff88000c78415-fffff88000c7841e 10 bytes - ataport!DllInitialize+4d (+0x05)
[ 48 89 44 24 50 c7 44 24:00 00 00 11 00 52 0b 00 ]
fffff88000c78422-fffff88000c7842b 10 bytes - ataport!DllInitialize+5a (+0x0d)
[ c7 44 24 58 50 02 00 00:26 00 00 00 00 00 11 10 ]
fffff88000c7842d-fffff88000c78440 20 bytes - ataport!DllInitialize+65 (+0x0b)
[ 80 ff ff 85 c0 78 3a 48:00 00 00 00 00 26 00 00 ]
fffff88000c78442-fffff88000c78446 5 bytes - ataport!DllInitialize+7a (+0x15)
[ 48 8d 84 24 90:26 00 00 00 00 ]
fffff88000c78448-fffff88000c78452 11 bytes - ataport!DllInitialize+80 (+0x06)
[ 00 00 45 33 c9 45 33 c0:11 30 52 0b 00 00 00 00 ]
fffff88000c78455-fffff88000c78464 16 bytes - ataport!DllInitialize+8d (+0x0d)
[ 48 89 44 24 20 ff 15 d8:00 00 00 11 40 52 0b 00 ]
fffff88000c78468-fffff88000c784b3 76 bytes - ataport!DllInitialize+a0 (+0x13)
[ ff 15 ba 7d ff ff e8 ed:11 50 52 0b 00 00 00 00 ]
fffff88000c784b7-fffff88000c7859d 231 bytes - ataport!IdePortDispatchPnp+b (+0x4f)
[ 4c 8b 49 40 80 78 01 19:00 11 a0 52 0b 00 00 00 ]
fffff88000c785a0-fffff88000c78624 133 bytes - ataport!IdePortPopulateDispatchTables+c (+0xe9)
[ 4c 8d 0d d1 f3 ff ff ba:00 00 26 00 00 00 00 00 ]
fffff88000c78627-fffff88000c78640 26 bytes - ataport!IdePortPopulateDispatchTables+93 (+0x87)
[ 48 89 05 f2 9e ff ff 48:00 11 a0 54 0b 00 00 00 ]
fffff88000c78642-fffff88000c7865c 27 bytes - ataport!IdePortPopulateDispatchTables+ae (+0x1b)
[ 00 48 8d 0d 4a a1 fe ff:26 00 00 00 00 00 11 c0 ]
fffff88000c7865f-fffff88000c78686 40 bytes - ataport!IdePortPopulateDispatchTables+cb (+0x1d)
[ 48 89 0d ea 9c ff ff 48:00 00 00 26 00 00 00 00 ]
fffff88000c78688-fffff88000c786de 87 bytes - ataport!IdePortPopulateDispatchTables+f4 (+0x29)
[ 00 48 89 0d c8 9c ff ff:11 00 54 0b 00 00 00 00 ]
WARNING: !chkimg output was truncated to 50 lines. Invoke !chkimg without '-lo [num_lines]' to view entire output.
3784 errors : !ataport (fffff88000c78000-fffff88000c78fff)

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: LARGE_4096

STACK_COMMAND: .cxr 0xfffff880031a0e10 ; kb

FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE_4096

BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE_4096

Followup: memory_corruption
---------

2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88000c784ac, The address that the exception occurred at
Arg3: fffff880031a15a8, Exception Record Address
Arg4: fffff880031a0e10, Context Record Address

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


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

FAULTING_IP:
ataport!IdePortDispatchPnp+0
fffff880`00c784ac 0000 add byte ptr [rax],al

EXCEPTION_RECORD: fffff880031a15a8 -- (.exr 0xfffff880031a15a8)
ExceptionAddress: fffff88000c784ac (ataport!IdePortDispatchPnp)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 000000000000001b
Attempt to write to address 000000000000001b

CONTEXT: fffff880031a0e10 -- (.cxr 0xfffff880031a0e10)
rax=000000000000001b rbx=fffffa8007277e10 rcx=fffffa8007b05050
rdx=fffffa8007277e10 rsi=fffffa8007b05050 rdi=fffffa8007ae7cb0
rip=fffff88000c784ac rsp=fffff880031a17e8 rbp=fffffa800a1ad800
r8=fffffa800775bc80 r9=000000000000001b r10=0000000000000000
r11=fffffa8007277fb8 r12=fffff80002dd3c80 r13=fffff880031a1880
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
ataport!IdePortDispatchPnp:
fffff880`00c784ac 0000 add byte ptr [rax],al ds:002b:00000000`0000001b=??
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

CURRENT_IRQL: 0

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

EXCEPTION_PARAMETER1: 0000000000000001

EXCEPTION_PARAMETER2: 000000000000001b

WRITE_ADDRESS: 000000000000001b

FOLLOWUP_IP:
ataport!IdePortDispatchPnp+0
fffff880`00c784ac 0000 add byte ptr [rax],al

BUGCHECK_STR: 0x7E

DEFAULT_BUCKET_ID: CODE_CORRUPTION

LOCK_ADDRESS: fffff80002ed8400 -- (!locks fffff80002ed8400)

Resource @ nt!PiEngineLock (0xfffff80002ed8400) Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE:
Lock address : 0xfffff80002ed8400
Thread Count : 0
Thread address: 0x0000000000000000
Thread wait : 0x0

LAST_CONTROL_TRANSFER: from fffff8000309370e to fffff88000c784ac

STACK_TEXT:
fffff880`031a17e8 fffff800`0309370e : 00000000`00000000 00000000`00000000 fffffa80`0a1ad800 fffff880`02f64180 : ataport!IdePortDispatchPnp
fffff880`031a17f0 fffff800`03093a7a : 00000000`00000000 fffffa80`0a1ad800 fffff800`02dd3c80 00000000`00000000 : nt!PnpAsynchronousCall+0xce
fffff880`031a1830 fffff800`03095d67 : fffff800`02ed81c0 fffffa80`07aeb990 00000000`00000002 00000000`00000588 : nt!PnpQueryDeviceRelations+0xfa
fffff880`031a18f0 fffff800`030c195c : fffffa80`07aeb990 fffffa80`07ae001f fffffa80`07aeb990 00000000`00000002 : nt!PipEnumerateDevice+0x117
fffff880`031a1950 fffff800`030c1f68 : fffff800`02ed5d80 00000000`00000000 00000000`00000001 fffff800`02f42698 : nt!PipProcessDevNodeTree+0x21c
fffff880`031a1bc0 fffff800`02dd62f7 : 00000001`00000003 00000000`00000000 00000000`00000001 00000000`00000000 : nt!PiProcessReenumeration+0x98
fffff880`031a1c10 fffff800`02ce1861 : fffff800`02dd5fd0 fffff800`02fd1801 fffffa80`06d1cb00 00000000`00000000 : nt!PnpDeviceActionWorker+0x327
fffff880`031a1cb0 fffff800`02f79a86 : 36f3b363`331b3133 fffffa80`06d1cb60 00000000`00000080 fffffa80`06d08040 : nt!ExpWorkerThread+0x111
fffff880`031a1d40 fffff800`02cb2b06 : fffff880`02f64180 fffffa80`06d1cb60 fffff880`02f6efc0 3ae1bc22`33fbb975 : nt!PspSystemThreadStartup+0x5a
fffff880`031a1d80 00000000`00000000 : fffff880`031a2000 fffff880`0319c000 fffff880`031a1090 00000000`00000000 : nt!KxStartSystemThread+0x16


CHKIMG_EXTENSION: !chkimg -lo 50 -d !ataport
fffff88000c78000-fffff88000c78012 19 bytes - ataport!DeviceBuildCompatibleId+64
[ 8d 4c 24 30 ff 15 8e 82:00 00 26 00 00 00 00 00 ]
fffff88000c78014-fffff88000c7801b 8 bytes - ataport!DeviceBuildCompatibleId+78 (+0x14)
[ 02 8d 50 04 b9 01 00 00:00 00 00 00 11 f0 4d 0b ]
fffff88000c7801d-fffff88000c780bb 159 bytes - ataport!DeviceBuildCompatibleId+81 (+0x09)
[ 41 b8 49 64 65 50 66 89:00 00 00 00 00 26 00 00 ]
fffff88000c780bf-fffff88000c780cd 15 bytes - ataport!DeviceBuildHardwareId+1f (+0xa2)
[ 48 8b 05 3a a0 ff ff 48:00 00 00 26 00 00 00 00 ]
fffff88000c780d1-fffff88000c780d6 6 bytes - ataport!DeviceBuildHardwareId+31 (+0x12)
[ 48 8b e9 be 82 02:00 26 00 00 00 00 ]
fffff88000c780d8-fffff88000c780db 4 bytes - ataport!DeviceBuildHardwareId+38 (+0x07)
[ 00 bf 01 00:11 b0 4e 0b ]
fffff88000c780de-fffff88000c780fb 30 bytes - ataport!DeviceBuildHardwareId+3e (+0x06)
[ 48 8b d6 8b cf 41 b8 49:00 00 00 00 26 00 00 00 ]
fffff88000c780fe-fffff88000c7810e 17 bytes - ataport!DeviceBuildHardwareId+5e (+0x20)
[ 4c 8b c6 33 d2 48 8b c8:00 00 00 00 26 00 00 00 ]
fffff88000c78111-fffff88000c78136 38 bytes - ataport!DeviceBuildHardwareId+71 (+0x13)
[ 4c 8d 2d 78 85 ff ff 80:00 26 00 00 00 00 00 11 ]
fffff88000c78138-fffff88000c7813b 4 bytes - ataport!DeviceBuildHardwareId+98 (+0x27)
[ 00 b9 00 01:11 10 4f 0b ]
fffff88000c7813e-fffff88000c7817e 65 bytes - ataport!DeviceBuildHardwareId+9e (+0x06)
[ 66 85 48 0c 74 09 4c 8d:00 00 00 00 26 00 00 00 ]
fffff88000c78182-fffff88000c78186 5 bytes - ataport!DeviceBuildHardwareId+e2 (+0x44)
[ 2b c7 0f 84 9e:26 00 00 00 00 ]
fffff88000c78188-fffff88000c781cd 70 bytes - ataport!DeviceBuildHardwareId+e8 (+0x06)
[ 00 00 2b c7 74 62 2b c7:11 70 4f 0b 00 00 00 00 ]
fffff88000c781d1-fffff88000c781e2 18 bytes - ataport!DeviceBuildHardwareId+131 (+0x49)
[ 49 3b d7 75 03 48 2b cf:00 26 00 00 00 00 00 11 ]
fffff88000c781e6-fffff88000c781ec 7 bytes - ataport!DeviceBuildHardwareId+146 (+0x15)
[ 48 8d 4c 24 40 e9 98:00 00 11 c0 50 0b 00 ]
fffff88000c781f0-fffff88000c78216 39 bytes - ataport!DeviceBuildHardwareId+150 (+0x0a)
[ 48 8b d1 4c 8d 05 56 67:00 00 26 00 00 00 00 00 ]
fffff88000c78218-fffff88000c7821f 8 bytes - ataport!DeviceBuildHardwareId+178 (+0x28)
[ 00 41 b1 5f f2 ae b8 28:11 f0 50 0b 00 00 00 00 ]
fffff88000c78222-fffff88000c78224 3 bytes - ataport!DeviceBuildHardwareId+182 (+0x0a)
[ 00 e9 88:26 00 00 ]
fffff88000c78228-fffff88000c7822f 8 bytes - ataport!DeviceBuildHardwareId+188 (+0x06)
[ 48 8b d1 4c 8d 05 ee 66:11 00 51 0b 00 00 00 00 ]
fffff88000c78232-fffff88000c78245 20 bytes - ataport!DeviceBuildHardwareId+192 (+0x0a)
[ 48 8d 4c 24 40 e8 cc b0:26 00 00 00 00 00 11 10 ]
fffff88000c78248-fffff88000c7825b 20 bytes - ataport!DeviceBuildHardwareId+1a8 (+0x16)
[ 48 8d 4c 24 40 4d 8b ce:11 20 51 0b 00 00 00 00 ]
fffff88000c7825e-fffff88000c7828c 47 bytes - ataport!DeviceBuildHardwareId+1be (+0x16)
[ 48 83 c9 ff 33 c0 48 8d:00 00 00 00 26 00 00 00 ]
fffff88000c7828f-fffff88000c782a6 24 bytes - ataport!DeviceBuildHardwareId+1ef (+0x31)
[ 41 b1 5f e8 d1 ae fe ff:00 00 00 26 00 00 00 00 ]
fffff88000c782a8-fffff88000c782ac 5 bytes - ataport!DeviceBuildHardwareId+208 (+0x19)
[ 00 f2 ae b8 08:11 80 50 0b 00 ]
fffff88000c782b0-fffff88000c782b2 3 bytes - ataport!DeviceBuildHardwareId+210 (+0x08)
[ bf 01 00:00 00 26 ]
fffff88000c782b5-fffff88000c782f8 68 bytes - ataport!DeviceBuildHardwareId+215 (+0x05)
[ 48 f7 d1 48 2b cf 44 8d:00 00 00 11 70 50 0b 00 ]
fffff88000c782fa-fffff88000c78364 107 bytes - ataport!DeviceBuildHardwareId+25a (+0x45)
[ ff 15 98 7f ff ff eb 0b:50 0b 00 00 00 00 00 00 ]
fffff88000c78368-fffff88000c78395 46 bytes - ataport!DeviceBuildHardwareId+2c8 (+0x6e)
[ 44 8d 41 e8 41 83 fc 05:11 c0 4f 0b 00 00 00 00 ]
fffff88000c78398-fffff88000c783a5 14 bytes - ataport!DeviceBuildHardwareId+2f8 (+0x30)
[ 00 48 33 cc e8 ff 6b ff:11 80 51 0b 00 00 00 00 ]
fffff88000c783a8-fffff88000c783ce 39 bytes - ataport!DeviceBuildHardwareId+308 (+0x10)
[ 00 49 8b 5b 38 49 8b 6b:11 90 51 0b 00 00 00 00 ]
fffff88000c783d1-fffff88000c783d5 5 bytes - ataport!DllInitialize+9 (+0x29)
[ 48 83 a4 24 90:00 26 00 00 00 ]
fffff88000c783d8-fffff88000c783de 7 bytes - ataport!DllInitialize+10 (+0x07)
[ 00 00 48 8d 15 7f 65:11 c0 51 0b 00 00 00 ]
fffff88000c783e1-fffff88000c783f0 16 bytes - ataport!DllInitialize+19 (+0x09)
[ 48 8d 4c 24 30 ff 15 0c:00 26 00 00 00 00 00 11 ]
fffff88000c783f2-fffff88000c783f6 5 bytes - ataport!DllInitialize+2a (+0x11)
[ 48 83 64 24 60:26 00 00 00 00 ]
fffff88000c783f8-fffff88000c783fc 5 bytes - ataport!DllInitialize+30 (+0x06)
[ 48 83 64 24 68:11 e0 51 0b 00 ]
fffff88000c783fe-fffff88000c7840c 15 bytes - ataport!DllInitialize+36 (+0x06)
[ 48 8d 44 24 30 4c 8d 44:00 00 00 00 26 00 00 00 ]
fffff88000c78410-fffff88000c78413 4 bytes - ataport!DllInitialize+48 (+0x12)
[ ba 0f 00 0f:00 00 26 00 ]
fffff88000c78415-fffff88000c7841e 10 bytes - ataport!DllInitialize+4d (+0x05)
[ 48 89 44 24 50 c7 44 24:00 00 00 11 00 52 0b 00 ]
fffff88000c78422-fffff88000c7842b 10 bytes - ataport!DllInitialize+5a (+0x0d)
[ c7 44 24 58 50 02 00 00:26 00 00 00 00 00 11 10 ]
fffff88000c7842d-fffff88000c78440 20 bytes - ataport!DllInitialize+65 (+0x0b)
[ 80 ff ff 85 c0 78 3a 48:00 00 00 00 00 26 00 00 ]
fffff88000c78442-fffff88000c78446 5 bytes - ataport!DllInitialize+7a (+0x15)
[ 48 8d 84 24 90:26 00 00 00 00 ]
fffff88000c78448-fffff88000c78452 11 bytes - ataport!DllInitialize+80 (+0x06)
[ 00 00 45 33 c9 45 33 c0:11 30 52 0b 00 00 00 00 ]
fffff88000c78455-fffff88000c78464 16 bytes - ataport!DllInitialize+8d (+0x0d)
[ 48 89 44 24 20 ff 15 d8:00 00 00 11 40 52 0b 00 ]
fffff88000c78468-fffff88000c784b3 76 bytes - ataport!DllInitialize+a0 (+0x13)
[ ff 15 ba 7d ff ff e8 ed:11 50 52 0b 00 00 00 00 ]
fffff88000c784b7-fffff88000c7859d 231 bytes - ataport!IdePortDispatchPnp+b (+0x4f)
[ 4c 8b 49 40 80 78 01 19:00 11 a0 52 0b 00 00 00 ]
fffff88000c785a0-fffff88000c78624 133 bytes - ataport!IdePortPopulateDispatchTables+c (+0xe9)
[ 4c 8d 0d d1 f3 ff ff ba:00 00 26 00 00 00 00 00 ]
fffff88000c78627-fffff88000c78640 26 bytes - ataport!IdePortPopulateDispatchTables+93 (+0x87)
[ 48 89 05 f2 9e ff ff 48:00 11 a0 54 0b 00 00 00 ]
fffff88000c78642-fffff88000c7865c 27 bytes - ataport!IdePortPopulateDispatchTables+ae (+0x1b)
[ 00 48 8d 0d 4a a1 fe ff:26 00 00 00 00 00 11 c0 ]
fffff88000c7865f-fffff88000c78686 40 bytes - ataport!IdePortPopulateDispatchTables+cb (+0x1d)
[ 48 89 0d ea 9c ff ff 48:00 00 00 26 00 00 00 00 ]
fffff88000c78688-fffff88000c786de 87 bytes - ataport!IdePortPopulateDispatchTables+f4 (+0x29)
[ 00 48 89 0d c8 9c ff ff:11 00 54 0b 00 00 00 00 ]
WARNING: !chkimg output was truncated to 50 lines. Invoke !chkimg without '-lo [num_lines]' to view entire output.
3784 errors : !ataport (fffff88000c78000-fffff88000c78fff)

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: LARGE_4096

STACK_COMMAND: .cxr 0xfffff880031a0e10 ; kb

FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE_4096

BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE_4096

Followup: memory_corruption
---------

2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88000c784ac, The address that the exception occurred at
Arg3: fffff880031a15a8, Exception Record Address
Arg4: fffff880031a0e10, Context Record Address

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


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

FAULTING_IP:
ataport!IdePortDispatchPnp+0
fffff880`00c784ac 0000 add byte ptr [rax],al

EXCEPTION_RECORD: fffff880031a15a8 -- (.exr 0xfffff880031a15a8)
ExceptionAddress: fffff88000c784ac (ataport!IdePortDispatchPnp)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 000000000000001b
Attempt to write to address 000000000000001b

CONTEXT: fffff880031a0e10 -- (.cxr 0xfffff880031a0e10)
rax=000000000000001b rbx=fffffa8007277e10 rcx=fffffa8007b05050
rdx=fffffa8007277e10 rsi=fffffa8007b05050 rdi=fffffa8007ae7cb0
rip=fffff88000c784ac rsp=fffff880031a17e8 rbp=fffffa800a1ad800
r8=fffffa800775bc80 r9=000000000000001b r10=0000000000000000
r11=fffffa8007277fb8 r12=fffff80002dd3c80 r13=fffff880031a1880
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
ataport!IdePortDispatchPnp:
fffff880`00c784ac 0000 add byte ptr [rax],al ds:002b:00000000`0000001b=??
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

CURRENT_IRQL: 0

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

EXCEPTION_PARAMETER1: 0000000000000001

EXCEPTION_PARAMETER2: 000000000000001b

WRITE_ADDRESS: 000000000000001b

FOLLOWUP_IP:
ataport!IdePortDispatchPnp+0
fffff880`00c784ac 0000 add byte ptr [rax],al

BUGCHECK_STR: 0x7E

DEFAULT_BUCKET_ID: CODE_CORRUPTION

LOCK_ADDRESS: fffff80002ed8400 -- (!locks fffff80002ed8400)

Resource @ nt!PiEngineLock (0xfffff80002ed8400) Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE:
Lock address : 0xfffff80002ed8400
Thread Count : 0
Thread address: 0x0000000000000000
Thread wait : 0x0

LAST_CONTROL_TRANSFER: from fffff8000309370e to fffff88000c784ac

STACK_TEXT:
fffff880`031a17e8 fffff800`0309370e : 00000000`00000000 00000000`00000000 fffffa80`0a1ad800 fffff880`02f64180 : ataport!IdePortDispatchPnp
fffff880`031a17f0 fffff800`03093a7a : 00000000`00000000 fffffa80`0a1ad800 fffff800`02dd3c80 00000000`00000000 : nt!PnpAsynchronousCall+0xce
fffff880`031a1830 fffff800`03095d67 : fffff800`02ed81c0 fffffa80`07aeb990 00000000`00000002 00000000`00000588 : nt!PnpQueryDeviceRelations+0xfa
fffff880`031a18f0 fffff800`030c195c : fffffa80`07aeb990 fffffa80`07ae001f fffffa80`07aeb990 00000000`00000002 : nt!PipEnumerateDevice+0x117
fffff880`031a1950 fffff800`030c1f68 : fffff800`02ed5d80 00000000`00000000 00000000`00000001 fffff800`02f42698 : nt!PipProcessDevNodeTree+0x21c
fffff880`031a1bc0 fffff800`02dd62f7 : 00000001`00000003 00000000`00000000 00000000`00000001 00000000`00000000 : nt!PiProcessReenumeration+0x98
fffff880`031a1c10 fffff800`02ce1861 : fffff800`02dd5fd0 fffff800`02fd1801 fffffa80`06d1cb00 00000000`00000000 : nt!PnpDeviceActionWorker+0x327
fffff880`031a1cb0 fffff800`02f79a86 : 36f3b363`331b3133 fffffa80`06d1cb60 00000000`00000080 fffffa80`06d08040 : nt!ExpWorkerThread+0x111
fffff880`031a1d40 fffff800`02cb2b06 : fffff880`02f64180 fffffa80`06d1cb60 fffff880`02f6efc0 3ae1bc22`33fbb975 : nt!PspSystemThreadStartup+0x5a
fffff880`031a1d80 00000000`00000000 : fffff880`031a2000 fffff880`0319c000 fffff880`031a1090 00000000`00000000 : nt!KxStartSystemThread+0x16


CHKIMG_EXTENSION: !chkimg -lo 50 -d !ataport
fffff88000c78000-fffff88000c78012 19 bytes - ataport!DeviceBuildCompatibleId+64
[ 8d 4c 24 30 ff 15 8e 82:00 00 26 00 00 00 00 00 ]
fffff88000c78014-fffff88000c7801b 8 bytes - ataport!DeviceBuildCompatibleId+78 (+0x14)
[ 02 8d 50 04 b9 01 00 00:00 00 00 00 11 f0 4d 0b ]
fffff88000c7801d-fffff88000c780bb 159 bytes - ataport!DeviceBuildCompatibleId+81 (+0x09)
[ 41 b8 49 64 65 50 66 89:00 00 00 00 00 26 00 00 ]
fffff88000c780bf-fffff88000c780cd 15 bytes - ataport!DeviceBuildHardwareId+1f (+0xa2)
[ 48 8b 05 3a a0 ff ff 48:00 00 00 26 00 00 00 00 ]
fffff88000c780d1-fffff88000c780d6 6 bytes - ataport!DeviceBuildHardwareId+31 (+0x12)
[ 48 8b e9 be 82 02:00 26 00 00 00 00 ]
fffff88000c780d8-fffff88000c780db 4 bytes - ataport!DeviceBuildHardwareId+38 (+0x07)
[ 00 bf 01 00:11 b0 4e 0b ]
fffff88000c780de-fffff88000c780fb 30 bytes - ataport!DeviceBuildHardwareId+3e (+0x06)
[ 48 8b d6 8b cf 41 b8 49:00 00 00 00 26 00 00 00 ]
fffff88000c780fe-fffff88000c7810e 17 bytes - ataport!DeviceBuildHardwareId+5e (+0x20)
[ 4c 8b c6 33 d2 48 8b c8:00 00 00 00 26 00 00 00 ]
fffff88000c78111-fffff88000c78136 38 bytes - ataport!DeviceBuildHardwareId+71 (+0x13)
[ 4c 8d 2d 78 85 ff ff 80:00 26 00 00 00 00 00 11 ]
fffff88000c78138-fffff88000c7813b 4 bytes - ataport!DeviceBuildHardwareId+98 (+0x27)
[ 00 b9 00 01:11 10 4f 0b ]
fffff88000c7813e-fffff88000c7817e 65 bytes - ataport!DeviceBuildHardwareId+9e (+0x06)
[ 66 85 48 0c 74 09 4c 8d:00 00 00 00 26 00 00 00 ]
fffff88000c78182-fffff88000c78186 5 bytes - ataport!DeviceBuildHardwareId+e2 (+0x44)
[ 2b c7 0f 84 9e:26 00 00 00 00 ]
fffff88000c78188-fffff88000c781cd 70 bytes - ataport!DeviceBuildHardwareId+e8 (+0x06)
[ 00 00 2b c7 74 62 2b c7:11 70 4f 0b 00 00 00 00 ]
fffff88000c781d1-fffff88000c781e2 18 bytes - ataport!DeviceBuildHardwareId+131 (+0x49)
[ 49 3b d7 75 03 48 2b cf:00 26 00 00 00 00 00 11 ]
fffff88000c781e6-fffff88000c781ec 7 bytes - ataport!DeviceBuildHardwareId+146 (+0x15)
[ 48 8d 4c 24 40 e9 98:00 00 11 c0 50 0b 00 ]
fffff88000c781f0-fffff88000c78216 39 bytes - ataport!DeviceBuildHardwareId+150 (+0x0a)
[ 48 8b d1 4c 8d 05 56 67:00 00 26 00 00 00 00 00 ]
fffff88000c78218-fffff88000c7821f 8 bytes - ataport!DeviceBuildHardwareId+178 (+0x28)
[ 00 41 b1 5f f2 ae b8 28:11 f0 50 0b 00 00 00 00 ]
fffff88000c78222-fffff88000c78224 3 bytes - ataport!DeviceBuildHardwareId+182 (+0x0a)
[ 00 e9 88:26 00 00 ]
fffff88000c78228-fffff88000c7822f 8 bytes - ataport!DeviceBuildHardwareId+188 (+0x06)
[ 48 8b d1 4c 8d 05 ee 66:11 00 51 0b 00 00 00 00 ]
fffff88000c78232-fffff88000c78245 20 bytes - ataport!DeviceBuildHardwareId+192 (+0x0a)
[ 48 8d 4c 24 40 e8 cc b0:26 00 00 00 00 00 11 10 ]
fffff88000c78248-fffff88000c7825b 20 bytes - ataport!DeviceBuildHardwareId+1a8 (+0x16)
[ 48 8d 4c 24 40 4d 8b ce:11 20 51 0b 00 00 00 00 ]
fffff88000c7825e-fffff88000c7828c 47 bytes - ataport!DeviceBuildHardwareId+1be (+0x16)
[ 48 83 c9 ff 33 c0 48 8d:00 00 00 00 26 00 00 00 ]
fffff88000c7828f-fffff88000c782a6 24 bytes - ataport!DeviceBuildHardwareId+1ef (+0x31)
[ 41 b1 5f e8 d1 ae fe ff:00 00 00 26 00 00 00 00 ]
fffff88000c782a8-fffff88000c782ac 5 bytes - ataport!DeviceBuildHardwareId+208 (+0x19)
[ 00 f2 ae b8 08:11 80 50 0b 00 ]
fffff88000c782b0-fffff88000c782b2 3 bytes - ataport!DeviceBuildHardwareId+210 (+0x08)
[ bf 01 00:00 00 26 ]
fffff88000c782b5-fffff88000c782f8 68 bytes - ataport!DeviceBuildHardwareId+215 (+0x05)
[ 48 f7 d1 48 2b cf 44 8d:00 00 00 11 70 50 0b 00 ]
fffff88000c782fa-fffff88000c78364 107 bytes - ataport!DeviceBuildHardwareId+25a (+0x45)
[ ff 15 98 7f ff ff eb 0b:50 0b 00 00 00 00 00 00 ]
fffff88000c78368-fffff88000c78395 46 bytes - ataport!DeviceBuildHardwareId+2c8 (+0x6e)
[ 44 8d 41 e8 41 83 fc 05:11 c0 4f 0b 00 00 00 00 ]
fffff88000c78398-fffff88000c783a5 14 bytes - ataport!DeviceBuildHardwareId+2f8 (+0x30)
[ 00 48 33 cc e8 ff 6b ff:11 80 51 0b 00 00 00 00 ]
fffff88000c783a8-fffff88000c783ce 39 bytes - ataport!DeviceBuildHardwareId+308 (+0x10)
[ 00 49 8b 5b 38 49 8b 6b:11 90 51 0b 00 00 00 00 ]
fffff88000c783d1-fffff88000c783d5 5 bytes - ataport!DllInitialize+9 (+0x29)
[ 48 83 a4 24 90:00 26 00 00 00 ]
fffff88000c783d8-fffff88000c783de 7 bytes - ataport!DllInitialize+10 (+0x07)
[ 00 00 48 8d 15 7f 65:11 c0 51 0b 00 00 00 ]
fffff88000c783e1-fffff88000c783f0 16 bytes - ataport!DllInitialize+19 (+0x09)
[ 48 8d 4c 24 30 ff 15 0c:00 26 00 00 00 00 00 11 ]
fffff88000c783f2-fffff88000c783f6 5 bytes - ataport!DllInitialize+2a (+0x11)
[ 48 83 64 24 60:26 00 00 00 00 ]
fffff88000c783f8-fffff88000c783fc 5 bytes - ataport!DllInitialize+30 (+0x06)
[ 48 83 64 24 68:11 e0 51 0b 00 ]
fffff88000c783fe-fffff88000c7840c 15 bytes - ataport!DllInitialize+36 (+0x06)
[ 48 8d 44 24 30 4c 8d 44:00 00 00 00 26 00 00 00 ]
fffff88000c78410-fffff88000c78413 4 bytes - ataport!DllInitialize+48 (+0x12)
[ ba 0f 00 0f:00 00 26 00 ]
fffff88000c78415-fffff88000c7841e 10 bytes - ataport!DllInitialize+4d (+0x05)
[ 48 89 44 24 50 c7 44 24:00 00 00 11 00 52 0b 00 ]
fffff88000c78422-fffff88000c7842b 10 bytes - ataport!DllInitialize+5a (+0x0d)
[ c7 44 24 58 50 02 00 00:26 00 00 00 00 00 11 10 ]
fffff88000c7842d-fffff88000c78440 20 bytes - ataport!DllInitialize+65 (+0x0b)
[ 80 ff ff 85 c0 78 3a 48:00 00 00 00 00 26 00 00 ]
fffff88000c78442-fffff88000c78446 5 bytes - ataport!DllInitialize+7a (+0x15)
[ 48 8d 84 24 90:26 00 00 00 00 ]
fffff88000c78448-fffff88000c78452 11 bytes - ataport!DllInitialize+80 (+0x06)
[ 00 00 45 33 c9 45 33 c0:11 30 52 0b 00 00 00 00 ]
fffff88000c78455-fffff88000c78464 16 bytes - ataport!DllInitialize+8d (+0x0d)
[ 48 89 44 24 20 ff 15 d8:00 00 00 11 40 52 0b 00 ]
fffff88000c78468-fffff88000c784b3 76 bytes - ataport!DllInitialize+a0 (+0x13)
[ ff 15 ba 7d ff ff e8 ed:11 50 52 0b 00 00 00 00 ]
fffff88000c784b7-fffff88000c7859d 231 bytes - ataport!IdePortDispatchPnp+b (+0x4f)
[ 4c 8b 49 40 80 78 01 19:00 11 a0 52 0b 00 00 00 ]
fffff88000c785a0-fffff88000c78624 133 bytes - ataport!IdePortPopulateDispatchTables+c (+0xe9)
[ 4c 8d 0d d1 f3 ff ff ba:00 00 26 00 00 00 00 00 ]
fffff88000c78627-fffff88000c78640 26 bytes - ataport!IdePortPopulateDispatchTables+93 (+0x87)
[ 48 89 05 f2 9e ff ff 48:00 11 a0 54 0b 00 00 00 ]
fffff88000c78642-fffff88000c7865c 27 bytes - ataport!IdePortPopulateDispatchTables+ae (+0x1b)
[ 00 48 8d 0d 4a a1 fe ff:26 00 00 00 00 00 11 c0 ]
fffff88000c7865f-fffff88000c78686 40 bytes - ataport!IdePortPopulateDispatchTables+cb (+0x1d)
[ 48 89 0d ea 9c ff ff 48:00 00 00 26 00 00 00 00 ]
fffff88000c78688-fffff88000c786de 87 bytes - ataport!IdePortPopulateDispatchTables+f4 (+0x29)
[ 00 48 89 0d c8 9c ff ff:11 00 54 0b 00 00 00 00 ]
WARNING: !chkimg output was truncated to 50 lines. Invoke !chkimg without '-lo [num_lines]' to view entire output.
3784 errors : !ataport (fffff88000c78000-fffff88000c78fff)

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MEMORY_CORRUPTOR: LARGE_4096

STACK_COMMAND: .cxr 0xfffff880031a0e10 ; kb

FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE_4096

BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE_4096

Followup: memory_corruption
---------

My System SpecsSystem Spec
.

08 Jun 2010   #2

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by Diamond View Post
So basically I got the BSOD while doing lots of things on my PC. I have now managed to finally see what's in the dmp but I am unsure of what it means. Anyway most of it points to the memory I guess but I was wondering why the !ataport bit was in there - meaning another error? I am slightly confused as well as my system memory is underclocked! I took my 1066 RAM and brought it down to 800 mhz so that I could have it at 1:1 (400 x8) FSB on my overclocked CPU which is at 3.2 Ghz (qx6700). But I did not lower the stock voltage of 2.1v on the RAM (not sure if this is a problem). The other setting are at stock: 5-6-6-18. Now I have run the sfc/scannow in CMD which says system 32 in the path for some reason :S (not sure if I need to change that and check the system 64 bit path?). Anyway it passed that I need to do a long memtest but my ram did pass this not long ago so I am guessing this will not turn up anything but I will do it anyway. Anyway tell me what you think for now - I have my suspicions but I will see what you guys think first. Here's the DMP Thanks!:

Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\060510-36707-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*Symbol information
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c64000 PsLoadedModuleList = 0xfffff800`02ea1e50
Debug session time: Sat Jun  5 21:04:58.057 2010 (UTC + 1:00)
System Uptime: 0 days 8:01:57.914
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88000c784ac, fffff880031a15a8, fffff880031a0e10}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

Followup: memory_corruption
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88000c784ac, The address that the exception occurred at
Arg3: fffff880031a15a8, Exception Record Address
Arg4: fffff880031a0e10, Context Record Address

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


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

FAULTING_IP: 
ataport!IdePortDispatchPnp+0
fffff880`00c784ac 0000            add     byte ptr [rax],al

EXCEPTION_RECORD:  fffff880031a15a8 -- (.exr 0xfffff880031a15a8)
ExceptionAddress: fffff88000c784ac (ataport!IdePortDispatchPnp)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 000000000000001b
Attempt to write to address 000000000000001b

CONTEXT:  fffff880031a0e10 -- (.cxr 0xfffff880031a0e10)
rax=000000000000001b rbx=fffffa8007277e10 rcx=fffffa8007b05050
rdx=fffffa8007277e10 rsi=fffffa8007b05050 rdi=fffffa8007ae7cb0
rip=fffff88000c784ac rsp=fffff880031a17e8 rbp=fffffa800a1ad800
 r8=fffffa800775bc80  r9=000000000000001b r10=0000000000000000
r11=fffffa8007277fb8 r12=fffff80002dd3c80 r13=fffff880031a1880
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
ataport!IdePortDispatchPnp:
fffff880`00c784ac 0000            add     byte ptr [rax],al ds:002b:00000000`0000001b=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

CURRENT_IRQL:  0

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

EXCEPTION_PARAMETER1:  0000000000000001

EXCEPTION_PARAMETER2:  000000000000001b

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f0c0e0
 000000000000001b 

FOLLOWUP_IP: 
ataport!IdePortDispatchPnp+0
fffff880`00c784ac 0000            add     byte ptr [rax],al

BUGCHECK_STR:  0x7E

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

LOCK_ADDRESS:  fffff80002ed8400 -- (!locks fffff80002ed8400)

Resource @ nt!PiEngineLock (0xfffff80002ed8400)    Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE: 
    Lock address  : 0xfffff80002ed8400
    Thread Count  : 0
    Thread address: 0x0000000000000000
    Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from fffff8000309370e to fffff88000c784ac

STACK_TEXT:  
fffff880`031a17e8 fffff800`0309370e : 00000000`00000000 00000000`00000000 fffffa80`0a1ad800 fffff880`02f64180 : ataport!IdePortDispatchPnp
fffff880`031a17f0 fffff800`03093a7a : 00000000`00000000 fffffa80`0a1ad800 fffff800`02dd3c80 00000000`00000000 : nt!PnpAsynchronousCall+0xce
fffff880`031a1830 fffff800`03095d67 : fffff800`02ed81c0 fffffa80`07aeb990 00000000`00000002 00000000`00000588 : nt!PnpQueryDeviceRelations+0xfa
fffff880`031a18f0 fffff800`030c195c : fffffa80`07aeb990 fffffa80`07ae001f fffffa80`07aeb990 00000000`00000002 : nt!PipEnumerateDevice+0x117
fffff880`031a1950 fffff800`030c1f68 : fffff800`02ed5d80 00000000`00000000 00000000`00000001 fffff800`02f42698 : nt!PipProcessDevNodeTree+0x21c
fffff880`031a1bc0 fffff800`02dd62f7 : 00000001`00000003 00000000`00000000 00000000`00000001 00000000`00000000 : nt!PiProcessReenumeration+0x98
fffff880`031a1c10 fffff800`02ce1861 : fffff800`02dd5fd0 fffff800`02fd1801 fffffa80`06d1cb00 00000000`00000000 : nt!PnpDeviceActionWorker+0x327
fffff880`031a1cb0 fffff800`02f79a86 : 36f3b363`331b3133 fffffa80`06d1cb60 00000000`00000080 fffffa80`06d08040 : nt!ExpWorkerThread+0x111
fffff880`031a1d40 fffff800`02cb2b06 : fffff880`02f64180 fffffa80`06d1cb60 fffff880`02f6efc0 3ae1bc22`33fbb975 : nt!PspSystemThreadStartup+0x5a
fffff880`031a1d80 00000000`00000000 : fffff880`031a2000 fffff880`0319c000 fffff880`031a1090 00000000`00000000 : nt!KxStartSystemThread+0x16


CHKIMG_EXTENSION: !chkimg -lo 50 -d !ataport
    fffff88000c78000-fffff88000c78012  19 bytes - ataport!DeviceBuildCompatibleId+64
    [ 8d 4c 24 30 ff 15 8e 82:00 00 26 00 00 00 00 00 ]
    fffff88000c78014-fffff88000c7801b  8 bytes - ataport!DeviceBuildCompatibleId+78 (+0x14)
    [ 02 8d 50 04 b9 01 00 00:00 00 00 00 11 f0 4d 0b ]
    fffff88000c7801d-fffff88000c780bb  159 bytes - ataport!DeviceBuildCompatibleId+81 (+0x09)
    [ 41 b8 49 64 65 50 66 89:00 00 00 00 00 26 00 00 ]
    fffff88000c780bf-fffff88000c780cd  15 bytes - ataport!DeviceBuildHardwareId+1f (+0xa2)
    [ 48 8b 05 3a a0 ff ff 48:00 00 00 26 00 00 00 00 ]
    fffff88000c780d1-fffff88000c780d6  6 bytes - ataport!DeviceBuildHardwareId+31 (+0x12)
    [ 48 8b e9 be 82 02:00 26 00 00 00 00 ]
    fffff88000c780d8-fffff88000c780db  4 bytes - ataport!DeviceBuildHardwareId+38 (+0x07)
    [ 00 bf 01 00:11 b0 4e 0b ]
    fffff88000c780de-fffff88000c780fb  30 bytes - ataport!DeviceBuildHardwareId+3e (+0x06)
    [ 48 8b d6 8b cf 41 b8 49:00 00 00 00 26 00 00 00 ]
    fffff88000c780fe-fffff88000c7810e  17 bytes - ataport!DeviceBuildHardwareId+5e (+0x20)
    [ 4c 8b c6 33 d2 48 8b c8:00 00 00 00 26 00 00 00 ]
    fffff88000c78111-fffff88000c78136  38 bytes - ataport!DeviceBuildHardwareId+71 (+0x13)
    [ 4c 8d 2d 78 85 ff ff 80:00 26 00 00 00 00 00 11 ]
    fffff88000c78138-fffff88000c7813b  4 bytes - ataport!DeviceBuildHardwareId+98 (+0x27)
    [ 00 b9 00 01:11 10 4f 0b ]
    fffff88000c7813e-fffff88000c7817e  65 bytes - ataport!DeviceBuildHardwareId+9e (+0x06)
    [ 66 85 48 0c 74 09 4c 8d:00 00 00 00 26 00 00 00 ]
    fffff88000c78182-fffff88000c78186  5 bytes - ataport!DeviceBuildHardwareId+e2 (+0x44)
    [ 2b c7 0f 84 9e:26 00 00 00 00 ]
    fffff88000c78188-fffff88000c781cd  70 bytes - ataport!DeviceBuildHardwareId+e8 (+0x06)
    [ 00 00 2b c7 74 62 2b c7:11 70 4f 0b 00 00 00 00 ]
    fffff88000c781d1-fffff88000c781e2  18 bytes - ataport!DeviceBuildHardwareId+131 (+0x49)
    [ 49 3b d7 75 03 48 2b cf:00 26 00 00 00 00 00 11 ]
    fffff88000c781e6-fffff88000c781ec  7 bytes - ataport!DeviceBuildHardwareId+146 (+0x15)
    [ 48 8d 4c 24 40 e9 98:00 00 11 c0 50 0b 00 ]
    fffff88000c781f0-fffff88000c78216  39 bytes - ataport!DeviceBuildHardwareId+150 (+0x0a)
    [ 48 8b d1 4c 8d 05 56 67:00 00 26 00 00 00 00 00 ]
    fffff88000c78218-fffff88000c7821f  8 bytes - ataport!DeviceBuildHardwareId+178 (+0x28)
    [ 00 41 b1 5f f2 ae b8 28:11 f0 50 0b 00 00 00 00 ]
    fffff88000c78222-fffff88000c78224  3 bytes - ataport!DeviceBuildHardwareId+182 (+0x0a)
    [ 00 e9 88:26 00 00 ]
    fffff88000c78228-fffff88000c7822f  8 bytes - ataport!DeviceBuildHardwareId+188 (+0x06)
    [ 48 8b d1 4c 8d 05 ee 66:11 00 51 0b 00 00 00 00 ]
    fffff88000c78232-fffff88000c78245  20 bytes - ataport!DeviceBuildHardwareId+192 (+0x0a)
    [ 48 8d 4c 24 40 e8 cc b0:26 00 00 00 00 00 11 10 ]
    fffff88000c78248-fffff88000c7825b  20 bytes - ataport!DeviceBuildHardwareId+1a8 (+0x16)
    [ 48 8d 4c 24 40 4d 8b ce:11 20 51 0b 00 00 00 00 ]
    fffff88000c7825e-fffff88000c7828c  47 bytes - ataport!DeviceBuildHardwareId+1be (+0x16)
    [ 48 83 c9 ff 33 c0 48 8d:00 00 00 00 26 00 00 00 ]
    fffff88000c7828f-fffff88000c782a6  24 bytes - ataport!DeviceBuildHardwareId+1ef (+0x31)
    [ 41 b1 5f e8 d1 ae fe ff:00 00 00 26 00 00 00 00 ]
    fffff88000c782a8-fffff88000c782ac  5 bytes - ataport!DeviceBuildHardwareId+208 (+0x19)
    [ 00 f2 ae b8 08:11 80 50 0b 00 ]
    fffff88000c782b0-fffff88000c782b2  3 bytes - ataport!DeviceBuildHardwareId+210 (+0x08)
    [ bf 01 00:00 00 26 ]
    fffff88000c782b5-fffff88000c782f8  68 bytes - ataport!DeviceBuildHardwareId+215 (+0x05)
    [ 48 f7 d1 48 2b cf 44 8d:00 00 00 11 70 50 0b 00 ]
    fffff88000c782fa-fffff88000c78364  107 bytes - ataport!DeviceBuildHardwareId+25a (+0x45)
    [ ff 15 98 7f ff ff eb 0b:50 0b 00 00 00 00 00 00 ]
    fffff88000c78368-fffff88000c78395  46 bytes - ataport!DeviceBuildHardwareId+2c8 (+0x6e)
    [ 44 8d 41 e8 41 83 fc 05:11 c0 4f 0b 00 00 00 00 ]
    fffff88000c78398-fffff88000c783a5  14 bytes - ataport!DeviceBuildHardwareId+2f8 (+0x30)
    [ 00 48 33 cc e8 ff 6b ff:11 80 51 0b 00 00 00 00 ]
    fffff88000c783a8-fffff88000c783ce  39 bytes - ataport!DeviceBuildHardwareId+308 (+0x10)
    [ 00 49 8b 5b 38 49 8b 6b:11 90 51 0b 00 00 00 00 ]
    fffff88000c783d1-fffff88000c783d5  5 bytes - ataport!DllInitialize+9 (+0x29)
    [ 48 83 a4 24 90:00 26 00 00 00 ]
    fffff88000c783d8-fffff88000c783de  7 bytes - ataport!DllInitialize+10 (+0x07)
    [ 00 00 48 8d 15 7f 65:11 c0 51 0b 00 00 00 ]
    fffff88000c783e1-fffff88000c783f0  16 bytes - ataport!DllInitialize+19 (+0x09)
    [ 48 8d 4c 24 30 ff 15 0c:00 26 00 00 00 00 00 11 ]
    fffff88000c783f2-fffff88000c783f6  5 bytes - ataport!DllInitialize+2a (+0x11)
    [ 48 83 64 24 60:26 00 00 00 00 ]
    fffff88000c783f8-fffff88000c783fc  5 bytes - ataport!DllInitialize+30 (+0x06)
    [ 48 83 64 24 68:11 e0 51 0b 00 ]
    fffff88000c783fe-fffff88000c7840c  15 bytes - ataport!DllInitialize+36 (+0x06)
    [ 48 8d 44 24 30 4c 8d 44:00 00 00 00 26 00 00 00 ]
    fffff88000c78410-fffff88000c78413  4 bytes - ataport!DllInitialize+48 (+0x12)
    [ ba 0f 00 0f:00 00 26 00 ]
    fffff88000c78415-fffff88000c7841e  10 bytes - ataport!DllInitialize+4d (+0x05)
    [ 48 89 44 24 50 c7 44 24:00 00 00 11 00 52 0b 00 ]
    fffff88000c78422-fffff88000c7842b  10 bytes - ataport!DllInitialize+5a (+0x0d)
    [ c7 44 24 58 50 02 00 00:26 00 00 00 00 00 11 10 ]
    fffff88000c7842d-fffff88000c78440  20 bytes - ataport!DllInitialize+65 (+0x0b)
    [ 80 ff ff 85 c0 78 3a 48:00 00 00 00 00 26 00 00 ]
    fffff88000c78442-fffff88000c78446  5 bytes - ataport!DllInitialize+7a (+0x15)
    [ 48 8d 84 24 90:26 00 00 00 00 ]
    fffff88000c78448-fffff88000c78452  11 bytes - ataport!DllInitialize+80 (+0x06)
    [ 00 00 45 33 c9 45 33 c0:11 30 52 0b 00 00 00 00 ]
    fffff88000c78455-fffff88000c78464  16 bytes - ataport!DllInitialize+8d (+0x0d)
    [ 48 89 44 24 20 ff 15 d8:00 00 00 11 40 52 0b 00 ]
    fffff88000c78468-fffff88000c784b3  76 bytes - ataport!DllInitialize+a0 (+0x13)
    [ ff 15 ba 7d ff ff e8 ed:11 50 52 0b 00 00 00 00 ]
    fffff88000c784b7-fffff88000c7859d  231 bytes - ataport!IdePortDispatchPnp+b (+0x4f)
    [ 4c 8b 49 40 80 78 01 19:00 11 a0 52 0b 00 00 00 ]
    fffff88000c785a0-fffff88000c78624  133 bytes - ataport!IdePortPopulateDispatchTables+c (+0xe9)
    [ 4c 8d 0d d1 f3 ff ff ba:00 00 26 00 00 00 00 00 ]
    fffff88000c78627-fffff88000c78640  26 bytes - ataport!IdePortPopulateDispatchTables+93 (+0x87)
    [ 48 89 05 f2 9e ff ff 48:00 11 a0 54 0b 00 00 00 ]
    fffff88000c78642-fffff88000c7865c  27 bytes - ataport!IdePortPopulateDispatchTables+ae (+0x1b)
    [ 00 48 8d 0d 4a a1 fe ff:26 00 00 00 00 00 11 c0 ]
    fffff88000c7865f-fffff88000c78686  40 bytes - ataport!IdePortPopulateDispatchTables+cb (+0x1d)
    [ 48 89 0d ea 9c ff ff 48:00 00 00 26 00 00 00 00 ]
    fffff88000c78688-fffff88000c786de  87 bytes - ataport!IdePortPopulateDispatchTables+f4 (+0x29)
    [ 00 48 89 0d c8 9c ff ff:11 00 54 0b 00 00 00 00 ]
WARNING: !chkimg output was truncated to 50 lines. Invoke !chkimg without '-lo [num_lines]' to view  entire output.
3784 errors : !ataport (fffff88000c78000-fffff88000c78fff)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE_4096

STACK_COMMAND:  .cxr 0xfffff880031a0e10 ; kb

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE_4096

BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE_4096

Followup: memory_corruption
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88000c784ac, The address that the exception occurred at
Arg3: fffff880031a15a8, Exception Record Address
Arg4: fffff880031a0e10, Context Record Address

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


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

FAULTING_IP: 
ataport!IdePortDispatchPnp+0
fffff880`00c784ac 0000            add     byte ptr [rax],al

EXCEPTION_RECORD:  fffff880031a15a8 -- (.exr 0xfffff880031a15a8)
ExceptionAddress: fffff88000c784ac (ataport!IdePortDispatchPnp)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 000000000000001b
Attempt to write to address 000000000000001b

CONTEXT:  fffff880031a0e10 -- (.cxr 0xfffff880031a0e10)
rax=000000000000001b rbx=fffffa8007277e10 rcx=fffffa8007b05050
rdx=fffffa8007277e10 rsi=fffffa8007b05050 rdi=fffffa8007ae7cb0
rip=fffff88000c784ac rsp=fffff880031a17e8 rbp=fffffa800a1ad800
 r8=fffffa800775bc80  r9=000000000000001b r10=0000000000000000
r11=fffffa8007277fb8 r12=fffff80002dd3c80 r13=fffff880031a1880
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
ataport!IdePortDispatchPnp:
fffff880`00c784ac 0000            add     byte ptr [rax],al ds:002b:00000000`0000001b=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

CURRENT_IRQL:  0

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

EXCEPTION_PARAMETER1:  0000000000000001

EXCEPTION_PARAMETER2:  000000000000001b

WRITE_ADDRESS:  000000000000001b 

FOLLOWUP_IP: 
ataport!IdePortDispatchPnp+0
fffff880`00c784ac 0000            add     byte ptr [rax],al

BUGCHECK_STR:  0x7E

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

LOCK_ADDRESS:  fffff80002ed8400 -- (!locks fffff80002ed8400)

Resource @ nt!PiEngineLock (0xfffff80002ed8400)    Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE: 
    Lock address  : 0xfffff80002ed8400
    Thread Count  : 0
    Thread address: 0x0000000000000000
    Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from fffff8000309370e to fffff88000c784ac

STACK_TEXT:  
fffff880`031a17e8 fffff800`0309370e : 00000000`00000000 00000000`00000000 fffffa80`0a1ad800 fffff880`02f64180 : ataport!IdePortDispatchPnp
fffff880`031a17f0 fffff800`03093a7a : 00000000`00000000 fffffa80`0a1ad800 fffff800`02dd3c80 00000000`00000000 : nt!PnpAsynchronousCall+0xce
fffff880`031a1830 fffff800`03095d67 : fffff800`02ed81c0 fffffa80`07aeb990 00000000`00000002 00000000`00000588 : nt!PnpQueryDeviceRelations+0xfa
fffff880`031a18f0 fffff800`030c195c : fffffa80`07aeb990 fffffa80`07ae001f fffffa80`07aeb990 00000000`00000002 : nt!PipEnumerateDevice+0x117
fffff880`031a1950 fffff800`030c1f68 : fffff800`02ed5d80 00000000`00000000 00000000`00000001 fffff800`02f42698 : nt!PipProcessDevNodeTree+0x21c
fffff880`031a1bc0 fffff800`02dd62f7 : 00000001`00000003 00000000`00000000 00000000`00000001 00000000`00000000 : nt!PiProcessReenumeration+0x98
fffff880`031a1c10 fffff800`02ce1861 : fffff800`02dd5fd0 fffff800`02fd1801 fffffa80`06d1cb00 00000000`00000000 : nt!PnpDeviceActionWorker+0x327
fffff880`031a1cb0 fffff800`02f79a86 : 36f3b363`331b3133 fffffa80`06d1cb60 00000000`00000080 fffffa80`06d08040 : nt!ExpWorkerThread+0x111
fffff880`031a1d40 fffff800`02cb2b06 : fffff880`02f64180 fffffa80`06d1cb60 fffff880`02f6efc0 3ae1bc22`33fbb975 : nt!PspSystemThreadStartup+0x5a
fffff880`031a1d80 00000000`00000000 : fffff880`031a2000 fffff880`0319c000 fffff880`031a1090 00000000`00000000 : nt!KxStartSystemThread+0x16


CHKIMG_EXTENSION: !chkimg -lo 50 -d !ataport
    fffff88000c78000-fffff88000c78012  19 bytes - ataport!DeviceBuildCompatibleId+64
    [ 8d 4c 24 30 ff 15 8e 82:00 00 26 00 00 00 00 00 ]
    fffff88000c78014-fffff88000c7801b  8 bytes - ataport!DeviceBuildCompatibleId+78 (+0x14)
    [ 02 8d 50 04 b9 01 00 00:00 00 00 00 11 f0 4d 0b ]
    fffff88000c7801d-fffff88000c780bb  159 bytes - ataport!DeviceBuildCompatibleId+81 (+0x09)
    [ 41 b8 49 64 65 50 66 89:00 00 00 00 00 26 00 00 ]
    fffff88000c780bf-fffff88000c780cd  15 bytes - ataport!DeviceBuildHardwareId+1f (+0xa2)
    [ 48 8b 05 3a a0 ff ff 48:00 00 00 26 00 00 00 00 ]
    fffff88000c780d1-fffff88000c780d6  6 bytes - ataport!DeviceBuildHardwareId+31 (+0x12)
    [ 48 8b e9 be 82 02:00 26 00 00 00 00 ]
    fffff88000c780d8-fffff88000c780db  4 bytes - ataport!DeviceBuildHardwareId+38 (+0x07)
    [ 00 bf 01 00:11 b0 4e 0b ]
    fffff88000c780de-fffff88000c780fb  30 bytes - ataport!DeviceBuildHardwareId+3e (+0x06)
    [ 48 8b d6 8b cf 41 b8 49:00 00 00 00 26 00 00 00 ]
    fffff88000c780fe-fffff88000c7810e  17 bytes - ataport!DeviceBuildHardwareId+5e (+0x20)
    [ 4c 8b c6 33 d2 48 8b c8:00 00 00 00 26 00 00 00 ]
    fffff88000c78111-fffff88000c78136  38 bytes - ataport!DeviceBuildHardwareId+71 (+0x13)
    [ 4c 8d 2d 78 85 ff ff 80:00 26 00 00 00 00 00 11 ]
    fffff88000c78138-fffff88000c7813b  4 bytes - ataport!DeviceBuildHardwareId+98 (+0x27)
    [ 00 b9 00 01:11 10 4f 0b ]
    fffff88000c7813e-fffff88000c7817e  65 bytes - ataport!DeviceBuildHardwareId+9e (+0x06)
    [ 66 85 48 0c 74 09 4c 8d:00 00 00 00 26 00 00 00 ]
    fffff88000c78182-fffff88000c78186  5 bytes - ataport!DeviceBuildHardwareId+e2 (+0x44)
    [ 2b c7 0f 84 9e:26 00 00 00 00 ]
    fffff88000c78188-fffff88000c781cd  70 bytes - ataport!DeviceBuildHardwareId+e8 (+0x06)
    [ 00 00 2b c7 74 62 2b c7:11 70 4f 0b 00 00 00 00 ]
    fffff88000c781d1-fffff88000c781e2  18 bytes - ataport!DeviceBuildHardwareId+131 (+0x49)
    [ 49 3b d7 75 03 48 2b cf:00 26 00 00 00 00 00 11 ]
    fffff88000c781e6-fffff88000c781ec  7 bytes - ataport!DeviceBuildHardwareId+146 (+0x15)
    [ 48 8d 4c 24 40 e9 98:00 00 11 c0 50 0b 00 ]
    fffff88000c781f0-fffff88000c78216  39 bytes - ataport!DeviceBuildHardwareId+150 (+0x0a)
    [ 48 8b d1 4c 8d 05 56 67:00 00 26 00 00 00 00 00 ]
    fffff88000c78218-fffff88000c7821f  8 bytes - ataport!DeviceBuildHardwareId+178 (+0x28)
    [ 00 41 b1 5f f2 ae b8 28:11 f0 50 0b 00 00 00 00 ]
    fffff88000c78222-fffff88000c78224  3 bytes - ataport!DeviceBuildHardwareId+182 (+0x0a)
    [ 00 e9 88:26 00 00 ]
    fffff88000c78228-fffff88000c7822f  8 bytes - ataport!DeviceBuildHardwareId+188 (+0x06)
    [ 48 8b d1 4c 8d 05 ee 66:11 00 51 0b 00 00 00 00 ]
    fffff88000c78232-fffff88000c78245  20 bytes - ataport!DeviceBuildHardwareId+192 (+0x0a)
    [ 48 8d 4c 24 40 e8 cc b0:26 00 00 00 00 00 11 10 ]
    fffff88000c78248-fffff88000c7825b  20 bytes - ataport!DeviceBuildHardwareId+1a8 (+0x16)
    [ 48 8d 4c 24 40 4d 8b ce:11 20 51 0b 00 00 00 00 ]
    fffff88000c7825e-fffff88000c7828c  47 bytes - ataport!DeviceBuildHardwareId+1be (+0x16)
    [ 48 83 c9 ff 33 c0 48 8d:00 00 00 00 26 00 00 00 ]
    fffff88000c7828f-fffff88000c782a6  24 bytes - ataport!DeviceBuildHardwareId+1ef (+0x31)
    [ 41 b1 5f e8 d1 ae fe ff:00 00 00 26 00 00 00 00 ]
    fffff88000c782a8-fffff88000c782ac  5 bytes - ataport!DeviceBuildHardwareId+208 (+0x19)
    [ 00 f2 ae b8 08:11 80 50 0b 00 ]
    fffff88000c782b0-fffff88000c782b2  3 bytes - ataport!DeviceBuildHardwareId+210 (+0x08)
    [ bf 01 00:00 00 26 ]
    fffff88000c782b5-fffff88000c782f8  68 bytes - ataport!DeviceBuildHardwareId+215 (+0x05)
    [ 48 f7 d1 48 2b cf 44 8d:00 00 00 11 70 50 0b 00 ]
    fffff88000c782fa-fffff88000c78364  107 bytes - ataport!DeviceBuildHardwareId+25a (+0x45)
    [ ff 15 98 7f ff ff eb 0b:50 0b 00 00 00 00 00 00 ]
    fffff88000c78368-fffff88000c78395  46 bytes - ataport!DeviceBuildHardwareId+2c8 (+0x6e)
    [ 44 8d 41 e8 41 83 fc 05:11 c0 4f 0b 00 00 00 00 ]
    fffff88000c78398-fffff88000c783a5  14 bytes - ataport!DeviceBuildHardwareId+2f8 (+0x30)
    [ 00 48 33 cc e8 ff 6b ff:11 80 51 0b 00 00 00 00 ]
    fffff88000c783a8-fffff88000c783ce  39 bytes - ataport!DeviceBuildHardwareId+308 (+0x10)
    [ 00 49 8b 5b 38 49 8b 6b:11 90 51 0b 00 00 00 00 ]
    fffff88000c783d1-fffff88000c783d5  5 bytes - ataport!DllInitialize+9 (+0x29)
    [ 48 83 a4 24 90:00 26 00 00 00 ]
    fffff88000c783d8-fffff88000c783de  7 bytes - ataport!DllInitialize+10 (+0x07)
    [ 00 00 48 8d 15 7f 65:11 c0 51 0b 00 00 00 ]
    fffff88000c783e1-fffff88000c783f0  16 bytes - ataport!DllInitialize+19 (+0x09)
    [ 48 8d 4c 24 30 ff 15 0c:00 26 00 00 00 00 00 11 ]
    fffff88000c783f2-fffff88000c783f6  5 bytes - ataport!DllInitialize+2a (+0x11)
    [ 48 83 64 24 60:26 00 00 00 00 ]
    fffff88000c783f8-fffff88000c783fc  5 bytes - ataport!DllInitialize+30 (+0x06)
    [ 48 83 64 24 68:11 e0 51 0b 00 ]
    fffff88000c783fe-fffff88000c7840c  15 bytes - ataport!DllInitialize+36 (+0x06)
    [ 48 8d 44 24 30 4c 8d 44:00 00 00 00 26 00 00 00 ]
    fffff88000c78410-fffff88000c78413  4 bytes - ataport!DllInitialize+48 (+0x12)
    [ ba 0f 00 0f:00 00 26 00 ]
    fffff88000c78415-fffff88000c7841e  10 bytes - ataport!DllInitialize+4d (+0x05)
    [ 48 89 44 24 50 c7 44 24:00 00 00 11 00 52 0b 00 ]
    fffff88000c78422-fffff88000c7842b  10 bytes - ataport!DllInitialize+5a (+0x0d)
    [ c7 44 24 58 50 02 00 00:26 00 00 00 00 00 11 10 ]
    fffff88000c7842d-fffff88000c78440  20 bytes - ataport!DllInitialize+65 (+0x0b)
    [ 80 ff ff 85 c0 78 3a 48:00 00 00 00 00 26 00 00 ]
    fffff88000c78442-fffff88000c78446  5 bytes - ataport!DllInitialize+7a (+0x15)
    [ 48 8d 84 24 90:26 00 00 00 00 ]
    fffff88000c78448-fffff88000c78452  11 bytes - ataport!DllInitialize+80 (+0x06)
    [ 00 00 45 33 c9 45 33 c0:11 30 52 0b 00 00 00 00 ]
    fffff88000c78455-fffff88000c78464  16 bytes - ataport!DllInitialize+8d (+0x0d)
    [ 48 89 44 24 20 ff 15 d8:00 00 00 11 40 52 0b 00 ]
    fffff88000c78468-fffff88000c784b3  76 bytes - ataport!DllInitialize+a0 (+0x13)
    [ ff 15 ba 7d ff ff e8 ed:11 50 52 0b 00 00 00 00 ]
    fffff88000c784b7-fffff88000c7859d  231 bytes - ataport!IdePortDispatchPnp+b (+0x4f)
    [ 4c 8b 49 40 80 78 01 19:00 11 a0 52 0b 00 00 00 ]
    fffff88000c785a0-fffff88000c78624  133 bytes - ataport!IdePortPopulateDispatchTables+c (+0xe9)
    [ 4c 8d 0d d1 f3 ff ff ba:00 00 26 00 00 00 00 00 ]
    fffff88000c78627-fffff88000c78640  26 bytes - ataport!IdePortPopulateDispatchTables+93 (+0x87)
    [ 48 89 05 f2 9e ff ff 48:00 11 a0 54 0b 00 00 00 ]
    fffff88000c78642-fffff88000c7865c  27 bytes - ataport!IdePortPopulateDispatchTables+ae (+0x1b)
    [ 00 48 8d 0d 4a a1 fe ff:26 00 00 00 00 00 11 c0 ]
    fffff88000c7865f-fffff88000c78686  40 bytes - ataport!IdePortPopulateDispatchTables+cb (+0x1d)
    [ 48 89 0d ea 9c ff ff 48:00 00 00 26 00 00 00 00 ]
    fffff88000c78688-fffff88000c786de  87 bytes - ataport!IdePortPopulateDispatchTables+f4 (+0x29)
    [ 00 48 89 0d c8 9c ff ff:11 00 54 0b 00 00 00 00 ]
WARNING: !chkimg output was truncated to 50 lines. Invoke !chkimg without '-lo [num_lines]' to view  entire output.
3784 errors : !ataport (fffff88000c78000-fffff88000c78fff)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE_4096

STACK_COMMAND:  .cxr 0xfffff880031a0e10 ; kb

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE_4096

BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE_4096

Followup: memory_corruption
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88000c784ac, The address that the exception occurred at
Arg3: fffff880031a15a8, Exception Record Address
Arg4: fffff880031a0e10, Context Record Address

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


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

FAULTING_IP: 
ataport!IdePortDispatchPnp+0
fffff880`00c784ac 0000            add     byte ptr [rax],al

EXCEPTION_RECORD:  fffff880031a15a8 -- (.exr 0xfffff880031a15a8)
ExceptionAddress: fffff88000c784ac (ataport!IdePortDispatchPnp)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 000000000000001b
Attempt to write to address 000000000000001b

CONTEXT:  fffff880031a0e10 -- (.cxr 0xfffff880031a0e10)
rax=000000000000001b rbx=fffffa8007277e10 rcx=fffffa8007b05050
rdx=fffffa8007277e10 rsi=fffffa8007b05050 rdi=fffffa8007ae7cb0
rip=fffff88000c784ac rsp=fffff880031a17e8 rbp=fffffa800a1ad800
 r8=fffffa800775bc80  r9=000000000000001b r10=0000000000000000
r11=fffffa8007277fb8 r12=fffff80002dd3c80 r13=fffff880031a1880
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
ataport!IdePortDispatchPnp:
fffff880`00c784ac 0000            add     byte ptr [rax],al ds:002b:00000000`0000001b=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

CURRENT_IRQL:  0

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

EXCEPTION_PARAMETER1:  0000000000000001

EXCEPTION_PARAMETER2:  000000000000001b

WRITE_ADDRESS:  000000000000001b 

FOLLOWUP_IP: 
ataport!IdePortDispatchPnp+0
fffff880`00c784ac 0000            add     byte ptr [rax],al

BUGCHECK_STR:  0x7E

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

LOCK_ADDRESS:  fffff80002ed8400 -- (!locks fffff80002ed8400)

Resource @ nt!PiEngineLock (0xfffff80002ed8400)    Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE: 
    Lock address  : 0xfffff80002ed8400
    Thread Count  : 0
    Thread address: 0x0000000000000000
    Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from fffff8000309370e to fffff88000c784ac

STACK_TEXT:  
fffff880`031a17e8 fffff800`0309370e : 00000000`00000000 00000000`00000000 fffffa80`0a1ad800 fffff880`02f64180 : ataport!IdePortDispatchPnp
fffff880`031a17f0 fffff800`03093a7a : 00000000`00000000 fffffa80`0a1ad800 fffff800`02dd3c80 00000000`00000000 : nt!PnpAsynchronousCall+0xce
fffff880`031a1830 fffff800`03095d67 : fffff800`02ed81c0 fffffa80`07aeb990 00000000`00000002 00000000`00000588 : nt!PnpQueryDeviceRelations+0xfa
fffff880`031a18f0 fffff800`030c195c : fffffa80`07aeb990 fffffa80`07ae001f fffffa80`07aeb990 00000000`00000002 : nt!PipEnumerateDevice+0x117
fffff880`031a1950 fffff800`030c1f68 : fffff800`02ed5d80 00000000`00000000 00000000`00000001 fffff800`02f42698 : nt!PipProcessDevNodeTree+0x21c
fffff880`031a1bc0 fffff800`02dd62f7 : 00000001`00000003 00000000`00000000 00000000`00000001 00000000`00000000 : nt!PiProcessReenumeration+0x98
fffff880`031a1c10 fffff800`02ce1861 : fffff800`02dd5fd0 fffff800`02fd1801 fffffa80`06d1cb00 00000000`00000000 : nt!PnpDeviceActionWorker+0x327
fffff880`031a1cb0 fffff800`02f79a86 : 36f3b363`331b3133 fffffa80`06d1cb60 00000000`00000080 fffffa80`06d08040 : nt!ExpWorkerThread+0x111
fffff880`031a1d40 fffff800`02cb2b06 : fffff880`02f64180 fffffa80`06d1cb60 fffff880`02f6efc0 3ae1bc22`33fbb975 : nt!PspSystemThreadStartup+0x5a
fffff880`031a1d80 00000000`00000000 : fffff880`031a2000 fffff880`0319c000 fffff880`031a1090 00000000`00000000 : nt!KxStartSystemThread+0x16


CHKIMG_EXTENSION: !chkimg -lo 50 -d !ataport
    fffff88000c78000-fffff88000c78012  19 bytes - ataport!DeviceBuildCompatibleId+64
    [ 8d 4c 24 30 ff 15 8e 82:00 00 26 00 00 00 00 00 ]
    fffff88000c78014-fffff88000c7801b  8 bytes - ataport!DeviceBuildCompatibleId+78 (+0x14)
    [ 02 8d 50 04 b9 01 00 00:00 00 00 00 11 f0 4d 0b ]
    fffff88000c7801d-fffff88000c780bb  159 bytes - ataport!DeviceBuildCompatibleId+81 (+0x09)
    [ 41 b8 49 64 65 50 66 89:00 00 00 00 00 26 00 00 ]
    fffff88000c780bf-fffff88000c780cd  15 bytes - ataport!DeviceBuildHardwareId+1f (+0xa2)
    [ 48 8b 05 3a a0 ff ff 48:00 00 00 26 00 00 00 00 ]
    fffff88000c780d1-fffff88000c780d6  6 bytes - ataport!DeviceBuildHardwareId+31 (+0x12)
    [ 48 8b e9 be 82 02:00 26 00 00 00 00 ]
    fffff88000c780d8-fffff88000c780db  4 bytes - ataport!DeviceBuildHardwareId+38 (+0x07)
    [ 00 bf 01 00:11 b0 4e 0b ]
    fffff88000c780de-fffff88000c780fb  30 bytes - ataport!DeviceBuildHardwareId+3e (+0x06)
    [ 48 8b d6 8b cf 41 b8 49:00 00 00 00 26 00 00 00 ]
    fffff88000c780fe-fffff88000c7810e  17 bytes - ataport!DeviceBuildHardwareId+5e (+0x20)
    [ 4c 8b c6 33 d2 48 8b c8:00 00 00 00 26 00 00 00 ]
    fffff88000c78111-fffff88000c78136  38 bytes - ataport!DeviceBuildHardwareId+71 (+0x13)
    [ 4c 8d 2d 78 85 ff ff 80:00 26 00 00 00 00 00 11 ]
    fffff88000c78138-fffff88000c7813b  4 bytes - ataport!DeviceBuildHardwareId+98 (+0x27)
    [ 00 b9 00 01:11 10 4f 0b ]
    fffff88000c7813e-fffff88000c7817e  65 bytes - ataport!DeviceBuildHardwareId+9e (+0x06)
    [ 66 85 48 0c 74 09 4c 8d:00 00 00 00 26 00 00 00 ]
    fffff88000c78182-fffff88000c78186  5 bytes - ataport!DeviceBuildHardwareId+e2 (+0x44)
    [ 2b c7 0f 84 9e:26 00 00 00 00 ]
    fffff88000c78188-fffff88000c781cd  70 bytes - ataport!DeviceBuildHardwareId+e8 (+0x06)
    [ 00 00 2b c7 74 62 2b c7:11 70 4f 0b 00 00 00 00 ]
    fffff88000c781d1-fffff88000c781e2  18 bytes - ataport!DeviceBuildHardwareId+131 (+0x49)
    [ 49 3b d7 75 03 48 2b cf:00 26 00 00 00 00 00 11 ]
    fffff88000c781e6-fffff88000c781ec  7 bytes - ataport!DeviceBuildHardwareId+146 (+0x15)
    [ 48 8d 4c 24 40 e9 98:00 00 11 c0 50 0b 00 ]
    fffff88000c781f0-fffff88000c78216  39 bytes - ataport!DeviceBuildHardwareId+150 (+0x0a)
    [ 48 8b d1 4c 8d 05 56 67:00 00 26 00 00 00 00 00 ]
    fffff88000c78218-fffff88000c7821f  8 bytes - ataport!DeviceBuildHardwareId+178 (+0x28)
    [ 00 41 b1 5f f2 ae b8 28:11 f0 50 0b 00 00 00 00 ]
    fffff88000c78222-fffff88000c78224  3 bytes - ataport!DeviceBuildHardwareId+182 (+0x0a)
    [ 00 e9 88:26 00 00 ]
    fffff88000c78228-fffff88000c7822f  8 bytes - ataport!DeviceBuildHardwareId+188 (+0x06)
    [ 48 8b d1 4c 8d 05 ee 66:11 00 51 0b 00 00 00 00 ]
    fffff88000c78232-fffff88000c78245  20 bytes - ataport!DeviceBuildHardwareId+192 (+0x0a)
    [ 48 8d 4c 24 40 e8 cc b0:26 00 00 00 00 00 11 10 ]
    fffff88000c78248-fffff88000c7825b  20 bytes - ataport!DeviceBuildHardwareId+1a8 (+0x16)
    [ 48 8d 4c 24 40 4d 8b ce:11 20 51 0b 00 00 00 00 ]
    fffff88000c7825e-fffff88000c7828c  47 bytes - ataport!DeviceBuildHardwareId+1be (+0x16)
    [ 48 83 c9 ff 33 c0 48 8d:00 00 00 00 26 00 00 00 ]
    fffff88000c7828f-fffff88000c782a6  24 bytes - ataport!DeviceBuildHardwareId+1ef (+0x31)
    [ 41 b1 5f e8 d1 ae fe ff:00 00 00 26 00 00 00 00 ]
    fffff88000c782a8-fffff88000c782ac  5 bytes - ataport!DeviceBuildHardwareId+208 (+0x19)
    [ 00 f2 ae b8 08:11 80 50 0b 00 ]
    fffff88000c782b0-fffff88000c782b2  3 bytes - ataport!DeviceBuildHardwareId+210 (+0x08)
    [ bf 01 00:00 00 26 ]
    fffff88000c782b5-fffff88000c782f8  68 bytes - ataport!DeviceBuildHardwareId+215 (+0x05)
    [ 48 f7 d1 48 2b cf 44 8d:00 00 00 11 70 50 0b 00 ]
    fffff88000c782fa-fffff88000c78364  107 bytes - ataport!DeviceBuildHardwareId+25a (+0x45)
    [ ff 15 98 7f ff ff eb 0b:50 0b 00 00 00 00 00 00 ]
    fffff88000c78368-fffff88000c78395  46 bytes - ataport!DeviceBuildHardwareId+2c8 (+0x6e)
    [ 44 8d 41 e8 41 83 fc 05:11 c0 4f 0b 00 00 00 00 ]
    fffff88000c78398-fffff88000c783a5  14 bytes - ataport!DeviceBuildHardwareId+2f8 (+0x30)
    [ 00 48 33 cc e8 ff 6b ff:11 80 51 0b 00 00 00 00 ]
    fffff88000c783a8-fffff88000c783ce  39 bytes - ataport!DeviceBuildHardwareId+308 (+0x10)
    [ 00 49 8b 5b 38 49 8b 6b:11 90 51 0b 00 00 00 00 ]
    fffff88000c783d1-fffff88000c783d5  5 bytes - ataport!DllInitialize+9 (+0x29)
    [ 48 83 a4 24 90:00 26 00 00 00 ]
    fffff88000c783d8-fffff88000c783de  7 bytes - ataport!DllInitialize+10 (+0x07)
    [ 00 00 48 8d 15 7f 65:11 c0 51 0b 00 00 00 ]
    fffff88000c783e1-fffff88000c783f0  16 bytes - ataport!DllInitialize+19 (+0x09)
    [ 48 8d 4c 24 30 ff 15 0c:00 26 00 00 00 00 00 11 ]
    fffff88000c783f2-fffff88000c783f6  5 bytes - ataport!DllInitialize+2a (+0x11)
    [ 48 83 64 24 60:26 00 00 00 00 ]
    fffff88000c783f8-fffff88000c783fc  5 bytes - ataport!DllInitialize+30 (+0x06)
    [ 48 83 64 24 68:11 e0 51 0b 00 ]
    fffff88000c783fe-fffff88000c7840c  15 bytes - ataport!DllInitialize+36 (+0x06)
    [ 48 8d 44 24 30 4c 8d 44:00 00 00 00 26 00 00 00 ]
    fffff88000c78410-fffff88000c78413  4 bytes - ataport!DllInitialize+48 (+0x12)
    [ ba 0f 00 0f:00 00 26 00 ]
    fffff88000c78415-fffff88000c7841e  10 bytes - ataport!DllInitialize+4d (+0x05)
    [ 48 89 44 24 50 c7 44 24:00 00 00 11 00 52 0b 00 ]
    fffff88000c78422-fffff88000c7842b  10 bytes - ataport!DllInitialize+5a (+0x0d)
    [ c7 44 24 58 50 02 00 00:26 00 00 00 00 00 11 10 ]
    fffff88000c7842d-fffff88000c78440  20 bytes - ataport!DllInitialize+65 (+0x0b)
    [ 80 ff ff 85 c0 78 3a 48:00 00 00 00 00 26 00 00 ]
    fffff88000c78442-fffff88000c78446  5 bytes - ataport!DllInitialize+7a (+0x15)
    [ 48 8d 84 24 90:26 00 00 00 00 ]
    fffff88000c78448-fffff88000c78452  11 bytes - ataport!DllInitialize+80 (+0x06)
    [ 00 00 45 33 c9 45 33 c0:11 30 52 0b 00 00 00 00 ]
    fffff88000c78455-fffff88000c78464  16 bytes - ataport!DllInitialize+8d (+0x0d)
    [ 48 89 44 24 20 ff 15 d8:00 00 00 11 40 52 0b 00 ]
    fffff88000c78468-fffff88000c784b3  76 bytes - ataport!DllInitialize+a0 (+0x13)
    [ ff 15 ba 7d ff ff e8 ed:11 50 52 0b 00 00 00 00 ]
    fffff88000c784b7-fffff88000c7859d  231 bytes - ataport!IdePortDispatchPnp+b (+0x4f)
    [ 4c 8b 49 40 80 78 01 19:00 11 a0 52 0b 00 00 00 ]
    fffff88000c785a0-fffff88000c78624  133 bytes - ataport!IdePortPopulateDispatchTables+c (+0xe9)
    [ 4c 8d 0d d1 f3 ff ff ba:00 00 26 00 00 00 00 00 ]
    fffff88000c78627-fffff88000c78640  26 bytes - ataport!IdePortPopulateDispatchTables+93 (+0x87)
    [ 48 89 05 f2 9e ff ff 48:00 11 a0 54 0b 00 00 00 ]
    fffff88000c78642-fffff88000c7865c  27 bytes - ataport!IdePortPopulateDispatchTables+ae (+0x1b)
    [ 00 48 8d 0d 4a a1 fe ff:26 00 00 00 00 00 11 c0 ]
    fffff88000c7865f-fffff88000c78686  40 bytes - ataport!IdePortPopulateDispatchTables+cb (+0x1d)
    [ 48 89 0d ea 9c ff ff 48:00 00 00 26 00 00 00 00 ]
    fffff88000c78688-fffff88000c786de  87 bytes - ataport!IdePortPopulateDispatchTables+f4 (+0x29)
    [ 00 48 89 0d c8 9c ff ff:11 00 54 0b 00 00 00 00 ]
WARNING: !chkimg output was truncated to 50 lines. Invoke !chkimg without '-lo [num_lines]' to view  entire output.
3784 errors : !ataport (fffff88000c78000-fffff88000c78fff)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE_4096

STACK_COMMAND:  .cxr 0xfffff880031a0e10 ; kb

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE_4096

BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE_4096

Followup: memory_corruption
---------
Code:
 
Well pretty straight forward. memory corruption. to test your memory you need to download an app called memtestx86, burn it to cd, and run it for at least 7 passes.

Let us know the results

Ken
My System SpecsSystem Spec
09 Jun 2010   #3

windows 7 pro 64 bit
 
 

Ok as I said earlier I had done extensive tests on the ram recently and as I thought last night it passed 8 passes of memtest 86. So any more ideas thanks!
My System SpecsSystem Spec
.


09 Jun 2010   #4

Windows 7 Professional x64
 
 

Since you mentioned overclock, write down your current settings, and then restore it to the default.

Overclocking causes its fair share of BSODs.
My System SpecsSystem Spec
09 Jun 2010   #5

windows 7 pro 64 bit
 
 

Quote   Quote: Originally Posted by Jonathan_King View Post
Since you mentioned overclock, write down your current settings, and then restore it to the default.

Overclocking causes its fair share of BSODs.
But the RAM is underclocked :S. And my PC is running 100 percent perfectly at the moment - could be weeks or never before it fails even in its current state so setting it to default wont really tell me anything. I really would like to keep the overclocked CPU and unclocked RAM set up as it is so much faster for my video / 3D stuff .

Anyway basically my suspicion is that when it happend it was a hot day so it might of been the RAM overheating - as my RAM is underclocked and still has the stock 2.1volts running through it (and stock ras cas settings) I am wondering if its slightly too much voltage for it? Would this produce extra heat?

RAM is 1066 mhz DDR2 RAM underclocked at 800 mhz (for 1:1 to my 400 mhz FSB). Thanks!
My System SpecsSystem Spec
09 Jun 2010   #6

windows 7 pro 64 bit
 
 

Could the overclocked CPU cause this error then?
My System SpecsSystem Spec
09 Jun 2010   #7

Windows 7 Professional x64
 
 

Quote   Quote: Originally Posted by Diamond View Post
Could the overclocked CPU cause this error then?
Yes, that's what I suspect. Jot down your current settings and then restore to defaults. Then, if the problems do not go away, you can restore your OC later.
My System SpecsSystem Spec
09 Jun 2010   #8

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by Diamond View Post
Could the overclocked CPU cause this error then?

Diamond

We can only report what the DMP file created by your computer when it crashed. It currently still says memory corruption. Have you tested the ram one stick at a time? Have you tested the Mobo one slot at a time.

As JK said everything to stock. Memory (not under or over), cpu (the same). It is only then you may be able to get a correct DMP


Good luck

Ken
My System SpecsSystem Spec
10 Jun 2010   #9

windows 7 pro 64 bit
 
 

Quote   Quote: Originally Posted by zigzag3143 View Post
Quote   Quote: Originally Posted by Diamond View Post
Could the overclocked CPU cause this error then?

Diamond

We can only report what the DMP file created by your computer when it crashed. It currently still says memory corruption. Have you tested the ram one stick at a time? Have you tested the Mobo one slot at a time.

As JK said everything to stock. Memory (not under or over), cpu (the same). It is only then you may be able to get a correct DMP


Good luck

Ken
Well it just crashed again while rendering a video - I am typing on it now so its ok but 2 crashes is a bit more serious than one for me so I will go with the normal settings - which will have to be underclocked RAM and normal clocked CPU. This is because my mother board is a bit crap and says it supports up to 8GB at 1066mhz but in reality it can only go to 800 mhz - I am hoping this is not why its BSODing. I am told by the hundrreds of other people with problems with this mo bo that its to do with a weak chipset http://www.asus.com/product.aspx?P_I...tyB&templete=2


The only other things I can think of are that I just installed a windows update for silverlight just before this all happend and my system HD has about 3GB left on it and with 8GB ram and 8GB page file maybe its cramped? Anyway time to lower the CPU settings ....


Oh actually I will just post the 2nd crash incase it helps (I see the ata port bit again - not sure if its relevant):
My System SpecsSystem Spec
10 Jun 2010   #10

windows 7 pro 64 bit
 
 

Update: aaah I just noticed something :O ! I tried prime 95 at max stress on CPU and the CPU went to 70 degrees C ! As its summer now I guess the room temp has pushed it up - it was maxing at 63 degrees before! I am assuming this could be it! 45 degrees in normal windows idle time :S .... im off to change some bios settings ...thanks....
My System SpecsSystem Spec
Reply

 BSOD mini dmp what does this mean? Thanks!




Thread Tools



Similar help and support threads for2: BSOD mini dmp what does this mean? Thanks!
Thread Forum
New BSOD 0x0000007a, no mini dump BSOD Help and Support
[HELP] Mini-BSOD, should I worry? BSOD Help and Support
help with bsod reading mini dump BSOD Help and Support
BSOD Asus Mini Dump BSOD Help and Support
BSOD, Mini Dump Attached. Help? BSOD Help and Support
BSOD at startup on my hp mini netbook BSOD Help and Support
BSOD upon start-up, mini-dump attached BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 11:11 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33