BSOD Event 41

There is no dump uploaded and no indications anywhere that you actually had a BSOD. I can see that it crashed, but are you sure you had a blue screen of death? Your OP complained only of an error 41 log entry - that's not indicating a BSOD. Can you explain in detail exactly what is happening on your system.

In any case, we need to ensure that your system is properly setup to write dumps. All of the following must be true...
  • The page file must be on the same drive as your operating system
  • Set page file size to "system managed"
  • Set system crash/recovery options to "Automatic memory dump"
  • The "Overwrite any existing file" box must be checked
  • The "Write an event to the system log" must be checked
  • The dump file location must be %SystemRoot%\MEMORY.DMP
  • Windows Error Reporting (WER) system service must be set to MANUAL
  • User account control must be running
In addition, the following can also prevent you seeing dumps...
  • SSD drives with older firmware may not create dumps (update the drive firmware)
  • Cleaner applications like Ccleaner delete dump files, so don't run them until you are fixed
  • Bad RAM may prevent the data from being saved and written to a file on reboot, so if all else fails test your RAM
 
It BSOD twice this morning exactly when these critical events came

1736776109554.webp

It happens normally when using chrome (twice the other week while using audacity (i lost the entire project)), i know when its about to happen because everything freezes up, then about 5 seconds later i get sound card crashing sound (basically it just gets stuck on 1 millisecond of sound for like a second) and then the BSOD comes along.

regarding the page file, is there a guide on how to do this?

thank you
 
i also noticed that it seems to almost always BSOD twice in a row with
[td]BugcheckCode[/td] [td]340[/td]
coming first and followed by
[td]BugcheckCode[/td] [td]239[/td]
always in that order
 
i also noticed that it seems to almost always BSOD twice in a row with
[td]BugcheckCode[/td] [td]340[/td]
coming first and followed by
[td]BugcheckCode[/td] [td]239[/td]
always in that order
That's useful, thank you. Those bugcheck codes are in decimal, converting to hex we have 0x154 (340 decimal) and 0xEF (239 decimal). The 0x154 is an UNEXPECTED_STORE_EXCEPTION and the 0xEF is a CRITICAL_PROCESS_DIED. The 0x154 is commonly caused by bad RAM and the 0xEF is almost always a hardware problem, often bad RAM.

We need to test you RAM now using Memtest86 as follows...
  1. Download Memtest86 (free), use the imageUSB.exe tool extracted from the download to make a bootable USB drive containing Memtest86 (1GB is plenty big enough). Do this on a different PC if you can, because you can't fully trust yours at the moment.
  2. Then boot that USB drive on your PC, Memtest86 will start running as soon as it boots.
  3. If no errors have been found after the four iterations of the 13 different tests that the free version does, then restart Memtest86 and do another four iterations. Even a single bit error is a failure.
Let us know how that goes.
 
That's useful, thank you. Those bugcheck codes are in decimal, converting to hex we have 0x154 (340 decimal) and 0xEF (239 decimal). The 0x154 is an UNEXPECTED_STORE_EXCEPTION and the 0xEF is a CRITICAL_PROCESS_DIED. The 0x154 is commonly caused by bad RAM and the 0xEF is almost always a hardware problem, often bad RAM.

We need to test you RAM now using Memtest86 as follows...
  1. Download Memtest86 (free), use the imageUSB.exe tool extracted from the download to make a bootable USB drive containing Memtest86 (1GB is plenty big enough). Do this on a different PC if you can, because you can't fully trust yours at the moment.
  2. Then boot that USB drive on your PC, Memtest86 will start running as soon as it boots.
  3. If no errors have been found after the four iterations of the 13 different tests that the free version does, then restart Memtest86 and do another four iterations. Even a single bit error is a failure.
Let us know how that goes.
ok, luckily i have my old computer which runs with no issues, i will create the usb on that tomorrow

i also managed to capture video of the crash (because the first one happend, i was expecting the second), along with the event log that was created at the exact time (my computer for some reason refuses to use internet time)
 

Attachments

I did manage to see the bugcheck code in that video; CRITICAL_PROCESS_DIED and that's almost always a hardware failure. GIven how you're seeing that I think it's 100% certain to be a hardware problem.

Let us know how that RAM test goes. Flaky RAM is going to be the most likely cause.
 
hello

so i wasnt really sure what to expect, but it just showed a blank screen with a little text at the bottom (which i found out is the test itself) when it had completed i got 3 large beeps but no report.
I did however find the text logs of the scan and i am not sure what i am looking for

thank you
 

Attachments

The Memtest86 result is fine....
Code:
2025-01-15 10:56:39 - Test result: PASS (Errors: 0)

However, I think it's revealed that, as we can see in the DxDiag86.txt output (at the end), there have been six 0x141 live kernel events (these are VIDEO_ENGINE_TIMEOUT_DETECTED errors) and two 0x193 live kernel events (these are VIDEO_DXGKRNL_LIVEDUMP errors). These all suggest that the problem here is the graphics card. On most laptops you can dynamically switch between the iGPU and the dGPU, so I would experiment in using only the iGPU a for a while - you might even disable the dGPU in Device Manager to be sure that only the iGPU is in use - and see whether these errors continue.
 
hi, done, i will test frequently and let you know.

Once thing i have noticed though is that i never get a crash while actually playing a game :)
only when doing non game related activities

Thanks
Richard
 

Attachments

  • igpu.webp
    igpu.webp
    69.8 KB · Views: 3
Which might suggest that the problem is either the iGPU in the CPU or, possibly, the iGPU driver. But you recently updated the iGPU driver.

TBH I'd prefer you to disable the dGPU in Device Manager so that we're 100% certain that only the iGPU is in use. Based on the live kernel dump I saw in post #18 I'm very much afraid that this might be an iGPU issue.
 
Ok I already disabled that.

To be honest, so far since switching to igpu I have used youtube and chrome all day yesterday with no issues and again ok today.

I will heavily use it for next few days and see.

Thank you

Richard
 
Hi

So it just crashed,

I enabled the code display and disabled auto restart on bsod so got i captured the error codes.

I also changed the dump location to desktop but it produced nothing

Richard
 

Attachments

  • 20250117_091727.webp
    20250117_091727.webp
    492.2 KB · Views: 4

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top