blue screen problem.

#1
i have this problem about BSOD. help me find solutions for this. i debug my dmp files and it was caused by ntkrnlmp.exe ( nt!IopProcessWorkItem+0 ). is it my hardrive? i have dell inspiron 5420 4gb ram 64 bit, i5 processor, nvidia video card. thanks.


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


Loading Dump File [C:\Users\dell\Desktop\New folder\051913-29515-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 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Machine Name:
Kernel base = 0xfffff800`0324c000 PsLoadedModuleList = 0xfffff800`0348f670
Debug session time: Sun May 19 09:57:04.597 2013 (UTC + 8:00)
System Uptime: 0 days 0:43:18.565
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck E1, {fffff800035b9d50, 2, fffffa800489d680, fffffa800489d680}

Probably caused by : ntkrnlmp.exe ( nt!IopProcessWorkItem+0 )

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

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

WORKER_THREAD_RETURNED_AT_BAD_IRQL (e1)
Arguments:
Arg1: fffff800035b9d50, address of worker routine (do ln on this to find guilty driver)
Arg2: 0000000000000002, IRQL returned at (should have been 0, but isn't).
Arg3: fffffa800489d680, workitem parameter
Arg4: fffffa800489d680, workitem address

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


FAULTING_IP:
nt!IopProcessWorkItem+0
fffff800`035b9d50 fff3 push rbx

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0xE1

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff80003349ef8 to fffff800032c1c00

STACK_TEXT:
fffff880`035d2b68 fffff800`03349ef8 : 00000000`000000e1 fffff800`035b9d50 00000000`00000002 fffffa80`0489d680 : nt!KeBugCheckEx
fffff880`035d2b70 fffff800`0355fede : f0363fa8`3b5dc9cd fffffa80`03cc8b50 00000000`00000080 fffffa80`03cb25f0 : nt! ?? ::FNODOBFM::`string'+0x58286
fffff880`035d2c00 fffff800`032b2906 : fffff880`033d7180 fffffa80`03cc8b50 fffff880`033e1fc0 86b3dfa2`e14b55c3 : nt!PspSystemThreadStartup+0x5a
fffff880`035d2c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nt!IopProcessWorkItem+0
fffff800`035b9d50 fff3 push rbx

SYMBOL_NAME: nt!IopProcessWorkItem+0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 5147d9c6

FAILURE_BUCKET_ID: X64_0xE1_nt!IopProcessWorkItem+0

BUCKET_ID: X64_0xE1_nt!IopProcessWorkItem+0

Followup: MachineOwner
 


usasma

Fantastic Member
Microsoft Community Contributor
#2
Good job debugging the memory dump file. We'll need some more info, and will have to "massage" the memory dump file to extract a bit more info from it. Please provide this information so we can provide a complete analysis: http://windows7forums.com/blue-screen-death-bsod/38837-how-ask-help-bsod-problem.html

Just FYI - ntkrnlmp.exe is the kernel (core) of the operating system. If this was really the cause, the system would have many more problems other than the occasional BSOD. Most often the reason for this is that a 3rd party driver did something to the kernel that it didn't like - so it expressed it's displeasure by crashing. So we'll start by looking for 3rd party drivers that are known to cause problems (from the info that I requested above).

Here's a link with a little bit of info on the error that you got: BSOD Index

While waiting for a reply, please run Driver Verifier according to these instructions: Driver Verifier Settings
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.
Top