HP Elite Mini 600 G9 faces BSOD problems post-Windows 11 upgrade on a desktop system.
HP Elite Mini 600 G9 faces BSOD problems post-Windows 11 upgrade on a desktop system.
Hey everyone, I’m looking for some guidance on the BSOD problem that’s been bothering me lately. I’ve shared the minidump files from one of the affected machines. So far, around three similar setups have faced the same issue. It started after an in-place upgrade from Windows 10 to Windows 11. Any advice would be greatly appreciated!
Attribuire la responsabilité à la mise à jour en place, et non au modèle du PC.
The newest Windows 11 update omitted kernel symbols, making it hard to debug dump files for some users. Symbols help the debugger understand driver commands; without them, data appears random. The developer builds these symbols and sends them to Microsoft, which then distributes them to clients. Locally, you might have your own symbols, allowing testing in a debugger. Open the Microsoft Store and install WinDbg (possibly named WinDbg Preview). With the debugger ready, double-click dump files to launch them. Click the blue "!Analyze -v" option once opened. If "Wrong Symbols" appears, you're facing the same problem and we can't resolve it. If not, save the output to a text file and share the link in the same way as your dump files. Repeat this process for all your dump files.
Thanks! I see the issue with the incorrect symbols in the Ntoskrnl output. The problem seems to occur even after a fresh Windows 11 installation. Any tips?
Hi Bjoolz, I successfully ran WinDbg on the impacted PC and this time 'netio.sys' was identified as the problem. I checked the Device Manager under Network adapters, aiming to uninstall or disable unused drivers except for the active physical NIC. The issue still remains, so I'm feeling stuck. Need help!
The most recent Windows update fixed the problem. If you have any updated dump files, please share them. I’m not sure about the details in your WinDbg screenshot, but it seems to be incorrect.