Windows 10: BSOD randomly, usually error 0x0000001a

Hello again,

I am resurrecting this old thread because I am the original poster and I am again having Windows 10 crashing problems.

Removing the incompatible RAM did indeed solve the frequent BSOD a few months ago, unless you count the fairly rare BSODs after that.

However, I now have a few other problems on the same machine. I will describe the symptoms, and maybe one of you more experienced users can see a common theme or pattern, because I would not be surprised if these problems are related to my previous one.

First of all, the problem started when I manually downloaded and installed the Windows 10 Creator's Update (Build 1703) on top of the Anniversary Update (Build 1607). I suddenly had several problems:

• USB mouse and keyboard freeze often. I have to unplug them and put them in other USB slots for them to work. Then those eventually freeze and I have to find two more slots. Used slots rarely work again without restarting. When I run out of slots I have to restart!
• My external USB hard drive has the same problem. It eventually stops working and I have to find another slot.
• Also, sometimes when I plug in the external hard drive, it seems to kill other USB slots -- for instance, the mouse and keyboard.
• I had a secondary internal hard drive. This disappeared when I upgraded to Creator's Update. (There is a small chance that this is a coincidence, because this had happened once or twice before the update.)
• Cursor often becomes invisible inside a particular window, and I have to minimize and maximize that window for the cursor to reappear.
• Cursor often feels laggy or choppy.

Now, a little while after I realized I had all these issues, I backed up all of my important data, wiped the hard drive, and reinstalled Windows 10 Build 1607. However, all of the problems seem to have remained. For instance, my hard drive is permanently unreadable and my mouse and keyboard freeze very frequently.

I can't quite figure out what's behind all these problems, but these might be a few clues.

• BSODs are not common. Instead, I am forced to eventually restart because of dead USB ports. (Often after forcing a restart, I will get a BSOD on boot-up. See attachment.)
• I have a compact horizontal desktop with a monitor on top of it. Could overheating be an issue?
• I have a secondary ASUS PB278Q 2560x1440 monitor. Because of the constant headaches of using my desktop, I recently plugged this monitor, mouse, and keyboard into my laptop. When I did this, I had the same USB freezing problem, and I'd have to use other USB ports until they died too. (The trackpad/ball and laptop keyboard still worked.) Also, when I unplugged my ASUS monitor, the laptop had a BSOD! Before this, I considered my laptop to be very reliable. I was using this monitor when I had my previous problem.
• Once in a while a USB port seems to un-freeze after a while. All USB ports work after rebooting.

Please see the attached ZIP. Three out of five BSOD messages are MEMORY_MANAGEMENT although, again, it seems to be BSODs aren't the main issue.

I am looking forward to your insights. Thank you!

 

There are many different bugchecks in the dumpfiles.

The cause for different error codes are usually hardware and lower level problems.

There are errors in windows filesystem too, so it could be an problem with the Win 10 update or your hard disk. Memory RAM seems to be okay now.

