My Problem was
When I start my PC and use it after some time(not specific) it shows blue screen and then my PC restarts itself. It occurs 2 -4 times a day. This problem generally occurs due to improper installed hardware or any software or their drivers.
First thing to Do
We have to stop auto restart first so that we can read the blue screen error and then find the solution. To do this Right click on My Computer > Properties > Advanced > Start up and Recovery Settings. Look for System Failure and
remove check-mark which is before Automatically Restart. OK. Next time when you get blue screen error your PC will not restart.
So I got the following blue screen error(Click Here for Original Screen Shot)
When I start my PC and use it after some time(not specific) it shows blue screen and then my PC restarts itself. It occurs 2 -4 times a day. This problem generally occurs due to improper installed hardware or any software or their drivers.
First thing to Do
We have to stop auto restart first so that we can read the blue screen error and then find the solution. To do this Right click on My Computer > Properties > Advanced > Start up and Recovery Settings. Look for System Failure and
remove check-mark which is before Automatically Restart. OK. Next time when you get blue screen error your PC will not restart.
So I got the following blue screen error(Click Here for Original Screen Shot)
It is 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL error.
Looking for the Cause
We have to study memory dump files. That are
1. A complete memory dump or a kernel memory dump that are usually saved in the C:\Windows directory and named MEMORY.DMP.
2. A small memory dump, aka a minidump, which are usually saved in the C:\Windows\Minidump directory.
Sometimes these are hidden by Windows. To show /unhide these hidden files click here.
Once you get dump files you will need debugger to analyze them. Download Debugging Tools for Windows.
Click here for more information about Using Debugging Tools for Windows to study memory dump files.
Using these tools I got following report-
Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini082809-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 XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.090206-1234
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Fri Aug 28 01:26:15.312 2009 (GMT-7)
System Uptime: 0 days 1:52:30.058
Loading Kernel Symbols
...............................................................
.......................................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000D1, {ffffffff, 2, 0, b733e258}
Unable to load image bdfndisf.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for bdfndisf.sys
*** ERROR: Module load completed but symbols could not be loaded for bdfndisf.sys
Probably caused by : bdfndisf.sys ( bdfndisf+29e4 )
Followup: MachineOwner
---------
So as I highlighted the Blue Screen Error and crashing was due to bdfndisf.sys. When I searched about bdfndisf.sys, I found that it is related to BitDefender Antivirus installed on my PC.
And the Solution
Perform the following procedure to get rid of blue screen error:
1. Go to Start >> Run and type ncpa.cpl
Hit OK.
2. Then right-click on Local Area Connection and choose Properties.
3. In that list uncheck BitDefender Firewall NDIS Filter Driver. OK. Now you will not get blue screen error.
Another Solution
Just upgrade to latest BitDefender. It is totally free.
2 comments:
...one of the best, most complete answers to a complex, potentially time consuming issue.
Your explanation allowed me to quickly get back to productive computing!
Thank you!
Very nice guide, I tryed this out tho, and for me the debug thingy ended up with "CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE" or just Inconclusive on the most things.
Any ideas what to do?
Mail me at milk-mxr@hotmail.com, Thanks.
Post a Comment