F5F Stay Refreshed Software Operating Systems Several crashes due to various causes

Several crashes due to various causes

Several crashes due to various causes

Pages (2): 1 2 Next
S
SozialPlays
Junior Member
1
06-28-2018, 04:00 AM
#1
I've been working on this problem for three days now. I'm experiencing BSODs after BSODs after BSODs. Here are the details of my BSOD logs:

- SYSTEM_SERVICE_EXCEPTION
- MEMORY_MANAGEMENT
- KMODE_EXCEPTION_NOT_HANDLED

My system specs are:

- CPU: AMD Ryzen 5 2600 (6 cores)
- RAM: 16 GB Corsair Vengeance 2400 MHz
- GPU: Sapphire Nitro+ Radeon RX 580 (4GB)
- Motherboard: MSI B450 I Gaming Plus AC mini ATX
- Power Supply: SeaSonic M12II 520 Bronze Evo Edition
- SSD (installed at time of testing): Samsung SSD 850 EVO 120 GB
- HDD (used for games): Western Digital Blue 1 TB

All components are under 10 months old. A friend who is very reliable told me a RAM stick was dead. I used just one RAM stick for a week without issues before going to RMA.

I've tried several fixes:

- Changed graphics card
- Reinstalled the operating system
- Updated BIOS
- Used only one RAM stick
- Reinstalled OS again
- Ran Memcheck and Chkdsk
- Ran sfc /scannow but it couldn't fix the problem
- Found modules causing BSOD: ntoskrnl.exe, ntfs.sys, hardware.sys

I recently attempted to copy the OS from my old CPU to the new one using a free online tool (before wiping everything). The OS wouldn't even boot on the new PC, which happened after a week before I RMAed the RAM.

Any advice would be greatly appreciated.
S
SozialPlays
06-28-2018, 04:00 AM #1

I've been working on this problem for three days now. I'm experiencing BSODs after BSODs after BSODs. Here are the details of my BSOD logs:

- SYSTEM_SERVICE_EXCEPTION
- MEMORY_MANAGEMENT
- KMODE_EXCEPTION_NOT_HANDLED

My system specs are:

- CPU: AMD Ryzen 5 2600 (6 cores)
- RAM: 16 GB Corsair Vengeance 2400 MHz
- GPU: Sapphire Nitro+ Radeon RX 580 (4GB)
- Motherboard: MSI B450 I Gaming Plus AC mini ATX
- Power Supply: SeaSonic M12II 520 Bronze Evo Edition
- SSD (installed at time of testing): Samsung SSD 850 EVO 120 GB
- HDD (used for games): Western Digital Blue 1 TB

All components are under 10 months old. A friend who is very reliable told me a RAM stick was dead. I used just one RAM stick for a week without issues before going to RMA.

I've tried several fixes:

- Changed graphics card
- Reinstalled the operating system
- Updated BIOS
- Used only one RAM stick
- Reinstalled OS again
- Ran Memcheck and Chkdsk
- Ran sfc /scannow but it couldn't fix the problem
- Found modules causing BSOD: ntoskrnl.exe, ntfs.sys, hardware.sys

I recently attempted to copy the OS from my old CPU to the new one using a free online tool (before wiping everything). The OS wouldn't even boot on the new PC, which happened after a week before I RMAed the RAM.

Any advice would be greatly appreciated.

M
230
07-05-2018, 04:37 PM
#2
I’m very likely dealing with unstable overclocking. Even if I cranked my CPU to 5/5.1 GHZ at any temperature, I’d still face BSOD errors with the System Service Exception. For memory handling, consider disabling XMP or enabling it if it’s not active. Otherwise, I’m not sure enough—bet to reach out for a return merchandise authorization.
M
MaddieStarr801
07-05-2018, 04:37 PM #2

I’m very likely dealing with unstable overclocking. Even if I cranked my CPU to 5/5.1 GHZ at any temperature, I’d still face BSOD errors with the System Service Exception. For memory handling, consider disabling XMP or enabling it if it’s not active. Otherwise, I’m not sure enough—bet to reach out for a return merchandise authorization.

L
Lakerats
Junior Member
14
07-17-2018, 12:29 AM
#3
All parts (CPU, GPU, RAM) are operating at the standard speed. Fixing another component will be difficult because I’m not the original owner.
L
Lakerats
07-17-2018, 12:29 AM #3

