BSOD randomly playing games.HELP!

P

pirata292

Member
Joined
Jun 7, 2017
Posts
17
[FONT=&quot][FONT=&quot]Hello guys, First of all, thanks for the help I really need because I do not know what else to do. VIDEO_SCHEDULER_INTERNAL_ERROR is an error. I have exchanged my memory with a friend and the error continues. I already switched video card with it too. When he installed my video card in his computer, and the memory, he did not have that problem. Thanks a lot for the help. I have already performed a stress test with Furmark and did not present BSOD. I already tested CPU stress and did not have any problems. Memory too. Please help me solve this problem. Thank you very much.[/FONT]
[FONT=&quot]All drivers.BIOS, and Windows, are up to date.[/FONT]


[/FONT]
[FONT=&quot]I had opened a topic previously, but they said that my copy was not original. I formatted and installed a genuine copy and the BSOD problem continues[/FONT]

· OS - Windows 10
· x64
· What was original installed OS on system?
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? purchased it from retailer
· Age of system (hardware) - 1 month
· Age of OS installation - have you re-installed the OS? Yes, 4 days

· CPU - Ryzen 1600
· Video Card - Gigabyte GTX 1060 G1 Gaming
· MotherBoard - MSI Tomahawk Arctic
· Power Supply - CORsair 600W
 

Attachments

Hi. . .

The bugchecks on the 2 BSODs -
0x3b - system service threw an exception; excp = memory access violation (0xc5)
0x119 - video scheduler has detected a fatal violation.

The probable cause on the first was NVIDIA video. Update your NVIDIA driver - Driver Reference Table - nvlddmkm.sys

The second BSOD named the NT Kernel as the probable cause. It IS NOT the cause -- it's merely listed as a default.

The process listed in the second BSOD -
Code: 
PROCESS_NAME:  DriverBooster.

Uninstall Driver Booster.

If you need to update drivers, use the Driver Reference Table (DRT) - https://www.sysnative.com/drivers/table/

Go into Device Manager; expand the driver category; look-up the driver name via "driver" tab; look-up the driver name in the DRT.

Regards. . .

jcgriff2

`

Code: 
[font=lucida console]
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\061017-17375-01.dmp]
Built by: 15063.0.amd64fre.rs2_release.170317-1834
Debug session time: Sat Jun 10 16:22:19.064 2017 (UTC - 4:00)
System Uptime: 0 days 2:16:22.727
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : dxgmms2.sys ( dxgmms2!VidSchiProcessIsrFaultedPacket+23e )
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
BUGCHECK_STR:  0x119
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  0x119_5_DRIVER_FAULTED_SYSTEM_COMMAND_dxgmms2!VidSchiProcessIsrFaultedPacket
Bugcheck code 00000119
Arguments 00000000`00000005 ffffd98e`8493f000 ffffd98e`84934800 00000000`0001bdf5
BiosVersion = H.40
BiosReleaseDate = 05/10/2017
SystemManufacturer = Micro-Star International Co., Ltd
SystemProductName = MS-7A34
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\060917-58968-01.dmp]
Built by: 15063.0.amd64fre.rs2_release.170317-1834
Debug session time: Fri Jun  9 21:12:23.855 2017 (UTC - 4:00)
System Uptime: 0 days 0:32:35.547
Probably caused by : ntkrnlmp.exe ( nt!SwapContext+1ec )
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  DriverBooster.
FAILURE_BUCKET_ID:  0x3B_nt!SwapContext
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`8d00c2ac ffffde00`3d7e8d70 00000000`00000000
BiosVersion = H.40
BiosReleaseDate = 05/10/2017
SystemManufacturer = Micro-Star International Co., Ltd
SystemProductName = MS-7A34
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/FONT]
 
jcgriff2 said:
Hi. . .

The bugchecks on the 2 BSODs -
0x3b - system service threw an exception; excp = memory access violation (0xc5)
0x119 - video scheduler has detected a fatal violation.

The probable cause on the first was NVIDIA video. Update your NVIDIA driver - Driver Reference Table - nvlddmkm.sys

The second BSOD named the NT Kernel as the probable cause. It IS NOT the cause -- it's merely listed as a default.

