Overclock.net › Forums › Intel › Intel CPUs › BSOD while idle but passed Prime95 & F@H
New Posts  All Forums:Forum Nav:

BSOD while idle but passed Prime95 & F@H - Page 2

post #11 of 32
you need more vcore bro

124 bsod = vcore 95% of the time
BallaTheTrollolol
(13 items)
 
  
CPUMotherboardGraphicsRAM
2500k 5gz 1.38v asrock Extreme4 gts 450 950 mhz / gtx 460 1gb 4gb Gskill ripjaws 
Hard DriveOSPowerCase
1tb samsung f3 , 2tb wd green windows 7 64 bit home ocz modxstream 600w corsair 600t 
  hide details  
Reply
BallaTheTrollolol
(13 items)
 
  
CPUMotherboardGraphicsRAM
2500k 5gz 1.38v asrock Extreme4 gts 450 950 mhz / gtx 460 1gb 4gb Gskill ripjaws 
Hard DriveOSPowerCase
1tb samsung f3 , 2tb wd green windows 7 64 bit home ocz modxstream 600w corsair 600t 
  hide details  
Reply
post #12 of 32
Quote:
Originally Posted by jp27 View Post
you need more vcore bro

124 bsod = vcore 95% of the time
No, it usually means Vtt or a Ram issue. 101 and 2 digit codes are vcore.


Edit i notice the 2 digit codes when my vcore is way too low and 101 when its closer to stable.
Mixed Bag
(13 items)
 
  
CPUMotherboardGraphicsRAM
i7 6950X 4600Mhz ASUS Rampage V Edition 10 1080 Ti FE HyperX 12-13-13 @2400Mhz 
Hard DriveCoolingOSMonitor
Samsung 850 EVO Corsair H100i GTX Windows 10 x64 ASUS ROG PG279Q Black 27" 
KeyboardPowerCaseMouse
Corsair K95 RGB EVGA SuperNOVA 1000 P2 Corsair Air 540 Corsair RGB 
Mouse Pad
Some naked Anime with a plump butt 
  hide details  
Reply
Mixed Bag
(13 items)
 
  
CPUMotherboardGraphicsRAM
i7 6950X 4600Mhz ASUS Rampage V Edition 10 1080 Ti FE HyperX 12-13-13 @2400Mhz 
Hard DriveCoolingOSMonitor
Samsung 850 EVO Corsair H100i GTX Windows 10 x64 ASUS ROG PG279Q Black 27" 
KeyboardPowerCaseMouse
Corsair K95 RGB EVGA SuperNOVA 1000 P2 Corsair Air 540 Corsair RGB 
Mouse Pad
Some naked Anime with a plump butt 
  hide details  
Reply
post #13 of 32
Thread Starter 
Quote:
Originally Posted by youra6 View Post
One way is to view the dump files which can take a while to get it set up. Here's the link on how to do so.

The easiest way is to browse the error message via Event viewer. Here is a great page for doing so:

The other way is to wait for your system to bluescreen again and find this window:



Just a FYI, a BCcode of 124 usually refers to the VTT voltage (either its too high or too low).

116 refers to the GPU drivers

I have found from personal experience that BCcode's such as d1 could be an assortment of problems, including the Vcore and memory.
Thanks. I will definitely use this once I get a BSOD again.

Quote:
Originally Posted by 2thAche View Post
You really need 4+ hours of prime, unstable systems can pass 1 hr. Also use the OCCT test, it can save you time initially. Make it OCCT stable then move to 4-5 hr prime95 on all cores.
I'll try out OCCT once I get home. As of right now, I have been folding for about 7 hours and still no BSOD. Is it really my voltage?
post #14 of 32
Thread Starter 
Ok I got the BSOD after about 8 hours of Folding. I took a screenshot of my Event Viewer. Anyone know what these means? The logs show warnings and such since I got this rig up and running last week.

post #15 of 32
This happened to me, my LLC was boosting the VCore too high under load so I turned the VCore down in BIOS. This then made me good under load but not have enough volts at idle. My LLC is weird, it pushes the volts way above the set voltage at load.
    
CPUMotherboardGraphicsRAM
i7 3770k Gigabyte Z77-UD5H-WB Golden GTX 670 Windforce 3X 2 x 4GB GSkill RipJawsX 
Hard DriveCoolingOSMonitor
OCZ Vertex 4 64GB- WD Caviar Black 1TB Noctua NH-D14 Windows 7 Dell U2311H IPS 
KeyboardPowerCaseMouse
xArmor iOne U9BL MX Blues Seasonic x750 LIAN LI PC-T60B Logitech G500 
Audio
Modded JVC HA-RX900 
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
i7 3770k Gigabyte Z77-UD5H-WB Golden GTX 670 Windforce 3X 2 x 4GB GSkill RipJawsX 
Hard DriveCoolingOSMonitor
OCZ Vertex 4 64GB- WD Caviar Black 1TB Noctua NH-D14 Windows 7 Dell U2311H IPS 
KeyboardPowerCaseMouse
xArmor iOne U9BL MX Blues Seasonic x750 LIAN LI PC-T60B Logitech G500 
Audio
Modded JVC HA-RX900 
  hide details  
