Error during Windows 10 setup System crashes immediately after installation
Error during Windows 10 setup System crashes immediately after installation
Hello, thank you for reaching out. It’s really helpful that there’s an option to get advice from others. After installing the new GPU and motherboard, I faced several crashes and realized a clean installation was necessary. Once I formatted all drives and performed a fresh install, BSODs persisted even when idle. I’ve tried disconnecting other drives, updated drivers, and checked for corrupted data, but the issue continues randomly. I’m unsure what else to try. Could you assist me? I have Windows 10 Pro, an ASUS ROG STRIX B550-A gaming PC with the latest BIOS, and I need to extract a 7zip file because the username in the SysnativeFileCollectionApp.7z file contains invalid characters.
Execute on one RAM stick, test each one separately inside the machine.
I also haven't turned on XMP or EXPO (which is the name it uses on AMD). It might be related to that. Also, the system has been running smoothly for about six hours now, with only minor slowdowns every ten minutes.
Examine the BSOD dump using windbg. Refer to the guide on analyzing memory dump files in Windows 10 for steps. The dump may be located at c:\windows\minidump or c:\windows\memory.dmp, depending on your startup options. Adjust BIOS settings if needed during idle checks.
I'm running a RAM test on my Ryzen 3800. I'll share the debug logs once the testing is complete.
\Windows\MEMORY.DMP]. Kernel bitmap: Address space is available, user space might not. ************* Path check summary ************** Response Time (ms) Location Deferred SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols Symbol search path: SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols Executable path: Windows 10 Kernel Version 19041 MP (16 procs) Free x64 Product: WinNT, suite: TerminalServer SingleUserTS Edition build lab: 19041.1.amd64fre.vb_release.191206-1406 Machine Name: Kernel base = 0xfffff807... ********** Analysis of the dump *********** Bugcheck findings *********** KERNEL SECURITY CHECK FAILED (139) – A core part has damaged a vital data structure. This could let someone with malicious intent take control. Details: Arg1: 000000000000001d, Type: memory safety violation, Address of trap frame, exception record, and a reserved debug flag. Key values: CPU time 3108, debug creation 8007007e, etc. ********** Important notes: - Memory key 1: CPU usage 3108 - Debug analysis created object at 8007007e - Symbols loading encountered missing .hh dbgerr004 value - Exception code c0000409 (stack buffer overflow) - OS version 10.0.19041.1 - Build layer 1
Additional info: OS build layers: 1
OS_BUILD_LAYERS: 1
BUGCHECK_P1: 1d
BUGCHECK_P2: fffff187c64df7a0
BUGCHECK_P3: fffff187c64df6f8
BUGCHECK_P4: 0
TRAP FRAME: 0xfffff187c64df7a0
Note: Some registers are zeroed or incorrect.
Registers: rax=ffffba8f184ddfa8, rbx=00000000, rcx=000000000000001d, ... *Continue analyzing*
For deeper insight, run !analyze -v 15 and follow the output carefully.*
I’ve encountered some new issues. After my PC was off for about 17 hours, I powered it back on. For the first time, it failed to start completely—almost instantly powering off before booting. Then a BSOD appeared after startup. Here’s the dump from Microsoft (Windows Debugger v10.0). All rights reserved. Loading Dump File [C:\Windows\MEMORY.DMP]. Kernel address space is available, but user address space might not. ************* Path validation summary ************** Response Time (ms) Location Deferred SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 10 Kernel Version 19041 MP (16 procs) Free x64 Product: WinNT, suite: TerminalServer SingleUserTS Edition build lab: 19041.1.amd64fre.vb_release.191206-1406 Machine Name: Kernel base = 0xfffff804`43c00000 PsLoadedModuleList = 0xfffff804`4482a290 Debug session time: Mon Jan 16 17:38:02.001 2023 (UTC +1:00) System Uptime: 0 days 0:00:21.624 Loading Kernel Symbols ............................................................... .......Page 802e01 not present in the dump file. Type ".hh dbgerr004" for details ... ............................................................. ............................................................. Loading User Symbols PEB is paged out (Peb.Ldr = 00000000`003be018). Type ".hh dbgerr001" for details Loading unloaded module list ...... For analysis, run !analyze -v 6: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MEMORY MANAGEMENT (1a) Any adjustments needed on parameter 1. Arguments: Arg1: 0000000000041792, a corrupt PTE was found. Parameter 2 holds the PTE address. Parameters 3/4 contain its low/high values. Arg2: fffffc3fff25c3b8 Debugging details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 3390 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-3BA0OOO ... * ... * More details available upon request. *