The computer has rebooted from a bugcheck. The bugcheck was: 0x00000139

Anonymous

The computer has rebooted from a bugcheck. The bugcheck was: 0x00000139 (0x0000000000000002, 0xffffc68f524dbd30, 0xffffc68f524dbc88, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: a23f65e8-6b3c-4a01-883e-912d1ec94e34.

I was playing Hollow Knight when my PC up and crashed, screen just went dark and then the PC reset itself.

https://drive.google.com/file/d/1Q_b-7SONLxhXh47JdG4gqYiIgA9E3olV/view?usp=sharing

For Mini

Thank you for your help!

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

51 answers

Anonymous

2024-09-19T13:57:50+00:00

What else would we need to look at to find out?
Was this answer helpful?

0 comments No comments
DaveM121 934.2K Reputation points Independent Advisor

2024-09-19T13:40:23+00:00

Not really, but if your PC does not crash tomorrow with Verifier enabled, that may indicate it is not a corrupt driver causing the crashes.
Was this answer helpful?

0 comments No comments
Anonymous

2024-09-19T13:15:43+00:00

okay that's good to know. Is there any reason why it's taking my PC so long to crash?
Was this answer helpful?

0 comments No comments
DaveM121 934.2K Reputation points Independent Advisor

2024-09-19T13:14:53+00:00

Yes, with Verifier enabled, your system will lag somewhat as the drivers are tested.
Was this answer helpful?

0 comments No comments
Anonymous

2024-09-19T13:13:22+00:00

Fair enough, thank you so much for helping! By the way is my system supposed to be running poorly?
Was this answer helpful?

0 comments No comments