Analyze a mini-dump for me?

K

Kil4Thril

2[H]4U
Joined
Sep 21, 2003
Messages
2,974
stats:
E5200
4GB Wintec RAM
Zotac 630i-ITX WiFi
Fujitsu HDD

Dual Prime blend and Memtest are both 24 hour stable. Temps aren't an issue. Random BSOD's, and here's my latest dump:

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


Loading Dump File [C:\Windows\Minidump\101809-20482-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\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
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c4d000 PsLoadedModuleList = 0xfffff800`02e8ae50
Debug session time: Sun Oct 18 17:56:01.671 2009 (GMT-4)
System Uptime: 1 days 6:43:29.860
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff80003cfbe10, 1, fffff80002df1991, 2}


Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!AllocateW32Process+4a )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff80003cfbe10, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff80002df1991, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ef50e0
fffff80003cfbe10

FAULTING_IP:
nt!ExAllocatePoolWithTag+5c1
fffff800`02df1991 488910 mov qword ptr [rax],rdx

MM_INTERNAL_CODE: 2

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: csrss.exe

CURRENT_IRQL: 0

TRAP_FRAME: fffff88001fe4830 -- (.trap 0xfffff88001fe4830)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff80003cfbe10 rbx=0000000000000000 rcx=fffff88003cfbe10
rdx=fffff900c1b3c340 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002df1991 rsp=fffff88001fe49c0 rbp=fffff88003cfbcc0
r8=0000000000000021 r9=fffff88003cfc140 r10=fffff88003cfbcc8
r11=000007fffffac000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!ExAllocatePoolWithTag+0x5c1:
fffff800`02df1991 488910 mov qword ptr [rax],rdx ds:0010:fffff800`03cfbe10=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002d3cbc2 to fffff80002cbef00

STACK_TEXT:
fffff880`01fe46c8 fffff800`02d3cbc2 : 00000000`00000050 fffff800`03cfbe10 00000000`00000001 fffff880`01fe4830 : nt!KeBugCheckEx
fffff880`01fe46d0 fffff800`02cbcfee : 00000000`00000001 fffff900`c1b3c000 fffffa80`05e17000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x40f90
fffff880`01fe4830 fffff800`02df1991 : 00000000`00000000 fffff880`01fe4a01 00000000`746c6644 fffff880`01fe4a70 : nt!KiPageFault+0x16e
fffff880`01fe49c0 fffff800`02cdfd06 : 00000000`00000000 00000000`00000029 fffffa80`05c5b060 fffff800`00000000 : nt!ExAllocatePoolWithTag+0x5c1
fffff880`01fe4ab0 fffff960`0018fa52 : fffffa80`05e17060 00000000`00000000 00000000`00000000 fffff800`02f8f7b6 : nt!ExAllocatePoolWithQuotaTag+0x56
fffff880`01fe4b00 fffff960`00184aaa : 00000000`00000000 fffffa80`05e17060 00000000`00000000 00000000`00000000 : win32k!AllocateW32Process+0x4a
fffff880`01fe4b30 fffff960`001880b8 : 00000000`00000000 00000000`00000002 00000000`00000002 fffff800`02ccb04b : win32k!xxxSetProcessInitState+0x2a
fffff880`01fe4b60 fffff960`00187fd6 : 00000000`00000002 00000000`000003e4 00000000`00000b08 00000000`00000000 : win32k!xxxUserNotifyProcessCreate+0xbc
fffff880`01fe4bb0 fffff800`02cbe153 : fffffa80`05c5b060 fffff880`01fe4c60 00000000`00000000 00000000`00000000 : win32k!NtUserNotifyProcessCreate+0x5e
fffff880`01fe4be0 000007fe`fd7613aa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0233f528 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fd7613aa


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!AllocateW32Process+4a
fffff960`0018fa52 488bd8 mov rbx,rax

SYMBOL_STACK_INDEX: 5

SYMBOL_NAME: win32k!AllocateW32Process+4a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc5e0

FAILURE_BUCKET_ID: X64_0x50_win32k!AllocateW32Process+4a

BUCKET_ID: X64_0x50_win32k!AllocateW32Process+4a

Followup: MachineOwner

I have updated the BIOS, and every driver, but still BSOD. What else should I check? The most strenuous thing this machine does is run a web browser.
 
Id try it with less sticks of memory (your running 4x 2gb sticks), reading it is kinda indicates memory (to me), although I havent checked win7 dmp files yet.
 
dbwillis said:
Id try it with less sticks of memory (your running 4x 2gb sticks), reading it is kinda indicates memory (to me), although I havent checked win7 dmp files yet.
Click to expand...


It's the machine listed at the beginning of the post, not my sig rig.
 
Bump. It seems to crash either on web browsing or possibly mouse scrolling. Does that help? Both IE and FF have died on me.
 
Can you share the dump somewhere?

This posting is provided "AS IS" with no warranties, and confers no rights.
 
nessus said:
Perform a surface check of the drive hosting your page file
Click to expand...


There's only one drive in the machine, and chkdsk found nothing. I ran it with the /r. Is it possible that the NVidia SATA drivers are doing it?:confused:
 
My guess, BAD CPU.

This posting is provided "AS IS" with no warranties, and confers no rights.
 
You must log in or register to reply here.
Back
Top