This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(252.8, 83%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EK%3C/text%3E%3C/svg%3E)
Started encountering issues with my computer around December of 2025 that have progressively gotten worse since. These issues are as following:
-BSODs concerning win32k.sys and memory_management + something to do with system that I couldn't catch before it reset
-Black screens (no error stated) in which the 'your device ran into a problem and needs to restart' screen appears before rebooting
-Rebooting into BIOS where I am unable to get out of BIOS as the touchscreen and pen drivers do not work
-Multiple error codes, the most common being: 161 263 132 6062 6008 10010 1101 1801 1001 All occurring around the same time that crashes or Black screens occur -Freezing, lagging, driver disconnections issues
It has only booted into BIOS twice and an IT friend of mine assisted me with this, they think my issues are due to a faulty battery for the internal clock, but as for my more recent errors like the BSOD I am unsure if this is still relevant. The black screens and rebooting occurs when idle, when booting, and when normally using the computer with no particular pattern of cause, something as simple as entering my password causes a system shut-down. Currently when I boot my computer it's only on for about a minute or two before giving me a BSOD to which it then reboots and works for a bit longer before any issues occur. I have some dump files but it doesn't seem like they are made for every single crash only the bsods that provide an error code.
Please upload any minidump files you have, I will check those to see if they provide any insight into a potential cause of the system crashes.
Please do not upload a very large Memory.dmp file.
Open Windows File Explorer.
Navigate to C:\Windows\Minidump
Copy any minidump files onto your Desktop, then zip those up.
Upload the zip file to the Cloud (OneDrive... etc.), then choose to share those and get a share link.
Then post the link here to the zip file, so I can take a look for you.
Hi, after I posted this I recieved another BSOD with the SYSTEM_SERVICE_EXCEPTION code and this has showed up in my minidump folder alongside two other BSODs from November last year to early 2025.
However, I did not get a dmp file from the MEMORY_MANAGEMENT BSOD and noted that event viewer had an error at the same time this particular bsod occurred. This was event 161 and stated that the dump file creation failed. I have uploaded all three BSODs to a mediafire link (below) incase the ones from 2025 have any relevance to the 2026 bsod but just wanted to let you know that the dump file from memory management is not there.
I do tend to have error 161 whenever I get a black screen with no code so I'm not sure just how many dump files are missing and why that seems to be selective considering the newest bsod was successful in creating a dmp.
https://www.mediafire.com/file/0ytcioyenbhlsey/013026-14609-01.zip/file
Please let me know if this link is not accessible and thank you very much for your response.
Your minidump files just indicate generic memory (RAM) corruption no specific cause of the crashes is listed
1
The best option is to download the widely available free utility MemTest86, then run a full 4 pass scan with that to test your RAM for physical errors
2
If no RAM errors are found, to try to force Windows to show any faulting drivers, the best option would be to turn on Driver Verifier, let your PC crash 3 times, then you must turn off Driver Verifier, and finally, upload any newly created minidump files
Before you run Driver Verifier, please create a new System Restore Point
.
.
.
Note, if you have any difficulty getting into Windows with Driver Verifier enabled:
Start your PC, just as Windows attempts to load (spinning dots), press and hold Power Button for 5 - 10 seconds to perform a Hard Shut Down
Do this twice
On the third start Windows will boot into the Recovery Environment and from there you can access System Repair, Safe Mode, Command Prompt... etc.
Go to Troubleshoot - Advanced Option - Startup Settings and click Restart
Upon restart, press 4 to enter Safe Mode
Open Command Prompt as Administrator and run these two commands, then restart your PC.
verifier /reset
verifier /bootmode resetonbootfail
Thank you for your response! I will look into the driver verifier and memtest86 solutions as soon as possible. I did however have a couple of concerns I was wondering if they would be an issue?
I only ask because I do see that people say memtest86 is run within the BIOS boot, and Additionally with driver verifier there is a need for keyboard inputs to escape the BSOD loop.
I can try to find a cable keyboard/mouse that works with USBC and hopefully that does register in the BIOS but I did just want to ask incase.
It would be best to try to find a keyboard that will work with USB-C when performing these steps.
