F5F Stay Refreshed Software Operating Systems Question Random BSODs in the past months?

Question Random BSODs in the past months?

Question Random BSODs in the past months?

Pages (2): 1 2 Next
T
tinodz
Member
218
12-25-2025, 03:29 PM
#1
Hi All
I've been experiencing repeated BSODs lately and am unsure how to proceed to fix the issue.
I receive varying error messages during the BSOD, with some appearing more often than others.
I've attempted several solutions but still face problems:

Hardware
- Removed graphics card (3090)
- Deleted each RAM stick
- Removed Primary SSD – tried booting from USB, but BSOD occurred
- Removed Secondary SSDs
- Changed BIOS settings back to default
- Disconnected all USB devices except keyboard/mouse and headset

Windows
- Ran DISM and SFC – the latter now fails with Windows Resource Protection when executed via cmd prompt with admin rights.
- I can share the .DMP files if useful; I’m not familiar enough with them to diagnose further.

Anyone have suggestions? Your help would be greatly appreciated.
EDIT: I’ve also started encountering crashes in Microsoft Edge – Error code: STATUS_ACCESS_VIOLATION.
I’m not sure if this is connected or separate.
T
tinodz
12-25-2025, 03:29 PM #1

Hi All
I've been experiencing repeated BSODs lately and am unsure how to proceed to fix the issue.
I receive varying error messages during the BSOD, with some appearing more often than others.
I've attempted several solutions but still face problems:

Hardware
- Removed graphics card (3090)
- Deleted each RAM stick
- Removed Primary SSD – tried booting from USB, but BSOD occurred
- Removed Secondary SSDs
- Changed BIOS settings back to default
- Disconnected all USB devices except keyboard/mouse and headset

Windows
- Ran DISM and SFC – the latter now fails with Windows Resource Protection when executed via cmd prompt with admin rights.
- I can share the .DMP files if useful; I’m not familiar enough with them to diagnose further.

Anyone have suggestions? Your help would be greatly appreciated.
EDIT: I’ve also started encountering crashes in Microsoft Edge – Error code: STATUS_ACCESS_VIOLATION.
I’m not sure if this is connected or separate.

M
MegaDisco
Senior Member
352
12-25-2025, 03:29 PM
#2
Follow option one from the provided link.
After that, proceed with the next steps:
Create a small memory dump using Windows' built-in feature during a BSOD.
Access File Explorer and go to C:\Windows\Minidump.
Transfer the generated mini-dump files to your Desktop.
Avoid using Winzip; use Windows' native tool instead.
Select the files on your Desktop, right-click and choose 'Send to' – Compressed (zipped) folder.
Upload the resulting zip file to the cloud (OneDrive, DropBox, etc.).
Share the link to the uploaded file so we can review it together.
M
MegaDisco
12-25-2025, 03:29 PM #2

Follow option one from the provided link.
After that, proceed with the next steps:
Create a small memory dump using Windows' built-in feature during a BSOD.
Access File Explorer and go to C:\Windows\Minidump.
Transfer the generated mini-dump files to your Desktop.
Avoid using Winzip; use Windows' native tool instead.
Select the files on your Desktop, right-click and choose 'Send to' – Compressed (zipped) folder.
Upload the resulting zip file to the cloud (OneDrive, DropBox, etc.).
Share the link to the uploaded file so we can review it together.

K
kynan12
Junior Member
11
12-25-2025, 03:29 PM
#3
Thank you for the quick reply, Colif.
These are the minidump files.
K
kynan12
12-25-2025, 03:29 PM #3

Thank you for the quick reply, Colif.
These are the minidump files.

H
HappyMiner_gr
Member
78
12-25-2025, 03:29 PM
#4
Make the dump files accessible publicly.
H
HappyMiner_gr
12-25-2025, 03:29 PM #4

Make the dump files accessible publicly.

R
Roxx_2b
Junior Member
33
12-25-2025, 03:29 PM
#5
Sorry about that, I believed I had it.
This should function now.
R
Roxx_2b
12-25-2025, 03:29 PM #5

Sorry about that, I believed I had it.
This should function now.

T
Tiborious
Junior Member
10
12-25-2025, 03:29 PM
#6
I understand you've excluded each RAM stick during testing, yet these results consistently highlight RAM as the issue. There are no references to third-party drivers in any of the reports, and they encounter various problems across different tests, including failures during memory operations. Would it be helpful if you ran Memtest86 on your RAM to verify?

Download
Memtest86 (free), use the imageUSB.exe tool from the download to create a bootable USB with Memtest86 (1GB is sufficient). Perform this on another PC if possible, since your current system isn't fully reliable at the moment.

Once you boot from the USB, Memtest86 should begin automatically. After completing the four iterations of the 13 tests in the free version, restart the tool and repeat the process again. Even a single bit error will indicate a failure.

Additionally, please download and run the
SysnativeBSODCollectionApp
and upload the resulting zip file to a cloud service with a link. This application gathers all troubleshooting information we typically need. It does not collect any personal data. It's utilized by several well-known Windows help forums (including this one). As a senior BSOD analyst on the Sysnative forum where this tool originated, I can confirm it's safe.

