Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Computer Randomly Shutsdown


  • Please log in to reply
7 replies to this topic

#1 TyronSmiteApril

TyronSmiteApril

  • Members
  • 110 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Indiana, USA
  • Local time:08:45 PM

Posted 26 November 2017 - 04:04 PM

So this is the second instance where this has happened each time while playing CSGO. I was playing computer freezes and does nothing, I have to restart it and when I restart the computer it doesn't post any video then shuts down and turns right back on over and over again. The first time I left it unplugged for a few hours came home to work on it and plugged it and it worked fine. Today when it happened I opened my computer reseated the video and ram and it powered up fine and is working as it should. Any suggestions would be appreciated.

 

http://speccy.piriform.com/results/urctVee7G1OmpIv7CTSScnu

 

Attached File  CAM.jpg   71.38KB   0 downloads

 

Attached File  Reliability monitor.png   21.66KB   0 downloads

 

For the windows stopped working at 1:04 I have this description

 

The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000009f (0x0000000000000003, 0xffffd208947b9560, 0xffff958182c5c8e0, 0xffffd2089d7b1010). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 5bfbb342-3395-4fe4-8711-f84a0189bb2c.

 

 

Dump referenced above

 

Microsoft ® Windows Debugger Version 6.3.9600.17336 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Tacoma\Documents\MEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\Vistasymbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\Vistasymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 14393 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 14393.1794.amd64fre.rs1_release.171008-1615
Machine Name:
Kernel base = 0xfffff801`55a93000 PsLoadedModuleList = 0xfffff801`55d91040
Debug session time: Sun Nov 26 12:56:21.362 2017 (UTC - 5:00)
System Uptime: 0 days 0:08:50.970
Loading Kernel Symbols
...............................................................
......Page 26ca1a not present in the dump file. Type ".hh dbgerr004" for details
..........................................................
................................................................
.
Loading User Symbols

Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, ffffd208947b9560, ffff958182c5c8e0, ffffd2089d7b1010}

Page 86620 not present in the dump file. Type ".hh dbgerr004" for details
Probably caused by : UsbHub3.sys

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffd208947b9560, Physical Device Object of the stack
Arg3: ffff958182c5c8e0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffd2089d7b1010, The blocked IRP

Debugging Details:
------------------


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  UsbHub3.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5789998e

MODULE_NAME: UsbHub3

FAULTING_MODULE: fffff80ead860000 UsbHub3

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

DPC_STACK_BASE:  FFFF958182C64FB0

STACK_TEXT:  
ffff9581`82c5c8a8 fffff801`55c894d7 : 00000000`0000009f 00000000`00000003 ffffd208`947b9560 ffff9581`82c5c8e0 : nt!KeBugCheckEx
ffff9581`82c5c8b0 fffff801`55c893ea : ffffd208`93272320 ffff9581`82934180 00000000`00000002 ffffd208`93272398 : nt!PopIrpWatchdogBugcheck+0xeb
ffff9581`82c5c910 fffff801`55ac8fb1 : ffffd208`93272358 ffffd208`93272358 00000000`00140001 00000000`00000002 : nt!PopIrpWatchdog+0x22
ffff9581`82c5c960 fffff801`55be581a : 00000000`00000000 ffff9581`82934180 ffff9581`82940cc0 ffffd208`92e89040 : nt!KiRetireDpcList+0x701
ffff9581`82c5cbe0 00000000`00000000 : ffff9581`82c5d000 ffff9581`82c56000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

IMAGE_VERSION:  10.0.14393.0

FAILURE_BUCKET_ID:  0x9F_3_POWER_DOWN_rtwlanu_IMAGE_UsbHub3.sys

BUCKET_ID:  0x9F_3_POWER_DOWN_rtwlanu_IMAGE_UsbHub3.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x9f_3_power_down_rtwlanu_image_usbhub3.sys

FAILURE_ID_HASH:  {da5959bc-270a-468b-e44f-87e9ba438f78}

