BSOD Playing PlayerUnknown's Battleground ntoskrnl.exe 0x0000000a

Hi everyone,

I just got my brand new Acer Predator G6-710 last night and already in two days I've encountered BSOD's while playing PUBG. All graphics drivers are up to date, and no windows updates are available, no drivers missing. All of my system specs are in my profile. Attached is the data dump, any help would be greatly appreciated.

Please let me know if there's anything I can do to help.

Attachment 147331

Computer Type: PC/Desktop
System Manufacturer/Model Number: Acer Predator G6-710
OS: Windows 10 Home
CPU: Processor Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz, 4200 Mhz, 4 Core(s), 8 Logical Processor(s)
Motherboard: Predator G6-710 (KBL)
Memory: 16GB DDR44 Dual Channel
Graphics Card: GeForce GTX 1080 Ti Founders Edition

Hi parad0x122 ,

There were 2 bsod mini dump files debugged and there was no misbehaving driver identified.
There will be multiple tests performed to identify the cause of the bsods.

Open administrative command prompt and type or copy and past these commands:

1) sfc /scannow
2) dism /online /cleanup-image /restorehealth

3) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

4) chkdsk /x /f /r (this may take many hours to run so plan to run overnight)
Post the results of the results into the thread:
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials

5) Turn off automatic restart and read these links on windows driver verifier:

https://answers.microsoft.com/en-us/...d-e95ee5d8669d
https://answers.microsoft.com/en-us/...3-c48669e4c983
Enable and Disable Driver Verifier in Windows 10 Windows 10 Performance Maintenance Tutorials

Code:

BugCheck A, {57, 2, 0, fffff800a06f0009}Probably caused by : hardware ( USBXHCI!Bulk_Transfer_CompleteCancelable+134e9 )

Code:

Event[11]:  Log Name: System  Source: Microsoft-Windows-Ntfs  Date: 2017-08-04T21:38:48.618  Event ID: 98  Task: N/A  Level: Warning  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-BN4JBEM  Description: Volume C: (\Device\HarddiskVolume3) requires an Online Scan.  An Online Scan will automatically run as part of the next scheduled maintenance task.  Alternatively you may run "CHKDSK /SCAN" locally via the command line, or run "REPAIR-VOLUME <drive:> -SCAN" locally or remotely via PowerShell.

Code:

Event[191]:  Log Name: System  Source: Microsoft-Windows-Ntfs  Date: 2017-08-04T21:41:26.548  Event ID: 98  Task: N/A  Level: Warning  Opcode: Info  Keyword: N/A  User: S-1-5-18  User Name: NT AUTHORITY\SYSTEM  Computer: DESKTOP-BN4JBEM  Description: Volume C: (\Device\HarddiskVolume3) requires an Online Scan.  An Online Scan will automatically run as part of the next scheduled maintenance task.  Alternatively you may run "CHKDSK /SCAN" locally via the command line, or run "REPAIR-VOLUME <drive:> -SCAN" locally or remotely via PowerShell.

After the chkdsk report plan to use windows driver verifier to find misbehaving drivers.

Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials

In the prior posts links were provided to read about the tool.
Before using windows driver verifier make sure you create a brand new restore point.
Make a backup image using Macrium.

Download and install each:
Bluescreenview: Blue screen of death (STOP error) information in dump files.
Whocrashed: http://www.resplendence.com/whocrashed

After each windows driver verifier produced bsod there will be a stop code typically driver verifier detected violation and sometimes it will display the misbehaving driver in the form *.sys. If you see the driver please record it an post it into the thread.
After each bsod you will turn off windows driver verifier using the windows recovery or advanced troubleshooting menu.
There are 3 methods to turn off windows driver verifier. Always use them in this order and only if the prior one fails.
1) startup options (not startup repair) > choose #6 safe mode with command prompt > type: verifier /reset
2) command prompt > opens Administrator X: \Windows\system32\cmd.exe > type: verifier /bootmode resetonbootfail
3) restore > leads to loss of mini dump file > so only use if the other 2 methods fail.

To practice navigating the windows advanced troubleshooting menu open administrative command prompt menu and type: shutdown /r /o /f /t 00

For each bsod you will use bluescreenview and whocrashed to identify the misbehaving driver. Then you will uninstall the misbehaving driver. Replacement drivers should be obtained first from the computer manufacturer's web site. If there is not a suitable driver available then use the component manufacturer website. Do not use any websites that automatically update drivers as they may install unwanted components.

Use this link to set up the custom settings for windows driver verifier:
https://answers.microsoft.com/en-us/...3-c48669e4c983

As the bsod occur update the zip so that we can debug the mini dump files and guide you through the repairs:
BSOD - Posting Instructions - Windows 10 Forums

I enabling driver verifier as described above and it resulted in a reboot loop after the setup required a restartt. I took a restore point prior to enabling it, and ended up having to revert back in order to use the system.

Were you able to open startup options?
Were you able to restart and select #6 startup options?
Were you able to open safe mode with command prompt?
Were you able to type verifier /reset?
If you were able to type verifier /reset what did you see on the display?

Were you able to click on advanced troubleshooting options command prompt?
Were you able to open Administrator X: \Windows\system32\cmd.exe?
Were you able to type: verifier /bootmode resetonbootfail?
Were you able to reboot?

Please see this link for turning off windows driver verifier: Enable and Disable Driver Verifier in Windows 10 Windows 10 Performance Maintenance Tutorials

Please practice using the windows advanced recovery options using this administrative command prompt command: shutdown /r /o /f /t 00