Share via

My computer keeps crashing and I cannot figure out why

Anonymous
2024-11-26T16:17:15+00:00

While using my computer it may freeze crash, blue screen crash or just close an application I currently have open. It has been doing this for a while. It does not seem to have any reproducible frequency to these events. Some times I will turn my computer on right away and it will crash. Others I may use my computer for days and it wont crash.

Here is the event viewer info from this morning's crash:

Fault bucket , type 0

Event Name: LiveKernelEvent

Response: Not available

Cab Id: 0

Problem signature:

P1: 144

P2: 101e

P3: ffff878e41957170

P4: 0

P5: 0

P6: 10_0_22631

P7: 0_0

P8: 256_1

P9: 

P10: 

Attached files:

\?\C:\Windows\LiveKernelReports\USBXHCI\USBXHCI-20241126-1055.dmp

\?\C:\Windows\SystemTemp\WER-8765-0.sysdata.xml

\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.1e8e3918-4216-46db-9cff-380582045fb7.tmp.WERInternalMetadata.xml

\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.50b273ae-407c-4d01-acf9-ac667202a49e.tmp.csv

\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.bd25b4ff-5733-4c42-ae34-a6408010fd30.tmp.txt

\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.b1aa7ab6-883c-44e0-b708-6f5f2c460ff3.tmp.xml

These files may be available here:

\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_144_8a29270fc4f421de7adfafcc25d2555f39023a6_00000000_8372ed26-2370-4950-bd63-cde6c888dc2a

Analysis symbol: 

Rechecking for solution: 0

Report Id: 8372ed26-2370-4950-bd63-cde6c888dc2a

Report Status: 4

Hashed bucket: 

Cab Guid: 0

Fault bucket , type 0

Event Name: BlueScreen

Response: Not available

Cab Id: 0

Problem signature:

P1: 1e

P2: ffffffffc0000005

P3: fffff806582ac311

P4: 0

P5: ffffffffffffffff

P6: 10_0_22631

P7: 0_0

P8: 256_1

P9: 

P10: 

Attached files:

\?\C:\Windows\Minidump\112624-8765-01.dmp

\?\C:\Windows\SystemTemp\WER-8765-0.sysdata.xml

\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.74ec57c2-ca5f-4ca3-8440-258d59a3ca68.tmp.WERInternalMetadata.xml

\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.c8a371b5-434c-4df3-9ca5-e8347e852732.tmp.csv

\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.7928ac1f-691a-461f-8333-4e7096580a3f.tmp.txt

\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.5e4a92a2-3dc3-496f-97a7-211a904476d3.tmp.xml

These files may be available here:

\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1e_143e25af7767718e57aab3c976f9ce9b097a258_00000000_cf434e08-dc2e-4bcd-adfc-830333205330

Analysis symbol: 

Rechecking for solution: 0

Report Id: becdd479-2dd1-498c-93d3-35fb10c965e8

Report Status: 4

Hashed bucket: 

Cab Guid: 0

Fault bucket , type 0

Event Name: LiveKernelEvent

Response: Not available

Cab Id: 0

Problem signature:

P1: 144

P2: 101e

P3: ffff878e41957170

P4: 0

P5: 0

P6: 10_0_22631

P7: 0_0

P8: 256_1

P9: 

P10: 

Attached files:

\?\C:\Windows\LiveKernelReports\USBXHCI\USBXHCI-20241126-1055.dmp

\?\C:\Windows\SystemTemp\WER-8765-0.sysdata.xml

\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.1e8e3918-4216-46db-9cff-380582045fb7.tmp.WERInternalMetadata.xml

\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.50b273ae-407c-4d01-acf9-ac667202a49e.tmp.csv

\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.bd25b4ff-5733-4c42-ae34-a6408010fd30.tmp.txt

\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.b1aa7ab6-883c-44e0-b708-6f5f2c460ff3.tmp.xml

These files may be available here:

\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_144_8a29270fc4f421de7adfafcc25d2555f39023a6_00000000_cab_8372ed26-2370-4950-bd63-cde6c888dc2a

Analysis symbol: 

Rechecking for solution: 0

Report Id: 8372ed26-2370-4950-bd63-cde6c888dc2a

Report Status: 2049

Hashed bucket: 

Cab Guid: 0

Fault bucket , type 0

Event Name: BlueScreen

Response: Not available

Cab Id: 0

Problem signature:

P1: 1e

P2: ffffffffc0000005

P3: fffff806582ac311

P4: 0

P5: ffffffffffffffff

P6: 10_0_22631

P7: 0_0

P8: 256_1

P9: 

P10: 

Attached files:

\?\C:\Windows\Minidump\112624-8765-01.dmp

\?\C:\Windows\SystemTemp\WER-8765-0.sysdata.xml

\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.74ec57c2-ca5f-4ca3-8440-258d59a3ca68.tmp.WERInternalMetadata.xml

\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.c8a371b5-434c-4df3-9ca5-e8347e852732.tmp.csv

\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.7928ac1f-691a-461f-8333-4e7096580a3f.tmp.txt

\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.5e4a92a2-3dc3-496f-97a7-211a904476d3.tmp.xml

These files may be available here:

\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1e_143e25af7767718e57aab3c976f9ce9b097a258_00000000_cab_cf434e08-dc2e-4bcd-adfc-830333205330