Reply
post #16 of 32
It seems to me if you crash at idle and not at load then your Vcore is going too low when your CPU downlocks at idle, and thus not supplying enough volts... unless you are using a fixed Vcore then just ignore what I said haha.
post #17 of 32
Quote:
Originally Posted by Tennobanzai View Post
Ok I got the BSOD after about 8 hours of Folding. I took a screenshot of my Event Viewer. Anyone know what these means? The logs show warnings and such since I got this rig up and running last week.

Woah dude, your log is full of red and yellow!

May want to address those issues... Eventid.net is a good place to start diagnosing the cause of errors.

Some info about the critical event ID 41 error caused by kernel-power:

Quote:
Originally Posted by Eventid.net
This event is simply recording the fact that the system was shut down ungracefully. It does not provide information on the source of the problem, but just the fact there is a problem. When this is happening there is a risk of data loss (the information still in the memory cache, that was not flushed to the hard disk). In most cases this indicates a serious problem with the operating system such as corrupted operating system files, faulty memory modules, faulty hardware drivers.

At the very least, the following steps should be performed:
1. Shut down the system, unplug it from power and wait at least 10 seconds.
2. Turn on the system, run a checkdsk against all the drives in order to identify and correct hard disk errors (this may or may not fix the problem, it depends on the nature of the corrupted files - if ay)
3. Run an antivirus and scan the whole system (it may take a while but it's a good thing to do anyway).
4. Run the Windows Update to install all the latests service pack and hotfixes applicable to that system.
5. If new hardware has been installed, disconnect it and try to obtain the latest drivers for it
6. Backup all the important data - you may not get many more chances to do that

Edited by MCBrown.CA - 1/31/11 at 4:10pm
At long last...
(13 items)
 
  
CPUMotherboardGraphicsRAM
920 D0 | 4104MHz@1.23V Big Bang XPower 5850 | 880/1050 6GB Sector 7 | 1728MHz 
Hard DriveOSMonitorPower
F115 W7P64 245BW SPI Magna 1kW 
Case
cardboard (case/loop in prog) 
  hide details  
Reply
At long last...
(13 items)
 
  
CPUMotherboardGraphicsRAM
920 D0 | 4104MHz@1.23V Big Bang XPower 5850 | 880/1050 6GB Sector 7 | 1728MHz 
Hard DriveOSMonitorPower
F115 W7P64 245BW SPI Magna 1kW 
Case
cardboard (case/loop in prog) 
  hide details  
Reply
post #18 of 32
Thread Starter 
Quote:
Originally Posted by MCBrown.CA View Post
Woah dude, your log is full of red and yellow!

May want to address those issues... Eventid.net is a good place to start diagnosing the cause of errors.

Some info about the critical event ID 41 error caused by kernel-power:
Thanks a bunch. I just realized all my BSODs are coming from the kernel-power while errors are coming from a bunch of stuff. I guess I will reinstall my OS and run some test on my RAM. This sucks since this is the 2nd set of RAM i'm on in the past week...

Anyone know where I should start? The description basically covers everything, lol.
Edited by Tennobanzai - 1/31/11 at 4:23pm
post #19 of 32
Did you try running with stock settings to eliminate any software/OS issues? I had this problem with my setup as well. I was able to run gobs and gobs of IBT, OCCT, Prime95 and even MemTest86. But I would lockup during mundane tasks such as surfing the net, idling, etc. Good members in this forum suggested that it was due to the fact I had power savings options on - EIST, Speed spectrum, etc. I turned all those off so my comp is basically at 3.8 Ghz all the time. And no issues. Of course, I started all over from scratch - meaning I discarded my previous overclock values and overclocked one more time to 3.8 ensuring I took my time and did it right.
Wife's bane
(17 items)
 
  
CPUMotherboardGraphicsRAM
i5-3570K @ 4.5 Ghz Gigabyte Z77 UD3H HIS R9-290 8 GB Samsung Wonder RAM 
Hard DriveHard DriveOptical DriveCooling
Crucial SSD for OS Samsung Spinpoint F3 Asus XSPC water block, 360 radiator, and 720 reservo... 
CoolingOSMonitorKeyboard
GPU cooling - XSPC Razer full GPU blocks Win 7 Home Premium Asus PB278Q 2560 X 1440p ISP Logitech G15 
PowerCaseMouseMouse Pad
NZXT Hale90 V2 NZXT Switch 810 Logitech G500 Steelseries QcK 
Audio
Optical out to Sony receiver; Deftech Monitor 3... 
  hide details  
Reply
Wife's bane
(17 items)
 
  
CPUMotherboardGraphicsRAM
i5-3570K @ 4.5 Ghz Gigabyte Z77 UD3H HIS R9-290 8 GB Samsung Wonder RAM 
Hard DriveHard DriveOptical DriveCooling
Crucial SSD for OS Samsung Spinpoint F3 Asus XSPC water block, 360 radiator, and 720 reservo... 
CoolingOSMonitorKeyboard
GPU cooling - XSPC Razer full GPU blocks Win 7 Home Premium Asus PB278Q 2560 X 1440p ISP Logitech G15 
PowerCaseMouseMouse Pad
NZXT Hale90 V2 NZXT Switch 810 Logitech G500 Steelseries QcK 
Audio
Optical out to Sony receiver; Deftech Monitor 3... 
  hide details  
Reply
post #20 of 32
0x124 usually means Vcore and always has for me. Either more or less.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Intel CPUs
Overclock.net › Forums › Intel › Intel CPUs › BSOD while idle but passed Prime95 & F@H