The errors I found in eventlog:
Code: 2017-06-16T12 36:57.215 Error: Volume C: (\Device\HarddiskVolume2) needs to be taken offline to perform a Full Chkdsk. Please run "CHKDSK /F" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell. 2017-06-16T12 36:57.215 Error: A corruption was discovered in the file system structure on volume C:. 2017-06-16T12 36:57.364 Error: The file system structure on volume C: cannot be corrected.Please run the chkdsk utility on the volume C:. 2017-06-16T12 37:07.405 Error: The file system structure on volume C: cannot be corrected.Please run the chkdsk utility on the volume C:. 2017-06-16T12 37:24.293 Error: A corruption was discovered in the file system structure on volume C:. 2017-06-16T12 38:21.038 Error: A corruption was discovered in the file system structure on volume C:. 2017-06-16T12 38:21.088 Error: A corruption was discovered in the file system structure on volume C:. 2017-06-16T12 38:21.107 Error: A corruption was discovered in the file system structure on volume C:. 2017-06-16T12 38:21.134 Error: A corruption was discovered in the file system structure on volume C:. 2017-06-16T12 38:21.157 Error: A corruption was discovered in the file system structure on volume C:. 2017-06-16T12 38:21.178 Error: A corruption was discovered in the file system structure on volume C:. 2017-06-16T12 38:21.185 Error: A corruption was discovered in the file system structure on volume C:. 2017-06-16T12 38:21.229 Error: A corruption was discovered in the file system structure on volume C:. 2017-06-16T12 38:21.241 Error: A corruption was discovered in the file system structure on volume C:. 2017-06-16T12 38:21.258 Error: A corruption was discovered in the file system structure on volume C:. 2017-06-16T12 38:21.270 Error: A corruption was discovered in the file system structure on volume C:. 2017-06-16T12 38:21.283 Error: A corruption was discovered in the file system structure on volume C:. 2017-06-16T12 38:21.289 Error: A corruption was discovered in the file system structure on volume C:.[/quote] Code: 2017-06-16T13 24:43.166 Error: An I/O operation initiated by the Registry failed unrecoverably.The Registry could not flush hive (file): '\??\C:\Windows\AppCompat\Programs\Amcache.hve'. 2017-06-16T18 56:03.600 Error: {Registry Hive Recovered} Registry hive (file): '\SystemRoot\System32\Config\BBI' was corrupted and it has been recovered. Some data might have been lost. 2017-06-16T20 33:06.801 Error: {Registry Hive Recovered} Registry hive (file): '\??\C:\Users\Philip\ntuser.dat' was corrupted and it has been recovered. Some data might have been lost. 2017-06-19T14 59:45.127 Error: {Registry Hive Recovered} Registry hive (file): '\SystemRoot\System32\Config\BBI' was corrupted and it has been recovered. Some data might have been lost.[/quote]

First step:
Repair Windows Filesystem:

1. Open an elevated command prompt.
2. In the elevated command prompt, type these commands below, and press Enter:

dism /Online /NoRestart /Cleanup-Image /CheckHealth
dism /Online /NoRestart /Cleanup-Image /ScanHealth
dism /Online /NoRestart /Cleanup-Image /RestoreHealth
dism /Online /NoRestart /Cleanup-Image /StartComponentCleanup
dism /Online /NoRestart /Cleanup-Image /AnalyzeComponentStore

sfc /scannow

chkdsk %systemdrive% /F /R /X
fsutil dirty set %systemdrive%

SFC:
The SFC command scans the integrity of all protected system files and replaces incorrect versions with correct Microsoft versions.
DISM:
If a Windows image becomes unserviceable, you can use the Deployment Imaging and Servicing Management (DISM) tool to update the files and correct the problem.
For example, you would use sfc /scannow command is unable to repair corrupted or modified system files because the component store (source) is corrupted. SFC should be able to repair the files afterwards.
CHKDSK:
Checking your drives for errors every once in a while can help fix some performance issues. Drive errors can usually be caused by bad sectors, improper shutdowns, bad software, corruption, physical damage, etc...

Second step:





Diagnostic Test

HDD TEST


Run HDTune to check health and scan for errors.







Note It may take some time, but look for signs of any errors or failure.

You can also run a disk check using chkdsk. Refer to the tutorial for details of how to do this.

 

Okay, I've run those commands.

I got all the way to chkdsk, and then I had to restart. Here is the command prompt output up to this point: BSOD commands 1 - Pastebin.com

Chkdsk ran on startup, and completed very quickly with no errors, I think.

Right after startup, Windows told me to restart to fix hard drive errors. Chkdsk again ran on startup and said it was scanning and repairing. I think this took a few minutes.

Then I ran the last command, fsutil. Output here: BSOD commands 2 - Pastebin.com

I then ran HD Tune (not quick mode). It took several hours and found no errors (it was all green).

