Constant BSOD - help appreciated!

maloflora

maloflora

maloflora

Associate
Joined
19 Aug 2007
Posts
68
Hi all,

I recently built a new PC with the following specs:


  • Gigabyte Z97X-Gaming 7 - Devils Canyon Core i7 4790K CPU & Motherboard Bundle
    MSI GeForce GTX 970 Gaming Edition
    TeamGroup Vulcan RED 8GB (2x4GB) DDR3 PC3-19200C11 2400MHz
    Corsair Hydro H100i
    Phantex Enthoo Primo

After a few weeks of working fine, suddenly from nowhere I get BSODs every time I log into Windows. I'm not overclocking at all, and temps seem fine for the CPU - hovering around 30 at idle and 50 max.

I can get into windows in safe mode, but not normally. The .dmp file shows two files in red (think that means in the crash stack):
hal.dll
ntoskrnl.exe

Bug check code: 0x00000124

I've run overnight MemTest - 12 runs no errors

In windows safe mode I've run 15 mins of Prime95.

All help desperately appreciated for what to try next!
 
No it does it every time, though there is no problem at all with safe mode. I've got VCORE at 1.308 - the BIOS optimised defaults. What other voltages should I be looking at?
 
Hi,

Which Windows version is it? Also list which PSU and any peripherals connected.

Here's another little memory related test meantime - if it's running at 2400MHz, set it to 1600. If already at 1600, enable XMP. See if there's any difference.
 
maloflora said:
No it does it every time, though there is no problem at all with safe mode. I've got VCORE at 1.308 - the BIOS optimised defaults. What other voltages should I be looking at?
Click to expand...

Vcore at 1.308 at stock clocks? That would be way too high. BIOS may need an update to fix that.
 
Thanks for all the replies. Window 7 64 bit.
Monitor, Logitech G7 speakers, G11 keyboard, G500 mouse
1 SSD (boot), 1 HD
Antec TruePower New Modular 650W Power Supply - about 4 years old

Will try memory at lower speeds
 
Sorry - I was already running it at 1.2 with no overclock - in desperation I reset BIOS and it put VCORE back to 1.3

It does it on both voltages.
 
maloflora said:
Sorry - I was already running it at 1.2 with no overclock - in desperation I reset BIOS and it put VCORE back to 1.3

It does it on both voltages.
Click to expand...

Okay. If it does it on both anyway, I would flash BIOS again to have that stock Vcore lowered.

Another very brief test you could get out of the way - run a system file check (as Admin) to see if any Windows files are corrupted, if you haven't already.

List the brand/model of the SSD (not sure if it's new or four years old like the PSU).
 
Thanks all. I'd already updated BIOS to F7 - that still set VCORE at 1.308. I've tried it at 1.2 and 1.25 - same happens. Have tried XMP and 1600 memory.

Tried Windows file checker and got 'Windows Resource Protection did not find any integrity violations.'

Should I try a clean reinstall and see if it can make it through the process? Or is it a faulty MB maybe? or CPU?

Edit: The SSD is a Toshiba Thnsnh128gbst. Something like http://toshiba.semicon-storage.com/e...-ssd/hg5d.html
 
maloflora said:
Thanks all. I'd already updated BIOS to F7 - that still set VCORE at 1.308. I've tried it at 1.2 and 1.25 - same happens. Have tried XMP and 1600 memory.

Tried Windows file checker and got 'Windows Resource Protection did not find any integrity violations.'

Should I try a clean reinstall and see if it can make it through the process? Or is it a faulty MB maybe? or CPU?

Edit: The SSD is a Toshiba Thnsnh128gbst. Something like http://toshiba.semicon-storage.com/e...-ssd/hg5d.html
Click to expand...

Wait for someone more familiar with Gigabyte to hopefully recommend another BIOS version to try, that will get the voltage down to an acceptable level at stock and with default settings no manual changes. It may not even be the cause but it's not right and so would be the first item on my to-do list. If there is no BIOS that will lower Vcore voltage at stock then it does sound like a problem with the mobo, from what you're saying.
 
124 BSOD can simply be down to the "synergy" between IMC, VTT (VCCSA) and VCORE voltages - especially with 2400MHz RAM this seems to creep up now and again and can't always be simply sorted by blindly increasing/decreasing VCORE alone.

There is some delta relationship that I don't understand but when any of the voltages are outside of that it can cause instability.
 
Last time I ran into the 124 BSOD I set the VCORE around 1.3v so as to discount CPU instability and as an easy reference for the other voltages and set IMC and VTT to slightly above 1.15v (think it was 1.175) don't exceed 1.2 for that, set the RAM to 2133MHz and that worked out stable so I then started tweaking from there.
 
Success! I used System restore to take me back to before I installed Gigabyte App Centre - I think that was causing the problems. I also put memory into slots 2 and 4 - not sure if that made any difference.

Thanks for all the help - fingers crossed it stays ok!
 
You must log in or register to reply here.
Back
Top Bottom