Analysis symbol: 

Rechecking for solution: 0

Report Id: becdd479-2dd1-498c-93d3-35fb10c965e8

Report Status: 2049

Hashed bucket: 

Cab Guid: 0

Often I get these errors as well. Not sure if they are a problem:

Application: Razer Synapse 3.exe

Framework Version: v4.0.30319

Description: The process was terminated due to an unhandled exception.

Exception Info: System.BadImageFormatException

   at Razer.Synapse3.App..cctor()

Exception Info: System.TypeInitializationException

   at Razer.Synapse3.App+<>c.<.ctor>b__23_0(System.ServiceProcess.ServiceController)

   at System.Linq.Enumerable.FirstOrDefault[System.\_\_Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]

   at Razer.Synapse3.App..ctor()

   at Razer.Synapse3.App.Main()

Faulting application name: Razer Synapse 3.exe, version: 3.1.627.5, time stamp: 0xe632de68

Faulting module name: KERNELBASE.dll, version: 10.0.22621.4541, time stamp: 0xa3036317

Exception code: 0xe0434352

Fault offset: 0x0014b472

Faulting process id: 0x0x3664

Faulting application start time: 0x0x1DB401BC15AF9D9

Faulting application path: C:\Program Files (x86)\Razer\Synapse3\WPFUI\Framework\Razer Synapse 3 Host\Razer Synapse 3.exe

Faulting module path: C:\Windows\System32\KERNELBASE.dll

Report Id: 6c43deaa-3bae-4127-bc98-1958d76e193c

Faulting package full name: 

Faulting package-relative application ID: 

Here are the 3 files that are in my minidump folder as well:

https://drive.google.com/file/d/1QipNWz4mJpS4xw70TpCbdRKg_CBz9tJw/view?usp=sharing

Hopefully somebody can help me out.

Thanks,

Jeff

Windows for home | Windows 11 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-11-27T09:34:08+00:00

    Hello，JAPerrone

    Thank you for posting in the Microsoft community.

    Thank you for the details, from your current content I see that it contains mainly the following errors:

    1. From the event viewer (LiveKernelEvent) and the blue screen log (ntkrnlmp.sys), it indicates a system kernel level error, usually related to hardware problems or driver conflicts.
    2. From the blue screen logs, you also see the dxgmms.sys module error, who refers to a DirectX technical error, which functions primarily in relation to memory management and graphic display of the graphics card, and usually signals a potential problem related to the graphics card or graphics rendering.
    3. The Razer Synapse 3 crash is mentioned in your Event Viewer logs, this error indicates that the Razer Synapse software may be incompatible with your system or its installation files may be corrupt.

    To summarize, you can see that there are multiple functional and hardware errors in your device, which points to the possibility of memory errors and more serious system or hardware errors, so please follow the steps below to troubleshoot the different aspects of the error.

    Usually this problem is caused by a driver, motherboard, or power supply failure, so it is recommended that you first go to your computer/hardware manufacturer's website and update the drivers to the latest version.

    If the problem persists, follow the steps below to check the RAM and hard disk and troubleshoot the three-way software interference and system file corruption causing the problem.

    I. Check the memory

    1. Tap Windows+R, type MdSched and tap Enter to open the memory diagnostic tool
    2. Tap Reboot Now and check for problems
    3. Follow the prompts to check, wait for it to complete, and check the report to see if there are any problems detected.

    II. Check the hard disk

    1. Search for cmd and run it in administrator mode
    2. Type 
       chkdsk c: /f
    3. Wait for the check to complete and see if the problem is checked and fixed.

    Disclaimer: Run chkdsk to check the file system and file system metadata of a volume for logical and physical errors. To avoid causing unnecessary trouble, please follow the above steps step by step and do not interrupt or cancel during the run, and make a backup of important data.

    III. Entering Safe Mode

    1. Click the Start button in the bottom left corner of the screen and select Settings.
    2. In the Settings window, click on “Update & Security” and in the left menu, select “Recovery”.
    3. In the Advanced Startup section, click the Restart Now button. This will restart your computer and take you to the advanced startup options.
    4. From the options that appear, select “Troubleshooting > Advanced Options > Boot Settings”.
    5. Click on the “Restart” button, the computer will restart and display the boot settings menu, press the number key “4” or “F4” to enter safe mode.

    Ⅳ. Try to repair the system

    1. Search for CMD, find the command prompt, and choose to run in administrator mode.
    2. Enter the following commands one by one, please make sure to execute the next command after the previous one is completed. 
       DISM /Online /Cleanup-Image /ScanHealth

 DISM /Online /Cleanup-Image /CheckHealth

 DISM /Online /Cleanup-Image /RestoreHealth

 SFC /Scannow
    3. After the scan is complete, you can check the scanning information to see if the problem has been detected and fixed.

    If the update has been completed and no memory or hard disk issues have been checked, and the above steps have been followed to rule out the possibility of a three-way software issue, and this problem persists, there may be a hardware failure, and it is recommended that you contact the manufacturer or a computer repair facility to have it checked.

    If you need further clarification, please let us know what you are experiencing during operation and we will advise you further.

    Best Regards，

    Rota|Microsoft Community Support Specialist

    Was this answer helpful?

    0 comments