Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Crash Analysis and Debugging › Windows 7 Crashes Overnight
New Posts  All Forums:Forum Nav:

Windows 7 Crashes Overnight

post #1 of 6
Thread Starter 
These are the error codes I'm getting: 0x00000050 (0xffffffffffffff8b, 0x0000000000000001, 0xfffff8000308b55a, 0x0000000000000000)

I was also getting this one in the past: 0x00000124 (0x0000000000000000, 0xfffffa800f7ae028, 0x00000000be200000, 0x000000000005110a) but it hasn't occurred in since I set my ram back to stock speeds.

Basically the crashes only occur If I 'lock' my computer overnight. If I leave it running unlocked, then it doesn't crash -well it hasn't yet anyway. I've tried reinstalling and updating drivers, running CCleaner, can'f resolve the problem.

I'm running an i5-3570k @4.2GHz Vcore = 1.070 (under H100, 12 hr prime95 stable)
ASRock Z77 Professional
16GB Corsair Vengeance 7-8-8-24 1600MHz
Samsung 830 128GB SSD (boot drive)
2TB Seagate Barrucuda HDD
Sapphire HD7950 OC edition
LITE-ON BD-R
Centon InfiniTV 4
Corsair AX850
Windows 7 Profession 64 bit
RAT 7
Logitech G510
SteelSeries V2 headset

I'm trying to get my system stable enough to run as a 24/7 folder so any help would be greatly appreciated. Thanks!
post #2 of 6

You are probably unstable. 124 BSOD usually means more vcore so I would up it a notch or 2 and see what that does.

 

Does the system do the same at stock? Any time you have an overclock and are experiencing any kind of instability, the first thing you should do is return the system to default settings (other than RAID and the like if you have it) to rule out any other cause.

 
Gsvlip Dudyrm
(15 items)
 
Oda'maksv
(9 items)
 
