BSOD worker thread returned at bad irql

vincent1028 · 02 Oct 2012

i just bought acer v3 471g and i got shock i get bsod many times!Before that i updated my nvidia driver to the latest but it keep BSOD showing driver power state failure and then I ran completely restore system to factory default.Already keep my windows updated to latest but still BSOD but this time was worker thread returned at bad irql.So any idea what is going on?I just bought my laptop for 3 days

(
So i attach some minidump file as i dono how to read it.If you need further infomation please do not hesitate to tell me..Somebody please help me !!

Arc · 02 Oct 2012

Welcome aboard, Vincent.
Follow it: Blue Screen of Death (BSOD) Posting Instructions.

vincent1028 · 03 Oct 2012

like this?sorry if i do wrong because i am new here

Arc · 03 Oct 2012

Vincent, your crash dumps are not showing any finite probable cause (Stop 0xE1, there should be a device driver behind it, but it is not revealed in the dump) . 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.

Let us know the results, with the subsequent crash dumps, if any.

vincent1028 · 04 Oct 2012

after verifier.exe for 28 hours and here is the result..

Arc · 04 Oct 2012

Code:

.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck E1, {fffff80003171610, 2, fffffa8003dd9110, fffffa8003dd9110}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt!IopProcessWorkItem+0 )

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

3: kd> ln fffff80003171610
(fffff800`03171610)   nt!IopProcessWorkItem   |  (fffff800`03171658)   nt!NtWaitForMultipleObjects
Exact matches:
    nt!IopProcessWorkItem = <no type information>

No Device driver, that should be here.

Please dont mind, I am asking you ... have you selected all non-microsoft drivers in the verifier? It failed, apparently.

vincent1028 · 04 Oct 2012

oh my god means i just wasted my 28 hours let my laptop running??I did selected all the non microsoft drivers..i also did checked in "display exisiting settings" and there are drivers running @.@

Arc · 04 Oct 2012

Dont worry, I requested a highly knowledgeable person to look at your thread.

Vir Gnarus · 04 Oct 2012

He's just making sure that you set all the settings properly. Driver Verifier is designed to make Windows more sensitive to driver bugs. If it detects one, it will perform the typical response (BSOD). You shouldn't let your system just sit idle with DV 'running'. Rather, just use it normally, and hopefully the next crash you experience would be one generated by the new Driver Verifier checks, and the crashdump should reflect that. Make sure it's still active, and let it go on in the background as you do whatever you do with the PC until it crashes, then send the resulting crashdump.

vincent1028 · 04 Oct 2012

i did use it normally..i use for online..download movies and even gamming..but there is no crash found in 28 hours..so is it means my computer does not have driver problem?