The process listed in the second BSOD -
Code: 
PROCESS_NAME:  DriverBooster.

Uninstall Driver Booster.

If you need to update drivers, use the Driver Reference Table (DRT) - https://www.sysnative.com/drivers/table/

Go into Device Manager; expand the driver category; look-up the driver name via "driver" tab; look-up the driver name in the DRT.

Regards. . .

jcgriff2

`

Code: 
[FONT=lucida console]
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\061017-17375-01.dmp]
Built by: 15063.0.amd64fre.rs2_release.170317-1834
Debug session time: Sat Jun 10 16:22:19.064 2017 (UTC - 4:00)
System Uptime: 0 days 2:16:22.727
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : dxgmms2.sys ( dxgmms2!VidSchiProcessIsrFaultedPacket+23e )
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
BUGCHECK_STR:  0x119
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  0x119_5_DRIVER_FAULTED_SYSTEM_COMMAND_dxgmms2!VidSchiProcessIsrFaultedPacket
Bugcheck code 00000119
Arguments 00000000`00000005 ffffd98e`8493f000 ffffd98e`84934800 00000000`0001bdf5
BiosVersion = H.40
BiosReleaseDate = 05/10/2017
SystemManufacturer = Micro-Star International Co., Ltd
SystemProductName = MS-7A34
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\060917-58968-01.dmp]
Built by: 15063.0.amd64fre.rs2_release.170317-1834
Debug session time: Fri Jun  9 21:12:23.855 2017 (UTC - 4:00)
System Uptime: 0 days 0:32:35.547
Probably caused by : ntkrnlmp.exe ( nt!SwapContext+1ec )
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  DriverBooster.
FAILURE_BUCKET_ID:  0x3B_nt!SwapContext
Bugcheck code 0000003B
Arguments 00000000`c0000005 fffff800`8d00c2ac ffffde00`3d7e8d70 00000000`00000000
BiosVersion = H.40
BiosReleaseDate = 05/10/2017
SystemManufacturer = Micro-Star International Co., Ltd
SystemProductName = MS-7A34
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/FONT]
Click to expand...


i update the nvidia driver Through the official website of nvidia.I did not use DriverBooster for this. I just used DriverBooster to update the other drivers.

With respect to my other post, it was me that I created and I had a copy of windows that was not genuine and I just formatted and currently I have a genuine copy.
Please help me.
 
If this system is just one month old and you bought it from a retailer -- take it back!

There obviously is some unknown hardware problem that I doubt we'll ever be able to help you fix.
 
jcgriff2 said:
If this system is just one month old and you bought it from a retailer -- take it back!

There obviously is some unknown hardware problem that I doubt we'll ever be able to help you fix.
Click to expand...


[FONT=&quot]New BSOD today[/FONT]
[FONT=&quot]
[/FONT]
[FONT=&quot]it's really frustrating for me. new pc, and i cant use :( [/FONT]
[FONT=&quot]
[/FONT]
[FONT=&quot][FONT=Segoe UI, Arial]On Sun 11/06/2017 21:07:05 your computer crashed
crash dump file: C:\Windows\Minidump\061117-30625-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]storport.sys[/FONT] (storport+0x1D550)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8000A78D550, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
file path: C:\Windows\system32\drivers\storport.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Microsoft Storage Port Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. [/FONT]



[FONT=Segoe UI, Arial]On Sun 11/06/2017 21:07:05 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]storport.sys[/FONT] (storport!StorPortQuerySystemTime+0x9F0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8000A78D550, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: [FONT=Segoe UI, Arial]KMODE_EXCEPTION_NOT_HANDLED[/FONT]
file path: C:\Windows\system32\drivers\storport.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Microsoft Storage Port Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. [/FONT]

[/FONT]
 
Both BSODs name the Microsoft driver storport.sys. This is listed as a default of sorts and definitely is not the cause.

Driver Reference Table - storport.sys

The actual cause is unknown hardware failure.

Seriously - take the system back and demand a new one.

Regards. . .

jcgriff2
 
I set up the computer from scratch piece by piece, I do not think it's a hardware problem. More BSOD when I'm playing.
I already uninstalled the video driver with the DDU and reinstalled. Minidump files in attachment

[FONT=Segoe UI, Arial]Crash dump directory: C:\Windows\Minidump[/FONT]
[FONT=Segoe UI, Arial][/FONT]
[FONT=Segoe UI, Arial]Crash dumps are enabled on your computer.
[/FONT]
[FONT=Segoe UI, Arial]On Sun 18/06/2017 14:45:06 your computer crashed
crash dump file: C:\Windows\Minidump\061817-19000-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]watchdog.sys[/FONT] (watchdog+0x355E)
Bugcheck code: 0x119 (0x5, 0xFFFFC80FAE826000, 0xFFFFC80FAE82BAD0, 0x53F75)
Error: [FONT=Segoe UI, Arial]VIDEO_SCHEDULER_INTERNAL_ERROR[/FONT]
file path: C:\Windows\system32\drivers\watchdog.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.


[/FONT]
[FONT=Segoe UI, Arial]On Sun 18/06/2017 14:45:06 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]nvlddmkm.sys[/FONT] (nvlddmkm+0xD9E13)
Bugcheck code: 0x119 (0x5, 0xFFFFC80FAE826000, 0xFFFFC80FAE82BAD0, 0x53F75)
Error: [FONT=Segoe UI, Arial]VIDEO_SCHEDULER_INTERNAL_ERROR[/FONT]
file path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_2d81f3535ced17c6\nvlddmkm.sys
product: [FONT=Segoe UI, Arial]NVIDIA Windows Kernel Mode Driver, Version 382.53 [/FONT]
company: [FONT=Segoe UI, Arial]NVIDIA Corporation[/FONT]
description: NVIDIA Windows Kernel Mode Driver, Version 382.53
Bug check description: This indicates that the video scheduler has detected a fatal violation.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 382.53 , NVIDIA Corporation).
Google query: [FONT=Segoe UI, Arial]NVIDIA Corporation VIDEO_SCHEDULER_INTERNAL_ERROR[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]On Sat 17/06/2017 18:05:26 your computer crashed
crash dump file: C:\Windows\Minidump\061717-22906-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]nvlddmkm.sys[/FONT] (nvlddmkm+0x26D67D)
Bugcheck code: 0x119 (0x5, 0xFFFF900928BED000, 0xFFFF900928D87AD0, 0x96B2A)
Error: [FONT=Segoe UI, Arial]VIDEO_SCHEDULER_INTERNAL_ERROR[/FONT]
file path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_2d81f3535ced17c6\nvlddmkm.sys
product: [FONT=Segoe UI, Arial]NVIDIA Windows Kernel Mode Driver, Version 382.53 [/FONT]
company: [FONT=Segoe UI, Arial]NVIDIA Corporation[/FONT]
description: NVIDIA Windows Kernel Mode Driver, Version 382.53
Bug check description: This indicates that the video scheduler has detected a fatal violation.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 382.53 , NVIDIA Corporation).
Google query: [FONT=Segoe UI, Arial]NVIDIA Corporation VIDEO_SCHEDULER_INTERNAL_ERROR[/FONT]


[/FONT]
[FONT=Segoe UI, Arial]On Sat 17/06/2017 14:08:30 your computer crashed
crash dump file: C:\Windows\Minidump\061717-22187-01.dmp
This was probably caused by the following module: [FONT=Segoe UI, Arial]watchdog.sys[/FONT] (watchdog+0x355E)
Bugcheck code: 0x119 (0x2, 0xFFFFFFFFC000000D, 0xFFFFE181A9F4E960, 0xFFFF8009450E9820)
Error: [FONT=Segoe UI, Arial]VIDEO_SCHEDULER_INTERNAL_ERROR[/FONT]
file path: C:\Windows\system32\drivers\watchdog.sys
product: [FONT=Segoe UI, Arial]Microsoft® Windows® Operating System[/FONT]
company: [FONT=Segoe UI, Arial]Microsoft Corporation[/FONT]
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.


[/FONT]
 

Attachments

I ran the test for about 50 minutes and no BSOD was related.
The only thing was that during the test, the screen froze for about 1 minute and the test continued. Do you want the print screen files of the tests?
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top