Random BSOD With Various Reasons During Gaming

After the "repair install", it seems like the BSOD is fixed though I'll monitor for a week or so after this. I'll mark this thread as solved if it stays stable for that duration.
Thank you very much to @ubuysa for the help and support all this time!!!
 
For my own interest and education, how did you perform the "repair install"?
Not sure how to explain it but I'll try:
  1. Get the Windows setup ISO that match the currently installed Windows. In my case it's version 22H2.
  2. Mount the ISO file
  3. Run setup.exe
  4. For me, I chose not to get the latest update from setup
  5. Click Next button, accept the EULA
  6. Make sure it choose to keep personal files and apps
  7. Click Install
  8. Wait until the install process is complete, including several reboots
After it's done, the Windows should be "repaired/refreshed" but still including the previously installed software.
 
After about a week of testing, it looks like the problem is almost solved as there's only one game where my PC would crash. I'm not sure if I should make a new thread as I'm not sure if this is a different problem.

There has been a total of 6 crashes, 5 managed to give BSODs, but only 4 produced dump file:
1st crash: didn't manage to dump, screen frozen
2nd crash: didn't manage to dump as it was stuck at 0% during dumping, was caused by nvlddmkm.sys with bug check string "SYSTEM_THREAD_EXCEPTION_NOT_HANDLED".
3rd crash: BSOD dump gives different culprit when showing the BSOD screen (luafv.sys, "SYSTEM_SERVICE_EXCEPTION") than the one stated by BlueScreenView (FLTMGR.SYS, "SYSTEM_THREAD_EXCEPTION_NOT_HANDLED").
4th to 6th crash: BSODs as normal

Thank you in advance.
 

Attachments

Last edited:
Did you re-run the SysnativeFileCollectionApp again before uploading that zip file? Everything in the file you uploaded is dated March. There is nothing current in there.
 
Hi! I had a similar issue not long ago that seemed to be caused by a bad M.2 port on my MB. The M.2 in that port had all of my game files in it, switching to a new m.2 port seemed to have resolved the issue finally.
Thank you for sharing your experience however I don't think my case is the same as yours as I've been using the laptop lightly for months now (I've changed my gaming rig) and it's stable.

Did you re-run the SysnativeFileCollectionApp again before uploading that zip file? Everything in the file you uploaded is dated March. There is nothing current in there.
Sorry, but are you talking about my post? My last post with the zip file was posted in March so the timestamp match.
 
Did you find a solution? I am having a similar issue. Attached my dmps as well, but when my game crashes, its not always a BSOD.
 

Attachments

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

Back
Top