Games crashing problem

[Rob_110]

My games are crashing.

my build:
asrock h61m-vg4
650w crosair psu 80+
Intel core i3 3220
8gb of ram
gigabyte gtx 1050ti
a kingston 120gb ssd
1tb toshiba hdd

i had ran stress tests and my cpu wasnt going over 56C and my mother board was stable at 70C

 

[scout_03]

what about the gpu temp use hwinfo to check this .

 

[Rob_110]

what about the gpu temp use hwinfo to check this .

The gpu at 70 on stress test

 

[mwryder55]

Does it crash using a video benchmark like Heaven? Also, how old is your power supply?

 

[scout_03]

try this to see if there is any minidump files in system whocrashed .

 

[Rob_110]

i have minidump folders and my psu is new and it does not crash on 3d mark

 

[scout_03]

post the result from whocrashed it will give it plain text .

 

[Rob_110]

post the result from whocrashed it will give it plain text .

Where do I find that?

 

[scout_03]

this and run it to analyse system then check report of result http://www.resplendence.com/whocrashed

 

[Rob_110]

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Tue 9/5/2017 4:55:53 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\090517-25203-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0xA1B00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF804E7711B00, 0xFFFF800056CF1CA0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.



On Tue 9/5/2017 4:55:53 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0xA1B00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF804E7711B00, 0xFFFF800056CF1CA0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.



On Sat 9/2/2017 3:26:30 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\090217-38609-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR



On Thu 8/24/2017 9:36:12 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\082417-26921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C4C0)
Bugcheck code: 0xA (0x304, 0x2, 0x0, 0xFFFFF803E62C6B96)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 8/24/2017 3:55:32 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\082417-28296-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x868A41)
Bugcheck code: 0xBE (0xFFFFF80440368A41, 0x1000000D5360121, 0xFFFFCD013AE24C50, 0xB)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_ce1961376673184c\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 385.41
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 385.41
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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 385.41 , NVIDIA Corporation).
Google query: NVIDIA Corporation ATTEMPTED_WRITE_TO_READONLY_MEMORY





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

19 crash dumps have been found and analyzed. Only 5 are included in this report. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 385.41 , NVIDIA Corporation)
em018_64.dll (HIPS module, ESET)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.


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.

 

[Rob_110]

this is what i get

 

[Rob_110]

sry if it is log

 

[scout_03]

check the gpu driver with directx and also the acpi one see this link https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0xa3--acpi-driver-internal

 

[Rob_110]

i checked in the nivada app and the gpu drivers are up to date

 

[scout_03]

then check all system driver could be a board one that need to be update like the acpi one .

 

[Rob_110]

and on direct x there is no problem found

 

[Rob_110]

how do you know if you got all drivers

 

[Rob_110]

can i go on whocrashed and go on local drivers?

 

[scout_03]

i would go on board maker link and check iffrom the date you have bought board there are new one also did you install the cd that came wiht when you bought it if not you might have some missing .

 

[Rob_110]

oh maybe that is why i ,didnt install the disc

 

[scout_03]

you might not have the chipset driver for the board with lan and audio even others so you could get the latest directly from asrock for this board .