Windows 10: BSOD on boot

Don't know why but I have been having some issues with multiple bsod on boot, after facing about a two or three of them the computer starts up fine. This doesn't happen everyday but its happening quite frequently for something to be wrong.

I have tried to diagnose what my issue is with no avail, part of me believes hardware failure. Though that could be me being paranoid.

Any help would be greatly appreciated.

:)

 

BSOD after upgrade to windows 10

After upgrading Win 7 to Windows 10 my PC endswith BSOD every time it boots up.

If I let it finish the boot without logging in, it BSODs at the end of the boot.

If I log in as soon as I am able to, it BSODs at the end of the boot/login.

Maybe one of the last services loaded is cause of the BSOD?

I can boot to safe mode with no problems,

and in the Windows system log I see lots of faults under the latest normal boot sequence.

What do I do to narrow down the problem?

 

system_thread_exception_not_handled (edevmon.sys) and system_service_exception(edevmon.sys) on asus laptop. doesnt boot on windows

I can't boot to windows. i'm always stuck up on BSOD and it keeps on restarting when it gets to BSOD and I can't boot to any recovery..

 

Hi pokeimon,

Welcome to the 10forums.

My focus for now will be to get rid of all the outdated drivers, i.e. drivers that older then the release date of Windows 10.
Please disconnect every USB device, exception for mouse and keyboard, while troubleshooting.
Please update (reinstall) Paragon or temporarily remove it.

Please uninstall ASUS AI Suite II
Code: *** WARNING: Unable to verify timestamp for AsIO.sys *** ERROR: Module load completed but symbols could not be loaded for AsIO.sys[/quote] Please update your Intel network drivers
Driver Reference Table - e1c63x64.sys
Code: *** WARNING: Unable to verify timestamp for e1c63x64.sys *** ERROR: Module load completed but symbols could not be loaded for e1c63x64.sys 2: kd> lmvm e1c63x64 start end module name fffff801`69140000 fffff801`691b0000 e1c63x64 T (no symbols) Loaded symbol image file: e1c63x64.sys Image path: \SystemRoot\system32\DRIVERS\e1c63x64.sys Image name: e1c63x64.sys Timestamp: Sat Aug 11 00:40:50 2012 (50258DF2) CheckSum: 0007E11B ImageSize: 00070000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote] Please update your Intel Rapid Storage Technology drivers.
Driver Reference Table - iaStorA.sys

Code: ffffd000`20bfb658 fffff801`fb86d300Unable to load image \SystemRoot\System32\drivers\iaStorA.sys, Win32 error 0n*** WARNING: Unable to verify timestamp for iaStorA.sys *** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys iaStorA+0x6d300 2: kd> lmvm iaStorA start end module name fffff801`fb800000 fffff801`fbab6000 iaStorA T (no symbols) Loaded symbol image file: iaStorA.sys Image path: \SystemRoot\System32\drivers\iaStorA.sys Image name: iaStorA.sys Timestamp: Mon Oct 28 22:15:26 2013 (526ED3EE) CheckSum: 0009FA1B ImageSize: 002B6000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote] Please fill in your system specsPlease follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely.How to fill in your system specs:

 

