Windows 10: BSOD and reboot - random times

Attachment 120491

I'm getting this weird random reboot - seems to happen when i'm away from the PC for a period of time.
Event viewer says:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000003, 0xffffe08123ffa260, 0xfffff801e7a988e0, 0xffffe081349b7010). A dump was saved in: C:\windows\MEMORY.DMP. Report Id: 5e74b7d4-377e-4f97-9de8-b4a354bfb2f9.

Anyone have any ideas?

:)

 

windows 10 anniversary update

oops i also forgot to mention that the press enter and f8 things do not work ...the only way out of this screen is to hold power button for a soft off and then count to 10 and reboot.......it does reboot to normal windows till the bsod comes back and the
bsod is very random it doenst matter what i am doing on the puter at the time it just crashes

 

Dell Alienware X51 R2 BSOD, random reboots and crashes

Unfortunately the clean boot did not address my issue. I am still having random reboots. No BSOD during the clean boot mode, but I have had two random reboots, after which the computer turns itself on and off again in quick succession, before coming
back online.

 

I'm not as good at reading the dump file as the guys who work BSOD threads are, but from a cursory look, I get

Code: \Driver\USBHUB3 DriverObject ffffe08121d9fa40Current Irp 00000000 RefCount 0 Type 00000022 Flags 00003044SecurityDescriptor ffff8004e4c15290 DevExt ffffe08123ff9e70 DevObjExt ffffe08123ffa3d8 DevNode ffffe0812419e960 ExtensionFlags (0000000000) Characteristics (0x00000100) FILE_DEVICE_SECURE_OPENAttachedDevice (Upper) ffffe08122995050*** WARNING: Unable to verify timestamp for msux64w10.sys*** ERROR: Module load completed but symbols could not be loaded for msux64w10.sys \Driver\msux64w10[/quote] msux64w10 is probably a Microsoft USB Fast/Gigabit Ethernet NIC NDIS6.40 64-bit Driver

If you have a USB ethernet dongle I would try to update the driver and see if that makes a difference.

The other dump file was

Code: Use !analyze -v to get detailed debugging information. BugCheck 9F, {3, ffff9c08a4d74060, fffff803af9568e0, ffff9c08a5f23b80} Probably caused by : pci.sys Followup: MachineOwner THREAD_SHA1_HASH_MOD_FUNC: 81a7ba75a791115b4f55c8910c64a260d525502e THREAD_SHA1_HASH_MOD_FUNC_OFFSET: dfbcb3f9a415e4b8c955f15c39a77a130e810657 THREAD_SHA1_HASH_MOD: f08ac56120cad14894587db086f77ce277bfae84 FOLLOWUP_NAME: MachineOwner IMAGE_VERSION: 10.0.14393.351 FAILURE_BUCKET_ID: 0x9F_3_USBXHCI_IMAGE_pci.sys BUCKET_ID: 0x9F_3_USBXHCI_IMAGE_pci.sys[/quote] That shows it to be the USB Host controller. So, it could be a USB problem. Maybe check the Advanced power options and see if the machine is allowed to turn off the USB hubs to save power and disable that option if updating the driver doesn't work.

 

As you have a surface book her some more info on the surface ethernet drivers and downloadlinks.
Surface Ethernet Drivers | Ask the Core Team

 

It looks like it was the USB host. I actually had to go into device manager to find how to shut it off since Surface doesnt have so much flexibility in the power option.s but once i shut if off, it hasnt reoccurred for the last week.

Thanks, everyone!