Windows 10: Games Crash to Desktop With No Errors (All Games) Occasional BSOD

Hi guys,

I really hope someone can help me on this one!

For the past couple of months I have been plagued with games minimising, crashing to desktop with no error messages and I'm completely fed up as I feel like I have tried everything to fix it but just can't.

I'm hoping someone on here knows how to read windows .dmp files as I have just found these today but again I don't really know what I'm looking at here! Anyways, my specs:

What I have tried:

I have had a few blue screen crashes but at the time of writing I don't have any blue screen .dmp files for some strange reason.
Also to note I clone my gaming monitor via HDMI to a dedicated streaming machine.

The .dmp files:

Code: Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (OSR Unique Expertise, Guaranteed Results) Online Crash Dump Analysis Service See http://www.osronline.com for more information Windows 8 Version 17134 MP (8 procs) Free x64 Product: WinNt, suite: SingleUserTS kernel32.dll version: 10.0.17134.12 (WinBuild.160101.0800) Machine Name: Debug session time: Mon Sep 10 15:50:08.000 2018 (UTC - 4:00) System Uptime: not available Process Uptime: 0 days 0:18:16.000 Kernel time: 0 days 0:03:52.000 User time: 0 days 1:37:58.000 TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\oca.ini, error 2 TRIAGER: Could not open triage file : e:\dump_analysis\program\winxp\triage.ini, error 2 TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\user.ini, error 2 ******************************************************************************* * * * Exception Analysis * * * ******************************************************************************* TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\guids.ini, error 2 *** WARNING: Unable to verify timestamp for dbdata.dll *** ERROR: Module load completed but symbols could not be loaded for dbdata.dll *** WARNING: Unable to verify timestamp for nvwgf2umx.dll *** ERROR: Module load completed but symbols could not be loaded for nvwgf2umx.dll TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2 GetUrlPageData2 (WinHttp) failed: 12029. *** The OS name list needs to be updated! Unknown Windows version: 10.0 *** FAULTING_IP: bfvob+5a6087f 00000001`45a6087f ff5008 call qword ptr [rax+8] EXCEPTION_RECORD: ffffffffffffffff -- (.exr 0xffffffffffffffff) ExceptionAddress: 0000000145a6087f (bfvob+0x0000000005a6087f) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 0000000000000008 Attempt to read from address 0000000000000008 PROCESS_NAME: bfvob.exe ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s". EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s". EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000008 READ_ADDRESS: 0000000000000008 FOLLOWUP_IP: bfvob+5a6087f 00000001`45a6087f ff5008 call qword ptr [rax+8] NTGLOBALFLAG: 0 APPLICATION_VERIFIER_FLAGS: 0 FAULTING_THREAD: 0000000000002dd4 BUGCHECK_STR: APPLICATION_FAULT_NULL_CLASS_PTR_READ_INVALID_POINTER_READ_NULL_POINTER_READ_CALL PRIMARY_PROBLEM_CLASS: NULL_CLASS_PTR_READ_CALL DEFAULT_BUCKET_ID: NULL_CLASS_PTR_READ_CALL IP_ON_HEAP: 000000000101157e The fault address in not in any loaded module, please check your build's rebase log at \bin\build_logs\timebuild\ntrebase.log for module which may contain the address if it were loaded. FRAME_ONE_INVALID: 1 LAST_CONTROL_TRANSFER: from 000000000101157e to 0000000145a6087f STACK_TEXT: 00000000`32a2f830 00000000`0101157e : 00000001`41962c19 00b70001`f5a4f100 00000000`00000000 00000000`00000000 : bfvob+0x5a6087f 00000000`32a2f838 00000001`41962c19 : 00b70001`f5a4f100 00000000`00000000 00000000`00000000 00030001`f8a26010 : 0x101157e 00000000`32a2f840 00b70001`f5a4f100 : 00000000`00000000 00000000`00000000 00030001`f8a26010 00000000`00000003 : bfvob+0x1962c19 00000000`32a2f848 00000000`00000000 : 00000000`00000000 00030001`f8a26010 00000000`00000003 00000001`41962c19 : 0xb70001`f5a4f100 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: bfvob+5a6087f FOLLOWUP_NAME: MachineOwner MODULE_NAME: bfvob IMAGE_NAME: bfvob.exe DEBUG_FLR_IMAGE_TIMESTAMP: 5b894e40 STACK_COMMAND: ~21s; .ecxr ; kb FAILURE_BUCKET_ID: NULL_CLASS_PTR_READ_CALL_c0000005_bfvob.exe!Unknown BUCKET_ID: X64_APPLICATION_FAULT_NULL_CLASS_PTR_READ_INVALID_POINTER_READ_NULL_POINTER_READ_CALL_bfvob+5a6087f WATSON_STAGEONE_URL: http://watson.microsoft.com/StageOne...htm?Retriage=1 Followup: MachineOwner --------- --------------------------------------------------------------------------------------------------------------------------------------------------------------------- Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (OSR Unique Expertise, Guaranteed Results) Online Crash Dump Analysis Service See http://www.osronline.com for more information Windows 8 Version 17134 MP (8 procs) Free x64 Product: WinNt, suite: SingleUserTS kernel32.dll version: 10.0.17134.12 (WinBuild.160101.0800) Machine Name: Debug session time: Tue Sep 11 06:42:12.000 2018 (UTC - 4:00) System Uptime: not available Process Uptime: 0 days 0:49:37.000 Kernel time: 0 days 0:10:31.000 User time: 0 days 4:41:47.000 TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\oca.ini, error 2 TRIAGER: Could not open triage file : e:\dump_analysis\program\winxp\triage.ini, error 2 TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\user.ini, error 2 ******************************************************************************* * * * Exception Analysis * * * ******************************************************************************* TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\guids.ini, error 2 *** WARNING: Unable to verify timestamp for bfvob.exe *** ERROR: Module load completed but symbols could not be loaded for bfvob.exe *** WARNING: Unable to verify timestamp for dbdata.dll *** ERROR: Module load completed but symbols could not be loaded for dbdata.dll *** WARNING: Unable to verify timestamp for GfeSDK.dll *** ERROR: Module load completed but symbols could not be loaded for GfeSDK.dll *** WARNING: Unable to verify timestamp for poco.dll *** ERROR: Module load completed but symbols could not be loaded for poco.dll TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2 GetUrlPageData2 (WinHttp) failed: 12029. *** The OS name list needs to be updated! Unknown Windows version: 10.0 *** FAULTING_IP: nvwgf2umx+b5b790 00007ff9`a2a7b790 4983791800 cmp qword ptr [r9+18h],0 EXCEPTION_RECORD: ffffffffffffffff -- (.exr 0xffffffffffffffff) ExceptionAddress: 00007ff9a2a7b790 (nvwgf2umx+0x0000000000b5b790) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 00000000000019db Attempt to read from address 00000000000019db DEFAULT_BUCKET_ID: INVALID_POINTER_READ PROCESS_NAME: bfvob.exe ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s". EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s". EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 00000000000019db READ_ADDRESS: 00000000000019db FOLLOWUP_IP: nvwgf2umx+b5b790 00007ff9`a2a7b790 4983791800 cmp qword ptr [r9+18h],0 NTGLOBALFLAG: 0 APPLICATION_VERIFIER_FLAGS: 0 FAULTING_THREAD: 0000000000002318 PRIMARY_PROBLEM_CLASS: INVALID_POINTER_READ BUGCHECK_STR: APPLICATION_FAULT_INVALID_POINTER_READ IP_ON_HEAP: 000000003eb82e90 The fault address in not in any loaded module, please check your build's rebase log at \bin\build_logs\timebuild\ntrebase.log for module which may contain the address if it were loaded. FRAME_ONE_INVALID: 1 LAST_CONTROL_TRANSFER: from 000000003eb82e90 to 00007ff9a2a7b790 STACK_TEXT: 00000000`3f00f630 00000000`3eb82e90 : 00000000`0000dbaf 00000000`00000000 00000000`7a376890 00000000`00000000 : nvwgf2umx+0xb5b790 00000000`3f00f638 00000000`0000dbaf : 00000000`00000000 00000000`7a376890 00000000`00000000 00007ff9`a2a7ad66 : 0x3eb82e90 00000000`3f00f640 00000000`00000000 : 00000000`7a376890 00000000`00000000 00007ff9`a2a7ad66 00000000`7adee540 : 0xdbaf SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nvwgf2umx+b5b790 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nvwgf2umx IMAGE_NAME: nvwgf2umx.dll DEBUG_FLR_IMAGE_TIMESTAMP: 5b7be952 STACK_COMMAND: ~25s; .ecxr ; kb FAILURE_BUCKET_ID: INVALID_POINTER_READ_c0000005_nvwgf2umx.dll!Unknown BUCKET_ID: X64_APPLICATION_FAULT_INVALID_POINTER_READ_nvwgf2umx+b5b790 WATSON_STAGEONE_URL: http://watson.microsoft.com/StageOne...htm?Retriage=1 Followup: MachineOwner --------- -------------------------------------------------------------------------------------------------------------------------------------------------------------------- Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (OSR Unique Expertise, Guaranteed Results) Online Crash Dump Analysis Service See http://www.osronline.com for more information Windows 8 Version 17134 MP (8 procs) Free x64 Product: WinNt, suite: SingleUserTS kernel32.dll version: 10.0.17134.12 (WinBuild.160101.0800) Machine Name: Debug session time: Thu Sep 13 10:31:00.000 2018 (UTC - 4:00) System Uptime: not available Process Uptime: 0 days 0:25:43.000 Kernel time: 0 days 0:06:42.000 User time: 0 days 2:05:00.000 TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\oca.ini, error 2 TRIAGER: Could not open triage file : e:\dump_analysis\program\winxp\triage.ini, error 2 TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\user.ini, error 2 ******************************************************************************* * * * Exception Analysis * * * ******************************************************************************* *** WARNING: Unable to verify timestamp for bf1.exe *** ERROR: Module load completed but symbols could not be loaded for bf1.exe TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\guids.ini, error 2 *** WARNING: Unable to verify timestamp for dbdata.dll *** ERROR: Module load completed but symbols could not be loaded for dbdata.dll *** WARNING: Unable to verify timestamp for nvwgf2umx.dll *** ERROR: Module load completed but symbols could not be loaded for nvwgf2umx.dll TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2 GetUrlPageData2 (WinHttp) failed: 12029. *** The OS name list needs to be updated! Unknown Windows version: 10.0 *** FAULTING_IP: +aaabe2 00000002`c0844a80 4029ad42010000 sub dword ptr [rbp+142h],ebp EXCEPTION_RECORD: ffffffffffffffff -- (.exr 0xffffffffffffffff) ExceptionAddress: 00000002c0844a80 ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000008 Parameter[1]: 00000002c0844a80 Attempt to execute non-executable address 00000002c0844a80 PROCESS_NAME: bf1.exe ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s". EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s". EXCEPTION_PARAMETER1: 0000000000000008 EXCEPTION_PARAMETER2: 00000002c0844a80 WRITE_ADDRESS: 00000002c0844a80 FOLLOWUP_IP: bf1+aaabe2 00000001`40aaabe2 ?? ??? FAILED_INSTRUCTION_ADDRESS: +aaabe2 00000002`c0844a80 4029ad42010000 sub dword ptr [rbp+142h],ebp NTGLOBALFLAG: 0 APPLICATION_VERIFIER_FLAGS: 0 FAULTING_THREAD: 0000000000002bbc BUGCHECK_STR: APPLICATION_FAULT_SOFTWARE_NX_FAULT_INVALID PRIMARY_PROBLEM_CLASS: SOFTWARE_NX_FAULT_INVALID DEFAULT_BUCKET_ID: SOFTWARE_NX_FAULT_INVALID LAST_CONTROL_TRANSFER: from 0000000140aaabe2 to 00000002c0844a80 STACK_TEXT: 00000000`2939e9d8 00000001`40aaabe2 : 00000000`2939eae0 00000002`ba874510 bf0e9215`bf45e403 bf0e9215`bf0e9215 : 0x2`c0844a80 00000000`2939e9e0 00000000`2939eae0 : 00000002`ba874510 bf0e9215`bf45e403 bf0e9215`bf0e9215 bf318990`00000000 : bf1+0xaaabe2 00000000`2939e9e8 00000002`ba874510 : bf0e9215`bf45e403 bf0e9215`bf0e9215 bf318990`00000000 bf318990`00000000 : 0x2939eae0 00000000`2939e9f0 bf0e9215`bf45e403 : bf0e9215`bf0e9215 bf318990`00000000 bf318990`00000000 beea0267`bf226799 : 0x2`ba874510 00000000`2939e9f8 bf0e9215`bf0e9215 : bf318990`00000000 bf318990`00000000 beea0267`bf226799 beea0267`beea0267 : 0xbf0e9215`bf45e403 00000000`2939ea00 bf318990`00000000 : bf318990`00000000 beea0267`bf226799 beea0267`beea0267 00000000`2939f960 : 0xbf0e9215`bf0e9215 00000000`2939ea08 bf318990`00000000 : beea0267`bf226799 beea0267`beea0267 00000000`2939f960 00000000`00000000 : 0xbf318990`00000000 00000000`2939ea10 beea0267`bf226799 : beea0267`beea0267 00000000`2939f960 00000000`00000000 00000000`00000000 : 0xbf318990`00000000 00000000`2939ea18 beea0267`beea0267 : 00000000`2939f960 00000000`00000000 00000000`00000000 0000042c`79756fa4 : 0xbeea0267`bf226799 00000000`2939ea20 00000000`2939f960 : 00000000`00000000 00000000`00000000 0000042c`79756fa4 00000000`3f800000 : 0xbeea0267`beea0267 00000000`2939ea28 00000000`00000000 : 00000000`00000000 0000042c`79756fa4 00000000`3f800000 00000000`fd002440 : 0x2939f960 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: bf1+aaabe2 FOLLOWUP_NAME: MachineOwner MODULE_NAME: bf1 IMAGE_NAME: bf1.exe DEBUG_FLR_IMAGE_TIMESTAMP: 5b69e2b3 STACK_COMMAND: dt ntdll!LdrpLastDllInitializer BaseDllName ; dt ntdll!LdrpFailureData ; ~18s; .ecxr ; kb FAILURE_BUCKET_ID: SOFTWARE_NX_FAULT_INVALID_c0000005_bf1.exe!Unknown BUCKET_ID: X64_APPLICATION_FAULT_SOFTWARE_NX_FAULT_INVALID_BAD_IP_bf1+aaabe2 WATSON_STAGEONE_URL: http://watson.microsoft.com/StageOne...htm?Retriage=1 Followup: MachineOwner --------- ------------------------------------------------------------------------------------------------------------------------------------------------------ Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (OSR Unique Expertise, Guaranteed Results) Online Crash Dump Analysis Service See http://www.osronline.com for more information Windows 8 Version 17134 MP (8 procs) Free x64 Product: WinNt, suite: SingleUserTS kernel32.dll version: 10.0.17134.12 (WinBuild.160101.0800) Machine Name: Debug session time: Thu Sep 13 10:55:11.000 2018 (UTC - 4:00) System Uptime: not available Process Uptime: 0 days 0:22:58.000 Kernel time: 0 days 0:06:22.000 User time: 0 days 1:56:51.000 TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\oca.ini, error 2 TRIAGER: Could not open triage file : e:\dump_analysis\program\winxp\triage.ini, error 2 TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\user.ini, error 2 ******************************************************************************* * * * Exception Analysis * * * ******************************************************************************* TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\guids.ini, error 2 *** WARNING: Unable to verify timestamp for dbdata.dll *** ERROR: Module load completed but symbols could not be loaded for dbdata.dll *** WARNING: Unable to verify timestamp for bf1.exe *** ERROR: Module load completed but symbols could not be loaded for bf1.exe TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2 GetUrlPageData2 (WinHttp) failed: 12029. *** The OS name list needs to be updated! Unknown Windows version: 10.0 *** FAULTING_IP: nvwgf2umx+ce1ab6 00007ffd`b1021ab6 895818 mov dword ptr [rax+18h],ebx EXCEPTION_RECORD: ffffffffffffffff -- (.exr 0xffffffffffffffff) ExceptionAddress: 00007ffdb1021ab6 (nvwgf2umx+0x0000000000ce1ab6) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000001 Parameter[1]: 0000000000000018 Attempt to write to address 0000000000000018 DEFAULT_BUCKET_ID: NULL_CLASS_PTR_WRITE PROCESS_NAME: bf1.exe ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s". EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s". EXCEPTION_PARAMETER1: 0000000000000001 EXCEPTION_PARAMETER2: 0000000000000018 WRITE_ADDRESS: 0000000000000018 FOLLOWUP_IP: nvwgf2umx+ce1ab6 00007ffd`b1021ab6 895818 mov dword ptr [rax+18h],ebx NTGLOBALFLAG: 0 APPLICATION_VERIFIER_FLAGS: 0 FAULTING_THREAD: 0000000000000b74 PRIMARY_PROBLEM_CLASS: NULL_CLASS_PTR_WRITE BUGCHECK_STR: APPLICATION_FAULT_NULL_CLASS_PTR_WRITE LAST_CONTROL_TRANSFER: from 0000000000000008 to 00007ffdb1021ab6 STACK_TEXT: 00000000`2accfde0 00000000`00000008 : 00000002`1260de28 00000000`00000000 ffffffff`fffffff8 00000000`00000000 : nvwgf2umx+0xce1ab6 00000000`2accfde8 00000002`1260de28 : 00000000`00000000 ffffffff`fffffff8 00000000`00000000 00000000`00000000 : 0x8 00000000`2accfdf0 00000000`00000000 : ffffffff`fffffff8 00000000`00000000 00000000`00000000 00000000`2ab915d0 : 0x2`1260de28 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nvwgf2umx+ce1ab6 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nvwgf2umx IMAGE_NAME: nvwgf2umx.dll DEBUG_FLR_IMAGE_TIMESTAMP: 5b90828b STACK_COMMAND: dt ntdll!LdrpLastDllInitializer BaseDllName ; dt ntdll!LdrpFailureData ; ~20s; .ecxr ; kb FAILURE_BUCKET_ID: NULL_CLASS_PTR_WRITE_c0000005_nvwgf2umx.dll!Unknown BUCKET_ID: X64_APPLICATION_FAULT_NULL_CLASS_PTR_WRITE_nvwgf2umx+ce1ab6 WATSON_STAGEONE_URL: http://watson.microsoft.com/StageOne...htm?Retriage=1 Followup: MachineOwner ---------[/quote] I've been pulling my hair out on this one for a few months now, I really appreciate any help anyone can give me!

