TL;DR skip to Paragraph 6, but not recommended please
So my friend and I built a custom PC a week ago, and I have been going through so much he** trying to fix this issue. Basically, when we first assembled it, it booted up fine and we were able to install Windows 10. After installing a few programs and drivers 30 minutes after we got into Windows, the computer locked up and I couldn't use the keyboard or mouse, so I couldn't bring up the Task Manager. The only way to fix the issue was by long-pressing the power button until it shut off.
I thought this was a one-time issue, so I left for the night. He was playing Space Engineers when he received a BSoD for the first time in the build with a MEMORY_MANAGEMENT issue. I didn't know what to do so he logged off for the night. The next day, he received 4 BSoDs. Him and I couldn't remember all of them, but none was related to MEMORY_MANAGEMENT, but some were IRQL_NOT_LESS_OR_EQUAL or something with FILENAME.sys.
The next day, he couldn't boot at all. The fans would run, and the motherboard would light up. I decided to come over and see if booting with one RAM stick would help, and long and behold we could boot again, but he still kept receiving BSoDs. The next day, he couldn't boot again: the keyboard and mouse wouldn't light up and work and the screen on the monitor was blank. We decided to open up the computer and reseat the RAM and GPU to see if it helped. We also unplugged the 24-pin and 8-pin connectors and plugged them back in. The computer wouldn't boot, but the fans would run; no signal would come to the monitor, just like as described above. I noticed on the motherboard LEDs that the DRAM and GPU light was on. Frustrated, I swapped out the single RAM stick with what we thought was the defective one and it booted again to Windows: the DRAM light went away and the GPU light turned on for a split second before going away. He was able to log into Windows and use the computer. So, now I'm confused: the RAM stick that we thought was defective seem to be working... again.
Anyways, I stayed for a little while, before he received another BSoD with a FILENAME.sys. We decided to reinstall Windows and the drivers. While we were reinstalling his programs, he browsed the web and watched streams with no problems whatsoever. While his games were being reinstalled, he browsed the internet for a good hour or two. When the first game finished, ten minutes into a game, instant BSoD relating to MEMORY_MANAGEMENT. What was different was that the computer rebooted on its own instead of having me press the power button after the computer shutdown afterwards. Anyways, it didn't happen again, and after I left he was able to play Space Engineers and other games for four hours before he logged off, no BSoDs. Now I am frustrated. I looked all over the web and no one else seems to be having the same problem as we are having. Sometimes, the BSoDs come within an hour, or within hours.
The following morning, he received a MEMORY_MANAGEMENT BSoD.
I took the computer to the nearest Micro Center and they ran Memtest with bad RAM modules showing up. They said the motherboard slots did not show any errors. They replaced the RAM and the day I got it back, the computer would crash but no more blue screens (yay I guess). The crashes are now hard crashes that freezes the screen and user interface, with the audio looping. The only way to reboot is by pressing the power button. The crashes would happen once every week or two. We decided to reinstall the OS by downloading the OS from the Microsoft website into a USB drive. We reinstalled it thinking it would fix the corrupt system files, but the crashes are still happening. Three weeks after reinstalling the OS, they are happening once or twice daily.
NOTE** CPU temps according to MSI Afterburner and the BIOS does not exceed 40C. We are also not OCing and we checked the BIOS to see if the RAM timings were right: 13-15-15-28. We also turned off XMP after it was no help. XMP did not make a difference in our results after receiving the computer with the new RAM modules.
Specs:
Motherboard: MSI H170 Gaming M3
CPU: Intel i5-6600 @3.3 GHz
GPU: MSI GTX 970 4G
Memory: CORSAIR Vengeance LPX 16GB (2 x 8GB) 288-Pin DDR4 SDRAM DDR4 2133 (PC4 17000) Desktop Memory Model CMK16GX4M2A2133C13
Storage: SAMSUNG 850 Evo 2.5" SATA III SSD (Boot Drive) & 1TB HDD (for Data)
Case: NZXT S340
PSU: CORSAIR RMx RM650X 650W ATX12V / EPS12V 80 PLUS GOLD Certified Full Modular Nvidia Sli ready and crossfire support Power Supply
EDIT: Here are the critical errors from Event Viewer. They seem to be all the same and the dates and time are exactly when the computer crashed after reinstalling the OS, so nothing before.
So my friend and I built a custom PC a week ago, and I have been going through so much he** trying to fix this issue. Basically, when we first assembled it, it booted up fine and we were able to install Windows 10. After installing a few programs and drivers 30 minutes after we got into Windows, the computer locked up and I couldn't use the keyboard or mouse, so I couldn't bring up the Task Manager. The only way to fix the issue was by long-pressing the power button until it shut off.
I thought this was a one-time issue, so I left for the night. He was playing Space Engineers when he received a BSoD for the first time in the build with a MEMORY_MANAGEMENT issue. I didn't know what to do so he logged off for the night. The next day, he received 4 BSoDs. Him and I couldn't remember all of them, but none was related to MEMORY_MANAGEMENT, but some were IRQL_NOT_LESS_OR_EQUAL or something with FILENAME.sys.
The next day, he couldn't boot at all. The fans would run, and the motherboard would light up. I decided to come over and see if booting with one RAM stick would help, and long and behold we could boot again, but he still kept receiving BSoDs. The next day, he couldn't boot again: the keyboard and mouse wouldn't light up and work and the screen on the monitor was blank. We decided to open up the computer and reseat the RAM and GPU to see if it helped. We also unplugged the 24-pin and 8-pin connectors and plugged them back in. The computer wouldn't boot, but the fans would run; no signal would come to the monitor, just like as described above. I noticed on the motherboard LEDs that the DRAM and GPU light was on. Frustrated, I swapped out the single RAM stick with what we thought was the defective one and it booted again to Windows: the DRAM light went away and the GPU light turned on for a split second before going away. He was able to log into Windows and use the computer. So, now I'm confused: the RAM stick that we thought was defective seem to be working... again.
Anyways, I stayed for a little while, before he received another BSoD with a FILENAME.sys. We decided to reinstall Windows and the drivers. While we were reinstalling his programs, he browsed the web and watched streams with no problems whatsoever. While his games were being reinstalled, he browsed the internet for a good hour or two. When the first game finished, ten minutes into a game, instant BSoD relating to MEMORY_MANAGEMENT. What was different was that the computer rebooted on its own instead of having me press the power button after the computer shutdown afterwards. Anyways, it didn't happen again, and after I left he was able to play Space Engineers and other games for four hours before he logged off, no BSoDs. Now I am frustrated. I looked all over the web and no one else seems to be having the same problem as we are having. Sometimes, the BSoDs come within an hour, or within hours.
The following morning, he received a MEMORY_MANAGEMENT BSoD.
I took the computer to the nearest Micro Center and they ran Memtest with bad RAM modules showing up. They said the motherboard slots did not show any errors. They replaced the RAM and the day I got it back, the computer would crash but no more blue screens (yay I guess). The crashes are now hard crashes that freezes the screen and user interface, with the audio looping. The only way to reboot is by pressing the power button. The crashes would happen once every week or two. We decided to reinstall the OS by downloading the OS from the Microsoft website into a USB drive. We reinstalled it thinking it would fix the corrupt system files, but the crashes are still happening. Three weeks after reinstalling the OS, they are happening once or twice daily.
NOTE** CPU temps according to MSI Afterburner and the BIOS does not exceed 40C. We are also not OCing and we checked the BIOS to see if the RAM timings were right: 13-15-15-28. We also turned off XMP after it was no help. XMP did not make a difference in our results after receiving the computer with the new RAM modules.
Specs:
Motherboard: MSI H170 Gaming M3
CPU: Intel i5-6600 @3.3 GHz
GPU: MSI GTX 970 4G
Memory: CORSAIR Vengeance LPX 16GB (2 x 8GB) 288-Pin DDR4 SDRAM DDR4 2133 (PC4 17000) Desktop Memory Model CMK16GX4M2A2133C13
Storage: SAMSUNG 850 Evo 2.5" SATA III SSD (Boot Drive) & 1TB HDD (for Data)
Case: NZXT S340
PSU: CORSAIR RMx RM650X 650W ATX12V / EPS12V 80 PLUS GOLD Certified Full Modular Nvidia Sli ready and crossfire support Power Supply
EDIT: Here are the critical errors from Event Viewer. They seem to be all the same and the dates and time are exactly when the computer crashed after reinstalling the OS, so nothing before.
Facebook
Twitter
Instagram