Followup: MachineOwner
---------

 

 

 

 

 

 

Most recent minidump

 

Microsoft ® Windows Debugger Version 6.3.9600.17336 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Tacoma\Documents\112617-5062-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 14393 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 14393.1794.amd64fre.rs1_release.171008-1615
Machine Name:
Kernel base = 0xfffff801`55a93000 PsLoadedModuleList = 0xfffff801`55d91040
Debug session time: Sun Nov 26 12:56:21.362 2017 (UTC - 5:00)
System Uptime: 0 days 0:08:50.970
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, ffffd208947b9560, ffff958182c5c8e0, ffffd2089d7b1010}

Probably caused by : UsbHub3.sys

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffd208947b9560, Physical Device Object of the stack
Arg3: ffff958182c5c8e0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffd2089d7b1010, The blocked IRP

Debugging Details:
------------------


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  UsbHub3.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5789998e

MODULE_NAME: UsbHub3

FAULTING_MODULE: fffff80ead860000 UsbHub3

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

DPC_STACK_BASE:  FFFF958182C64FB0

STACK_TEXT:  
ffff9581`82c5c8a8 fffff801`55c894d7 : 00000000`0000009f 00000000`00000003 ffffd208`947b9560 ffff9581`82c5c8e0 : nt!KeBugCheckEx
ffff9581`82c5c8b0 fffff801`55c893ea : ffffd208`93272320 ffff9581`82934180 00000000`00000002 ffffd208`93272398 : nt!PopIrpWatchdogBugcheck+0xeb
ffff9581`82c5c910 fffff801`55ac8fb1 : ffffd208`93272358 ffffd208`93272358 00000000`00140001 00000000`00000002 : nt!PopIrpWatchdog+0x22
ffff9581`82c5c960 fffff801`55be581a : 00000000`00000000 ffff9581`82934180 ffff9581`82940cc0 ffffd208`92e89040 : nt!KiRetireDpcList+0x701
ffff9581`82c5cbe0 00000000`00000000 : ffff9581`82c5d000 ffff9581`82c56000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

IMAGE_VERSION:  10.0.14393.0

FAILURE_BUCKET_ID:  0x9F_3_POWER_DOWN_rtwlanu_IMAGE_UsbHub3.sys

BUCKET_ID:  0x9F_3_POWER_DOWN_rtwlanu_IMAGE_UsbHub3.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x9f_3_power_down_rtwlanu_image_usbhub3.sys

FAILURE_ID_HASH:  {da5959bc-270a-468b-e44f-87e9ba438f78}

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffd208947b9560, Physical Device Object of the stack
Arg3: ffff958182c5c8e0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffd2089d7b1010, The blocked IRP

Debugging Details:
------------------


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  UsbHub3.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5789998e

MODULE_NAME: UsbHub3

FAULTING_MODULE: fffff80ead860000 UsbHub3

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

DPC_STACK_BASE:  FFFF958182C64FB0

STACK_TEXT:  
ffff9581`82c5c8a8 fffff801`55c894d7 : 00000000`0000009f 00000000`00000003 ffffd208`947b9560 ffff9581`82c5c8e0 : nt!KeBugCheckEx
ffff9581`82c5c8b0 fffff801`55c893ea : ffffd208`93272320 ffff9581`82934180 00000000`00000002 ffffd208`93272398 : nt!PopIrpWatchdogBugcheck+0xeb
ffff9581`82c5c910 fffff801`55ac8fb1 : ffffd208`93272358 ffffd208`93272358 00000000`00140001 00000000`00000002 : nt!PopIrpWatchdog+0x22
ffff9581`82c5c960 fffff801`55be581a : 00000000`00000000 ffff9581`82934180 ffff9581`82940cc0 ffffd208`92e89040 : nt!KiRetireDpcList+0x701
ffff9581`82c5cbe0 00000000`00000000 : ffff9581`82c5d000 ffff9581`82c56000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

