Windows 10: 0x00000119 ntoskrnl.exe+16c310

Okay, so I when to wake up my monitor from "sleep" and when I did there was just a black screen and then my computer started up, even though it was already on. After I go to the desktop I download BlueScreenView because I had the suspicion that it was a BSOD and from the dump, it was so I have come here for help with this issue.

I have also had an issue recently where I can't wake my computer from sleep without a reboot, so I disabled sleep from right now.

About my CPU and GPU, my CPU is OC'd to 4.4Ghz and my GPU is running at its out of the box "stock" overclock. Also, I reinstalled Win 10 just recently as well.

:)

 

Windows 10 Creators Update BSOD kernel crash - UNEXPECTED_KERNEL_MODE_TRAP

For reference, in case anyone is wondering, I am seeing the exact same crash as originally reported (ntoskrnl.exe+16c310) after applying the Cumulative Update KB4020102
from yesterday. No change.

 

BSOD 0x00000133, ntoskrnl.exe+16c310

Hi Jan,





The Blue Screen of Death error 0x00000133 ntoskrnl.exe + 16c310 occurs when a problem causes the Windows NT Operating System Kernel to work properly. Here’s an
article that would walk you through the steps on how to resolve your concern depending on the type of blue
screen error you’re getting.



Let us know if you need additional assistance.

 

Please uninstall everything of AMD using Display Driver Uninstaller and install new drivers from AMD. Be sure to install as less as possible software using custom/advanced options, you can use this tutorial for the installation part *Arrow AMD Graphics Drivers - Install Without Catalyst Install Manager - Windows 7 Help Forums

 

Okay thanks, I will give this a try and see what happens.

 

Just tested it out with no luck, the drivers installed just fine that way but I had the same issue.

 

Was the same issue difficulty awaking from sleep or bsod or both? If it was another bsod please keep sending the minidump files until it is fixed.

In administrative command prompt run: sfc /scannow and dism /online /cleanup-image /restorehealth
If there were any integrity violations that were or were not fixed please report. Or if they were not able to complete please report.

Until the bsod is completely fixed you can place the computer in clean boot to reduce or eliminate the bsod. Often you will end up with the fastest boot times.

How to perform a Clean Boot in Windows 10 - TechNet Articles - United States (English) - TechNet Wiki


https://support.microsoft.com/en-us/...oot-in-windows

 

I checked with BlueScreenView and found a dump file from the 20th, at that time I was NOT running with the drivers installed the way that you asked me. I have added the files here.

As for the issues that I have had after the reinstalled drivers, all that I can test is the sleep which is still hit and miss. Sometimes it will work and sometimes it will not display something buy everything will still be held in RAM after I do the reboot. But I also have not used my PC enough after the reinstall to run into an issue. Also, I never get a BSOD but there are dump files from stuff I never even known that had happened.

 

I ran the tests and they both ran just fine without any issues. Also, I disabled a few programs on boot but not all going to see what happens.

 

Let's see if this can be fixed by turning off fast boot:
win + x simultaneously then click power options
click choose what the power buttons do
click change settings that are currently available
uncheck turn on fast startup
save changes and reboot

Check your boot and shutdown times.
Sometimes it can be left off other times rechecking fast startup seems to allows a reset

Let us know the progress.

 

Okay so I disable fast startup and here are my times before and after.

With Fast Startup: Boot: 24 Sec Shutdown: 10 Sec
Without Fast Startup: Boot: 23.7 Sec Shutdown: 5.5 Sec
This was all done with a few of the programs disabled on startup, mainly the ones I don't need right away.

Now when I put my PC into sleep it is not to get fast boot times it is to save what I was working on so I can continue where I left off without reopening the files. I also tried sleep and when the computer booted it acted like the PC was fully shutdown so nothing was saved.

 

@zbook is on a good path, but I doubt fast startup causes a 0x9C which basically indicates a hardware error occured.
I recommend to run the below instructed stress tests and post the requested results.
Please read the instructions carefully, most of the asked questions are answered in either the instructions or the tutorial.
If you have any question after reading the tutorial and instruction, please don't hesitate to ask.
Code: Event[3560]: Log Name: System Source: Microsoft-Windows-Kernel-Boot Date: 2017-05-20T15:10:36.851 Event ID: 16 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-GKV5H8I Description: Windows failed to resume from hibernate with error status 0xC0000001.[/quote]