You're welcome to review the contents of the zip file before uploading, though you shouldn't modify or delete any files. For details on each file, refer to the provided link.
T
Tiborious
12-25-2025, 03:29 PM #6

I understand you've excluded each RAM stick during testing, yet these results consistently highlight RAM as the issue. There are no references to third-party drivers in any of the reports, and they encounter various problems across different tests, including failures during memory operations. Would it be helpful if you ran Memtest86 on your RAM to verify?

Download
Memtest86 (free), use the imageUSB.exe tool from the download to create a bootable USB with Memtest86 (1GB is sufficient). Perform this on another PC if possible, since your current system isn't fully reliable at the moment.

Once you boot from the USB, Memtest86 should begin automatically. After completing the four iterations of the 13 tests in the free version, restart the tool and repeat the process again. Even a single bit error will indicate a failure.

Additionally, please download and run the
SysnativeBSODCollectionApp
and upload the resulting zip file to a cloud service with a link. This application gathers all troubleshooting information we typically need. It does not collect any personal data. It's utilized by several well-known Windows help forums (including this one). As a senior BSOD analyst on the Sysnative forum where this tool originated, I can confirm it's safe.

You're welcome to review the contents of the zip file before uploading, though you shouldn't modify or delete any files. For details on each file, refer to the provided link.

K
koopa14
Member
114
12-25-2025, 03:29 PM
#7
I encountered issues launching MemTest86 from USB, so I tried using it through the BIOS (V10.0 Free, Build 1000). It took 10 hours with no errors, and all 40 tests passed. I plan to repeat the process overnight to verify. After that, I’ll run SysnativeBSODCollectionApp.
K
koopa14
12-25-2025, 03:29 PM #7

I encountered issues launching MemTest86 from USB, so I tried using it through the BIOS (V10.0 Free, Build 1000). It took 10 hours with no errors, and all 40 tests passed. I plan to repeat the process overnight to verify. After that, I’ll run SysnativeBSODCollectionApp.

B
Blaster12121
Member
155
12-25-2025, 03:29 PM
#8
I've completed Memtest86 a second time and it still shows no issues. I'm attaching a link to the SysnativeBSOD files here. I didn't know about the Sysnative forums before, otherwise I would have shared there.
B
Blaster12121
12-25-2025, 03:29 PM #8

I've completed Memtest86 a second time and it still shows no issues. I'm attaching a link to the SysnativeBSOD files here. I didn't know about the Sysnative forums before, otherwise I would have shared there.

P
PainfulFist
Member
151
12-25-2025, 03:29 PM
#9
What issues do you face? Did you create the boot USB as described earlier? Was it placed at the top of the boot sequence? What occurred when it attempted to start?

Memtest86 functions properly in a UEFI setup, which is what you're using, but failing to boot might indicate something else. We should understand what happens during the process.

From the dumps and your logs, I still believe RAM is the most probable cause. However, I’m a bit puzzled because you mentioned...
But now it’s clear you only have one 32GB RAM stick in slot A2. What are you missing here?

Also, keep in mind that many of us participate in various forums, so sharing this here is acceptable. Cross-posting isn’t recommended.
P
PainfulFist
12-25-2025, 03:29 PM #9

What issues do you face? Did you create the boot USB as described earlier? Was it placed at the top of the boot sequence? What occurred when it attempted to start?

Memtest86 functions properly in a UEFI setup, which is what you're using, but failing to boot might indicate something else. We should understand what happens during the process.

From the dumps and your logs, I still believe RAM is the most probable cause. However, I’m a bit puzzled because you mentioned...
But now it’s clear you only have one 32GB RAM stick in slot A2. What are you missing here?

Also, keep in mind that many of us participate in various forums, so sharing this here is acceptable. Cross-posting isn’t recommended.

B
BBballoonboy
Junior Member
49
12-25-2025, 03:29 PM
#10
I set up the USB fine correctly. When selecting the USB as the first boot device, the lights flash once or twice on the USB drive during startup, then Windows loads from the SSD without any errors.
Earlier, I encountered a similar issue when using a Windows 11 USB to attempt a repair of my installation—it would bypass the USB and proceed directly to the SSD.
EDIT: I retried by disabling the SSD and keeping only the USB in the boot order; the system restarted after a restart attempt.
I own two 32GB RAM sticks. After removing one, I removed the other for testing purposes. The machine is now running with just one stick installed. If you could install the second stick back in and capture logs during a BSOD, that might assist further.
B
BBballoonboy
12-25-2025, 03:29 PM #10

I set up the USB fine correctly. When selecting the USB as the first boot device, the lights flash once or twice on the USB drive during startup, then Windows loads from the SSD without any errors.
Earlier, I encountered a similar issue when using a Windows 11 USB to attempt a repair of my installation—it would bypass the USB and proceed directly to the SSD.
EDIT: I retried by disabling the SSD and keeping only the USB in the boot order; the system restarted after a restart attempt.
I own two 32GB RAM sticks. After removing one, I removed the other for testing purposes. The machine is now running with just one stick installed. If you could install the second stick back in and capture logs during a BSOD, that might assist further.

Pages (2): 1 2 Next