Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD worker thread returned at bad irql

02 Oct 2012   #1

Windows 7 Home Premium 64bit
 
 
BSOD worker thread returned at bad irql

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 !!


My System SpecsSystem Spec
.

02 Oct 2012   #2
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

Welcome aboard, Vincent.
Follow it: Blue Screen of Death (BSOD) Posting Instructions.
My System SpecsSystem Spec
03 Oct 2012   #3

Windows 7 Home Premium 64bit
 
 

like this?sorry if i do wrong because i am new here
My System SpecsSystem Spec
.


03 Oct 2012   #4
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

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.
My System SpecsSystem Spec
04 Oct 2012   #5

Windows 7 Home Premium 64bit
 
 

after verifier.exe for 28 hours and here is the result..
My System SpecsSystem Spec
04 Oct 2012   #6
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

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.
My System SpecsSystem Spec
04 Oct 2012   #7

Windows 7 Home Premium 64bit
 
 

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 @.@
My System SpecsSystem Spec
04 Oct 2012   #8
Arc

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1
 
 

Dont worry, I requested a highly knowledgeable person to look at your thread.
My System SpecsSystem Spec
04 Oct 2012   #9

Microsoft Community Contributor Award Recipient

Windows 7 64-bit
 
 

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.
My System SpecsSystem Spec
04 Oct 2012   #10

Windows 7 Home Premium 64bit
 
 

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?
My System SpecsSystem Spec
Reply

 BSOD worker thread returned at bad irql




Thread Tools



Similar help and support threads for2: BSOD worker thread returned at bad irql
Thread Forum
BSOD Worker Thread Returned At Bad IRQL while using BitTorrent BSOD Help and Support
Sporadic BSOD WORKER THREAD RETURNED AT BAD IRQL BSOD Help and Support
Solved BSOD Worker thread returned at bad IRQL BSOD Help and Support
Solved BSOD while using firefox, worker thread returned bad IRQL? BSOD Help and Support
BSOD - WORKER THREAD RETURNED AT BAD IRQL ntoskrnl.exe BSOD Help and Support
BSOD: Worker thread returned at bad irql BSOD Help and Support
Solved BSOD 3 mins after startup, Worker thread returned with bad irql BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 04:16 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33