The last dumpfile
Code: ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck C2, {10, ffffe000eb0f23d0, 2000000, ffffe000eb0f23f0} Probably caused by : disk.sys ( disk!DiskDeviceControl+8f ) Followup: MachineOwner --------- STACK_TEXT: ffffd000`20bfb198 fffff801`9f850dca : 00000000`000000c2 00000000`00000010 ffffe000`eb0f23d0 00000000`02000000 : nt!KeBugCheckEx ffffd000`20bfb1a0 fffff801`fc5d271f : ffffd000`20bfb340 fffff801`00000000 ffffe000`eb04d300 ffffd001`00000700 : nt!ExFreePool+0x2aa ffffd000`20bfb280 fffff801`fc5dd17f : ffffe000`e99fcbc0 ffffd000`20bfb429 00000000`00000001 fffff801`fc60c000 : CLASSPNP!ClassSendSrbSynchronous+0xd9f ffffd000`20bfb3b0 fffff801`fc5d3317 : 00000000`00000001 ffffe000`eb0e35a0 ffffe000`00000001 00000000`eb0e3501 : CLASSPNP!DeviceProcessDsmTrimRequest+0x2fb ffffd000`20bfb480 fffff801`fc5d3906 : 00000000`00000000 00000000`00001000 00000000`00000000 ffffd001`000006a1 : CLASSPNP!ClasspDeviceTrimProcess+0x23b ffffd000`20bfb540 fffff801`fc5b16cf : ff000101`00000101 fffff801`00000000 00000000`002d9404 fffff801`00000000 : CLASSPNP!ClassDeviceControl+0x3c6 ffffd000`20bfb6b0 fffff801`fc5d8a73 : ffffe000`e614aa30 fffff801`9f676e70 ffffe000`e3a8c660 00000000`00000000 : disk!DiskDeviceControl+0x8f ffffd000`20bfb740 fffff801`fb6f4925 : ffffe000`eb07b2a0 ffffe000`e614aa00 ffffe000`eb0e3540 00000000`000007ff : CLASSPNP!ClassDeviceControlDispatch+0x53 ffffd000`20bfb770 fffff801`fb6e2935 : ffffe000`eb07b200 00000000`00000000 00000000`00000000 ffffe000`eb07b2a0 : partmgr!PmIoctlRedirect+0x4d ffffd000`20bfb7e0 fffff801`fb6f38c8 : ffffe000`e616bc30 ffffe000`e616bc00 ffffe000`e75fcbb0 ffffd001`00000100 : partmgr!PmFilterDeviceControl+0x2a5 ffffd000`20bfb830 fffff801`fb6e21a7 : ffffe000`e75fcbb0 ffffe000`eb0e35b0 00000000`00000000 ffffe000`eb07b568 : partmgr!PartitionIoctlDsm+0x2b8 ffffd000`20bfb8c0 fffff801`fb7a153c : ffffe000`e77eedd0 00000000`00000000 ffffe000`e83fe180 ffffd000`00000024 : partmgr!PmLegacyDeviceControl+0x27 ffffd000`20bfb8f0 fffff801`9f6fc3ca : ffffe000`e83fe180 00000000`00000002 ffffe000`eb07b2a0 ffffd000`20bfbae0 : volmgr!VmDeviceControl+0x25c ffffd000`20bfb950 fffff801`9faa636d : ffffe000`e83fe608 ffffe000`e83fe180 fffff801`fc4272a0 00000000`00000000 : nt!IoSynchronousCallDriver+0x52 ffffd000`20bfb9b0 fffff801`fc411688 : ffffe000`eb07b2a0 ffffd000`20bfbae0 ffffe000`e83fe180 ffffe000`e83fe000 : nt!IoForwardIrpSynchronously+0x41 ffffd000`20bfb9e0 fffff801`fc41123d : 00000000`00000000 ffffc000`923d1a00 ffffe000`eb07b2a0 ffffe000`eadca260 : fvevol!FveManageDataSetAttributes+0x26c ffffd000`20bfbc00 fffff801`fc4d8687 : 00000000`00000000 ffffe000`e616bc00 00000000`00000103 fffff801`fbc0d334 : fvevol!FveFilterDeviceControl+0x20d ffffd000`20bfbcc0 fffff801`fc4ca9b5 : 00000000`00000000 00000000`00000000 ffffe000`eb07b2a0 00000000`00000000 : volsnap!VspManageDataSetAttributes+0x2c7 ffffd000`20bfbe90 fffff801`fbc1cb86 : ffffe000`eb3cd6c8 ffffe000`eadca260 ffffe000`e4bce040 ffffe000`eb392080 : volsnap!VolSnapDeviceControl+0x425 ffffd000`20bfbf50 fffff801`9f764337 : ffffd000`20405f70 00000000`00000000 00000000`00000000 00000000`00000000 : NTFS!NtfsStorageDriverCallout+0x16 ffffd000`20bfbf80 fffff801`9f7642fd : 00000000`00006000 00000000`00000012 ffffd000`20bfc000 fffff801`9f694ea1 : nt!KxSwitchKernelStackCallout+0x27 ffffd001`9bf67860 fffff801`9f694ea1 : 00000000`00000006 00000000`00006000 fffff6e8`001053b8 ffffd000`00000000 : nt!KiSwitchKernelStackContinue ffffd001`9bf67880 fffff801`9f694c16 : 00000000`00000009 00000000`00006000 00000000`00000000 ffffd001`9bf67900 : nt!KiExpandKernelStackAndCalloutOnStackSegment+0x131 ffffd001`9bf67900 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExpandKernelStackAndCalloutSwitchStack+0xa6 STACK_COMMAND: kb FOLLOWUP_IP: disk!DiskDeviceControl+8f fffff801`fc5b16cf 488b4c2450 mov rcx,qword ptr [rsp+50h] SYMBOL_STACK_INDEX: 6 SYMBOL_NAME: disk!DiskDeviceControl+8f FOLLOWUP_NAME: MachineOwner MODULE_NAME: disk IMAGE_NAME: disk.sys DEBUG_FLR_IMAGE_TIMESTAMP: 5632d16e IMAGE_VERSION: 10.0.10586.0 BUCKET_ID_FUNC_OFFSET: 8f FAILURE_BUCKET_ID: 0xc2_10_disk!DiskDeviceControl[/quote] If you are using Paragon software like Harddisk manager etc. please update to windows 10 compatible version, the drivers are from 2014.

 

Thank you for your help, I currently did all the driver/software changed except for RST since I couldn't find a newer one that installs incorrectly.