STOP 0x124 Troubleshooting

Read carefully before proceeding.

*Arrow Run Prime95 - Stress Test Your CPU - Windows 10 Forums & CPU - Stress Test Using IntelBurnTest - Windows 7 Help Forums

*Arrow Run MemTest86+ - Test RAM - Windows 10 Forums

*Arrow Run HDTune to

• check the health,
• scan for errors, no quick scan but full scan
• run a benchmark.

It may take some time, but please take the time you need to perform it properly.
When above is done please make screenshots of the following

• the health,
• the error scan,
• the benchmark incl. following
  • transfer rate,
  • access time,
  • burst rate,
  • cpu usage.

*Arrow Run SeaTools DOS to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use - Windows 7 Help Forums
Run the long test.
*Arrow Run chkdsk
Disk Check - Windows 7 Help Forums
Use option TWO with parameter /r
Upload the chkdsk log *Arrow Check Disk (chkdsk) - Read Event Viewer Log - Windows 7 Help Forums






FOUR

GPU TEST
*Arrow Run FurMark - GPU Stress Test - Windows 10 Forums



Note Run Furmark for around 30 minutes.


Warning Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them and abort the test if overheating occurs.
Make a photo of the result and post it.

In Furmark you can find a tool called 'GPU-Z' (if you want to install GPU-Z is up to you), when GPU-Z is open click on the 'Sensors' tab, on this tab you can monitor

• the frequency of the GPU,
• the GPU memory clock,
• the temperature,
• the power,
• the load on the GPU,
• Etc.

I would like you to make a screenshot of GPU-Z after you have either cancelled Furmark for any reason or Furmark is finished, post this screenshot in your next reply with the result of Furmark.

 

Did u install MSI Afterburner for testing purposes to fix your BSOD? If not, its a software which is known for causing Bluescreens.

To limit the problem...there are a bunch of GPU and HDD errors in windows eventlog. U should focus on GPU and HDD (filesystem):

GPU driver crashes:
Code: 34:2017-05-03T15 03:31.119 Display driver amdkmdap stopped responding and has successfully recovered.: . 37:2017-05-04T19 33:46.760 Display driver amdkmdap stopped responding and has successfully recovered.: . 43:2017-05-15T21 48:39.889 Display driver amdkmdap stopped responding and has successfully recovered.: . 44:2017-05-15T21 48:39.890 Display driver amdkmdap stopped responding and has successfully recovered.: .[/quote]
DISK and filesystem errors:
Code: 2017-05-16T18 39:43.111 Error: The file system structure on volume C: cannot be corrected.Please run the chkdsk utility on the volume C:. 2017-05-23T17 43:16.003 Error: The file system structure on volume C: cannot be corrected.Please run the chkdsk utility on the volume C:. 2017-05-23T17 43:17.282 Error: A corruption was discovered in the file system structure on volume C:. 2017-05-23T18 08:20.032 Error: The file system structure on volume C: cannot be corrected.Please run the chkdsk utility on the volume C:. 2017-05-23T18 08:20.043 Error: Volume C: (\Device\HarddiskVolume3) 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-05-23T18 08:20.043 Error: A corruption was discovered in the file system structure on volume C:. 2017-05-23T18 08:20.043 Error: The file system structure on volume C: cannot be corrected.Please run the chkdsk utility on the volume C:. 2017-05-23T18 08:20.646 Error: There was insufficient disk space on volume \\?\Volume{b15122c2-0000-0000-0000-50d61b000000} to create the shadow copy of volume C:. Shadow copy storage creation failed. 2017-05-23T18 08:20.653 Error: A corruption was discovered in the file system structure on volume C:. 2017-05-23T18 08:20.653 Error: A corruption was discovered in the file system structure on volume C:. 2017-05-23T18 08:20.653 Error: A corruption was discovered in the file system structure on volume C:. 2017-05-23T18 08:20.653 Error: A corruption was discovered in the file system structure on volume C:. 2017-05-23T18 08:23.133 Error: There was insufficient disk space on volume \\?\Volume{b15122c2-0000-0000-0000-50d61b000000} to create the shadow copy of volume C:. Shadow copy storage creation failed. 2017-05-23T18 08:26.182 Error: There was insufficient disk space on volume \\?\Volume{b15122c2-0000-0000-0000-50d61b000000} to create the shadow copy of volume C:. Shadow copy storage creation failed. 2017-05-23T18 08:26.183 Error: A corruption was discovered in the file system structure on volume C:. 2017-05-23T18 08:28.185 Error: There was insufficient disk space on volume \\?\Volume{b15122c2-0000-0000-0000-50d61b000000} to create the shadow copy of volume C:. Shadow copy storage creation failed. 2017-05-23T18 08:30.435 Error: There was insufficient disk space on volume \\?\Volume{b15122c2-0000-0000-0000-50d61b000000} to create the shadow copy of volume C:. Shadow copy storage creation failed.[/quote]

 

