Windows 10: Windows 10 1809 / BSOD / The computer has rebooted from a bugcheck. The bugcheck was:...

This is almost exactly the same issue as my previous post at https://answers.microsoft.com/en-us/windows/forum/all/windows-10-1809-bsod-the-computer-has-rebooted/82f4d353-6d69-4077-af9d-7bc91126b8f8 except this time what I thought was the offending item (surface ethernet) was not actually connected.


This used to happen frequently, but this is the first time in a while, so I think there's an underlying issue of some type which I'd like to get sorted out before my warranty expires (plus it's really annoying as any unsaved work is gone)


I hibernated the computer, and went to bed. When I turned it on in the morning, instead of resuming from hibernate, it started from scratch. When I looked in Event Viewer, it said that it had BSOD around the time I hibernated it, though weirdly I did not notice - the screen just went blank when I hibernated it as usual and I went to bed.


Windows 10 1809


Microsoft Surface Book 2


The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000004, 0x000000000000012c, 0xffff8c0d4b4bf040, 0xfffff40507a8f800). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: e851761c-784a-4a14-92a1-7b327424bb56.


Minidump and sysinfo file zipped here -> https://1drv.ms/f/s!AqgJIvQRKGp6gzMAzLG2eg6xvFYH


Any help or advice appreciated.


The laptop is still under warranty, so if it's suspected that this is a hardware or warrantable issue, that would be good to know and I'll arrange to take it back to Microsoft, however I feel like it would be hard to "prove" that it's faulty as it happens irregularly.

:)

 

(BSOD) bugcheck was: 0x000000a0 INTERNAL_POWER_ERROR

Has any one got this BSOD when stress testing a overclock before? i can get the minidump if some one can read it for me i was trying for 4.5Ghz @ 1.31v and after around 20min of stressing i would get this BSOD and it would shut my system down not even sure i saw a BSOD just a shutdown?

 

Windows 10 | BSOD | bugcheck was: 0x1000007e (0xffffffffc0000005, 0xfffff80685a78d2a, 0xffffc7001c02

I recently put a fresh OS install on my Alienware 17R2. It is a Windows 10 Laptop. Ever since I have been getting the BSOD every few hours. From research I found out that it could possibly be from a Driver, but seeing as I just put a new OS installation on it, I couldnt tell you which once since they all just reinstalled including the ones for the computer directly. Hopefully you guys will be able to tell me more. I also have the Minidump but don't know where I need to upload the Minidump file that was created. I've tried everything that I know to do to fix it on my end, including reinstalling the OS system Again, running both sfc and the dism or whatever its called in the command prompt. Both found no issues. Hopefully you guys can shed some light on what is going on. I really need to get this fixed soon, as my college classes just started today for summer classes, and this is my only computer.

Computer Information:

Windows 10
Nvidia 960M Graphics
Intel HD Graphics 4600
16GB RAM


The computer has rebooted from a bugcheck. The bugcheck was: 0x1000007e (0xffffffffc0000005, 0xfffff80685a78d2a, 0xffffc7001c029758, 0xffffc7001c028f90). A dump was saved in: C:\Windows\Minidump\051817-11703-01.dmp. Report Id: d7bf07c3-b142-4a36-8afc-bc17dcf40b9a.

 

Windows 10 1809 / BSOD / The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f

Windows 10 1809

Microsoft Surface Book 2

After leaving computer idle/sleeping for some time, when I come back to "wake it up", I find that it has rebooted with the following BSOD while I was away.

This seems to happen perhaps once every day or two. Alternatively, it might only be happening when it has been "asleep" for a long time before I "wake it up".

I did not notice this happening before updating to 1809, though it's possible it may have and I may not have noticed.

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xffffaf88b982d060, 0xffffbf8cd4a3f7d0, 0xffffaf88ba5d42e0). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 5de9fe7e-bb67-4b00-b326-4dcd08da0185.

Minidump and sysinfo file zipped here -> Shared items 29-04-2019

Any help or advice appreciated.

The laptop is still under warranty, so if it's suspected that this is a hardware or warrantable issue, that would be good to know and I'll arrange to take it back to Microsoft, however I feel like it would be hard to "prove" that it's faulty as it happens
irregularly.