Hi All
Wanted to get your opinion on an issue I've started to notice with my machine.
I recently upgraded basically everything but my gpu in the system and then did a new Win 10 reinstall.
New specs:
MB: MSI MEG Z390 Godlike
Ram: 16 GB (2x8), 3600 DDR4 - installed in the correct slots per MB manual.
CPU: i9 9900K
PSU: Corsair AX1000
System Storage: Samsung 970 pro 512 GB nvme SSD
The entire system is watercooled, and ambient temperatures are quite stable, even under load I have not seen any components go above 55 degrees Celsius.
After the new install the PC was working fine, so after a couple of days of just light use I started jumping into overclocking both CPU and the GPU. I started with the GPU since that's basically the only one constant in the build and had previously stable clocks on it. so i replicated the previous overclock, ran a few stress tests for a couple of hours and found it was stable enough so i moved onto the cpu
I followed MSI's guide's here for manual OC settings for i9 9900K: https://www.msi.com/blog/intel-9th-cpu-overclocking-5ghz-with-z390-motherboards
I was able to achieve stable 5.0 GHZ overclocks, verified everything with stress tests for about 2 hrs. Then I decided to jump to 5.1 ghz. Initially everything worked, then the system froze during a Time Spy run in 3D Mark. After that the system could not even load windows. I reset everything in the bios, went back to base clocks, even switched the xmp off just to be sure. But I still had problems and could not start windows for hours, couldn't even get to the login screen, the PC always froze, I was able to load the installer from USB though but i had a few files i didn't want to loose already on the disc so didn't want to reformat yet and the system would not allow installing just windows as some partition was formatted NTFS instead of FAT (don't remember the exact error message). I switched it off overnight just to give it a try tomorrow, and it actually booted. Don't really know why...
But then the issue started re-appearing. Interestingly it only or mostly happens when i reboot the PC for some reason, instead of shutting it down completely. I get a variety of blue screen errors (usually they happen at the login screen before i can type in the password). I have not wrote down all of them, I think the latest one I got was "IRQL NOT LESS OR EQUAL". I checked the guides for this, and the previous ones too and most of them pointed to the same issue:
My ram was still eligible for exchange so I did swap them out today, so it's a brand new 2x8 module, but the issue kept re-occurring. So that'd probably leave me with 1) or 3). I could replace the MB as well, but given it's a watercooled system, i'd prefer not to drain it again and start from zero.
I decided to actually swap out my old SSDs to a new 2TB M2 next week, so planning to do another fresh install of windows anyways, so i could eliminate 1). I've tried already scandisk, defregment. but none of them showed any issues for the disk (it's on the new Samsung Nvme, so been in use for about 10 days)
I'll try to write down all other error messages next time i run into the blue screen frenzy to give a clearer picture, but wanted to see if someone here could provide any guidance on how to eliminate the possible root cause. Currently I'm not running any overclocks on either the CPU or the GPU, only XMP is activated for the ram
Wanted to get your opinion on an issue I've started to notice with my machine.
I recently upgraded basically everything but my gpu in the system and then did a new Win 10 reinstall.
New specs:
MB: MSI MEG Z390 Godlike
Ram: 16 GB (2x8), 3600 DDR4 - installed in the correct slots per MB manual.
CPU: i9 9900K
PSU: Corsair AX1000
System Storage: Samsung 970 pro 512 GB nvme SSD
The entire system is watercooled, and ambient temperatures are quite stable, even under load I have not seen any components go above 55 degrees Celsius.
After the new install the PC was working fine, so after a couple of days of just light use I started jumping into overclocking both CPU and the GPU. I started with the GPU since that's basically the only one constant in the build and had previously stable clocks on it. so i replicated the previous overclock, ran a few stress tests for a couple of hours and found it was stable enough so i moved onto the cpu
I followed MSI's guide's here for manual OC settings for i9 9900K: https://www.msi.com/blog/intel-9th-cpu-overclocking-5ghz-with-z390-motherboards
I was able to achieve stable 5.0 GHZ overclocks, verified everything with stress tests for about 2 hrs. Then I decided to jump to 5.1 ghz. Initially everything worked, then the system froze during a Time Spy run in 3D Mark. After that the system could not even load windows. I reset everything in the bios, went back to base clocks, even switched the xmp off just to be sure. But I still had problems and could not start windows for hours, couldn't even get to the login screen, the PC always froze, I was able to load the installer from USB though but i had a few files i didn't want to loose already on the disc so didn't want to reformat yet and the system would not allow installing just windows as some partition was formatted NTFS instead of FAT (don't remember the exact error message). I switched it off overnight just to give it a try tomorrow, and it actually booted. Don't really know why...
But then the issue started re-appearing. Interestingly it only or mostly happens when i reboot the PC for some reason, instead of shutting it down completely. I get a variety of blue screen errors (usually they happen at the login screen before i can type in the password). I have not wrote down all of them, I think the latest one I got was "IRQL NOT LESS OR EQUAL". I checked the guides for this, and the previous ones too and most of them pointed to the same issue:
- Corrupt file system
- Hardware issues - probably RAM
- Hardware issues - possible MB.
My ram was still eligible for exchange so I did swap them out today, so it's a brand new 2x8 module, but the issue kept re-occurring. So that'd probably leave me with 1) or 3). I could replace the MB as well, but given it's a watercooled system, i'd prefer not to drain it again and start from zero.
I decided to actually swap out my old SSDs to a new 2TB M2 next week, so planning to do another fresh install of windows anyways, so i could eliminate 1). I've tried already scandisk, defregment. but none of them showed any issues for the disk (it's on the new Samsung Nvme, so been in use for about 10 days)
I'll try to write down all other error messages next time i run into the blue screen frenzy to give a clearer picture, but wanted to see if someone here could provide any guidance on how to eliminate the possible root cause. Currently I'm not running any overclocks on either the CPU or the GPU, only XMP is activated for the ram