IMAGE_VERSION:  10.0.14393.0

FAILURE_BUCKET_ID:  0x9F_3_POWER_DOWN_rtwlanu_IMAGE_UsbHub3.sys

BUCKET_ID:  0x9F_3_POWER_DOWN_rtwlanu_IMAGE_UsbHub3.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x9f_3_power_down_rtwlanu_image_usbhub3.sys

FAILURE_ID_HASH:  {da5959bc-270a-468b-e44f-87e9ba438f78}

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffd208947b9560, Physical Device Object of the stack
Arg3: ffff958182c5c8e0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffd2089d7b1010, The blocked IRP

Debugging Details:
------------------


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  UsbHub3.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5789998e

MODULE_NAME: UsbHub3

FAULTING_MODULE: fffff80ead860000 UsbHub3

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

DPC_STACK_BASE:  FFFF958182C64FB0

STACK_TEXT:  
ffff9581`82c5c8a8 fffff801`55c894d7 : 00000000`0000009f 00000000`00000003 ffffd208`947b9560 ffff9581`82c5c8e0 : nt!KeBugCheckEx
ffff9581`82c5c8b0 fffff801`55c893ea : ffffd208`93272320 ffff9581`82934180 00000000`00000002 ffffd208`93272398 : nt!PopIrpWatchdogBugcheck+0xeb
ffff9581`82c5c910 fffff801`55ac8fb1 : ffffd208`93272358 ffffd208`93272358 00000000`00140001 00000000`00000002 : nt!PopIrpWatchdog+0x22
ffff9581`82c5c960 fffff801`55be581a : 00000000`00000000 ffff9581`82934180 ffff9581`82940cc0 ffffd208`92e89040 : nt!KiRetireDpcList+0x701
ffff9581`82c5cbe0 00000000`00000000 : ffff9581`82c5d000 ffff9581`82c56000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

IMAGE_VERSION:  10.0.14393.0

FAILURE_BUCKET_ID:  0x9F_3_POWER_DOWN_rtwlanu_IMAGE_UsbHub3.sys

BUCKET_ID:  0x9F_3_POWER_DOWN_rtwlanu_IMAGE_UsbHub3.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x9f_3_power_down_rtwlanu_image_usbhub3.sys

FAILURE_ID_HASH:  {da5959bc-270a-468b-e44f-87e9ba438f78}

Followup: MachineOwner
---------

 


Edited by TyronSmiteApril, 26 November 2017 - 04:34 PM.


BC AdBot (Login to Remove)

 


#2 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,029 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:07:45 PM

Posted 26 November 2017 - 05:46 PM

We need more information about your system than what you've provided. Hence, please follow these BSOD posting instructions and attach the requested files by replying to this topic. You may skip the part of step three where it instructs you to create a new topic, since you already have a topic here. There's no need to create another topic. :wink:

Thank you.

Regards,
bwv848

 

P.S. In the mean time, is it possible to PHYSICALLY remove your USB dongle from the system and uninstall ALL of its drivers?


Edited by bwv848, 26 November 2017 - 05:48 PM.

If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#3 TyronSmiteApril

TyronSmiteApril
  • Topic Starter

  • Members
  • 110 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Indiana, USA
  • Local time:08:45 PM

Posted 26 November 2017 - 06:29 PM

We need more information about your system than what you've provided. Hence, please follow these BSOD posting instructions and attach the requested files by replying to this topic. You may skip the part of step three where it instructs you to create a new topic, since you already have a topic here. There's no need to create another topic. :wink:

Thank you.

Regards,
bwv848

 

P.S. In the mean time, is it possible to PHYSICALLY remove your USB dongle from the system and uninstall ALL of its drivers?

 

My bad I only didn't provide it as it wasn't a BSOD

Attached Files



#4 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,029 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:07:45 PM

Posted 26 November 2017 - 06:59 PM

