Unknown Bluescreen

Hi,

I have had some bluescreens just doing random tasks (no idea how to reproduce). Event log reveals nothing to me as there is no driver name. I have attached the pertinent files in the ZIP file.

I am clueless on this one. Running Windows 7 x86 with no prior problems with this hardware on Vista x86 and no prior bluescreens like this one.

Thanks in advance!

Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Attached files:
C:\Windows\Minidump\020910-17097-01.dmp
C:\Users\mark\AppData\Local\Temp\WER-8774728-0.sysdata.xml
C:\Users\mark\AppData\Local\Temp\WEREE18.tmp.WERInternalMetadata.xml

These files may be available here:
C:\Users\mark\AppData\Local\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_0fa6589d

Analysis symbol:
Rechecking for solution: 0
Report Id: 020910-17097-01
Report Status: 4

zsharp said:

Hi,

I have had some bluescreens just doing random tasks (no idea how to reproduce). Event log reveals nothing to me as there is no driver name. I have attached the pertinent files in the ZIP file.

I am clueless on this one. Running Windows 7 x86 with no prior problems with this hardware on Vista x86 and no prior bluescreens like this one.

Thanks in advance!

Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1:
P2:
P3:
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Attached files:
C:\Windows\Minidump\020910-17097-01.dmp
C:\Users\mark\AppData\Local\Temp\WER-8774728-0.sysdata.xml
C:\Users\mark\AppData\Local\Temp\WEREE18.tmp.WERInternalMetadata.xml

These files may be available here:
C:\Users\mark\AppData\Local\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_0fa6589d

Analysis symbol:
Rechecking for solution: 0
Report Id: 020910-17097-01
Report Status: 4

Pretty straight forward. Memory corruption

I would download memtestx86 and run for 5 passes
run a system file check
type cmd in search>right click and run as admin>sfc /scannow
If you are overclocking stop

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\020910-17097-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82c3b000 PsLoadedModuleList = 0x82d83810
Debug session time: Tue Feb  9 09:56:36.142 2010 (GMT-5)
System Uptime: 0 days 0:31:36.921
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols
Loading unloaded module list
......
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: c0416e68, lock type that was held (value 1,2,3, or PTE address)
Arg2: c0000185, error status (normally i/o status code)
Arg3: 033d0860, current process (virtual address for lock type 3, or PTE)
Arg4: 82dcd7db, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)

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

GetPointerFromAddress: unable to read from 82da3700

ERROR_CODE: (NTSTATUS) 0xc0000185 - The I/O device reported an I/O error.

DISK_HARDWARE_ERROR: There was error with disk hardware

BUGCHECK_STR:  0x7a_c0000185

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  8771bc90 -- (.trap 0xffffffff8771bc90)
ErrCode = 00000010
eax=82dcd7db ebx=82d755bc ecx=00000000 edx=00000000 esi=84eba798 edi=82da11b0
eip=82dcd7db esp=8771bd04 ebp=8771bd50 iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
nt!IopErrorLogThread:
82dcd7db 69696969696969  imul    ebp,dword ptr [ecx+69h],69696969h ds:0023:00000069=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 82cef60a to 82d17d10

