Random Blue Screens of Death

M

Merritt

Poster
Joined
Mar 15, 2009
Messages
116
Periodically when I am running a game through steam, and I have it minimized, my computer will blue screen and crash. Is this unusual? I would assume it is. I also seem to blue screen only when my game is minimized and rarely when its up and running. The only game to blue screen while running is L4D. Does anyone else experience such issues as this?
 
Driver issues maybe. I know most the people that get BSODs is because their drivers are conflicting with something.
 
Can you upload the minidump? It will be in C:\Windows\Minidump
You can use a free file hosting site like Mediafire or something similar. If you upload it, I'll debug it and see what it has to say.
 
s14sh3r said:
Can you upload the minidump? It will be in C:WindowsMinidump
You can use a free file hosting site like Mediafire or something similar. If you upload it, I'll debug it and see what it has to say.
Click to expand...

I'd agree, pull the mini-dump so we can have a look at it. Also, if you go into the event viewer under system and copy any errors that occur around the blue screens, it could help speed the process up.
Once we have the error info, we should be able to give a good idea of what to do next.
 
i dont know exactly how you guys want my minidump and my event view has most of its errors from system restore
 
i had the same problem turned out that it was my CPU it was dead it was Athlon i think it was like 4000+ or something cant remember the problem was fixed when i changed my CPU
 
Incase you don't have the chance to get the minidump (ie. Windows fails and it won't appear), there is also an option somewhere around the Control Panel to make it so, that after a Blue Screen the computer won't automatically reboot and the BSOD stays on the screen, giving you good time to read it and maybe take a picture of it and post it here so we can have a look at it and figure out what is going on.

To make the bluescreen stay on,

Right click on My Computer and go to properties. Go to the Advanced tab and under Startup and Recovery go to settings. Under system failure uncheck Automatically Restart.
I'm pretty sure that's it for Windows XP, but with a little bit of tinkering, you can easily find it anyway if you happen to run Vista or Windows 7. :)
 
get ccleaner and defragler. run thoughs
For l4d if your using a dual core you might need to change the affinity that works for me. simply press ctrl alt del, go to prosses find left 4 dead.exe right click, click set affinity, then un check cpu 0 or cpu 1, That should work
 
Merritt sent me the minidump and I debugged it. He asked me to explain a little bit about minidumps and what can be learned from them.

Basically, whenever your computer BSOD's, it creates a file called a minidump that contains information about the crash. In order to analyze it, you have to use a program called a debugger. The output of your minidump was this:

Code: 
Bugcheck Analysis                                   
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffff80000003, The exception code that was not handled
Arg2: fffffa6004d73002, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: fffffa800cdd9040, Parameter 1 of the exception

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


EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid

FAULTING_IP: 
BdfNdisf6+2002
fffffa60`04d73002 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  fffffa800cdd9040

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80001c41a87 to fffff80001c5f450

STACK_TEXT:  
fffff800`02fb50f8 fffff800`01c41a87 : 00000000`0000001e ffffffff`80000003 fffffa60`04d73002 00000000`00000000 : nt!KeBugCheckEx
fffff800`02fb5100 fffff800`01c5f2a9 : fffff800`02fb5838 fffffa80`0a8cbbd0 fffff800`02fb58e0 fffffa80`0a5b9470 : nt! ?? ::FNODOBFM::`string'+0x29117
fffff800`02fb5700 fffff800`01c5d577 : fffffa80`0861e9a4 fffffa80`0861e9a4 fffffa80`0a5b9640 fffff800`01c4eeed : nt!KiExceptionDispatch+0xa9
fffff800`02fb58e0 fffffa60`04d73003 : fffffa80`0a8cbbd0 fffffa60`04d7aec0 fffffa80`00000001 00000000`00000000 : nt!KiBreakpointTrap+0xb7
fffff800`02fb5a70 fffffa80`0a8cbbd0 : fffffa60`04d7aec0 fffffa80`00000001 00000000`00000000 00000000`00000000 : BdfNdisf6+0x2003
fffff800`02fb5a78 fffffa60`04d7aec0 : fffffa80`00000001 00000000`00000000 00000000`00000000 fffffa80`0a5b9470 : 0xfffffa80`0a8cbbd0
fffff800`02fb5a80 fffffa80`00000001 : 00000000`00000000 00000000`00000000 fffffa80`0a5b9470 fffff800`02fb5ab0 : BdfNdisf6+0x9ec0
fffff800`02fb5a88 00000000`00000000 : 00000000`00000000 fffffa80`0a5b9470 fffff800`02fb5ab0 fffffa80`0a5b9570 : 0xfffffa80`00000001


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
BdfNdisf6+2002
fffffa60`04d73002 ??              ???

SYMBOL_NAME:  BdfNdisf6+2002

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: BdfNdisf6

IMAGE_NAME:  BdfNdisf6.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a92aa1a

FAILURE_BUCKET_ID:  X64_0x1E_BdfNdisf6+2002

BUCKET_ID:  X64_0x1E_BdfNdisf6+2002

Followup: MachineOwner



This tells us that the BSOD was caused by BdfNdisf6.sys. A quick google says that file belongs to BitDefender Firewall. I found some info that says it's a conflict between BitDefender and your network drivers.

The first thing to to is to uninstall Bitdefender and see if that solves the crashing. If it does, you can reinstall BD and see if it happens again. If it does, try reinstalling the latest driver for your network card.


I'm fairly new to debugging myself, so if any of you pros have an further insight it would be appreciated :)
 
cammo said:
get ccleaner and defragler. run thoughs
For l4d if your using a dual core you might need to change the affinity that works for me. simply press ctrl alt del, go to prosses find left 4 dead.exe right click, click set affinity, then un check cpu 0 or cpu 1, That should work
Click to expand...

auslogics does a better more thorough job than defragler

-Blue
 
That makes pretty good sense slasher, thank you for the help, ill see what i can do to take care of the issue, and thank you everyone else for the assistance, i appreciate it!
 
Its a memory problem maybe. Most blue screens i have seen are pointed to memory issues within windows. Sometimes it may look like something else and sometimes could be. But with my exp it is the memory.

And from what i seen, it could be a driver conflct. iF you are having issues with a piece of hardware uninstall it and try again. I always let windows find drivers for me on my stuff. I never use the drivers that come wtih something i got.
 
Last edited:
still crashing. i didnt uninstall bitdefender cuz im worried that uninstalling and reinstalling will count against my 3 installs, i reinstalled the network driver and no avail. I have had 4 crashes in the last 2 hours and its really starting to piss me off. i disabled the firewall to see how things are going and so far...knock on wood...no crash.
 
You may not need to uninstall BitDefender, just stop it from running. If is automatically starts with windows, either find it in the System Tray and end it or use TaskMan to end it. Then try L4D.
 
well i mean, its my antivirus, i really dont NOT want it to run right? I just disable the firewall and its ok... so far.
 
You must log in or register to reply here.

Similar threads

Saf
  • Sticky
Official eGO Minecraft Player Guide
Replies
1
Views
1K
Saf
Saf

Latest posts

Back
Top