Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Crash Analysis and Debugging › can someone view this DMP file for me?
New Posts  All Forums:Forum Nav:

can someone view this DMP file for me?

post #1 of 4
Thread Starter 
i just came home and saw my pc shutdown. but i cant tell why it shutdown because i cant view the dump file
071813-9297-01.zip 35k .zip file
i would find out for myself but it would take me forever to download the debugging tool for windows
post #2 of 4
Here ya go!
post #3 of 4
Dump Analysis (Click to show)
* *
* Bugcheck Analysis *
* *

Use !analyze -v to get detailed debugging information.

BugCheck 101, {31, 0, fffff88003d65180, 2}

*** WARNING: Unable to verify timestamp for netr28x.sys
*** ERROR: Module load completed but symbols could not be loaded for netr28x.sys
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner

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

An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arg1: 0000000000000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff88003d65180, The PRCB address of the hung processor.
Arg4: 0000000000000002, 0.

Debugging Details:







fffff800`05ec7e68 fffff800`03ad5a3a : 00000000`00000101 00000000`00000031 00000000`00000000 fffff880`03d65180 : nt!KeBugCheckEx
fffff800`05ec7e70 fffff800`03a886e7 : fffffa80`00000000 fffff800`00000002 00000000`00026160 fffffa80`0b0e8850 : nt! ?? ::FNODOBFM::`string'+0x4e3e
fffff800`05ec7f00 fffff800`03ff9895 : fffff800`0401f460 fffff800`05ec80b0 fffff800`0401f460 fffffa80`00000000 : nt!KeUpdateSystemTime+0x377
fffff800`05ec8000 fffff800`03a7b153 : 00000000`00000000 0000057f`f4dda698 00000059`00000018 fffffa80`0cacff88 : hal!HalpHpetClockInterrupt+0x8d
fffff800`05ec8030 fffff800`03a839d8 : fffff800`03bf9e80 fffff800`00000001 00000000`00000000 fffff800`05ec82c8 : nt!KiInterruptDispatchNoLock+0x163
fffff800`05ec81c0 fffff800`03a9e251 : 00000000`00000000 00000000`00000001 00000000`00000001 fffff800`03a899b0 : nt!KeFlushMultipleRangeTb+0x258
fffff800`05ec8290 fffff800`03bafb5e : 00000000`00000001 fffff800`05ec8400 fffff6fd`400a5ac0 fffff800`03b3fe1c : nt!MiFlushTbAsNeeded+0x1d1
fffff800`05ec83a0 fffff800`03bb2f26 : fffff800`03c0f6c0 00000000`00000041 00000000`00000000 fffff880`02688a30 : nt!MiAllocatePoolPages+0x4de
fffff800`05ec84e0 fffff800`03a5ed8a : fffffa80`00000000 00000000`00000000 00000000`30363832 00000000`00000000 : nt!ExAllocatePoolWithTag+0x316
fffff800`05ec85d0 fffff880`07b6016c : fffffa80`0bcc3910 fffff880`0a35947a fffff800`05ec86a0 fffffa80`0bcc3910 : nt!ExAllocatePoolWithTagPriority+0x4a
fffff800`05ec8660 fffffa80`0bcc3910 : fffff880`0a35947a fffff800`05ec86a0 fffffa80`0bcc3910 fffffa80`0eebfbd7 : netr28x+0x3916c
fffff800`05ec8668 fffff880`0a35947a : fffff800`05ec86a0 fffffa80`0bcc3910 fffffa80`0eebfbd7 00000000`00000000 : 0xfffffa80`0bcc3910
fffff800`05ec8670 fffff880`0a359b01 : fffffa80`0e06e440 00000000`00000087 fffffa80`0e06e440 fffff800`00000000 : nwifi!WPP_SF_dll+0x26a
fffff800`05ec8700 fffffa80`14b567f0 : 00000000`00000000 fffff880`024e2964 fffffa80`0ac1be90 fffffa80`0bb6d000 : nwifi!Pt6RepackRecvNBL+0x49d
fffff800`05ec8800 00000000`00000000 : fffff880`024e2964 fffffa80`0ac1be90 fffffa80`0bb6d000 fffffa80`00000000 : 0xfffffa80`14b567f0




MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image




Followup: MachineOwner

0: kd> !locks
fffff80003c24450: Unable to get value of ExpSystemResourcesList
0: kd> !locks -v -p -d
**** Dump Resource Performance Data ****

0: kd> lmvm netr28x
start end module name
fffff880`07b27000 fffff880`07bc6000 netr28x T (no symbols)
Loaded symbol image file: netr28x.sys
Image path: netr28x.sys
Image name: netr28x.sys
Timestamp: Thu Feb 26 05:02:09 2009 (49A60631)
CheckSum: 000A3BDB
ImageSize: 0009F000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4

I'd start by updating the drivers related to " Ralink RT2860 series Wireless LAN Card "

netr28x.sys - http://carrona.org/drivers/driver.php?id=netr28x.sys

BUT as you can see it says "ANALYSIS_INCONCLUSIVE"
so it might also be hardware related.
post #4 of 4

A *101 means that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can occurs when the processor is not responding or is deadlocked. We're going to need a kernel dump to properly and further analyze a *101 as you cannot go into deadlocks and such with a minidump.

Either that or enable Driver Verifier to see if it's device driver related:

Driver Verifier:
What is Driver Verifier?
Driver Verifier is included in Windows 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot driver issues. Windows kernel-mode components can cause system corruption or system failures as a result of an improperly written driver, such as an earlier version of a Windows Driver Model (WDM) driver.
Essentially, if there's a 3rd party driver believed to be at issue, enabling Driver Verifier will help flush out the rogue driver by flagging it and causing your system to BSOD.
Before enabling Driver Verifier, it is recommended to create a System Restore Point:
Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"
How to enable Driver Verifier:
Start > type "verifier" without the quotes > Select the following options -
1. Select - "Create custom settings (for code developers)"
2. Select - "Select individual settings from a full list"
3. Check the following boxes -
- Special Pool
- Pool Tracking
- Force IRQL Checking
- Deadlock Detection
- Security Checks (Windows 7)
- Concurrentcy Stress Test (Windows 8)
- DDI compliance checking (Windows 8)
- Miscellaneous Checks
4. Select - "Select driver names from a list"
5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
6. Check EVERY box that is NOT provided by Microsoft / Microsoft Corporation.
7. Click on Finish.
8. Restart.
Important information regarding Driver Verifier:
- If Driver Verifier finds a violation, the system will BSOD.
- After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will flag it, and as stated above, that will cause / force a BSOD.
If this happens, do not panic, do the following:
- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.
- Once in Safe Mode - Start > type "system restore" without the quotes.
- Choose the restore point you created earlier.
If you did not set up a restore point, do not worry, you can still disable Driver Verifier to get back into normal Windows:
- Start > Search > type "cmd" without the quotes.
- To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.
- Restart and boot into normal Windows.
How long should I keep Driver Verifier enabled for?
It varies, many experts and analysts have different recommendations. Personally, I recommend keeping it enabled for at least 36-48 hours. If you don't BSOD by then, disable Driver Verifier.
My system BSOD'd, where can I find the crash dumps?
They will be located in C:\Windows\Minidump
Any other questions can most likely be answered by this article:


New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Crash Analysis and Debugging
Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Crash Analysis and Debugging › can someone view this DMP file for me?