Computer talk OS Windows Linux MAC

**chuft** · 3 September 2025, 23:42

So has turning the XMP and Precision Boost off, stopped the crashes? Overclocking.

Did you ever use WhoCrashed to look at the big dump file?

There was a wargame we used to play called Enemy at the Gates about Stalingrad. It had an explicit supply system with trucks, supply dumps etc. Capturing an enemy supply dump was of course quite advantageous. We eventually began referring to the game in this way.

"What are you doing on Saturday? "Taking a dump in southern Russia."

**boredjedi** · 4 September 2025, 00:18

Originally posted by chuft

So has turning the XMP and Precision Boost off, stopped the crashes? Overclocking.

Did you ever use WhoCrashed to look at the big dump file?

There was a wargame we used to play called Enemy at the Gates about Stalingrad. It had an explicit supply system with trucks, supply dumps etc. Capturing an enemy supply dump was of course quite advantageous. We eventually began referring to the game in this way.

"What are you doing on Saturday? "Taking a dump in southern Russia."

I didn't turn off the Precision Boost yet. I want to run the memory with no XMP first for a while. This is the computer
lulling me into false sense of security. It does it many time. I have stated I can quite a few days without any
BSODs and then it starts in again. It's rather a cyclical pattern.

I've been using both WhoCrashed and WinDbg. I just copy and paste the error text into the comment.
Both were giving denied access on that morning Dump file. When I tried to load. And that morning crashing was with the XMP off.

And yeah I loaded that big dumper into both programs.

Good ol' supply dumps.

**boredjedi** · 4 September 2025, 06:19

Been waiting for this one. The Memory Management BSOD.

In the WinDbg

PROCESS_NAME: brave.exe

MODULE_NAME: hardware
IMAGE_NAME: memory_corruption
STACK_COMMAND: .process /r /p 0xffffe383bf9540c0; .thread 0xffffe383c08c50c0 ; kb
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT
OS_VERSION: 10.0.26100.1
BUILDLAB_STR: ge_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {e3faf315-c3d0-81db-819a-6c43d23c63a7}
Followup: MachineOwner

**chuft** · 4 September 2025, 11:17

Maybe it's just bum RAM sticks. Might be the easiest thing to replace and check. How are your overall temps?

I don't remember the history here. Has this computer worked properly in the past, or was it always like this since you built it?

**boredjedi** · 4 September 2025, 22:32

Temps are great across the board. According to all temperature diodes. The Ram I've checked before with MemTest86.
I have that burned on a CD and run it from boot. It's been updated to handle DDR4 and DDR5 ram.

This computer has been doing this since the day I installed Windows 11.

Don't forget, I haven't done the Precision Boost off yet. That'll be last and final test for this issue.

**boredjedi** · 4 September 2025, 22:47

I went to check the other minidump files with WinDbg.
I noticed last night when I posted that current BSOD
the process name was the Brave browser that caused the crash.

8/27 PROCESS_NAME: CrossDeviceSer

8/30 PROCESS_NAME: TiWorker.exe (That's a background process that helps manage Windows Updates)

9/01 2:12 am PROCESS_NAME: System
9/01 6:11pm PROCESS_NAME: brave.exe

9/02 PROCESS_NAME: System

9/04 PROCESS_NAME: brave.exe

**chuft** · 4 September 2025, 22:51

Originally posted by boredjedi

This computer has been doing this since the day I installed Windows 11.

Well that raises the question (but does not beg it) - did it run properly before on Win10? Or did it never work?

**boredjedi** · 4 September 2025, 23:06

Originally posted by chuft

Well that raises the question (but does not beg it) - did it run properly before on Win10? Or did it never work?

Windows 11 from the beginning. I didn't install 10 on it or even try Linux on it yet.
I have Windows 10 on the laptop.

September 2022 bought all the new parts and the Windows 11.

**chuft** · 4 September 2025, 23:53

It's been BSODing since Sep 2022?

**boredjedi** · 5 September 2025, 00:44

Originally posted by chuft

It's been BSODing since Sep 2022?

Yeah, I mentioned earlier on. Off and on. But as the updates kept
growing and growing it got worse and worse. Same like now.
When I first reinstalled the OS back in April it was relatively calmer.
Didn't go away completely. But now as the Updates have been
adding up again, it's back to it's routine. Like I said it's weird.
I can go days with none and then boom it becomes obnoxious for a few days.

My only thought now is that 4.9ghz overclocking by the Precision Boosting
Since it doesn't do the 4.9ghz all the time. It might fit the pattern
of making the hardware and OS unstable. Maybe after these 3 years I'll have my answer.

**boredjedi** · 8 September 2025, 01:39

I turned the XMP back on yesterday and so far no BSODs.
It's in the I'm behaving myself phase.

I had to do the DISM procedure to correct the Update fails.
Even though sfc /scannow has been fine with the results.
Updates working fine again.

**chuft** · 8 September 2025, 01:50

What is the DISM procedure?

**boredjedi** · 8 September 2025, 01:58

Originally posted by chuft

What is the DISM procedure?

It's when you are having fails in updates and run the sfc /scannow and errors come back.
When that happens, DISM to the rescue.

You should remember the posts a while ago about it.
From the previous post.

Via the Command Prompt Admin level
DISM /Online /Cleanup-image /StartComponentCleanup
DISM /Online /Cleanup-image /RestoreHealth

Still doesn't correct the issue until you do one more thing.
You need to go to C:Windows\Logs\DISM\dism.log
and delete that file. You're actually supposed to do that before
even running the DISM clean cleanup/restorhealth commands.

In technical speak

[QUOTE]
Deployment Image Servicing and Management (DISM.exe) is a command-line tool that can be used to service and prepare Windows images, including those used for Windows PE, Windows Recovery Environment (Windows RE) and Windows Setup. DISM can be used to service a Windows image (.wim) or a virtual hard disk (.vhd or .vhdx).

DISM comes built into Windows and is available through the command line or from Windows PowerShell. To learn more about using DISM with PowerShell, see Deployment Imaging Servicing Management (DISM) Cmdlets in Windows PowerShell.
[QUOTE]

https://learn.microsoft.com/en-us/wi...iew=windows-11

**boredjedi** · 8 September 2025, 04:07

Well, I had this computer on since yesterday morning with the memory XMP profile on.
Only 2 shut downs and 2 restarts to see if I get a BSOD on shut down and restart.
None. I've stressed the computer out etc... Still no BSOD. This is why this has been
a head scratcher. I'll probably be getting them in a few days or so. If the pattern holds.

https://www.reddit.com/r/techsupport..._blue_screens/
https://www.elevenforum.com/t/bsod-r...-months.23080/
https://learn.microsoft.com/en-us/an...installation(s)

Hi,

I have several users that are experiencing frequent BSOD events and getting different Stop codes. These are happening randomly throughout the day. Some examples: IRQL_NOT_LESS_OR_EQUAL, SYSTEM_SERVICE_EXCEPTION, PAGE_FAULT_IN_NONPAGED_AREA.

We have seen it on 23H2 and older versions.

https://learn.microsoft.com/en-us/an...g-frequent-bso

You don't have to go to those links but it's just to show I ain't crazy. There's even more links expressing this random BSOD issue.

**chuft** · 8 September 2025, 21:55

I don't think you're crazy. But most random problems are caused by hardware. Software problems can typically be replicated at will.

Computer talk OS Windows Linux MAC

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment