Multiple BSOD ntoskrnl.exe bugcheck_str: 0xE1 VISTA_DRIVER_FAULT

[jcwike]

-System-Provider
[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}
EventID41
Version2
Level1
Task63
Opcode0
Keywords0x8000000000000002-

TimeCreated
[ SystemTime] 2013-08-31T15:16:24.630810800Z
EventRecordID177700
Correlation-Execution

-EventDataBugcheckCode225
BugcheckParameter10xfffff80004d87ad0
BugcheckParameter20x2
BugcheckParameter30xfffffa80072e9180
BugcheckParameter40xfffffa80072e9180
SleepInProgressfalse
PowerButtonTimestamp0

-------------------------------------------------------------------------------------------------
Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (OSR)
Online Crash Dump Analysis Service
See OSR Online - The Home Page for Windows Driver Developers for more information
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18205.amd64fre.win7sp1_gdr.130708-1532
Machine Name:
Kernel base = 0xfffff800`04a1a000 PsLoadedModuleList = 0xfffff800`04c5d6d0
Debug session time: Sat Aug 31 11:15:50.704 2013 (UTC - 4:00)
System Uptime: 0 days 0:02:20.531
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

WORKER_THREAD_RETURNED_AT_BAD_IRQL (e1)
Arguments:
Arg1: fffff80004d87ad0, 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: fffffa80072e9180, workitem parameter
Arg4: fffffa80072e9180, workitem address

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

FAULTING_IP:
nt!IopProcessWorkItem+0
fffff800`04d87ad0 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 fffff80004b17ef8 to fffff80004a8fb80

STACK_TEXT:
fffff880`033afb68 fffff800`04b17ef8 : 00000000`000000e1 fffff800`04d87ad0 00000000`00000002 fffffa80`072e9180 : nt!KeBugCheckEx
fffff880`033afb70 fffff800`04d2dbae : 00000000`00000000 fffffa80`06d19b50 00000000`00000080 fffffa80`06c9d9e0 : nt! ?? ::FNODOBFM::`string'+0x58286
fffff880`033afc00 fffff800`04a808c6 : fffff880`031d7180 fffffa80`06d19b50 fffff880`031e1fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`033afc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nt!IopProcessWorkItem+0
fffff800`04d87ad0 fff3 push rbx

SYMBOL_NAME: nt!IopProcessWorkItem+0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 51db806a

FAILURE_BUCKET_ID: X64_0xE1_nt!IopProcessWorkItem+0

BUCKET_ID: X64_0xE1_nt!IopProcessWorkItem+0

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

 

[Arc]

Hello jcwike.

You have a huge lot of items at startup. Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

By doing it, you will not loss any functionality at all.



Your crash dumps are not showing any finite probable cause. In such a situation, it is better to enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any. Post it following the Blue Screen of Death (BSOD) Posting Instructions.