F5F Stay Refreshed Hardware Desktop Question PC crashes unexpectedly and occasionally doesn't show a blue screen during games. Assistance needed.

Question PC crashes unexpectedly and occasionally doesn't show a blue screen during games. Assistance needed.

Question PC crashes unexpectedly and occasionally doesn't show a blue screen during games. Assistance needed.

1
1hulk
Junior Member
11
12-05-2025, 07:50 PM
#1
It appears the issue is quite inconsistent, making it difficult to intentionally trigger since crashes occur irregularly—sometimes days, other times months. It mainly affected Rainbow Six Siege, with a couple of unusual crashes on BF2042 and 2-4 instances on BF2042. I’m pretty sure some of these didn’t generate a dump file, though I recall at least one or two Rainbow Six Siege games that did. I’ve tried updating graphics drivers multiple times during the past few months, but nothing resolved it.

I’ve attached the Minidump link for reference:
https://drive.google.com/file/d/16E23obQ...sp=sharing

The two dumps from September 21st are from BF2042, while the others are from Rainbow Six Siege. The main problem seems to be around the 2nd of November and 23rd of December, which are the Rainbow Six Siege ones. I’m unsure why, but I’ll run Memtest again to rule out anything unexpected.

I’ve also checked the Event Viewer, but it doesn’t provide any relevant details. I ran SFC scannow and DISM multiple times, yet it only repaired a few random corrupted files—rarely, if at all.

Debug results from the latest minidump are attached below.
AGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This can’t be handled by try-except.

Typical arguments:
- Address: fffffa8dd1252c64
- Memory referenced: 0000000000000002 (X64, bit 0 if PTE missing)
- Bit 1: Write (bit 0: read, bit 1: write)
- Bit 3: Corrupted PTE detected
- Bit 4: No execute attempt on corrupted PTE
- CPU memory issues: 984 ms, 2879 ms elapsed
- Memory stats: 87 MB peak, version 10.2509.29.03

Other details include error codes, kernel versions, and debug flags.

No relevant warnings were found in Event Viewer.
I recently ran check disk checks, but no issues were detected. Last Memtest was a few months ago and still passed.

Debugging info:
- BEDaisy.exe is running
- Memory address fffff807d7bc44c0 returned unavailable
- Exception details: IP address 0xfffff8078f4e9d5d, error code 0x50
- Kernel version: 5.27.0.0
- File type: Dump.Attributes indicate a corrupted memory reference

The situation seems tied to BEDaisy.sys, possibly related to a recent update or hardware concern. I’ll keep monitoring and will provide further analysis after a short break.
1
1hulk
12-05-2025, 07:50 PM #1

It appears the issue is quite inconsistent, making it difficult to intentionally trigger since crashes occur irregularly—sometimes days, other times months. It mainly affected Rainbow Six Siege, with a couple of unusual crashes on BF2042 and 2-4 instances on BF2042. I’m pretty sure some of these didn’t generate a dump file, though I recall at least one or two Rainbow Six Siege games that did. I’ve tried updating graphics drivers multiple times during the past few months, but nothing resolved it.

I’ve attached the Minidump link for reference:
https://drive.google.com/file/d/16E23obQ...sp=sharing

The two dumps from September 21st are from BF2042, while the others are from Rainbow Six Siege. The main problem seems to be around the 2nd of November and 23rd of December, which are the Rainbow Six Siege ones. I’m unsure why, but I’ll run Memtest again to rule out anything unexpected.

I’ve also checked the Event Viewer, but it doesn’t provide any relevant details. I ran SFC scannow and DISM multiple times, yet it only repaired a few random corrupted files—rarely, if at all.

Debug results from the latest minidump are attached below.
AGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This can’t be handled by try-except.

Typical arguments:
- Address: fffffa8dd1252c64
- Memory referenced: 0000000000000002 (X64, bit 0 if PTE missing)
- Bit 1: Write (bit 0: read, bit 1: write)
- Bit 3: Corrupted PTE detected
- Bit 4: No execute attempt on corrupted PTE
- CPU memory issues: 984 ms, 2879 ms elapsed
- Memory stats: 87 MB peak, version 10.2509.29.03

Other details include error codes, kernel versions, and debug flags.

No relevant warnings were found in Event Viewer.
I recently ran check disk checks, but no issues were detected. Last Memtest was a few months ago and still passed.

Debugging info:
- BEDaisy.exe is running
- Memory address fffff807d7bc44c0 returned unavailable
- Exception details: IP address 0xfffff8078f4e9d5d, error code 0x50
- Kernel version: 5.27.0.0
- File type: Dump.Attributes indicate a corrupted memory reference

The situation seems tied to BEDaisy.sys, possibly related to a recent update or hardware concern. I’ll keep monitoring and will provide further analysis after a short break.

D
DJStampy0305
Member
125
12-14-2025, 12:39 AM
#2
Adjust MB Settimgs to Stock Typically on Exit Page.
D
DJStampy0305
12-14-2025, 12:39 AM #2

Adjust MB Settimgs to Stock Typically on Exit Page.

M
Marcos_PvP_
Member
55
12-14-2025, 01:14 AM
#3
Adjust Fan Curve, It's Usually Automatic!
M
Marcos_PvP_
12-14-2025, 01:14 AM #3

Adjust Fan Curve, It's Usually Automatic!

J
jesselove5
Member
81
12-14-2025, 01:47 AM
#4
I adjusted the fan curve, but I still experience some high temperatures because of the 1440p monitor upgrade. I ordered better fans to address this, though they haven't arrived yet. The older issues occurred before the upgrade when temperatures were manageable.

What did you mean with the smutli thread?

I ran a full chkdsk to fix the problem. CHKDSK found free space marked as allocated in the volume bitmap. Windows has already made corrections to the file system. No further steps are needed.
J
jesselove5
12-14-2025, 01:47 AM #4

I adjusted the fan curve, but I still experience some high temperatures because of the 1440p monitor upgrade. I ordered better fans to address this, though they haven't arrived yet. The older issues occurred before the upgrade when temperatures were manageable.

What did you mean with the smutli thread?

I ran a full chkdsk to fix the problem. CHKDSK found free space marked as allocated in the volume bitmap. Windows has already made corrections to the file system. No further steps are needed.

S
Sertero28
Senior Member
589
12-14-2025, 03:13 AM
#5
This advice seems unrelated to the issue at hand. It doesn't appear to address your concerns effectively. The tool you mentioned could be very useful, but you can create it yourself for free instead of purchasing from a questionable seller on Walmart.
S
Sertero28
12-14-2025, 03:13 AM #5

This advice seems unrelated to the issue at hand. It doesn't appear to address your concerns effectively. The tool you mentioned could be very useful, but you can create it yourself for free instead of purchasing from a questionable seller on Walmart.

F
Faanix
Junior Member
8
12-14-2025, 04:56 AM
#6
At least for now I removed battle-eye anticheat by deleting the folder from my Ubisoft files and checking the game files. I haven’t experienced a full PC crash or reset yet, though it’s been quite rare so far. It’s been about nine days since then and I’ve only had two game crashes, which is normal considering the bug fixes from BugIsoft.
F
Faanix
12-14-2025, 04:56 AM #6

At least for now I removed battle-eye anticheat by deleting the folder from my Ubisoft files and checking the game files. I haven’t experienced a full PC crash or reset yet, though it’s been quite rare so far. It’s been about nine days since then and I’ve only had two game crashes, which is normal considering the bug fixes from BugIsoft.