| Page 1 of 1 |
sausje
Banned
Posts: 17716
Location: Limboland, Netherlands
|
|
| Back to top |
|
 |
garus
VIP Member
Posts: 34200
|
 Posted: Sun, 20th May 2012 15:27 Post subject: |
|
|
snip
Last edited by garus on Tue, 27th Aug 2024 21:34; edited 1 time in total
|
|
| Back to top |
|
|
sausje
Banned
Posts: 17716
Location: Limboland, Netherlands
|
| Posted: Sun, 20th May 2012 15:29 Post subject: |
|
|
Can't, the bluescreen gets stuck at 100 and doesn't do anything further...
So there is no dump..
Proud member of Frustrated Association of International Losers Failing Against the Gifted and Superior (F.A.I.L.F.A.G.S)
|
|
| Back to top |
|
|
garus
VIP Member
Posts: 34200
|
| Posted: Sun, 20th May 2012 15:33 Post subject: |
|
|
snip
Last edited by garus on Tue, 27th Aug 2024 21:34; edited 1 time in total
|
|
| Back to top |
|
|
sausje
Banned
Posts: 17716
Location: Limboland, Netherlands
|
| Posted: Sun, 20th May 2012 15:35 Post subject: |
|
|
Thing is, i cannot reproduce the BSOD, it just happens at random moments (just now when closing D3 for example, and sometimes overnight)..
So it is kinda hard to check what hardware is causing it, but my guess is the CPU, but what... Doubt it would be the OC... Otherwise i might have a faulty CPU..
Proud member of Frustrated Association of International Losers Failing Against the Gifted and Superior (F.A.I.L.F.A.G.S)
|
|
| Back to top |
|
|
garus
VIP Member
Posts: 34200
|
| Posted: Sun, 20th May 2012 15:35 Post subject: |
|
|
snip
Last edited by garus on Tue, 27th Aug 2024 21:34; edited 1 time in total
|
|
| Back to top |
|
|
sausje
Banned
Posts: 17716
Location: Limboland, Netherlands
|
| Posted: Sun, 20th May 2012 15:41 Post subject: |
|
|
Well i'm not going to test removing hardware that i daily use and will miss when removed, till i actually know what COULD cause it.
Removing 1 stick of ram put me back on 4gb, wich puts me on borderline ram usage in most games already, removing 1 vidcard sets me back quite some fps in most games..
Other parts i wouldn't know what would be causing this error.
I could try stock settings, but i already forgot how to put them back, need Werelds for that 
Proud member of Frustrated Association of International Losers Failing Against the Gifted and Superior (F.A.I.L.F.A.G.S)
|
|
| Back to top |
|
|
Werelds
Special Little Man
Posts: 15098
Location: 0100111001001100
|
|
| Back to top |
|
|
garus
VIP Member
Posts: 34200
|
| Posted: Sun, 20th May 2012 15:47 Post subject: |
|
|
snip
Last edited by garus on Tue, 27th Aug 2024 21:34; edited 1 time in total
|
|
| Back to top |
|
|
sausje
Banned
Posts: 17716
Location: Limboland, Netherlands
|
| Posted: Sun, 20th May 2012 15:47 Post subject: |
|
|
| Werelds wrote: | Just reduce the OC by 200 (take the multiplier down by 2 steps). Should be enough to rule out an unstable OC  |
So this is error pure based on unstable OC?
Even tho i'm only on 4.2 and we tested it 
Proud member of Frustrated Association of International Losers Failing Against the Gifted and Superior (F.A.I.L.F.A.G.S)
|
|
| Back to top |
|
|
|
|
|
| Back to top |
|
|
|
|
| Posted: Tue, 22nd May 2012 05:19 Post subject: |
|
|
Error code 101 is vcore related. Either up your vcore or lower your overclock, simple as that. Whichever the case is, your CPU isnt getting enough juice to be running at that frequency. Ive found that this problem also occurs if your PSU is going bad or if youre running your rig off a power strip which is giving power to multiple devices.
Few things you can try
1. up the vcore or lower your overclock
2. Give your PC direct power either from a wall socket or a surge protector power strip that doesn't have any other devices on it
3. Check and make sure your PSU's 12V rail is actually giving near 12V (preferably with a multimeter). If you use BIOS, just post here what your readings are in your BIOS.
This error code also shows up in some rare cases when the CPU overheats. But Im pretty sure you keep an eye on your temps as I assume most people these days do
Also get CPU-Z and post here what your idle and load vcores are. If idle vcore is HIGHER than load vcore, then turn off vdroop in your BIOS.
ASUS Maximus XII Formula | Core i9 10900k @ 5.2Ghz | 32GB G.Skill DDR4 4200Mhz | EVGA RTX 3080 Ti FTW3 Ultra Hydro Copper | ASUS ROG PG35VQ
|
|
| Back to top |
|
|
sausje
Banned
Posts: 17716
Location: Limboland, Netherlands
|
| Posted: Tue, 22nd May 2012 10:13 Post subject: |
|
|
Well we did indeed only up the multiplier, not the vcore at all, because then it would run too hot at anything higher then 4.2
But i'm not going to mess with vcore settings, ill leave those things to Werelds.
Proud member of Frustrated Association of International Losers Failing Against the Gifted and Superior (F.A.I.L.F.A.G.S)
|
|
| Back to top |
|
|
Werelds
Special Little Man
Posts: 15098
Location: 0100111001001100
|
| Posted: Tue, 22nd May 2012 10:35 Post subject: |
|
|
Again, reduce the MP by a step or two to test it. Even if it's lacking VCore, lowering the target frequency will also need less voltage.
|
|
| Back to top |
|
|
sausje
Banned
Posts: 17716
Location: Limboland, Netherlands
|
| Posted: Tue, 22nd May 2012 13:21 Post subject: |
|
|
I will do that on my next reboot/bluescreen, cba to reboot now
Proud member of Frustrated Association of International Losers Failing Against the Gifted and Superior (F.A.I.L.F.A.G.S)
|
|
| Back to top |
|
|
Frant
King's Bounty
Posts: 24642
Location: Your Mom
|
| Posted: Tue, 22nd May 2012 13:34 Post subject: |
|
|
CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Drop clocks and vcore.
Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn!
"The sky was the color of a TV tuned to a dead station" - Neuromancer
|
|
| Back to top |
|
|
sausje
Banned
Posts: 17716
Location: Limboland, Netherlands
|
| Posted: Tue, 29th May 2012 13:06 Post subject: |
|
|
Well set MP back to 40, and now getting other BSOD: STOP 0x00000124
This one is happening virtually twice a day...
Proud member of Frustrated Association of International Losers Failing Against the Gifted and Superior (F.A.I.L.F.A.G.S)
|
|
| Back to top |
|
|
|
|
| Posted: Tue, 29th May 2012 14:47 Post subject: |
|
|
How much vcore your board gives on auto settings. For 4-4.2 ghz stock voltage should be enough.
|
|
| Back to top |
|
|
sausje
Banned
Posts: 17716
Location: Limboland, Netherlands
|
| Posted: Tue, 29th May 2012 15:02 Post subject: |
|
|
Well that was the part Werelds got confused at, as we had all sorts values, but none the same..
According to CPU-Z 1.044v atm
Proud member of Frustrated Association of International Losers Failing Against the Gifted and Superior (F.A.I.L.F.A.G.S)
|
|
| Back to top |
|
|
|
|
| Posted: Tue, 29th May 2012 15:45 Post subject: |
|
|
| sausje wrote: | Well set MP back to 40, and now getting other BSOD: STOP 0x00000124
This one is happening virtually twice a day... |
Error coder 124 is PLL/VTT related. Trying upping them by just a bit. Otherwise lower your clock speeds a bit more
ASUS Maximus XII Formula | Core i9 10900k @ 5.2Ghz | 32GB G.Skill DDR4 4200Mhz | EVGA RTX 3080 Ti FTW3 Ultra Hydro Copper | ASUS ROG PG35VQ |
|
| Back to top |
|
|
sausje
Banned
Posts: 17716
Location: Limboland, Netherlands
|
| Posted: Tue, 29th May 2012 16:00 Post subject: |
|
|
So you are telling me to basically drop my OC fully?
What's the point of me having those parts and not being able to OC ffs 
Proud member of Frustrated Association of International Losers Failing Against the Gifted and Superior (F.A.I.L.F.A.G.S)
|
|
| Back to top |
|
|
|
|
|
| Back to top |
|
|
garus
VIP Member
Posts: 34200
|
| Posted: Tue, 29th May 2012 16:27 Post subject: |
|
|
snip
Last edited by garus on Tue, 27th Aug 2024 21:36; edited 1 time in total
|
|
| Back to top |
|
|
Slizza
Posts: 2345
Location: Bulgaria
|
| Posted: Tue, 29th May 2012 20:42 Post subject: |
|
|
just set to defaults and see if it persists.
Then learn to over clock it yourself and start again if all is clear.
Overclocking is child's play on sandy bridge. Old women coild do it.
Corsair 750D :: 750W DPS-G:: Asus x370 PRO :: R7 1800X ::16gb DDR4 :: GTX 1070::525gb SSD::Coolermaster 240MM AIO::
|
|
| Back to top |
|
|
Frant
King's Bounty
Posts: 24642
Location: Your Mom
|
| Posted: Tue, 29th May 2012 22:08 Post subject: |
|
|
Run memtest+ overnight to test the RAM.
If memtest passes with no errors, then it's a good chance you need a tad more vcore on the CPU.
Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn!
"The sky was the color of a TV tuned to a dead station" - Neuromancer
|
|
| Back to top |
|
|
Frant
King's Bounty
Posts: 24642
Location: Your Mom
|
| Posted: Tue, 29th May 2012 22:14 Post subject: |
|
|
http://www.xtremesystems.org/forums/showthread.php?266589-The-OverClockers-BSOD-code-list
The OverClockers BSOD code list
BSOD codes for overclocking
0x101 = increase vcore
0x124 = increase/decrease QPI/VTT first, if not increase/decrease vcore...have to test to see which one it is
BSOD Codes for SandyBridge
0x124 = add/remove vcore or QPI/VTT voltage (usually Vcore, once it was QPI/VTT)
0x101 = add more vcore
Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn!
"The sky was the color of a TV tuned to a dead station" - Neuromancer
|
|
| Back to top |
|
|
| Page 1 of 1 |
All times are GMT + 1 Hour |