Hi,

 

In the mean time, is it possible to PHYSICALLY remove your USB dongle from the system and uninstall ALL of its drivers?

Does the system behave better? Can't get any symbols for the dumps; hence they are of little use.


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#5 TyronSmiteApril

TyronSmiteApril
  • Topic Starter

  • Members
  • 110 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Indiana, USA
  • Local time:08:45 PM

Posted 26 November 2017 - 07:55 PM

Hi,

 

In the mean time, is it possible to PHYSICALLY remove your USB dongle from the system and uninstall ALL of its drivers?

Does the system behave better? Can't get any symbols for the dumps; hence they are of little use.

 

The only "usb dongles" I have are for my headset G930 and for my internet AC600 WLAN USB. The computer acts fine now with them in, it just randomly froze again today for the second time(first time was a few weeks prior) and it wouldn't start back up just kept attempting to start and restart over and over and wouldn't post any video. After reseating the RAM and GPU it powered on. I also ran memtest and had all passes no fails.



#6 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,029 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:07:45 PM

Posted 26 November 2017 - 08:19 PM

I was referring to this device:

Realtek RTL8811AU Wireless LAN 802.11ac USB 2.0 Network Adapter

Its driver was blamed in the dump analysis you provided in your first few posts. Unfortunately for some reason I am unable to analyze the dumps, as I am running into a plethora of symbol issues (strange indeed!).

 

USB dongles such as these have been known to cause all sorts of issues, most often BSODs and general system instability. They are unstable and fragile; on the other hand, a dedicated PCI wireless card makes a far better choice.

 

Networking and graphics are highly intertwined with each other (especially in modern NVIDIA drivers). If one breaks, usually the other breaks. That's why I'm insisting you at least try removing that thing if possible. :)

 

Regards,

bwv848


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)


#7 TyronSmiteApril

TyronSmiteApril
  • Topic Starter

  • Members
  • 110 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Indiana, USA
  • Local time:08:45 PM

Posted 26 November 2017 - 08:23 PM

I was referring to this device:

Realtek RTL8811AU Wireless LAN 802.11ac USB 2.0 Network Adapter

Its driver was blamed in the dump analysis you provided in your first few posts. Unfortunately for some reason I am unable to analyze the dumps, as I am running into a plethora of symbol issues (strange indeed!).

 

USB dongles such as these have been known to cause all sorts of issues, most often BSODs and general system instability. They are unstable and fragile; on the other hand, a dedicated PCI wireless card makes a far better choice.

 

Networking and graphics are highly intertwined with each other (especially in modern NVIDIA drivers). If one breaks, usually the other breaks. That's why I'm insisting you at least try removing that thing if possible. :)

 

Regards,

bwv848

 

I could remove it but then I am unable to use my computer on the internet, I will check about getting a Ethernet cable that can reach my box but for now its the only option I have. I will keep you posted much appreciated.

 

Just a sidenote, I moved the adapter to a different port as the one it was in was a 3.0 and the adapter isn't.

 

Edit Edit: I also updated the drivers for it as well.


Edited by TyronSmiteApril, 26 November 2017 - 08:28 PM.


#8 bwv848

bwv848

    Bleepin' Owl


  • BSOD Kernel Dump Expert
  • 3,029 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:92.96 million miles away from the sun
  • Local time:07:45 PM

Posted 26 November 2017 - 08:29 PM

No problem, let's keep in touch. :)

 

BTW, I suggest you run MemTest86 (tonight when you're done with the system) according to these instructions: http://www.carrona.org/memdiag.html Whilst you have run it before, I'd like you to run it for EIGHT passes. This is to ensure your RAM is fine.

 

Also suggest you test ALL disks with SeaTools: http://www.carrona.org/hddiag.html


If I do not reply in three days, please message me.
 
BC BSOD Posting Instructions | Carrona BSOD Index | Driver Reference Table (DRT)





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users