Can anyone read minidumps?

Looks like it's Chrome, or possible a plugin that you're using...

Code: 
MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000005003, The subtype of the bugcheck.
Arg2: fffff70001080000
Arg3: 000000000000cc49
Arg4: 0000b7d800019890

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


BUGCHECK_STR:  0x1a_5003

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

[color=orange]PROCESS_NAME:  chrome.exe[/color]

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800030fe0fc to fffff80003092c40

STACK_TEXT:  
fffff880`0ad8f9c8 fffff800`030fe0fc : 00000000`0000001a 00000000`00005003 fffff700`01080000 00000000`0000cc49 : nt!KeBugCheckEx
fffff880`0ad8f9d0 fffff800`030a019e : 00000000`00000001 00000000`038a1000 fffff880`0ad8fc20 fffff680`0001c508 : nt! ?? ::FNODOBFM::`string'+0x2a80f
fffff880`0ad8fac0 fffff800`03090d6e : 00000000`00000001 00000000`038a1000 00000000`00000001 00000000`0000001e : nt!MmAccessFault+0x5de
fffff880`0ad8fc20 00000000`269c0a65 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0033f308 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x269c0a65


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+2a80f
fffff800`030fe0fc cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+2a80f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+2a80f

BUCKET_ID:  X64_0x1a_5003_nt!_??_::FNODOBFM::_string_+2a80f

Followup: MachineOwner
---------
 
Last edited:
I'm at work and really didn't have time to check them all. I should have checked a few earlier, sorry for not doing that.

I just looked at a few of them and I see a lot of things that point to vmware and memory corruption. Looks like this:

Code: 
READ_ADDRESS:  c1292580 

CURRENT_IRQL:  0

FAULTING_IP: 
nt!MiDispatchFault+1c0
80850468 8b8481f80c0000  mov     eax,dword ptr [ecx+eax*4+0CF8h]

CUSTOMER_CRASH_COUNT:  5

DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP

BUGCHECK_STR:  0xA

[color=orange]PROCESS_NAME:  vmserverdWin32.[/color]

TRAP_FRAME:  b8325bd4 -- (.trap 0xffffffffb8325bd4)
ErrCode = 00000000
eax=00284222 ebx=c0014220 ecx=c0881000 edx=00000007 esi=00000008 edi=88a87ca0
eip=80850468 esp=b8325c48 ebp=b8325cc8 iopl=0         nv up ei ng nz ac pe cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010297
nt!MiDispatchFault+0x1c0:
80850468 8b8481f80c0000  mov     eax,dword ptr [ecx+eax*4+0CF8h] ds:0023:c1292580=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 80850468 to 8088c9cb

STACK_TEXT:  
b8325bd4 80850468 badb0d00 00000007 80843e44 nt!KiTrap0E+0x2a7
b8325cc8 8085f030 00000021 02844000 c0014220 nt!MiDispatchFault+0x1c0
b8325d4c 8088c800 00000001 02844000 00000001 nt!MmAccessFault+0xe30
b8325d4c 7c86166d 00000001 02844000 00000001 nt!KiTrap0E+0xdc
WARNING: Frame IP not in any known module. Following frames may be wrong.
00bbe8c8 00000000 00000000 00000000 00000000 0x7c86166d


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiDispatchFault+1c0
80850468 8b8481f80c0000  mov     eax,dword ptr [ecx+eax*4+0CF8h]

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiDispatchFault+1c0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4b7a90ad

[color=orange]IMAGE_NAME:  memory_corruption[/orange]

FAILURE_BUCKET_ID:  0xA_nt!MiDispatchFault+1c0

BUCKET_ID:  0xA_nt!MiDispatchFault+1c0

Followup: MachineOwner
---------
 
What are you using to view them? i have windbg which reads crashdump but its not showing me any of that info.
 
Windbg.

You have to add the debug symbols:
1. Open file, choose Symbol Path
2. Delete whatever is already there and enter:
Code: 
SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Save the workspace and close Windbg. Open it again.

Then open your crash dump:
1. File, open crash dump, choose your file

Now analyze it:
1. in the text box to the right of kd> enter:
Code: 
!analyze -v

It will analyze the dump and spit out the pretty info.
 
You also have a TDR (timeout detection and recovery) failure in your nvidia driver, and a kernel stack corruption.

I'm going to guess bad memory or unstable OC. Try memtest and revert your OC if you have one.
 
It seems this is the issues
6-11 nvlddmkm
6-19 Chrome.exe
6-30 BFBC2Game.exe
7-19 svchost.exe
8-15 Steam.exe
8-16 System(different than others)
8-17 svchost.exe
8-24 chrome.exe

Thoughts?
 
Tawnos said:
You also have a TDR (timeout detection and recovery) failure in your nvidia driver, and a kernel stack corruption.

I'm going to guess bad memory or unstable OC. Try memtest and revert your OC if you have one.
Click to expand...

which one is that in? There is no OC on this machine.
 
Run memtest86+ for at least 3 runs, this will rule out your CPU and RAM.
 
German Muscle said:
Should i do each stick by itself or all of them together?
Click to expand...
Altogether (because if your RAM is fine, you'll save a ton of time vs if you did them individually). Just know how big each stick is and which DIMM slots they are in (DIMM0, DIMM1, DIMM2, DIMM3). When and if errors come up, just use basic math to determine which stick the errors are in (and then you can individually test said stick -- errors should come up rather quickly). Memtest86+ will report where in the entire addressing space the error occurred, i.e. at 748mb (first stick if all sticks are 1GB) or 3711mb (fourth stick if all sticks are 4GB).

0 MB to 1024 MB is DIMM0,
1025 MB to 2048 MB is DIMM1,
etc.

And if you are OC'd and get errors, try stock speeds. If you don't get errors then, it may be that your overclock was too high. If that is the case, you may want to then try running IntelBurnTest for 10 runs on Maximum; if it fails this then it's definitely because your overclock is too much and your CPU can't handle it.
 
Last edited:
German Muscle said:
which one is that in? There is no OC on this machine.
Click to expand...

6-11 is the TDR. That means the OS sent a packet through the scheduler to the video card, and the video card didn't respond in time. This is usually when you see the message in the system notification area that says "windows has detected an error blah blah blah recovered". If it happens too many times within a certain period, it's considered an unrecoverable error and the system bugchecks.

The remainder of them all have to do with memory, whether it's mapping or unmapping, corrupted memory, etc. Since it hits a variety of processes and a few different bugchecks, your most likely culprit is bad memory. While other things can cause them, they're less likely to produce this class of errors.
 
I just checked and i have a full stick not being seen. Ill take that out and do a memtest. If there are any issues ill call PNY as this memory supposedly has a lifetime warranty.
 
I am shocked that no one has mentioned using the application whocrashed. A really nice simple straight forward program to read minidumps. It basically tells you exactly what caused the issue.
 
thedocta45 said:
I am shocked that no one has mentioned using the application whocrashed. A really nice simple straight forward program to read minidumps. It basically tells you exactly what caused the issue.
Click to expand...

That's because I use ntsd daily, so it's already installed, plus it provides a useful stack and other info. Why would I use something that gives me info that isn't as useful? :)
 
You must log in or register to reply here.
Back
Top