Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Crash Analysis and Debugging › BSOD 0.0000003b caused by Msfs.SYS
New Posts  All Forums:Forum Nav:

BSOD 0.0000003b caused by Msfs.SYS

post #1 of 5
Thread Starter 
Hi,

Has someone encountered this one before? This is my first time ever seeing this particular BSOD code.



I am running the same overclock that was stable for 7 months roughly. CPU always stayed under 60c and voltage at just 1.32v, very safe values for this pup.

The OC was stress tested 3 times for 12 hours (Prime95 Blend with 90% memory selected) and all passed with flying colors.

GPU was at bone stock.
No drivers installed recently only the following:

-Java update (on the day it happened, today)
-Google talk (installed a month ago roughly)

What happened was I was playing a game (League of Legends, very weak in terms horsepower needed to run this one) and I get an error that Google Talk crashed. Closed the error, tabbed back to the game and after~20 minutes of gameplay I get hit with the 0x000003b BSOD.

I have not encountered this particular BSOD before from overclocking across multiple CPU's, I am a bit lost and Google search didn't provide conclusive info.

Experts, please advise.
Edited by Scorpion667 - 2/7/13 at 10:38pm
    
CPUMotherboardGraphicsRAM
3930k 4.7 1.368v RIVE BIOS 2105 680L 1330/7011 16GB Samsung 2133Mhz  
Hard DriveCoolingOSMonitor
Crucial M4 240GB  H110 after 4x H220 RMA Win 8.1 64bit XL2420T Lightboost  
KeyboardPowerCaseMouse
SS 6Gv2  EVGA 1300G2  Arc Midi R2 Zowie AM, many opticals 
Mouse PadAudioAudioAudio
SS QCK+ Xonar Essence STX AK100 MKII Shure SE846  
AudioAudioOther
Ultrasone Pro 900 Sennheiser HD700 Intel EXPI9301CT NIC 
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
3930k 4.7 1.368v RIVE BIOS 2105 680L 1330/7011 16GB Samsung 2133Mhz  
Hard DriveCoolingOSMonitor
Crucial M4 240GB  H110 after 4x H220 RMA Win 8.1 64bit XL2420T Lightboost  
KeyboardPowerCaseMouse
SS 6Gv2  EVGA 1300G2  Arc Midi R2 Zowie AM, many opticals 
Mouse PadAudioAudioAudio
SS QCK+ Xonar Essence STX AK100 MKII Shure SE846  
AudioAudioOther
Ultrasone Pro 900 Sennheiser HD700 Intel EXPI9301CT NIC 
  hide details  
Reply
post #2 of 5
Any bangs in device manager?
post #3 of 5
Thread Starter 
Just this one, been there since ages ago. Related to a GPU stress testing utility called ATItool.
    
CPUMotherboardGraphicsRAM
3930k 4.7 1.368v RIVE BIOS 2105 680L 1330/7011 16GB Samsung 2133Mhz  
Hard DriveCoolingOSMonitor
Crucial M4 240GB  H110 after 4x H220 RMA Win 8.1 64bit XL2420T Lightboost  
KeyboardPowerCaseMouse
SS 6Gv2  EVGA 1300G2  Arc Midi R2 Zowie AM, many opticals 
Mouse PadAudioAudioAudio
SS QCK+ Xonar Essence STX AK100 MKII Shure SE846  
AudioAudioOther
Ultrasone Pro 900 Sennheiser HD700 Intel EXPI9301CT NIC 
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
3930k 4.7 1.368v RIVE BIOS 2105 680L 1330/7011 16GB Samsung 2133Mhz  
Hard DriveCoolingOSMonitor
Crucial M4 240GB  H110 after 4x H220 RMA Win 8.1 64bit XL2420T Lightboost  
KeyboardPowerCaseMouse
SS 6Gv2  EVGA 1300G2  Arc Midi R2 Zowie AM, many opticals 
Mouse PadAudioAudioAudio
SS QCK+ Xonar Essence STX AK100 MKII Shure SE846  
AudioAudioOther
Ultrasone Pro 900 Sennheiser HD700 Intel EXPI9301CT NIC 
  hide details  
Reply
post #4 of 5
Could be the memory. Memtest86 on the sticks as a whole and if they pass, test each stick. Or try lowering the clock/upping the volts. Also make sure that Windows doesn't have it's own driver for anything, and if there's a chipset driver available, do it. But I'd start with the memory.
post #5 of 5
Thread Starter 
It very well could be the memory as you said. Sub-timings aren't my specialty and the mem is overclocked. As well, my CPU PLL (Phase Lock Loop) voltage is very low, 1.3v (stock 1.8v) which is lower than most 3930k's need for stability. I've seen some samples show instability with 1.625v on this particular value. Also a possibility.
I will give those things a shot, much appreciated!
Edited by Scorpion667 - 2/7/13 at 11:02pm
    
CPUMotherboardGraphicsRAM
3930k 4.7 1.368v RIVE BIOS 2105 680L 1330/7011 16GB Samsung 2133Mhz  
Hard DriveCoolingOSMonitor
Crucial M4 240GB  H110 after 4x H220 RMA Win 8.1 64bit XL2420T Lightboost  
KeyboardPowerCaseMouse
SS 6Gv2  EVGA 1300G2  Arc Midi R2 Zowie AM, many opticals 
Mouse PadAudioAudioAudio
SS QCK+ Xonar Essence STX AK100 MKII Shure SE846  
AudioAudioOther
Ultrasone Pro 900 Sennheiser HD700 Intel EXPI9301CT NIC 
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
3930k 4.7 1.368v RIVE BIOS 2105 680L 1330/7011 16GB Samsung 2133Mhz  
Hard DriveCoolingOSMonitor
Crucial M4 240GB  H110 after 4x H220 RMA Win 8.1 64bit XL2420T Lightboost  
KeyboardPowerCaseMouse
SS 6Gv2  EVGA 1300G2  Arc Midi R2 Zowie AM, many opticals 
Mouse PadAudioAudioAudio
SS QCK+ Xonar Essence STX AK100 MKII Shure SE846  
AudioAudioOther
Ultrasone Pro 900 Sennheiser HD700 Intel EXPI9301CT NIC 
  hide details  
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Crash Analysis and Debugging
Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Crash Analysis and Debugging › BSOD 0.0000003b caused by Msfs.SYS