STACK_TEXT:  
8771baec 82cef60a 0000007a c0416e68 c0000185 nt!KeBugCheckEx+0x1e
8771bb60 82ce70d5 8c707fbc 8771bbb8 82d6f540 nt!MiWaitForInPageComplete+0x2fd
8771bbf4 82cc2e3f 82d6f540 82dcd7db 8c707f28 nt!MiIssueHardFault+0x3b2
8771bc78 82c815f8 00000008 82dcd7db 00000000 nt!MmAccessFault+0x2656
8771bc78 82dcd7db 00000008 82dcd7db 00000000 nt!KiTrap0E+0xdc
8771bd50 82e4966d 00000001 a6f324f7 00000000 nt!IopErrorLogThread
8771bd90 82cfb0d9 82ca8e1e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    82dcd000-82dcd012  19 bytes - nt!LdrResGetRCConfig+298
    [ d2 e9 60 fe ff ff 8b 55:3c 40 69 00 4e 44 72 71 ]
    82dcd014-82dcd02e  27 bytes - nt!LdrResGetRCConfig+2ac (+0x14)
    [ 00 c0 85 ff 7d 02 33 d2:38 00 00 00 00 00 00 00 ]
    82dcd030-82dcd033  4 bytes - nt!LdrResGetRCConfig+2c8 (+0x1c)
    [ 52 6a 00 6a:88 1c d2 82 ]
    82dcd035-82dcd0a9  117 bytes - nt!LdrResGetRCConfig+2cd (+0x05)
    [ ff 75 08 e8 82 90 e7 ff:c0 54 a7 c8 cf 54 a7 c8 ]
    82dcd0ab-82dcd12a  128 bytes - nt!LdrpSectionTableFromVirtualAddress+5f (+0x76)
    [ c2 10 00 90 90 90 90 90:9d a9 9b c0 82 48 2f e4 ]
    82dcd12c-82dcd140  21 bytes - nt!MiSessionWideReserveImageAddress+e (+0x81)
    [ 0f 31 53 c1 e8 04 56 89:02 ab d7 82 64 03 5d 9d ]
    82dcd142-82dcd15c  27 bytes - nt!MiSessionWideReserveImageAddress+24 (+0x16)
    [ 59 ff 35 f8 ee d7 82 a8:00 00 94 03 5d 9d 07 00 ]
    82dcd15e-82dcd176  25 bytes - nt!MiSessionWideReserveImageAddress+40 (+0x1c)
    [ c8 8b f9 57 56 89 7d f4:5d 9d a1 d2 f7 82 68 4f ]
    82dcd178-82dcd202  139 bytes - nt!MiSessionWideReserveImageAddress+5a (+0x1a)
    [ 00 00 00 08 77 10 ff 05:c8 cf 54 a7 00 00 00 00 ]
    82dcd204-82dcd20b  8 bytes - nt!MiSessionWideReserveImageAddress+e6 (+0x8c)
    [ c0 75 07 c7 45 f8 21 00:48 04 5d 9d c5 4a 15 8c ]
    82dcd20d-82dcd20f  3 bytes - nt!MiSessionWideReserveImageAddress+ef (+0x09)
    [ c0 8b 45:6e 92 a2 ]
    82dcd211-82dcd24b  59 bytes - nt!MiSessionWideReserveImageAddress+f3 (+0x04)
    [ eb 51 ff 75 10 57 ff 75:08 5d 9d 00 00 00 00 00 ]
    82dcd24d-82dcd27b  47 bytes - nt!MiSessionWideReserveImageAddress+12f (+0x3c)
    [ df d7 82 e8 4b 4a f2 ff:00 00 00 00 6e 92 a2 00 ]
    82dcd27e-82dcd284  7 bytes - nt!IoOpenDeviceInterfaceRegistryKey+e (+0x31)
    [ 83 ec 0c 66 ff 88 84:00 00 70 2f 4f a7 00 ]
    82dcd288-82dcd2ab  36 bytes - nt!IoOpenDeviceInterfaceRegistryKey+18 (+0x0a)
    [ 53 56 57 6a 01 be 80 0e:00 00 00 00 d0 04 5d 9d ]
    82dcd2ad-82dcd2f7  75 bytes - nt!IoOpenDeviceInterfaceRegistryKey+3d (+0x25)
    [ 00 8b d8 3b df 7c 38 8b:05 5d 9d a6 c7 41 85 68 ]
    82dcd2f9-82dcd2fc  4 bytes - nt!IoOpenDeviceInterfaceRegistryKey+89 (+0x4c)
    [ 00 8d 81 84:8e 8f a2 00 ]
    82dcd300-82dcd301  2 bytes - nt!IoOpenDeviceInterfaceRegistryKey+90 (+0x07)
    [ 66 ff:00 00 ]
    82dcd303-82dcd30e  12 bytes - nt!IoOpenDeviceInterfaceRegistryKey+93 (+0x03)
    [ 0f b7 00 66 3b c7 75 15:00 70 8f 50 a7 00 00 00 ]
    82dcd310-82dcd342  51 bytes - nt!IoOpenDeviceInterfaceRegistryKey+a0 (+0x0d)
    [ 74 0e 66 39 b9 86 00 00:00 00 00 00 88 05 5d 9d ]
    82dcd344-82dcd3a9  102 bytes - nt!LdrResFindResource+14 (+0x34)
    [ 00 c0 eb 2f ff 75 24 8b:8c 05 5d 9d e0 54 f7 82 ]
    82dcd3ac-82dcd3b6  11 bytes - nt!ExCovReadjustUnloadedModuleEntry+2c (+0x68)
    [ 66 ff 88 84 00 00 00 b9:00 00 00 00 f0 05 5d 9d ]
    82dcd3b8-82dcdf4e  2967 bytes - nt!ExCovReadjustUnloadedModuleEntry+38 (+0x0c)
    [ e8 76 d3 f0 ff 8b 35 c8:c0 00 00 00 90 00 00 00 ]
    82dcdf50-82dcdfd8  137 bytes - nt!PsRevertToSelf+86 (+0xb98)
    [ e9 ff 85 ff 74 0e 8b cf:69 69 69 69 69 69 69 69 ]
    82dcdfdb-82dcdfe7  13 bytes - nt!PopRequestShutdownWait+14 (+0x8b)
    [ e8 cb cb f8 ff 8b f8 85:00 00 00 00 00 00 00 00 ]
    82dcdfea-82dcdfed  4 bytes - nt!PopRequestShutdownWait+23 (+0x0f)
    [ c0 e9 11 01:00 00 00 00 ]
    82dcdff0-82dcdfff  16 bytes - nt!PopRequestShutdownWait+29 (+0x06)
    [ 8b 4d 08 89 4f 04 e8 7d:00 00 00 00 00 00 00 00 ]
4061 errors : !nt (82dcd000-82dcdfff)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE_4096

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE_4096

BUCKET_ID:  MEMORY_CORRUPTION_LARGE_4096

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

Hi and thank you for a quick reply! I tried running Memtest 3 times only to have my PC overheat and shut down during the tests...

If I assume the test results in errors, is a solution to memory corruption buying new RAM chips?

Thanks.

Bump...

Thanks