CPUMotherboardGraphicsRAM
3770k @ 4.5 1.312 load Zotac Z77 ITX Wifi GTX 1070 Gaming 2126/2249 w/ Hybrid cooler TridentX 16GB 2400MHz 
Hard DriveHard DriveCoolingCooling
Samsung 850 Pro 1TB Seagate 2TB H105 EVGA Hybrid GPU cooler 
OSMonitorKeyboardPower
Windows 10 Asus MG279Q - 24" 144Hz 1080p Filco Majestic II w/ Cherry Reds Seasonic X 760W 
CaseMouseMouse PadAudio
Bitfelix Prodigy Logitech G400 Razer Goliath AKG A701 
AudioAudio
JDS Labs Objective 2 JDS Labs ODAC 
CPUMotherboardGraphicsRAM
Core i5 750 3.99 (190x21) 1.376v Load ASUS P7P55d-E Pro GTX 670 FTW <- Poor overclocker :( 8GB (4x2GB) G.Skill DDR3 1600 
Hard DriveHard DriveOptical DriveOS
Samsung 830 Evo 128GB 2x 2TB  Some DVD drive OSX 10.10.4 
MonitorPowerCaseMouse
Asus 1080P Crap TX 750 HAF 922 G400s 
Mouse PadOther
Apple Keyboard Xbox One controler 
CPURAMHard DriveHard Drive
C2D 2,26GHz under volted @ .978v 8GB  Crucial M4 64GB SSD 500GB Scorpio Black 
OSMonitorKeyboardMouse
OS X 10.0 1280x800 Built-in Trackpad 
Audio
Built-in 
  hide details  
Reply
 
Gsvlip Dudyrm
(15 items)
 
Oda'maksv
(9 items)
 
CPUMotherboardGraphicsRAM
3770k @ 4.5 1.312 load Zotac Z77 ITX Wifi GTX 1070 Gaming 2126/2249 w/ Hybrid cooler TridentX 16GB 2400MHz 
Hard DriveHard DriveCoolingCooling
Samsung 850 Pro 1TB Seagate 2TB H105 EVGA Hybrid GPU cooler 
OSMonitorKeyboardPower
Windows 10 Asus MG279Q - 24" 144Hz 1080p Filco Majestic II w/ Cherry Reds Seasonic X 760W 
CaseMouseMouse PadAudio
Bitfelix Prodigy Logitech G400 Razer Goliath AKG A701 
AudioAudio
JDS Labs Objective 2 JDS Labs ODAC 
CPUMotherboardGraphicsRAM
Core i5 750 3.99 (190x21) 1.376v Load ASUS P7P55d-E Pro GTX 670 FTW <- Poor overclocker :( 8GB (4x2GB) G.Skill DDR3 1600 
Hard DriveHard DriveOptical DriveOS
Samsung 830 Evo 128GB 2x 2TB  Some DVD drive OSX 10.10.4 
MonitorPowerCaseMouse
Asus 1080P Crap TX 750 HAF 922 G400s 
Mouse PadOther
Apple Keyboard Xbox One controler 
CPURAMHard DriveHard Drive
C2D 2,26GHz under volted @ .978v 8GB  Crucial M4 64GB SSD 500GB Scorpio Black 
OSMonitorKeyboardMouse
OS X 10.0 1280x800 Built-in Trackpad 
Audio
Built-in 
  hide details  
Reply
post #3 of 6
Thread Starter 
That was my first thought too, but the 124 error went away after I removed my RAM overclock, I haven't seen it in 10+ days. I can certainly try reverting to stock, but I crash so infrequently it would make it tough to test (it doesn't happen every time I lock overnight). I actually passed a 12hr Prime95 at Vcore = 1.065, but had a single thread fail at 12h25m, so i bumped it up a bit. Things had been running pretty smooth until about a month ago. I believe this was around the time I added a second set of 2x4GB RAM, which is why the first thing I did was remove the overclock, That seemed to pretty much fix the problem, then the 050 code popped up last night. Which as far as know, hasn't come up before.

I noticed I missed a few updates to drivers, so I updated those.

Any idea what the 050 code is?

I was also getting a 109 code that went away at the same time the 124 did.
post #4 of 6
0x50 is PAGE_FAULT_IN_NONPAGED_AREA, so essentially some kernel mode driver decided to reference memory that didn't exist in non-paged pool. This can be due to faulty/unstable RAM also - but is generally more of a software thing.
With some minidumps (if you are still getting it) we could probably get to the bottom of it!

0x109 is 100% memory problem which explained why it went away at the same time at 0x124.
Ol' Sandy
(28 items)
 
"Zeus"
(12 items)
 
Elite Preview
(6 items)
 
CPUMotherboardGraphicsRAM
Intel Xeon E3-1230v3 Gigabyte GA-Z97X-UD5H-BK MSI Gaming GTX 980 Kingston 32GB (4x8) 
Hard DriveHard DriveHard DriveHard Drive
Plextor PX-256M5S 256GB Samsung EVO 1TB Hitachi HDS721010CLA332 Hitachi HDS723020BLA642 
Hard DriveHard DriveHard DriveOptical Drive
Hitachi HDS723020BLA642 Hitachi HUA722010CLA330 WDC WD10EARS-00Z5B1 TSSTcorp CDDVDW SH-S223B 
CoolingCoolingOSMonitor
Phanteks PH-TC14PE with TY-140's Lamptron FCv5 (x2) Windows 8 Pro 64-bit Dell U2412M 
MonitorMonitorMonitorKeyboard
Dell U2412M Dell U2212HM Dell U2713HM Topre Realforce 87UB | Ducky DK9087 G2 Pro 
PowerCaseMouseMouse Pad
Corsair AX-750 Corsair Obsidian 650D Logitech G700 XTRAC Ripper XXL 
AudioAudioAudioAudio
Beyerdynamic DT-770 Pro 250ohm Schiit Bifrost DAC Schiit Asgard 2 HiVi Swan M50W 2.1 
CPUMotherboardRAMHard Drive
Intel Xeon E5-2620 Super Micro X9SRL-F-B 128GB 1333MHz LSI 9271-8i 
OSPowerCase
VMware ESXi 5.5 SeaSonic SS-400FL2 Fractal Define R3 
CPUMotherboardGraphicsRAM
Intel Core i5-3437U HP EliteBook Folio 9470m  Intel HD Graphics 4000  16GB DDR3 SDRAM 
Hard DriveOS
256GB SSD Windows 10 Insider Preview 
  hide details  
Reply
Ol' Sandy
(28 items)
 
"Zeus"
(12 items)
 
Elite Preview
(6 items)
 
CPUMotherboardGraphicsRAM
Intel Xeon E3-1230v3 Gigabyte GA-Z97X-UD5H-BK MSI Gaming GTX 980 Kingston 32GB (4x8) 
Hard DriveHard DriveHard DriveHard Drive
Plextor PX-256M5S 256GB Samsung EVO 1TB Hitachi HDS721010CLA332 Hitachi HDS723020BLA642 
Hard DriveHard DriveHard DriveOptical Drive
Hitachi HDS723020BLA642 Hitachi HUA722010CLA330 WDC WD10EARS-00Z5B1 TSSTcorp CDDVDW SH-S223B 
CoolingCoolingOSMonitor
Phanteks PH-TC14PE with TY-140's Lamptron FCv5 (x2) Windows 8 Pro 64-bit Dell U2412M 
MonitorMonitorMonitorKeyboard
Dell U2412M Dell U2212HM Dell U2713HM Topre Realforce 87UB | Ducky DK9087 G2 Pro 
PowerCaseMouseMouse Pad
Corsair AX-750 Corsair Obsidian 650D Logitech G700 XTRAC Ripper XXL 
AudioAudioAudioAudio
Beyerdynamic DT-770 Pro 250ohm Schiit Bifrost DAC Schiit Asgard 2 HiVi Swan M50W 2.1 
CPUMotherboardRAMHard Drive
Intel Xeon E5-2620 Super Micro X9SRL-F-B 128GB 1333MHz LSI 9271-8i 
OSPowerCase
VMware ESXi 5.5 SeaSonic SS-400FL2 Fractal Define R3 
CPUMotherboardGraphicsRAM
Intel Core i5-3437U HP EliteBook Folio 9470m  Intel HD Graphics 4000  16GB DDR3 SDRAM 
Hard DriveOS
256GB SSD Windows 10 Insider Preview 
  hide details  
Reply
post #5 of 6
Quote:
Originally Posted by irun4edmund View Post

That was my first thought too, but the 124 error went away after I removed my RAM overclock, I haven't seen it in 10+ days. I can certainly try reverting to stock, but I crash so infrequently it would make it tough to test (it doesn't happen every time I lock overnight). I actually passed a 12hr Prime95 at Vcore = 1.065, but had a single thread fail at 12h25m, so i bumped it up a bit. Things had been running pretty smooth until about a month ago. I believe this was around the time I added a second set of 2x4GB RAM, which is why the first thing I did was remove the overclock, That seemed to pretty much fix the problem, then the 050 code popped up last night. Which as far as know, hasn't come up before.
I noticed I missed a few updates to drivers, so I updated those.
Any idea what the 050 code is?
I was also getting a 109 code that went away at the same time the 124 did.

