BlueScreen problem... again.

[tilvio]

Hello...
I am having the BlueScreen problem... again. My OS is Windows 7 64 bits.

My computer randomly shuts down.
This is the event log:

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\123009-26551-01.dmp
C:\Users\GREGUAR\AppData\Local\Temp\WER-63804-0.sysdata.xml


Analysis symbol:
Rechecking for solution: 0
Report Id: 123009-26551-01
Report Status: 0

I'm also attaching the zipped .dmp and .xml files for more information.

Thanks in advance!
Silvio.

 

[Georgian19]

same problems in other topic i have.

 

[Capt.Jack Sparrow]

Hello...
I am having the BlueScreen problem... again. My OS is Windows 7 64 bits.

My computer randomly shuts down.
This is the event log:

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\123009-26551-01.dmp
C:\Users\GREGUAR\AppData\Local\Temp\WER-63804-0.sysdata.xml


Analysis symbol:
Rechecking for solution: 0
Report Id: 123009-26551-01
Report Status: 0

I'm also attaching the zipped .dmp and .xml files for more information.

Thanks in advance!
Silvio.

Hi Silvio, Welcome to SF,

[FONT=Segoe UI, Arial]On Thu 31-12-2009 01:45:24 your computer crashed
This was likely caused by the following module: [FONT=Segoe UI, Arial]ntoskrnl.exe[/FONT]
Bugcheck code: 0x7A (0xFFFFF6FC50051D00, 0xFFFFFFFFC000009C, 0x52D02820, 0xFFFFF8A00A3A0E8C)
Error: [FONT=Segoe UI, Arial]KERNEL_DATA_INPAGE_ERROR[/FONT]
Dump file: C:\Windows\Minidump\123009-26551-01.dmp
[/FONT][FONT=Segoe UI, Arial]file path: C:\Windows\system32\ntoskrnl.exe
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.
[/FONT]

I guess the problems is with Memory

Download memtestx86 and run for 5 passes

Run the System Integrity Checker - Start sfc/ scannow right click and Run as Administrator

Also Run the Memory Diagnostics & HD Diagnostic

Hope this helps

 

[zigzag3143]

Hello...
I am having the BlueScreen problem... again. My OS is Windows 7 64 bits.

My computer randomly shuts down.
This is the event log:

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\123009-26551-01.dmp
C:\Users\GREGUAR\AppData\Local\Temp\WER-63804-0.sysdata.xml


Analysis symbol:
Rechecking for solution: 0
Report Id: 123009-26551-01
Report Status: 0

I'm also attaching the zipped .dmp and .xml files for more information.

Thanks in advance!
Silvio.

Silvio

Hi and welcome


This crash had several things going on first some drivers from 2006. second memory (probably because of this)DISK_HARDWARE_ERROR: There was error with disk hardware


That being the case you should
run chkdsk/f
run sfc /scannow

If those dont fix it download and run memtestx86 and run 5 passes

Hope this helps and BACKUP just n case


Ken J+

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


Loading Dump File [C:\Users\K\Desktop\123009-26551-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 x64
Product: WinNt, suite: TerminalServer SingleUserTS
[B]Built by: 7600.16385.amd64fre.win7_rtm.090713-1255[/B]
Machine Name:
Kernel base = 0xfffff800`02a65000 PsLoadedModuleList = 0xfffff800`02ca2e50
Debug session time: Wed Dec 30 18:12:26.283 2009 (GMT-5)
System Uptime: 0 days 4:59:46.062
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7A, {fffff6fc50051d00, ffffffffc000009c, 52d02820, fffff8a00a3a0e8c}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+34cde )

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

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

[B]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: fffff6fc50051d00, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000009c, error status (normally i/o status code)
Arg3: 0000000052d02820, current process (virtual address for lock type 3, or PTE)
Arg4: fffff8a00a3a0e8c, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)[/B]

Debugging Details:
------------------
[SIZE=3][U][I][B]

ERROR_CODE: (NTSTATUS) 0xc000009c - STATUS_DEVICE_DATA_ERROR

DISK_HARDWARE_ERROR: There was error with disk hardware[/B][/I][/U][/SIZE]

BUGCHECK_STR:  0x7a_c000009c

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
[B]
PROCESS_NAME:  svchost.exe[/B]

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880047593a0 -- (.trap 0xfffff880047593a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000006972 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002daba26 rsp=fffff88004759530 rbp=fffff8a0007b7010
 r8=fffff8a0008b7aa0  r9=fffff880047596ec r10=0000000000000001
r11=fffff880047595a8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!CmpFindSubKeyByNameWithStatus+0x86:
fffff800`02daba26 663907          cmp     word ptr [rdi],ax ds:0d01:00000000`00000000=????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002b4a438 to fffff80002ad6f00

STACK_TEXT:  
fffff880`04759088 fffff800`02b4a438 : 00000000`0000007a fffff6fc`50051d00 ffffffff`c000009c 00000000`52d02820 : nt!KeBugCheckEx
fffff880`04759090 fffff800`02ac8d8b : fffffa80`02c44e90 fffff880`04759200 fffff800`02c61b40 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x34cde
fffff880`04759170 fffff800`02af1da4 : 00000000`00000000 00000000`00000000 ffffffff`ffffffff fffff880`047594f0 : nt!MiIssueHardFault+0x28b
fffff880`04759240 fffff800`02ad4fee : 00000000`00000000 00000000`c0000034 00000000`00000000 fffff800`02c09646 : nt!MmAccessFault+0x11c4
fffff880`047593a0 fffff800`02daba26 : fffff8a0`007b7010 00000000`c0000034 fffff8a0`008b7aa0 00000000`00120012 : nt!KiPageFault+0x16e
fffff880`04759530 fffff800`02dae8ef : fffff8a0`0923da2c fffff880`04759ad0 fffff880`04759670 fffff8a0`00000000 : nt!CmpFindSubKeyByNameWithStatus+0x86
fffff880`047595b0 fffff800`02dcd764 : fffff800`02dadae0 00000000`00000000 fffffa80`04794b10 00000000`00000001 : nt!CmpParseKey+0xe0f
fffff880`04759880 fffff800`02dd2876 : fffffa80`04794b10 fffff880`04759a00 00000000`00000040 fffffa80`018dca50 : nt!ObpLookupObjectName+0x585
fffff880`04759980 fffff800`02db1bec : 00000000`00000000 00000000`00000000 fffff880`04759c01 00000000`00000000 : nt!ObOpenObjectByName+0x306
fffff880`04759a50 fffff800`02db3d3b : 00000000`0644e4a0 00000000`00000001 00000000`0644e528 00000000`00000000 : nt!CmOpenKey+0x28a
fffff880`04759ba0 fffff800`02ad6153 : 00000000`00000008 00000000`00000000 00000000`002cd001 fffffa80`00000004 : nt!NtOpenKeyEx+0xf
fffff880`04759be0 00000000`77460e0a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0644e438 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77460e0a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+34cde
fffff800`02b4a438 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+34cde

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

FAILURE_BUCKET_ID:  X64_0x7a_c000009c_nt!_??_::FNODOBFM::_string_+34cde

BUCKET_ID:  X64_0x7a_c000009c_nt!_??_::FNODOBFM::_string_+34cde

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

 

[usasma]

Free Hard Drive Diagnostic: HD Diagnostic

Then run this:

CHKDSK /R:
Run CHKDSK /R from an elevated (Run as adminstrator) Command Prompt.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.

Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"

CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry.
Copy/paste the results into your next post.