| atapi.sys |
ATAPI IDE Miniport Driver |
Windows Update |
Code:
BugCheck 133, {1, 1e00, 0, 0}Probably caused by : atapi.sys ( atapi!AtapiHwInterrupt+6a )
Code:
BugCheck FE, {5, ffff800159cc51a0, 10024397, ffff8001657a3688}Probably caused by : memory_corruption
Code:
BugCheck 133, {1, 1e00, 0, 0}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sysProbably caused by : atapi.sys ( atapi!AtapiHwInterrupt+6a )
| HDAudBus.sys |
High Definition Audio Bus Driver |
Windows Update |
Code:
BugCheck 133, {1, 1e00, 0, 0}Probably caused by : HDAudBus.sys ( HDAudBus!HdaController::Isr+cf )
Code:
BugCheck 133, {1, 1e00, 0, 0}Probably caused by : ntkrnlmp.exe ( nt!KeAccumulateTicks+1472ba )
Code:
BugCheck 133, {1, 1e00, 0, 0}
| ndis.sys |
NDIS 6.20 Wrapper Driver |
Windows Update |
Code:
Use !analyze -v to get detailed debugging information.BugCheck 133, {1, 1e00, 0, 0}Probably caused by : HDAudBus.sys ( HDAudBus!HdaController::Isr+16c )
Code:
BugCheck 133, {1, 1e00, 0, 0}*** WARNING: Unable to verify timestamp for nvlddmkm.sys*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sysProbably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+d33e )
Code:
BugCheck 133, {1, 1e00, 0, 0}Probably caused by : HDAudBus.sys ( HDAudBus!HdaController::Isr+1f3 )
Code:
BugCheck 133, {1, 1e00, 0, 0}Probably caused by : atapi.sys ( atapi!AtapiHwInterrupt+34 )
Code:
BugCheck 133, {1, 1e00, 0, 0}Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+d33e )
Code:
BugCheck 133, {1, 1e00, 0, 0}Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+d33e )
Code:
BugCheck 133, {1, 1e00, 0, 0}Probably caused by : atapi.sys ( atapi!AtapiHwInterrupt+34 )
Code:
BugCheck 133, {1, 1e00, 0, 0}*** WARNING: Unable to verify timestamp for rt640x64.sys*** ERROR: Module load completed but symbols could not be loaded for rt640x64.sysProbably caused by : atapi.sys ( atapi!AtapiHwInterrupt+34 )
The system failed to flush data to the transaction log. Corruption may occur in VolumeId: L:, DeviceName: \Device\HarddiskVolume14.(A device which does not exist was specified.)
Code:
A corruption was discovered in the file system structure on volume C:.The exact nature of the corruption is unknown. The file system structures need to be scanned and fixed offline.
Code:
A corruption was discovered in the file system structure on volume Windows 10 SSD.The exact nature of the corruption is unknown. The file system structures need to be scanned and fixed offline.
| hidusb.sys |
USB Miniport Driver for Input Devices |
Windows Update |
Code:
The driver \Driver\HidUsb failed to load for the device USB\VID_05A4&PID_9881&MI_01\6&11ea56c&0&0001.
Code:
The system failed to flush data to the transaction log. Corruption may occur in VolumeId: G:, DeviceName: \Device\HarddiskVolume8.(A device which does not exist was specified.)
Code:
An error was detected on device \Device\Harddisk6\DR11 during a paging operation.
Some of these steps you had indicated that you did but please repeat these so we can have it viewable in the thread:
1) winver (in the pop up about windows > view your windows version and build > type this information into the thread)
2) sfc /scannow
3) dism /online /cleanup-image /restorehealth
4) chkdsk /scan (run on each drive) (if it displays any corruption plan to run chkdsk /x /f /r overnight on the drive)
When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on copy > paste into the thread
5) msconfig (in the pop up system configuration > move the dot from normal startup to selective startup > uncheck load startup items > click service tab > in left lower corner check hide all Microsoft services > in the lower right side click disable all > click apply or ok > do not reboot)
6) taskmgr (in the pop up task manager > click on the start up tab > click on status so that the column sorts with enable rising to the top > right click on each row with enable and change to disable)
7) shutdown /r (you will reboot the computer so that it is in clean boot)
Evaluate the performance on your computer in clean boot during typical use. Are the boots faster or slower? Are the shutdowns faster or slower? Are the hangs more frequent, less frequent or the same? Are the spontaneous bsod more frequent, less frequent or the same?
8) Uninstall all Nvidia software and drivers:
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 Driver Uninstaller Download version 17.0.6.6
9) Were you previously using this software/driver:
It was a older misbehaving driver. If you still have any of this software please uninstall it.
10) Run memtest86+ version 5.01 for at least 8 runs. This may take hours so plan to run it overnight.Memtest86+ - Advanced Memory Diagnostic Tool
Memory problems. - Microsoft Community
Please use the Microsoft snipping tool to make an image of the Memtest86+ and post and image into the thread.
11) Run one of these SMART tests on each of your drives:
CrystalDiskInfo - Software - Crystal Dew World
http://www.hdtune.com/
Hard Disk Sentinel - HDD health and temperature monitoring
For all HD please also use Sea Tools for windows to perform SMART, short and long generic tests:
http://www.seagate.com/support/downl...ls-win-master/
How to use SeaTools for Windows
Please use the Microsoft snipping tool to make an image of each SMART test result and post images into the thread.
12) Uninstall all Realtek drivers and update with new drivers
Quote