If you need any other info please let me know, I'll be watching this page like a hawk!

Many thanks in advance!

:)

 

2 BSOD screens and multiple game crashes

Hello,

My computer started to encounter BSOD and game crashing to desktop a few days ago. BSOD could occur when I browsed on chrome or when playing games such as Starcraft 2 or Rainbow Six Siege. I decided to reset my PC - twice in fact. First time I saved my personal
data, but the system kept crashing, so I decided to wipe everything off for a fresh start but to no avail.

I proceeded to reinstall the games and the games still crashed to desktop with occasional BSODs. Specific BSOD errors include:

- IQRL_NOT_LESS_OR_EQUAL

- Memory Management

I have tried:

sfc/scannow

DISM.exe /Online /Cleanup-Image/ RestoreHealth

sfc/scannow revealed data corruption at first, but after fixing it through https://answers.microsoft.com/en-us...-primary/5182a7da-e922-481f-94fb-f2f4b27fe7e0, no issues were shown
during the scan.

I updated both my graphics card driver and ethernet driver on device manager as well. None seemed to have worked.

I would gladly appreciate any help on this issue.

Thanks.

 

Games crashing to desktop

Hi All my games are crashing to the desktop , i did have error 10016 in event viewer but have fixed that now but still my games crash to desktop. Everything is up to date , done a fresh install of windows 10 but didn't install updates as i beleived that
was the issue.

Made another question about this earlier today and someone responded about using CMD to run sfcnow but my CMD prompt wasnt working , opening and closing straight away. so another install of windows 10 and cmd prompt is working again.

Now event viewer isnt showing any errors after the games crash to desktop.

 

BSOD/crash playing games, memory error on shutdown


Been a few more days, haven't had much play time in the biggest offending games but did have a crash last night in Destiny 2. Did the general 'program has stopped working' message, and I couldn't re-launch the game until I rebooted my computer. In that state, I tried restarting Explorer, closing a bunch of other programs I had running, etc seeing if I could narrow down what was the cause...eventually gave up and rebooted.

I've also turned off fast startup as zbook suggested. Since then I don't think I've seen the Explorer memory error on shutdown, but I think that has become rarer since I installed the chipset drivers.

I've run the HD Tune on the rest of the drives. I'm going to need another large block of time before attempting the chkdsk /r on D: or the SeaTools DOS since the error check took almost 7.5 hours. Here are the results: