F5F Stay Refreshed Software Operating Systems Blues Screen Crash ?

Blues Screen Crash ?

Blues Screen Crash ?

C
CheckMyPvP_
Junior Member
24
01-06-2021, 02:37 PM
#1
Hi there, I just experienced my first BSOD on my gaming PC using Windows 11 while playing Space Marine 2. The temperatures are normal, so it's not overheating. The Diagnostic Data Viewer displays the details—perhaps someone has more insight than I do. Here are the specifics: problem signature, event name LiveKernelEvent, code 144, parameters 1003, ffffb40a297aa170, 0, 0, OS version 10_0_22631, service pack 0_0, product 768_1, and a bucket ID of 18446744073709551615.
C
CheckMyPvP_
01-06-2021, 02:37 PM #1

Hi there, I just experienced my first BSOD on my gaming PC using Windows 11 while playing Space Marine 2. The temperatures are normal, so it's not overheating. The Diagnostic Data Viewer displays the details—perhaps someone has more insight than I do. Here are the specifics: problem signature, event name LiveKernelEvent, code 144, parameters 1003, ffffb40a297aa170, 0, 0, OS version 10_0_22631, service pack 0_0, product 768_1, and a bucket ID of 18446744073709551615.

T
TheBozoPlays
Senior Member
642
01-09-2021, 01:23 PM
#2
Have you attempted these troubleshooting steps?
Check or revert your graphics driver
Avoid overclocking
Execute SFC and DISM
Enhance your CPU
https://www.thewindowsclub.com/fix-livek...-computers
T
TheBozoPlays
01-09-2021, 01:23 PM #2

Have you attempted these troubleshooting steps?
Check or revert your graphics driver
Avoid overclocking
Execute SFC and DISM
Enhance your CPU
https://www.thewindowsclub.com/fix-livek...-computers

N
NightBlue_3
Junior Member
42
01-17-2021, 04:46 AM
#3
I used sfc /scannow and it detected corrupt files, replacing them. I also ran DISM, but nothing appeared to show up—just a message saying everything is 100% complete followed by the restore operation finishing successfully. Could either be the problem?
No overclocking, just a standard 7800X3D.
Graphics drivers were updated a few weeks ago and have been working fine with normal use until this BSOD occurred.
N
NightBlue_3
01-17-2021, 04:46 AM #3

I used sfc /scannow and it detected corrupt files, replacing them. I also ran DISM, but nothing appeared to show up—just a message saying everything is 100% complete followed by the restore operation finishing successfully. Could either be the problem?
No overclocking, just a standard 7800X3D.
Graphics drivers were updated a few weeks ago and have been working fine with normal use until this BSOD occurred.

Y
yolosolohi48
Member
167
01-29-2021, 12:56 PM
#4
I often notice sfc /scannow reporting fixes on machines that are in perfect condition, so I no longer have concerns about it. Also, using DISM likely didn’t help much, but it’s worth a try. Do you have a restore point available? If you have an affordable spare SATA SSD, consider installing a new Windows installation. It should take no more than two hours to complete the basic setup and install the game that fails. Take your main SSD out of the way to avoid further issues. This could help determine whether the issue is software-related or hardware problems.
Y
yolosolohi48
01-29-2021, 12:56 PM #4

I often notice sfc /scannow reporting fixes on machines that are in perfect condition, so I no longer have concerns about it. Also, using DISM likely didn’t help much, but it’s worth a try. Do you have a restore point available? If you have an affordable spare SATA SSD, consider installing a new Windows installation. It should take no more than two hours to complete the basic setup and install the game that fails. Take your main SSD out of the way to avoid further issues. This could help determine whether the issue is software-related or hardware problems.

T
ThePunisher99
Member
57
01-30-2021, 02:00 PM
#5
Bugcheck code 0x144 relates to a USB3 problem, identified as a BUGCODE_USB3_DRIVER issue. It may indicate a malfunctioning device connected via USB3, or it could require an updated chipset driver.
T
ThePunisher99
01-30-2021, 02:00 PM #5

Bugcheck code 0x144 relates to a USB3 problem, identified as a BUGCODE_USB3_DRIVER issue. It may indicate a malfunctioning device connected via USB3, or it could require an updated chipset driver.