F5F Stay Refreshed Software Operating Systems Question BSODs, and several applications are behaving oddly?

Question BSODs, and several applications are behaving oddly?

Question BSODs, and several applications are behaving oddly?

Pages (2): 1 2 Next
_
_FinnPlay_YT
Junior Member
12
11-16-2025, 02:10 AM
#1
Random BSODs appear with different modules and error codes, along with crashes and odd app behavior. The issues started months ago, happening 1-2 times daily, sometimes more often, often when the PC is idle. Initially thought it was GPU-related because some games crashed with visual glitches, so I replaced the GPU with a new one, but it didn’t resolve the problem. Later, many applications began displaying random undocumented errors and crashing, like Firefox tabs freezing even without add-ins. This strongly indicated a faulty RAM stick, despite Memtest86 showing no issues. I replaced all four RAM modules with new ones, but the problem persisted. I also performed SSD and hard drive tests, which didn’t reveal anything. After a clean Windows reinstall, nothing changed. Most BSODs point to ntoskrnl.exe, sometimes Ntfs.sys or other files, but I have no idea what to suspect. Temperatures are normal, BSODs occur randomly even without load, so it’s unlikely the power supply is the cause. The behavior suggests RAM is the issue, though I’ve already replaced it. I’m still unsure and would appreciate any advice.
_
_FinnPlay_YT
11-16-2025, 02:10 AM #1

Random BSODs appear with different modules and error codes, along with crashes and odd app behavior. The issues started months ago, happening 1-2 times daily, sometimes more often, often when the PC is idle. Initially thought it was GPU-related because some games crashed with visual glitches, so I replaced the GPU with a new one, but it didn’t resolve the problem. Later, many applications began displaying random undocumented errors and crashing, like Firefox tabs freezing even without add-ins. This strongly indicated a faulty RAM stick, despite Memtest86 showing no issues. I replaced all four RAM modules with new ones, but the problem persisted. I also performed SSD and hard drive tests, which didn’t reveal anything. After a clean Windows reinstall, nothing changed. Most BSODs point to ntoskrnl.exe, sometimes Ntfs.sys or other files, but I have no idea what to suspect. Temperatures are normal, BSODs occur randomly even without load, so it’s unlikely the power supply is the cause. The behavior suggests RAM is the issue, though I’ve already replaced it. I’m still unsure and would appreciate any advice.

Y
YellowDevs
Member
170
11-16-2025, 06:10 AM
#2
I had a comparable problem, by chance is your system drive the ADATA one? For me random BSOD with different codes kept appearing. I tried memtest, reinstalling Windows, and reseating everything. The NVMe health was good too (the drive was a year old), but after cloning Windows to another NVMe, the issue never returned. Maybe that could be the reason your PC is crashing.
Y
YellowDevs
11-16-2025, 06:10 AM #2

I had a comparable problem, by chance is your system drive the ADATA one? For me random BSOD with different codes kept appearing. I tried memtest, reinstalling Windows, and reseating everything. The NVMe health was good too (the drive was a year old), but after cloning Windows to another NVMe, the issue never returned. Maybe that could be the reason your PC is crashing.

J
Jarvan_IV
Member
120
12-04-2025, 02:55 PM
#3
Welcome to the forums, newcomer!
I even performed a clean reinstall of Windows, but it didn’t help.
Have you recreated the bootable USB installer to check for corruption? Did you install the OS in offline mode?
Motherboard: Intel b660
This is the chipset and the manufacturer of the chipset. Could you tell me the model of your motherboard? What BIOS version are you using? How is the processor being cooled?
RAM: Kingston Fury Renegade 128GB 3600 DDR4 CL16 DIMM (four sticks, 32GB each)
I’m using two sticks in slots A2 and B2. See if the problem continues.
Power Supply: Deepcool PM850D 80 PLUS GOLD 850 W
How long has the PSU been in use?
I examined your .dmp files with WinDBG; pCloud.exe
Can you uninstall that and check if the instability is resolved?
J
Jarvan_IV
12-04-2025, 02:55 PM #3

Welcome to the forums, newcomer!
I even performed a clean reinstall of Windows, but it didn’t help.
Have you recreated the bootable USB installer to check for corruption? Did you install the OS in offline mode?
Motherboard: Intel b660
This is the chipset and the manufacturer of the chipset. Could you tell me the model of your motherboard? What BIOS version are you using? How is the processor being cooled?
RAM: Kingston Fury Renegade 128GB 3600 DDR4 CL16 DIMM (four sticks, 32GB each)
I’m using two sticks in slots A2 and B2. See if the problem continues.
Power Supply: Deepcool PM850D 80 PLUS GOLD 850 W
How long has the PSU been in use?
I examined your .dmp files with WinDBG; pCloud.exe
Can you uninstall that and check if the instability is resolved?

L
Lord_Foxtrot
Senior Member
408
12-04-2025, 04:28 PM
#4
No, my operating system is set up on the SN770 drive. Adata is presently formatted and lacks any partitions, I haven't used it.
L
Lord_Foxtrot
12-04-2025, 04:28 PM #4

No, my operating system is set up on the SN770 drive. Adata is presently formatted and lacks any partitions, I haven't used it.

H
HetYoshiTeam
Member
164
12-08-2025, 09:15 AM
#5
The MB is a Gigabyte Intel B660 DS3H, version 1.0. The BIOS update is available, including fixes for the degradation problems affecting 13th and 14th Gen processors. Read the notes carefully before updating.
This board isn't ideal for pairing with a 13th Gen i9 processor. A more robust VRM and a Z series chipset would have been better choices.
H
HetYoshiTeam
12-08-2025, 09:15 AM #5