This has not solved the problem. In fact, none of the USB ports are working anymore. They all seem to be permanently disabled. It almost seems like one of these processes killed all the USB ports. Is this possible?

You mentioned hardware problems. Could the motherboard be overheating or dying? I wonder if this would explain the random hardware problems I mentioned previously.

 

Did u receive any bsod after running those commands?
Did u install the correct drivers for USB controller?
What about running in safemode?

Start Windows 10 in Safe Mode

If you have a problem with your PC, you can troubleshoot by starting it in safe mode. Safe mode starts Windows with a minimal set of drivers and services. If a problem doesn't reappear when you start your PC in safe mode, you can eliminate the default settings and basic device drivers and services as possible causes.

Boot into Safe Mode on Windows 10 Windows 10 Performance Maintenance Tutorials

 

No BSOD after those commands. I tried previously to install the correct USB drivers (and I tried again just now), but it didn't work. And I just tried safe mode, but still no USB ports are working.

 

There are a few things you can do:

1. Reset BIOS via BIOS settings or removing BIOS battery for about 30 minutes.
2. Check BIOS settings if somethings strange with USB settings.
3. Verify if USB Keyboard is working at boot prompt before windows is loading. Press keys like F2, F8, F12. See what happens.
4. Is the Keyboard LED on?
5. Put an USB stick with an live system like ubuntu or another Unix distribution. See if its loading.
6. Boot an live linux like ubuntu from USB stick or CD-Rom an check if USB ports are working.
7. Try every USB port (2.0, 3.0,...) on front and back.
8. Completely power off pc, put out power cable over night.

 

I put Lubuntu on USB and the computer recognized it and booted into Lubuntu! The mouse didn't work in Lubuntu (wasn't sure about the keyboard). And when I boot into Windows 10, my USB drive *works* in every port I've tried (3 or 4). However, the keyboard and mouse won't work in any ports. There is no light on the keyboard even when booting up. So it appears that the keyboard and mouse are dead. But why? And why at the same time? And why did they stop working and then work again in different ports? Thanks.

 

And now, they dont work in different ports again? You should test them on another computer if possible.

 

Code: DRIVER_POWER_STATE_FAILURE (9f)A driver has failed to complete a power IRP within a specific time.Arguments:Arg1: 0000000000000003, A device object has been blocking an Irp for too long a timeArg2: ffffc109bd45d060, Physical Device Object of the stackArg3: ffffd1807525b960, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stackArg4: ffffc109c29805b0, The blocked IRPDebugging Details:------------------DUMP_FILE_ATTRIBUTES: 0xc Insufficient Dumpfile Size Kernel Generated Triage DumpDRVPOWERSTATE_SUBCODE: 3IMAGE_NAME: pci.sysDEBUG_FLR_IMAGE_TIMESTAMP: 5850cc6bMODULE_NAME: pciFAULTING_MODULE: fffff807abfb0000 pciCUSTOMER_CRASH_COUNT: 1DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULTBUGCHECK_STR: 0x9FPROCESS_NAME: SystemCURRENT_IRQL: 2ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64freDPC_STACK_BASE: FFFFD18075262FB0STACK_TEXT: ffffd180`7525b928 fffff801`33a158b3 : 00000000`0000009f 00000000`00000003 ffffc109`bd45d060 ffffd180`7525b960 : nt!KeBugCheckExffffd180`7525b930 fffff801`33a157c6 : ffffc109`c534d010 00000000`00000001 00000000`00000001 ffffd180`74fef180 : nt!PopIrpWatchdogBugcheck+0xebffffd180`7525b990 fffff801`33855930 : ffffc109`c534d048 00000000`00315708 00000000`00140001 00000000`00000000 : nt!PopIrpWatchdog+0x22ffffd180`7525b9e0 fffff801`33970d6a : ffffffff`00000000 ffffd180`74fef180 ffffd180`74ffbcc0 ffffc109`c3a4d440 : nt!KiRetireDpcList+0x440ffffd180`7525bc60 00000000`00000000 : ffffd180`7525c000 ffffd180`75256000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5aSTACK_COMMAND: kbFOLLOWUP_NAME: MachineOwnerIMAGE_VERSION: 10.0.14393.594FAILURE_BUCKET_ID: 0x9F_3_POWER_DOWN_nvlddmkm_IMAGE_pci.sysBUCKET_ID: 0x9F_3_POWER_DOWN_nvlddmkm_IMAGE_pci.sysANALYSIS_SOURCE: KMFAILURE_ID_HASH_STRING: km:0x9f_3_power_down_nvlddmkm_image_pci.sysFAILURE_ID_HASH: {5337281a-2de3-9ebb-5277-3f179de9b48f}[/quote]

