-
T-Mobile Home Internet: Revisiting 5G connectivity for the home after two years
-
Multi-million dollar Cheyenne supercomputer auction ends with $480,085 bid — buyer walked away with 8,064 Intel Xeon Broadwell CPUs, 313TB DDR4-2400 ECC RAM, and some water leaks
Blue Screen on I7 920 , 4ghz overclock
- Thread starter Get_rekt
- Start date
Solution
jason3871
Honorable
- Jul 10, 2015
- 295
- 0
- 10,860
Increase vcore. Hope this list helps you out.
BSOD codes for overclocking
BSOD Codes for i7 x58 chipset
0x101 = increase vcore
0x124 = increase/decrease QPI/VTT first, if not increase/decrease vcore...have to test to see which one it is
0x0A = unstable RAM/IMC, increase QPI first, if that doesn't work increase vcore
0x1A = Memory management error. It usually means a bad stick of Ram. Test with Memtest or whatever you prefer. Try raising your Ram voltage
0x1E = increase vcore
0x3B = increase vcore
0x3D = increase vcore
0xD1 = QPI/VTT, increase/decrease as necessary, can also be unstable Ram, raise Ram voltage
0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances
0x50 = RAM timings/Frequency or uncore multi unstable, increase RAM voltage or adjust QPI/VTT, or lower uncore if you're higher than 2x
0x109 = Not enough or too Much memory voltage
0x116 = Low IOH (NB) voltage, GPU issue (most common when running multi-GPU/overclocking GPU)
0x7E = Corrupted OS file, possibly from overclocking. Run sfc /scannow and chkdsk /r
BSOD codes for overclocking
BSOD Codes for i7 x58 chipset
0x101 = increase vcore
0x124 = increase/decrease QPI/VTT first, if not increase/decrease vcore...have to test to see which one it is
0x0A = unstable RAM/IMC, increase QPI first, if that doesn't work increase vcore
0x1A = Memory management error. It usually means a bad stick of Ram. Test with Memtest or whatever you prefer. Try raising your Ram voltage
0x1E = increase vcore
0x3B = increase vcore
0x3D = increase vcore
0xD1 = QPI/VTT, increase/decrease as necessary, can also be unstable Ram, raise Ram voltage
0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances
0x50 = RAM timings/Frequency or uncore multi unstable, increase RAM voltage or adjust QPI/VTT, or lower uncore if you're higher than 2x
0x109 = Not enough or too Much memory voltage
0x116 = Low IOH (NB) voltage, GPU issue (most common when running multi-GPU/overclocking GPU)
0x7E = Corrupted OS file, possibly from overclocking. Run sfc /scannow and chkdsk /r
bugcheck 0x101 is a watchdog timer going off. This means some hardware did not respond within the timeout period. in this case 31 clock ticks.
I would expect that your overclock is messing up the timing to the PCI/e card. if you want to try to get the overclock to work you might try and increase the PCI/e bus speed slightly. (maybe to 103MHz)
I would expect that your overclock is messing up the timing to the PCI/e card. if you want to try to get the overclock to work you might try and increase the PCI/e bus speed slightly. (maybe to 103MHz)
TRENDING THREADS
-
News Apple debuts M4 processor in new iPad Pros with 38 TOPS on neural engine- Started by Admin
- Replies: 61
-
News Firefox user loses 7,470 opened tabs saved over two years after they can’t restore browsing session
- Started by Admin
- Replies: 54
-
Question Sapphire RX 5700 XT Nitro+ is not working in main PCIe slot ?
- Started by digows
- Replies: 24
-
Question I replaced my broken Mother Board and now my windows wont start- Started by Crystal_B
- Replies: 16
-
Facebook
Twitter
Instagram