F5F Stay Refreshed Software Operating Systems PC Blue Screen or Freezing Up, Event Number 41 with keywords like: 70368744177664 and 2.

PC Blue Screen or Freezing Up, Event Number 41 with keywords like: 70368744177664 and 2.

PC Blue Screen or Freezing Up, Event Number 41 with keywords like: 70368744177664 and 2.

Pages (2): Previous 1 2
J
Juan2610
Posting Freak
875
04-11-2026, 10:15 PM
#11
Just put one piece of RAM into a slot and then move it to the next slot. You might see that your new memory chip isn't working right at first...
J
Juan2610
04-11-2026, 10:15 PM #11

Just put one piece of RAM into a slot and then move it to the next slot. You might see that your new memory chip isn't working right at first...

D
dat__b0i
Member
59
04-12-2026, 01:48 AM
#12
Should I run memtest with these settings too? The freezing act still hasn't changed after swapping out my old RAM for new ones, so I'm unsure if it's the memory itself at all. But I'll just try sticking each one in each slot to see what happens.
D
dat__b0i
04-12-2026, 01:48 AM #12

Should I run memtest with these settings too? The freezing act still hasn't changed after swapping out my old RAM for new ones, so I'm unsure if it's the memory itself at all. But I'll just try sticking each one in each slot to see what happens.

C
coyote888
Posting Freak
838
04-16-2026, 01:06 PM
#13
I told you about the RAM slots being unreliable before, so I suggested putting just one stick into each spot. As you do this, it's smart to test each new stick against everything else individually, not all at once.
C
coyote888
04-16-2026, 01:06 PM #13

I told you about the RAM slots being unreliable before, so I suggested putting just one stick into each spot. As you do this, it's smart to test each new stick against everything else individually, not all at once.

B
BeJesusChryst
Junior Member
10
04-16-2026, 01:32 PM
#14
So after a month and a half, new RAM passed the memtest with flying colors. But now freezing happens again when unplugging from the UPS (strange, I know). The system locks up completely with no blue screen. Everything freezes: display goes dark, sound cuts out, mouse won't move, keyboard doesn't work. Waited for hours and nothing changed. Honestly, I'm really losing my mind here.
B
BeJesusChryst
04-16-2026, 01:32 PM #14

So after a month and a half, new RAM passed the memtest with flying colors. But now freezing happens again when unplugging from the UPS (strange, I know). The system locks up completely with no blue screen. Everything freezes: display goes dark, sound cuts out, mouse won't move, keyboard doesn't work. Waited for hours and nothing changed. Honestly, I'm really losing my mind here.

B
brobear7
Posting Freak
892
04-17-2026, 06:37 PM
#15
Turn Windows into Safe Mode. In this mode only the most important parts of Windows run, so extra drivers and things that aren't needed don't load. You might notice some devices not working right or even stopping, because you're using the simple display driver instead of a better one. You won't be able to do your work normally here; it is designed just to check if problems are from hardware or software, nothing else. If the computer freezes, crashes, or shows an error code like BSOD in Safe Mode, then you have a hardware issue. But if it stays running without freezing, crashing, or showing those errors, then your problems are probably from drivers or software, and we can check further to find out what's wrong. Start by turning on Safe Mode without any internet connection at first, because this loads the least amount of Windows and drivers. Leave it running here for as long as you can stand up and do try using it as much as possible. It is very important to know if or not it will freeze, crash, or show those errors in this mode, so keep trying it for several hours. Don't get impatient and stop early! Then (if everything ran normally) try starting it again with internet access. You'll be able to use more features here, but leave it running for many hours just to make sure if it will freeze, crash, or show those errors. IT IS VERY BORING TESTING A PC IN SAFE MODE - BUT IT'S ALSO VERY IMPORTANT. PLEASE DON'T QUIT EARLY!
B
brobear7
04-17-2026, 06:37 PM #15

Turn Windows into Safe Mode. In this mode only the most important parts of Windows run, so extra drivers and things that aren't needed don't load. You might notice some devices not working right or even stopping, because you're using the simple display driver instead of a better one. You won't be able to do your work normally here; it is designed just to check if problems are from hardware or software, nothing else. If the computer freezes, crashes, or shows an error code like BSOD in Safe Mode, then you have a hardware issue. But if it stays running without freezing, crashing, or showing those errors, then your problems are probably from drivers or software, and we can check further to find out what's wrong. Start by turning on Safe Mode without any internet connection at first, because this loads the least amount of Windows and drivers. Leave it running here for as long as you can stand up and do try using it as much as possible. It is very important to know if or not it will freeze, crash, or show those errors in this mode, so keep trying it for several hours. Don't get impatient and stop early! Then (if everything ran normally) try starting it again with internet access. You'll be able to use more features here, but leave it running for many hours just to make sure if it will freeze, crash, or show those errors. IT IS VERY BORING TESTING A PC IN SAFE MODE - BUT IT'S ALSO VERY IMPORTANT. PLEASE DON'T QUIT EARLY!

A
AmazinglyCool
Senior Member
695
04-18-2026, 09:26 PM
#16
I tried starting up the PC into Safe Mode, but it stopped working right away. I didn't mention that when installing Windows fresh, I had to take out most of my hard drives so the process could finish; otherwise, it would freeze too. Now I am going to disconnect all the drives from the system. Let's see if the freezing happens without them. EDIT: Yeah, it's still freezing even in Safe Mode.
A
AmazinglyCool
04-18-2026, 09:26 PM #16

I tried starting up the PC into Safe Mode, but it stopped working right away. I didn't mention that when installing Windows fresh, I had to take out most of my hard drives so the process could finish; otherwise, it would freeze too. Now I am going to disconnect all the drives from the system. Let's see if the freezing happens without them. EDIT: Yeah, it's still freezing even in Safe Mode.

E
eldiablored
Member
57
04-19-2026, 01:56 AM
#17
In that case you have a hardware problem for sure. I know you've tested the RAM, but running on just one stick at a time would be useful. Unplug all external devices except mouse, keyboard, and one monitor. Unplug all internal storage drives you don't need to boot. If the boot drive is an M.2 drive then remove and reseat it. Remove and reseat all PCIe cards. Check all cables and connectors - at both ends - to ensure they are fully home.
E
eldiablored
04-19-2026, 01:56 AM #17

In that case you have a hardware problem for sure. I know you've tested the RAM, but running on just one stick at a time would be useful. Unplug all external devices except mouse, keyboard, and one monitor. Unplug all internal storage drives you don't need to boot. If the boot drive is an M.2 drive then remove and reseat it. Remove and reseat all PCIe cards. Check all cables and connectors - at both ends - to ensure they are fully home.

G
GoIden_Sun
Junior Member
6
04-19-2026, 03:35 AM
#18
I just finished talking about all that and still running into the same problems. But I finally found something in the Event Viewer that could be helpful! After every crash, I get an error from WHEA-Logger called Event 1, and it's creating this .dmp file at drive.google.com. I'm having a hard time reading those files though. Maybe they will give me some light on why things are breaking?
G
GoIden_Sun
04-19-2026, 03:35 AM #18

I just finished talking about all that and still running into the same problems. But I finally found something in the Event Viewer that could be helpful! After every crash, I get an error from WHEA-Logger called Event 1, and it's creating this .dmp file at drive.google.com. I'm having a hard time reading those files though. Maybe they will give me some light on why things are breaking?

Pages (2): Previous 1 2