Code: 6: kd> !irp ffffc109c29805b0Irp is active with 3 stacks 2 is current (= 0xffffc109c29806c8) No Mdl: No System Buffer: Thread 00000000: Irp stack trace. Pending has been returned cmd flg cl Device File Completion-Context [ 16, 0] 0 0 ffffc109bd45d060 00000000 fffff807ae2aed70-ffffd1807c4998e0 \Driver\pci dxgkrnl!DpiFdoPowerCompletionRoutine Args: 00000000 00000000 00000000 00000002>[ 16, 2] 0 e1 ffffc109be806030 00000000 fffff8013393d510-ffffc109c534d010 Success Error Cancel pending Unable to load image nvlddmkm.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for nvlddmkm.sys*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys \Driver\nvlddmkm nt!PopRequestCompletion Args: 00041100 00000001 00000001 00000002 [ 0, 0] 0 0 00000000 00000000 00000000-ffffc109c534d010 Args: 00000000 00000000 00000000 00000000[/quote] pci.sys NT Plug and Play PCI Enumerator Windows Update

nvlddmkm.sys nVidia Video drivers Download Drivers | NVIDIA
Get from OEM for laptops


1) 13) Uninstall all Nvidia drivers/software
The best way to do this is to uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from your Graphics card manufacturer or from the NVidia website.
When you do this be sure the "clean install" box is checked and only install the Graphics driver and the PhysX driver.Display Driver Uninstaller Download version 17.0.6.7: Official Display Driver Uninstaller DDU Download


2) open administrative command prompt and type or copy and paste: chkdsk /x /r
This may take many hours so plan to run overnight.
Please find the chkdsk results in the eventvwr using the information in these links and post into the thread:

Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
CHKDSK: What is it and how do I run it? - Ask Leo!
How do I see the results of a CHKDSK that ran on boot? - Ask Leo!
How to find chkdsk results in Windows 10 - Winaero uses 26226 find

 

BSODHunter, okay, I just tried connecting the keyboard and mouse to another computer and they both work! So the problem is obviously with my computer hardware or software.

zbook, my computer is a desktop. I mentioned my laptop earlier because I was trying to see if my ASUS monitor was the problem, so I connected to my laptop. But I will try following your directions about the Nvidia drivers/software and chkdsk.

 

zbook, doing that clean uninstall and reinstall fixed the keyboard and mouse issue, at least so far! I'll post here if I find any problems. And I already ran chkdsk previously in the thread. Would you still recommend it?

 

graphics driver reinstall fixed keyboard and mouse issue? wtf

 

Yeah, I don't understand why that made it work...

BTW, I may upgrade to Creator's Update again, because now I think maybe that wasn't the reason for my computer issues. Any thoughts?

 

The drive was marked dirty.
This allows you to reboot without having it automatically repair.
The drive problem remains unaddressed.
It's important to have a healthy partition.
Please run chdsk /x /r and then post the completed results in the thread.

This link was in xp days but it has useful info: chkdisk-type of file system is NTFS, the volume is dirty, what does - Microsoft Community

 

Okay, I've run the chkdsk /x /r command and here are the results: Chkdsk results - Pastebin.com