MingoMongo
Well-known member
Stats:
Windows 7 64bit SP1, ASUS P8Z68 Deluxe/Gen3, Intel Core i5-2500K, Corsair Vengeance 8GB Dual Channel DDR3 Memory Kit (CMZ8GX3M2A1866C9), Asus Nvidia GeForce GTX 960, Samsung SSD 860 EVO 500GB (Windows drive), WDC WD1002FAEX, Seagate ST2000DM006, Corsair Gold AX1200 (1200 Watts)
Disclaimer: I posted about this a while ago on the Windows Upgrade board but there's no responses. Since I've now found other BSODs, I'm thinking it might be a wider issue than just Windows updating.
In any case, upgrading to Windows 10 was giving me a "SYSTEM THREAD EXCEPTION NOT HANDLED" BSOD saying: "0xC1900101 - 0x40017, The installation failed in the SECOND_BOOT phase with an error during BOOT operation". This would happen and produce no dump files. sfc /scannow in cmd comes up with no issues, CheckSUR has no issues after I removed some old Avast registries, and Windows Memory Diagnostic finds no issues. Additionally, I have found that after using driver verifier, booting fine then resetting it in command prompt, I get a BSOD when I restart my PC and it begins shutting down. There's no message, but there's a code of "STOP 0x0000007E (0xFFFFFFFF80000003, 0xFFFFF80004AF3700, 0xFFFFF8800D067688, 0xFFFFF8800D066EF0)", again no crash logs.
I saw on forums switching OS to a SSD can cause problems with dump file generation, could that be happening? It's still set on "Kernel memory dump" at "%SystemRoot%\MEMORY.DMP".
Windows 7 64bit SP1, ASUS P8Z68 Deluxe/Gen3, Intel Core i5-2500K, Corsair Vengeance 8GB Dual Channel DDR3 Memory Kit (CMZ8GX3M2A1866C9), Asus Nvidia GeForce GTX 960, Samsung SSD 860 EVO 500GB (Windows drive), WDC WD1002FAEX, Seagate ST2000DM006, Corsair Gold AX1200 (1200 Watts)
Disclaimer: I posted about this a while ago on the Windows Upgrade board but there's no responses. Since I've now found other BSODs, I'm thinking it might be a wider issue than just Windows updating.
In any case, upgrading to Windows 10 was giving me a "SYSTEM THREAD EXCEPTION NOT HANDLED" BSOD saying: "0xC1900101 - 0x40017, The installation failed in the SECOND_BOOT phase with an error during BOOT operation". This would happen and produce no dump files. sfc /scannow in cmd comes up with no issues, CheckSUR has no issues after I removed some old Avast registries, and Windows Memory Diagnostic finds no issues. Additionally, I have found that after using driver verifier, booting fine then resetting it in command prompt, I get a BSOD when I restart my PC and it begins shutting down. There's no message, but there's a code of "STOP 0x0000007E (0xFFFFFFFF80000003, 0xFFFFF80004AF3700, 0xFFFFF8800D067688, 0xFFFFF8800D066EF0)", again no crash logs.
I saw on forums switching OS to a SSD can cause problems with dump file generation, could that be happening? It's still set on "Kernel memory dump" at "%SystemRoot%\MEMORY.DMP".