To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Then we get a blue screen or the system reboots (it depends on what the system settings are). The system goes to a BSOD because there is some exceptions happened in the kernel (either the device driver errors or the service errors), and Windows implements this mechanism: When it detects some errors occur in the kernel, it will kill the box in case some more severe damage happens. Since Windows system uses separated user mode and kernel mode memory space, stop errors are always caused by kernel portion components, such as a third-party device drivers, backup software or anti-virus services (buggy services). Probably caused by : ntoskrnl.exe ( nt+77dda )Ĭan I upload the dump file for some to take a look? Thanks. * using the -y argument when starting the debugger.
* using the _NT_SYMBOL_PATH environment variable. * Symbols can not be loaded because symbol path is not initialized. I tried to read the mini dump file using the debug tool. This appears to start to happen after I ran my Windows update a week ago. The notebook gets into BSoD in 7-10 min if I try to restart or place it in sleep. Hi, I have the same HP Notebook dv6t-2000, quad and the same problem (driver_power_state_failure).
0 kommentar(er)