I'm assuming you ran 27.7 Build 2 (or newer, haven't checked lately) of Prime95, it's much more thorough and uses the newest AVX. I also assume you enabled both error checking methods, ran blend, and also set max ram to ~80% of your maximum RAM. It does none of these things by default so it will not fully test your overclock.

If you did all this and still passed 12hrs, it could be a software issue as tompsonn said. You may have corrupted your OS while overclocking, and you are 100% sure you had unstable RAM. This can easily corrupt a OS. Your current BSOD might require you to reformat to fix. If you can pass 12hrs of the newest prime95 with the above settings, reformatting would be what i'd personally do next.
The Leviathan
(20 items)
 
  
CPUMotherboardGraphicsRAM
Intel i7 6700k @ 4.7GHz MSI Z170A Gaming M7 12GB NVIDIA Titan X (Pascal) 32GB G.Skill Ripjaws V (DDR4 3200) 
Hard DriveHard DriveCoolingCooling
2x 1TB Samsung 960 PRO 193TB unRAID Server 3x 140mm Noctua NF-A14 Noctua NH-D15 
OSMonitorKeyboardPower
Windows 10 Pro x64 65" LG 65E6P (4K OLED) Ducky DK9008 Shine 3  Corsair AX860 
CaseMouseAudioAudio
Corsair Obsidian 750D Logitech G502 Proteus Sprectrum Denon X7200WA (Receiver) 2x Klipsch RF-7 (Front Speakers) 
AudioAudioAudioAudio
4x Klipsch RS-62 (Surround Speakers) Klipsch RC-64 (Center Speaker) 4x Klipsch CDT-5800-C II (Atmos Speakers) 2x SVS PB16-Ultra (Subwoofers) 
  hide details  
Reply
The Leviathan
(20 items)
 
  
CPUMotherboardGraphicsRAM
Intel i7 6700k @ 4.7GHz MSI Z170A Gaming M7 12GB NVIDIA Titan X (Pascal) 32GB G.Skill Ripjaws V (DDR4 3200) 
Hard DriveHard DriveCoolingCooling
2x 1TB Samsung 960 PRO 193TB unRAID Server 3x 140mm Noctua NF-A14 Noctua NH-D15 
OSMonitorKeyboardPower
Windows 10 Pro x64 65" LG 65E6P (4K OLED) Ducky DK9008 Shine 3  Corsair AX860 
CaseMouseAudioAudio
Corsair Obsidian 750D Logitech G502 Proteus Sprectrum Denon X7200WA (Receiver) 2x Klipsch RF-7 (Front Speakers) 
AudioAudioAudioAudio
4x Klipsch RS-62 (Surround Speakers) Klipsch RC-64 (Center Speaker) 4x Klipsch CDT-5800-C II (Atmos Speakers) 2x SVS PB16-Ultra (Subwoofers) 
  hide details  
Reply
post #6 of 6
Thread Starter 
I checked and I had run v25.11 I'm not sure If I downloaded the wrong version or if that was the latest release when I downloaded it. Anyway, I set it to run this morning while I was at work and according to the windows log, I BSOD'd 2h10m in. Error 0x000000101. I agree that my OS is probably corrupted, about to do a reformat. Thanks for the help guys
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 › Windows 7 Crashes Overnight