BSOD with multiple error reports at any given time

AV8R92 · 07 Mar 2015

Hello everyone,

So for about 2 months now I've been having problems with BSOD. It came out of nowhere, didn't download anything or install any new hardware, just started happening. At first the only error code I got was a 07F, I googled it and found out that it was RAM and I talked to geek squad and the guy said I needed to buy new RAM. New RAM installed and still get 07F. I also get code 0x00000050, 0x00000124, 0x00000101. 07F pops up at random times, 0124 pops up when I have the internet running. I was in the middle of a math exam when it crashed with the 0124 error code, nothing else was open except Google chrome (also tried in Firefox) and the calculator. I also use my computer for gaming, I've had it crash in World of Tanks with a 101 code and also in Flight Simulator X. FSX crashed today with the 101 code and all I have running is Active Sky 2012 (a weather generator) and FSX, I was able to start engines and start my taxi out then it crashed. Whenever it crashes though it makes a GRRRRRRR noise, not from the computer but through the speakers. Anyways, I appreciate the help with y'all looking at this. I'll attach the zip file and a few pics of the blue screen I got with my phone.

Thanks again!

Golden · 07 Mar 2015

Unfortunately your attachement doesn't contain any .dmp files needed to look at the issue. However, from your photo's I can see that TEEFER.SYS is blamed - that is a Symantec/Norton file.

As hard as it is to believe, anti-virus software are common causes of BSOD's, and Norton is one of the common ones on some systems. At this stage, the best I can suggest is to uninstall it fully, replacing it with MSE. I also suggest removing MacAfee. Then reboot and do the following:

1. Configure Windows to create minidumps:
Dump Files - Configure Windows to Create on BSOD

2. Set the paging file on C: to be the same size as the physically installed RAM:
Virtual Memory Paging File - Change

3. Set the Windows Error Reporting service to MANUAL:
Services - Start or Disable

Now please do the following:

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
Driver Verifier - Enable and Disable

Driver Verifier will cause your computer to run very sluggishly - this is normal. What it is trying to do is force your system to BSOD and isolate the offending driver/s. When it does, reboot, disable driver verifier, reboot as normal and upload the new dmp file/s here.

I recommend creating a system restore point before turning on driver verifier:
System Restore Point - Create

If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
Safe Mode

AV8R92 · 08 Mar 2015

Okay so I ran the verifier and got it to crash but no minidump files were created. I followed the directions to create it and the program dm log cant find it, its not even in the folder that the computer says it goes to. Ill still attach the log to see if you can find anything and also to pics of the bsod that I got with my phone. The first one was after verifier crashed the computer and wasn't even able to log in then the second one is when fsx just started up.

Golden · 08 Mar 2015

SaiH0763.sys is a Saitek driver - probably the joystick? Its quite old - see if you can find an updated driver.

Code:

SaiH0763     SaiH0763               SaiH0763               Kernel        Manual     Running    OK         TRUE        FALSE        16,768     126,464    0      2/15/2008 8:15:05 AM   C:\Windows\system32\DRIVERS\SaiH0763.sys         3,328

I see you haven't uninstalled Symantec/Norton - I suggest you do that.

Code:

SymDS        Symantec Data Store    Symantec Data Store    Kernel        Boot       Running    OK         TRUE        FALSE        53,248     335,872    0      4/28/2011 6:42:29 PM   C:\Windows\system32\Drivers\SEP\0C0103E8\009D.10 8,192     
SymEFA       Symantec Extended File Symantec Extended File File System   Boot       Running    OK         TRUE        FALSE        163,840    557,056    0      8/23/2011 9:21:27 PM   C:\Windows\system32\Drivers\SEP\0C0103E8\009D.10 16,384    
SymIRON      Symantec Iron Driver   Symantec Iron Driver   Kernel        System     Running    OK         TRUE        FALSE        8,192      118,784    0      9/9/2011 7:25:20 PM    C:\Windows\system32\Drivers\SEP\0C0103E8\009D.10 4,096     
SYMNETS      Symantec Network Secur Symantec Network Secur Kernel        System     Running    OK         TRUE        FALSE        24,576     258,048    0      9/6/2011 6:50:40 PM    C:\Windows\system32\Drivers\SEP\0C0103E8\009D.10 12,288    
Teefer2      Symantec Endpoint Prot Symantec Endpoint Prot Kernel        System     Running    OK         TRUE        FALSE        4,096      40,960     0      8/16/2011 5:25:27 AM   C:\Windows\system32\DRIVERS\Teefer.sys           12,288

0x7F's can often bee disk related. Unfortunately, I can't be sure without the .dmp files. Test the disk using the DOS version of SeaTools to run a LONG test:
SeaTools for DOS and Windows - How to Use

AV8R92 · 10 Mar 2015

Okay so I think I fixed the saitek driver problem. Ive uninstalled Symantec/Norton and installed MSE, and Ive set up my computer to create dump files. Just crashed with a 07F error with fltmgr.sys as the problem but no dump was created. Im gonna try running FSX again because thats what made it crash last time.

Golden · 11 Mar 2015

OK. If no .dmp files are created, then please download this .bat file and run it from your desktop. It will create a file called dump.txt in your \Temp folder. Upload that .txt file here please.

AV8R92 · 13 Mar 2015

Okay here's that file. Sorry I'm now just getting back, been busy with work.

Golden · 13 Mar 2015

I see no reason why the .dmp files should not be written.

Re-run DM Log Collector to generate a fresh ZIP file please.

AV8R92 · 14 Mar 2015

here you go

Golden · 14 Mar 2015

You have several of these messages in eventlog:

Code:

Event[73565]:
  Log Name: System
  Source: mbamchameleon
  Date: 2015-03-14T11:24:20.400
  Event ID: 61703
  Task: N/A
  Level: Information
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Rob-PC
  Description: 
Mbamchameleon Failed to obtain file name information - C00000BE

Can you update the NVidia ethernet driver - its a little outdated.

Did you run the DOS version of the LONG test of Seatools?