yangzhibin84
Junior Member
- Joined
- Mar 21, 2018
- Messages
- 14
- Reaction score
- 0
Recently built a PC but right after this happens. Below is the Error report. Please help 
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Wed 21/3/2018 5:30:48 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\032118-7343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x175510)
Bugcheck code: 0x119 (0x2, 0xFFFFFFFFC000000D, 0xFFFFFA8CC9595960, 0xFFFFBF0A1F66C0D0)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the video scheduler has detected a fatal violation.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 21/3/2018 5:30:48 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!RtlDeleteHashTable+0x207)
Bugcheck code: 0x119 (0x2, 0xFFFFFFFFC000000D, 0xFFFFFA8CC9595960, 0xFFFFBF0A1F66C0D0)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
Bug check description: This indicates that the video scheduler has detected a fatal violation.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Conclusion
--------------------------------------------------------------------------------
2 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Wed 21/3/2018 5:30:48 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\032118-7343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x175510)
Bugcheck code: 0x119 (0x2, 0xFFFFFFFFC000000D, 0xFFFFFA8CC9595960, 0xFFFFBF0A1F66C0D0)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the video scheduler has detected a fatal violation.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 21/3/2018 5:30:48 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!RtlDeleteHashTable+0x207)
Bugcheck code: 0x119 (0x2, 0xFFFFFFFFC000000D, 0xFFFFFA8CC9595960, 0xFFFFBF0A1F66C0D0)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
Bug check description: This indicates that the video scheduler has detected a fatal violation.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Conclusion
--------------------------------------------------------------------------------
2 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