DISK and filesystem errors:
Code: 2017-05-16T18 39:43.111 Error: The file system structure on volume C: cannot be corrected.Please run the chkdsk utility on the volume C:. 2017-05-23T17 43:16.003 Error: The file system structure on volume C: cannot be corrected.Please run the chkdsk utility on the volume C:. 2017-05-23T17 43:17.282 Error: A corruption was discovered in the file system structure on volume C:. 2017-05-23T18 08:20.032 Error: The file system structure on volume C: cannot be corrected.Please run the chkdsk utility on the volume C:. 2017-05-23T18 08:20.043 Error: Volume C: (\Device\HarddiskVolume3) 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-05-23T18 08:20.043 Error: A corruption was discovered in the file system structure on volume C:. 2017-05-23T18 08:20.043 Error: The file system structure on volume C: cannot be corrected.Please run the chkdsk utility on the volume C:. 2017-05-23T18 08:20.646 Error: There was insufficient disk space on volume \\?\Volume{b15122c2-0000-0000-0000-50d61b000000} to create the shadow copy of volume C:. Shadow copy storage creation failed. 2017-05-23T18 08:20.653 Error: A corruption was discovered in the file system structure on volume C:. 2017-05-23T18 08:20.653 Error: A corruption was discovered in the file system structure on volume C:. 2017-05-23T18 08:20.653 Error: A corruption was discovered in the file system structure on volume C:. 2017-05-23T18 08:20.653 Error: A corruption was discovered in the file system structure on volume C:. 2017-05-23T18 08:23.133 Error: There was insufficient disk space on volume \\?\Volume{b15122c2-0000-0000-0000-50d61b000000} to create the shadow copy of volume C:. Shadow copy storage creation failed. 2017-05-23T18 08:26.182 Error: There was insufficient disk space on volume \\?\Volume{b15122c2-0000-0000-0000-50d61b000000} to create the shadow copy of volume C:. Shadow copy storage creation failed. 2017-05-23T18 08:26.183 Error: A corruption was discovered in the file system structure on volume C:. 2017-05-23T18 08:28.185 Error: There was insufficient disk space on volume \\?\Volume{b15122c2-0000-0000-0000-50d61b000000} to create the shadow copy of volume C:. Shadow copy storage creation failed. 2017-05-23T18 08:30.435 Error: There was insufficient disk space on volume \\?\Volume{b15122c2-0000-0000-0000-50d61b000000} to create the shadow copy of volume C:. Shadow copy storage creation failed.[/quote] [/quote] I Installed MSI afterburner to fix a No Display issue and GPU underclocking issue. I am currently using it to under volt and increase power limit on my GPU as it is easier to than Wattman and I also don't have Wattman anymore.

 

Currently you may have already in progress stress tests for CPU and GPU, memory and HD tests. As these are performed please post the results.

If you are on the desk top with administrative command please run:
powercfg /systempowerreport (copy and paste the browser html link into the forum)


In case there is a software component related to the failure to wake from sleep problem see if turning hybernate off has any impact: administrative command prompt: powercfg /h off
then reboot, put to sleep and attempt to wake
Report results (improvement, no improvement)

In control panel then troubleshooting then left side pane view all then find and fix problems with your computer's power settings: run this troubleshooter and post results (snipping tool picture of details).
Then reboot, put to sleep and attempt wake.
Report results (improvement, no improvement)