BSOD: Windows keeps rebooting when shutdown needed

Status
Not open for further replies.

Darmin

Posts: 10   +0
Hi,

I am getting an error when shutdown initiated on HP 6830s laptop.

Could anyone provide feedback what this minidump indicates?



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

Use !analyze -v to get detailed debugging information.

BugCheck C2, {7, cd4, 142b0603, e2303838}

Unable to load image win32k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for win32k.sys
Probably caused by : hardware ( win32k!DrvCreateMDEV+8d7 )

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

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

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 00000007, Attempt to free pool which was already freed
Arg2: 00000cd4, (reserved)
Arg3: 142b0603, Memory contents of the pool block
Arg4: e2303838, Address of the block of pool being deallocated

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


POOL_ADDRESS: e2303838

BUGCHECK_STR: 0xc2_7

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO

PROCESS_NAME: ðQlŠ

MISALIGNED_IP:
nt!KiUnexpectedInterrupt105+1
804f9deb 5d pop ebp

LAST_CONTROL_TRANSFER: from 8054a583 to 804f9deb

STACK_TEXT:
ba297c08 8054a583 000000c2 00000007 00000cd4 nt!KiUnexpectedInterrupt105+0x1
ba297c58 bf802a9b e2303838 00000000 ba297c80 nt!IopGetDriverPathInformation+0x78
ba297dbc 00000000 00c8fce4 00000000 7c90eb94 win32k!DrvCreateMDEV+0x8d7


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!DrvCreateMDEV+8d7
bf802a9b ?? ???

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: win32k!DrvCreateMDEV+8d7

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: hardware

FAILURE_BUCKET_ID: IP_MISALIGNED

BUCKET_ID: IP_MISALIGNED

Followup: MachineOwner
 
Could be anything, we need a few like 3 to 5 minidumps to try and narrow down the cause. Can you please zip up a few minidumps and attach them to your original post?
 
Status
Not open for further replies.
Back