All parts (CPU, GPU, RAM) are operating at the standard speed. Fixing another component will be difficult because I’m not the original owner.

H
heroboy17
Senior Member
528
07-18-2018, 10:20 AM
#4
I encountered the same problem too. I was seeing identical blue screens and using a 2600 model. It appears to have been resolved by executing DISM.exe /Online /Cleanup-image /Restorehealth, then booting into safe mode and running sfc /scannow. Instead of crashing, it detected corrupt files, fixed them, and I haven’t experienced another failure since.
H
heroboy17
07-18-2018, 10:20 AM #4

I encountered the same problem too. I was seeing identical blue screens and using a 2600 model. It appears to have been resolved by executing DISM.exe /Online /Cleanup-image /Restorehealth, then booting into safe mode and running sfc /scannow. Instead of crashing, it detected corrupt files, fixed them, and I haven’t experienced another failure since.

C
CreeperJax27
Junior Member
4
07-26-2018, 09:32 AM
#5
I upgraded my SSD to a different HDD and ran sfc /scannow, but no errors were detected. However, I still experienced a BSOD with the new drive. I plan to try your solution tonight and will share the update afterward. Thank you!
C
CreeperJax27
07-26-2018, 09:32 AM #5

I upgraded my SSD to a different HDD and ran sfc /scannow, but no errors were detected. However, I still experienced a BSOD with the new drive. I plan to try your solution tonight and will share the update afterward. Thank you!

T
Tuetme
Senior Member
418
07-26-2018, 01:56 PM
#6
That's it, I'm done.
T
Tuetme
07-26-2018, 01:56 PM #6

That's it, I'm done.

S
SnifePvP
Posting Freak
872
07-28-2018, 01:36 PM
#7
Have you experimented with another processor?
S
SnifePvP
07-28-2018, 01:36 PM #7

Have you experimented with another processor?

B
Bladeksx
Junior Member
11
07-28-2018, 04:41 PM
#8
I identified the issue after running memtest86 on each RAM stick individually. One showed no errors, while the other had over 1000 errors. I suspect a faulty RAM module. I plan to replace it again, but can you confirm if there’s any way to verify my system isn’t interfering with the RAM before returning it?
B
Bladeksx
07-28-2018, 04:41 PM #8

I identified the issue after running memtest86 on each RAM stick individually. One showed no errors, while the other had over 1000 errors. I suspect a faulty RAM module. I plan to replace it again, but can you confirm if there’s any way to verify my system isn’t interfering with the RAM before returning it?

S
Strafeliner
Member
165
07-28-2018, 07:53 PM
#9
Wow, I hadn't seen this comment but I was coming back to this thread to let you know the same exact thing. Ran memtest on both sticks of RAM and one was bad (it actually had so many errors that the test had to stop before completing). I've been using just the one stick while I wait for a replacement and I haven't had any more blue screens. Were both of your sticks of RAM that were bad the same model?
S
Strafeliner
07-28-2018, 07:53 PM #9

Wow, I hadn't seen this comment but I was coming back to this thread to let you know the same exact thing. Ran memtest on both sticks of RAM and one was bad (it actually had so many errors that the test had to stop before completing). I've been using just the one stick while I wait for a replacement and I haven't had any more blue screens. Were both of your sticks of RAM that were bad the same model?

Z
zuper_ah
Member
142
07-30-2018, 07:45 AM
#10
I owned two Corsair sticks, one was defective. I returned it once, but the issue persisted. Still, I’m not out of trouble—there are occasional game crashes where the display disconnects. I’ve tried many fixes without success. I suspect my motherboard might be the culprit, but since I don’t have a spare to test, I checked forums and asked questions. I’m still searching for a solution. Most likely, the problem lies with my motherboard or CPU, though the CPU seems unlikely at this point. It’s frustrating, but I’m not giving up.
Z
zuper_ah
07-30-2018, 07:45 AM #10

I owned two Corsair sticks, one was defective. I returned it once, but the issue persisted. Still, I’m not out of trouble—there are occasional game crashes where the display disconnects. I’ve tried many fixes without success. I suspect my motherboard might be the culprit, but since I don’t have a spare to test, I checked forums and asked questions. I’m still searching for a solution. Most likely, the problem lies with my motherboard or CPU, though the CPU seems unlikely at this point. It’s frustrating, but I’m not giving up.

Pages (2): 1 2 Next