Tech Support Guy banner
Status
Not open for further replies.

Need Help deciphering Mini Dump

1K views 6 replies 2 participants last post by  kluftern2 
#1 ·
So here is what I debugged:

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa80065e8050, Physical Device Object of the stack
Arg3: fffffa800676b060, Functional Device Object of the stack
Arg4: fffffa8005342620, The blocked IRP

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


OVERLAPPED_MODULE: Address regions for 'athrx' and 'athrx.sys' overlap

DRVPOWERSTATE_SUBCODE: 3

IRP_ADDRESS: fffffa8005342620

DEVICE_OBJECT: fffffa80065e8050

DRIVER_OBJECT: fffffa8006115ac0

IMAGE_NAME: o2sdx64.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 47f47e6c

MODULE_NAME: o2sdx64

FAULTING_MODULE: fffffa6002bd5000 o2sdx64

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff80001cc604e to fffff80001c66650

STACK_TEXT:
fffff800`034f39f8 fffff800`01cc604e : 00000000`0000009f 00000000`00000003 fffffa80`065e8050 fffffa80`0676b060 : nt!KeBugCheckEx
fffff800`034f3a00 fffff800`01c6ebb3 : fffff800`034f3af0 00000000`00000000 00000000`00000001 fffff800`01db7f01 : nt! ?? ::FNODOBFM::`string'+0x18318
fffff800`034f3a70 fffff800`01c6f538 : fffff800`034f3cd0 fffffa80`06214602 fffff800`034f3cc8 fffffa60`00000010 : nt!KiTimerListExpire+0x333
fffff800`034f3ca0 fffff800`01c6fd9f : 000009f4`37e5e890 00000000`00000000 fffffa80`00000010 fffff800`01d89a80 : nt!KiTimerExpiration+0x1d8
fffff800`034f3d10 fffff800`01c70e72 : fffff800`01d86680 fffff800`01d86680 00000000`00000000 fffff800`01d8bb80 : nt!KiRetireDpcList+0x1df
fffff800`034f3d80 fffff800`01e3f5c0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x62
fffff800`034f3db0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!zzz_AsmCodeRange_End+0x4


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0x9F_disk.sys_CNVIRP_IMAGE_o2sdx64.sys

BUCKET_ID: X64_0x9F_disk.sys_CNVIRP_IMAGE_o2sdx64.sys

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

Please tell me what it means
 
See less See more
#2 ·
Well it is a driver error.

1. How recent is it? Check event viewer for errors, there could be more specific information.

2. Have you got anything external connected to your computer?

You should also right click computer and check device manager and see if there are any issues with any of your hardware, and the drivers installed. This will be shown by a yellow icon.
 
#4 ·
Control panel - Admin tools - Event viewer

Look for any related errors and see what it says.

I found a good explanation, look below.

'My wife has gotten a blue screen saying "Physical Memory Dump" twice today (after several hours both times). Any idea what's causing this? What does it mean?'

Someone else may come in here with a better explanation, but my understanding runs something like this:

Physical memory dumps usually involve something using entirely too much RAM when they shouldn't be. The dump takes place to free up memory so that the system could keep running. A few things can cause this, few of them good.

If it's happened twice in a day, it probably means that some piece of hardware is about to go (or already has). Safe bet would be that a memory stick (or part of one) has gone bad. Since the computer expects to be able to use that, it's discovery that it doesn't have all the memory that it thought it did traumatizes the poor thing.

Think of how you'd feel if you discovered that your basement disappeared, right after you bought a bunch of stuff that needed to be stored in there. Your reaction might be to react by just throwing stuff away that you thought was no good and just taking up space. The downside would be that you might accidentally throw away something you need.

The good news is that a RAM dump is not permanently removing information; it's just removing it for the session until necessary. Still, dumps often require restarts because something necessary disappeared. It's not really a great analogy, but I think it helps explain the idea.

You might want to do a check on the RAM or the HDD to see what the problem is. There is also a possibility that it's from a program that isn't bright enough to only use the amount of RAM that's there.
 
Status
Not open for further replies.
You have insufficient privileges to reply here.
Top