The MB is a Gigabyte Intel B660 DS3H, version 1.0. The BIOS update is available, including fixes for the degradation problems affecting 13th and 14th Gen processors. Read the notes carefully before updating.
This board isn't ideal for pairing with a 13th Gen i9 processor. A more robust VRM and a Z series chipset would have been better choices.

J
Jeffrey_12
Junior Member
13
12-15-2025, 04:36 PM
#6
Thank you, and yes, that's the board I have. I just completed the flashing to F32. I'll wait and observe any changes. What would you have preferred instead, considering the components available? Any recommendations?
J
Jeffrey_12
12-15-2025, 04:36 PM #6

Thank you, and yes, that's the board I have. I just completed the flashing to F32. I'll wait and observe any changes. What would you have preferred instead, considering the components available? Any recommendations?

A
Abood_99am
Member
115
12-17-2025, 03:47 AM
#7
Just completed flashing to F32. Ensure CMOS is cleared after confirming you're running the latest BIOS. What alternative MB would you prefer with your current components? Any particular recommendations?
A
Abood_99am
12-17-2025, 03:47 AM #7

Just completed flashing to F32. Ensure CMOS is cleared after confirming you're running the latest BIOS. What alternative MB would you prefer with your current components? Any particular recommendations?

G
gamer2hokv
Member
198
12-17-2025, 04:19 AM
#8
Sorry if you've already addressed this, but did these problems begin after the BIOS flash or earlier?
If it happened after, the image might be corrupted and you could try re-flashing an older version.
Before the BIOS flash, my advice is to use a digital multimeter and test the rails under load.
There are many guides on Digital multimeter power supply testing—search online or check YouTube.
If voltage or current deviates by more than 5% in either direction, it could lead to various issues.
G
gamer2hokv
12-17-2025, 04:19 AM #8

Sorry if you've already addressed this, but did these problems begin after the BIOS flash or earlier?
If it happened after, the image might be corrupted and you could try re-flashing an older version.
Before the BIOS flash, my advice is to use a digital multimeter and test the rails under load.
There are many guides on Digital multimeter power supply testing—search online or check YouTube.
If voltage or current deviates by more than 5% in either direction, it could lead to various issues.

X
xAlphaLegend
Member
222
12-18-2025, 04:24 PM
#9
If the BIOS update doesn't resolve the problem (it's highly probable), I'd suspect a motherboard issue. When XMP is active, attempt to turn it off and observe any improvements.
X
xAlphaLegend
12-18-2025, 04:24 PM #9

If the BIOS update doesn't resolve the problem (it's highly probable), I'd suspect a motherboard issue. When XMP is active, attempt to turn it off and observe any improvements.

J
jlien11
Senior Member
253
12-21-2025, 01:03 AM
#10
The partition wizzard driver can be removed using an uninstaller or by executing microsoft autoruns64.exe. I attempted to update cbfs20.sys on Wed Nov 9 04:58:18 2022. The bugcheck I examined suggested a driver issue rather than a memory error, indicating the problem stemmed from the driver trying to access data that wasn't present. I considered deleting pagefile.sys by disabling virtual memory and restarting, then trying again. The process ran as pCloud.exe. I plan to run another bugcheck to compare results.

Note: The debugger tends to flag files with check sum issues, and the second bugcheck also reported an access violation in the file system. Both checks took a considerable time—over two days and ten hours—to manifest. The next bugcheck emerged from the file system during a cleanup operation.

System details:
- Machine ID: 5
- Release: 24.0
- Vendor: American Megatrends International, LLC.
- Version: F4
- Release Date: 08/08/2022
- Manufacturer: Gigabyte Technology Co., Ltd.
- Product: B660 DS3H DDR4
- Family: B660 MB

CPU information:
- Frequency: 2995 MHz
- Processor: Intel® Core™ i9-13900KF
- Status: Update successful (REG_DWORD 2)
- Vendor: GenuineIntel
- MSR8B: 10500000000
J
jlien11
12-21-2025, 01:03 AM #10

The partition wizzard driver can be removed using an uninstaller or by executing microsoft autoruns64.exe. I attempted to update cbfs20.sys on Wed Nov 9 04:58:18 2022. The bugcheck I examined suggested a driver issue rather than a memory error, indicating the problem stemmed from the driver trying to access data that wasn't present. I considered deleting pagefile.sys by disabling virtual memory and restarting, then trying again. The process ran as pCloud.exe. I plan to run another bugcheck to compare results.

Note: The debugger tends to flag files with check sum issues, and the second bugcheck also reported an access violation in the file system. Both checks took a considerable time—over two days and ten hours—to manifest. The next bugcheck emerged from the file system during a cleanup operation.

System details:
- Machine ID: 5
- Release: 24.0
- Vendor: American Megatrends International, LLC.
- Version: F4
- Release Date: 08/08/2022
- Manufacturer: Gigabyte Technology Co., Ltd.
- Product: B660 DS3H DDR4
- Family: B660 MB

CPU information:
- Frequency: 2995 MHz
- Processor: Intel® Core™ i9-13900KF
- Status: Update successful (REG_DWORD 2)
- Vendor: GenuineIntel
- MSR8B: 10500000000

Pages (2): 1 2 Next