Blue Screens during games

[usasma]

OK, the first step is to create a System Restore point. Go to Start and type in "sysdm.cpl" (without the quotes) and press Enter.

Then click on the System Protection tab and click on the "Create" button to create a Restore Point.

Next, open up REGEDIT and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl
Right click on the key and select "Export" and export the CrashControl key to your Desktop.
Then set the CrashDumpEnabled key data value to 3 (that's to create minidumps).

Next, create a new DWord named AlwaysKeepMemoryDump and make the data value equal to 1

Then wait for the next crash to see if that'll fix it.

Alternatively, copy the following text into a Notepad document and save it as CrashFix.reg Then double click on the .reg file to merge it with your registry:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl]
"AutoReboot"=dword:00000001
"CrashDumpEnabled"=dword:00000003
"Overwrite"=dword:00000001
"LogEvent"=dword:00000001
"MinidumpsCount"=dword:00000032
"DumpFile"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,\
  74,00,25,00,5c,00,4d,00,45,00,4d,00,4f,00,52,00,59,00,2e,00,44,00,4d,00,50,\
  00,00,00
"MinidumpDir"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,\
  00,74,00,25,00,5c,00,4d,00,69,00,6e,00,69,00,64,00,75,00,6d,00,70,00,00,00
"DumpFilters"=hex(7):64,00,75,00,6d,00,70,00,66,00,76,00,65,00,2e,00,73,00,79,\
  00,73,00,00,00,00,00
"AlwaysKeepMemoryDump"=dword:00000001

 

[duckstaped]

Alright, I edited it and I haven't even crashed so.... I'm not sure what the deal is but when/if I crash, I will be back with either some minidumps or some sort of information...

thanks for the help so far!!

 

[duckstaped]

So... after about an hour of L4D2 I finally crashed... No blue screen- just a black screen and then reboot. There is no minidump file left behind either..

Looking at my System Log it looks like "Event 6, FilterManager : File System Filter 'FileInfo' (6.1, ‎2009‎-‎07‎-‎13T18:34:25.000000000Z) has successfully loaded and registered with Filter Manager." was the last thing to happen before I got an error... very well could have lead to the cause?

At the same time, though, it almost seemed like heat because of the duration of time I spent playing. Although most people have told me that if it were overheating- or if it were even the graphics card, it would more than likely artifact or freeze the image... I really don't know though..

So, for some reason, my computer isn't reporting minidumps from the type of crash I am having. That, at least, means something in itself... i'd think?

 

[usasma]

Try running the MSINFO32 command again and upload the new report. It may tell us something about the crash.

 

[duckstaped]

I couldn't find anything :\
http://www.files.failedmiserably.com/data/msinfo-12-27-09.zip

 

[usasma]

Nope, nothing in the MSINFO32 except for an AppCrash in BF2.exe

I would suspect that this is a hardware problem - most likely with your graphics card.
Heat can do anything - it depends on where the heat is causing a problem. I had one similar to this in a system a while back - diagnosed it by accident when I touched the graphics card and burnt myself!

Run it until it crashes, then unplug it and check inside the case.
VERY CAREFULLY approach the video card with your finger (so you don't get burnt) to see if it's overheating.

While in the case you can do this to check other components also (RAM, north & southbridge, cpu cooler, etc)

 

[duckstaped]

yeah... that's kind of a problem though because this machine is under warranty, and if I open it, i'm fairly sure that it will void all warranties.... which sucks.

I guess this means I should probably try to get in touch with the people who built the computer, although I have absolutely no clue on how to really do that, and if they can do anything..

 

[Hammersmith]

Old question, I know - sorry for reviving the thread.

I'm getting almost exactly the same problem as duckstaped had. My gaming laptop is randomly restarting itself, sometimes after a half hour of gaming, sometimes it will be fine and run for hours. I haven't had a single BSOD, only sudden restarts.

I've turned off the automatic restart option, I've thrown out Norton and the Windows desktop widgets, I've checked my drivers and I'm starting to wonder if I've got a dodgy piece of hardware.

One thing that attracted me to this thread is that the OP noted the same event message as I did, within a few seconds of the restart:

"File System Filter 'FileInfo' (6.1, ‎2009‎-‎07‎-‎13T18:34:25.000000000Z) has successfully loaded and registered with Filter Manager."

It seems to be a frequent event - occurring once every forty minutes to every two or three hours - which is much more frequent than my unpleasant Kernel 41 restart.

Any suggestions?

 

[duckstaped]

I'm fairly certain it was my motherboard that caused the crashes- I replaced it and got new issues, and then replaced my video card and everything was good.

I know that's vague and sucks but I was pretty sure it was the RAM- I checked each stick of RAM and none of them passed the test. So, it had to be the motherboard RAM slots being defective.... switching mobo's fixed my first problem... but, if I can recall, I did get a different problem with my video card once I got the mobo replaced.

All of this was under warranty, which is why I don't remember specifically since I didn't pay a dime. Hopefully that helps some? Do you have multiple sticks of RAM? I kept getting RAM related blue screens. I just began writing down every blue screen I got and then gave them to my tech support person, and she figured it had to be RAM or Mobo RAM slots.

Good luck!