BSOD Windows not shutting down

Attachment 160517

When shutting down the pc it just restarts and I have to manually just press the button and thoughts how to fix this?

Thanks guys

A DVD/CD/Multimedia burning(iTunes?,Noton Safe and Restore?, Gear products?) program is the cause
Remove such programs to fix BSODs
Download Malwarebytes
Install, update it and run a system scan

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {4, 258, 8594fa70, 82f45b24}

*** WARNING: Unable to verify timestamp for GEARAspiWDM.sys
*** ERROR: Module load completed but symbols could not be loaded for GEARAspiWDM.sys
Probably caused by : cdrom.sys ( cdrom!DeviceSendPowerProcessRequest+15b )


DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 00000004, The power transition timed out waiting to synchronize with the Pnp
    subsystem.
Arg2: 00000258, Timeout in seconds.
Arg3: 8594fa70, The thread currently holding on to the Pnp lock.
Arg4: 82f45b24

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


DRVPOWERSTATE_SUBCODE:  4

FAULTING_THREAD:  8594fa70

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 82e9c69d to 82e95766

STACK_TEXT:  
8eb17668 82e9c69d 8594fa70 00000000 82f48d20 nt!KiSwapContext+0x26
8eb176a0 82e9b4f7 8594fb30 8594fa70 8eb1778c nt!KiSwapThread+0x266
8eb176c8 82e950cf 8594fa70 8594fb30 00000000 nt!KiCommitThreadWait+0x1df
8eb17744 8c61f0a5 8eb1778c 00000000 00000000 nt!KeWaitForSingleObject+0x393
8eb17764 8c61f5de 00000000 880b3e18 8eb177bc Wdf01000!FxCREvent::EnterCRAndWait+0x1d
8eb17774 8c6214df 00000000 7a3a3dd8 8eb17804 Wdf01000!FxCREvent::EnterCRAndWaitAndLeave+0xe
8eb177bc 8c62cffe 000b3e18 8eb17804 8eb177e8 Wdf01000!FxIoTarget::SubmitSync+0x1db
8eb177e0 8ced4916 00000020 880b3e18 85c5c220 Wdf01000!imp_WdfRequestSend+0x178
8eb17824 8ced4790 00000004 00000314 897cd098 cdrom!DeviceSendPowerProcessRequest+0x15b
8eb17838 8c661d5c 79bf8c00 00000005 00000314 cdrom!DeviceEvtD0Exit+0x83
8eb17858 8c660d81 897cd098 897cd1a4 897cd098 Wdf01000!FxPkgPnp::PowerGotoD3Stopped+0xc7
8eb178e0 8c661bb2 00000314 897cd1a4 897cd098 Wdf01000!FxPkgPnp::PowerEnterNewState+0x11c
8eb17904 8c6625bb 8eb1791c 00000008 897cd098 Wdf01000!FxPkgPnp::PowerProcessEventInner+0x171
8eb17928 8c66b747 00000001 8eb1795c 8c66b67c Wdf01000!FxPkgPnp::PowerProcessEvent+0x15c
8eb17934 8c66b67c 897cd098 897cd214 897cd098 Wdf01000!FxPkgPnp::NotPowerPolOwnerStopping+0x12
8eb1795c 8c6687f5 0000055b 897cd214 897cd098 Wdf01000!FxPkgPnp::NotPowerPolicyOwnerEnterNewState+0x105
8eb17980 8c669388 00000002 00000008 897cd098 Wdf01000!FxPkgPnp::PowerPolicyProcessEventInner+0x264
8eb179a4 8c666079 00000001 00000000 8eb179dc Wdf01000!FxPkgPnp::PowerPolicyProcessEvent+0x172
8eb179b4 8c665484 897cd098 897cd140 897cd098 Wdf01000!FxPkgPnp::PnpEventStartedStopping+0x11
8eb179dc 8c665db2 0000010e 897cd140 897cd098 Wdf01000!FxPkgPnp::PnpEnterNewState+0x104
8eb17a00 8c66647a 8eb17a18 00000000 897cd098 Wdf01000!FxPkgPnp::PnpProcessEventInner+0x149
8eb17a24 8c65d68f 00000200 00000000 86aad8e8 Wdf01000!FxPkgPnp::PnpProcessEvent+0x13e
8eb17a50 8c65ee02 897cd098 882e6e00 882e6e00 Wdf01000!FxPkgPnp::_PnpRemoveDevice+0x8b
8eb17a70 8c63ba3f 882e6e00 8eb17a98 8c63bc63 Wdf01000!FxPkgPnp::Dispatch+0x207
8eb17a7c 8c63bc63 88c9d148 882e6e00 882e6ef8 Wdf01000!FxDevice::Dispatch+0x7f
8eb17a98 82e55593 88c9d148 00000000 882e6f1c Wdf01000!FxDevice::DispatchWithLock+0x7b
8eb17ab0 92e02ecb 88dde348 882e6f00 882e6e00 nt!IofCallDriver+0x63
WARNING: Stack unwind information not available. Following frames may be wrong.
8eb17ac8 92e00728 88dde348 882e6e00 00000000 GEARAspiWDM+0x2ecb
8eb17af0 82e55593 1bdde290 022e6e00 8eb17b8c GEARAspiWDM+0x728
8eb17b08 82ff6f95 8824e2d8 860f2b30 8824e2d8 nt!IofCallDriver+0x63
8eb17b38 830e3a63 8824e2d8 00000000 860f2b30 nt!IopSynchronousCall+0xc2
8eb17b90 82efa352 8824e2d8 00000002 b947d5f8 nt!IopRemoveDevice+0xd4
8eb17bbc 830db7a3 00000015 b947d5f8 00000000 nt!PnpRemoveLockedDeviceNode+0x16c
8eb17bd0 830dba57 00000002 00000015 00000000 nt!PnpDeleteLockedDeviceNode+0x2d
8eb17c04 830df431 8824e2d8 b947d5f8 00000002 nt!PnpDeleteLockedDeviceNodes+0x4c
8eb17cc4 82fcf2ca 8eb17cf4 00000000 ba256008 nt!PnpProcessQueryRemoveAndEject+0x946
8eb17cdc 82fdd3ca 00000000 85f1a170 8594fa70 nt!PnpProcessTargetDeviceEvent+0x38
8eb17d00 82e9baab 85f1a170 00000000 8594fa70 nt!PnpDeviceEventWorker+0x216
8eb17d50 83026f64 00000001 bc7138bc 00000000 nt!ExpWorkerThread+0x10d
8eb17d90 82ecf219 82e9b99e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  .thread 0xffffffff8594fa70 ; kb

FOLLOWUP_IP: 
cdrom!DeviceSendPowerProcessRequest+15b
8ced4916 84c0            test    al,al

SYMBOL_STACK_INDEX:  8

SYMBOL_NAME:  cdrom!DeviceSendPowerProcessRequest+15b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: cdrom

IMAGE_NAME:  cdrom.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce788f1

FAILURE_BUCKET_ID:  0x9F_cdrom!DeviceSendPowerProcessRequest+15b

BUCKET_ID:  0x9F_cdrom!DeviceSendPowerProcessRequest+15b

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

Will do, ill let you know what the outcome is I dont have Norton.. I hardly use iTunes I could remove that I use CDBurner to burn stuff...

Related to RtVlan60.sys NDIS 6.0 Intermediate Miniport Driver from Windows (R) Codename Longhorn DDK provider

Related to pcouffin.sys Patin-Couffin low level access layer for CD devices from VSO Software.

Related to adfs.sys Adobe Drive File System Driver.

Hey guys I was just on my computer using Microsoft Word and the PC just shut down and I got the blue screen.

Thanks in advance if you can solve my problem

Regards Sean

Hey dude,

Sorry I totally forgot to reply. Yeah my previous problem had been solved I have now encountered another. My apologise for not reply to say if your problem had been solved or not.

Regards Sean

Any ideas??

Sean

Remove this software libusb
No recent dumps are present in your attachment, last dumps still blame GEARAspiWDM.sys or a software using it

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 97f4d19c, a268fb30, a268f710}

*** WARNING: Unable to verify timestamp for libusb0.sys
*** ERROR: Module load completed but symbols could not be loaded for libusb0.sys
Probably caused by : libusb0.sys ( libusb0+42fc )


SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 97f4d19c, The address that the exception occurred at
Arg3: a268fb30, Exception Record Address
Arg4: a268f710, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
usbhub!UsbhFdoSetPowerDx_Action+36
97f4d19c 8b4728          mov     eax,dword ptr [edi+28h]

EXCEPTION_RECORD:  a268fb30 -- (.exr 0xffffffffa268fb30)
ExceptionAddress: 97f4d19c (usbhub!UsbhFdoSetPowerDx_Action+0x00000036)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 00000028
Attempt to read from address 00000028

CONTEXT:  a268f710 -- (.cxr 0xffffffffa268f710)
eax=87b46c30 ebx=876ce028 ecx=87b46b30 edx=78447350 esi=87b46b30 edi=00000000
eip=97f4d19c esp=a268fbf8 ebp=a268fc10 iopl=0         nv up ei ng nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010282
usbhub!UsbhFdoSetPowerDx_Action+0x36:
97f4d19c 8b4728          mov     eax,dword ptr [edi+28h] ds:0023:00000028=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  00000000

EXCEPTION_PARAMETER2:  00000028

READ_ADDRESS: GetPointerFromAddress: unable to read from 82db1718
Unable to read MiSystemVaType memory at 82d91160
 00000028 

FOLLOWUP_IP: 
libusb0+42fc
91db72fc ??              ???

BUGCHECK_STR:  0x7E

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER:  from 97f4df66 to 97f4d19c

STACK_TEXT:  
a268fc10 97f4df66 87b46c30 00000000 87b46b30 usbhub!UsbhFdoSetPowerDx_Action+0x36
a268fc38 97f4ddc8 876ce5d8 00000004 87b46b30 usbhub!UsbhFdoDevicePowerState+0x189
a268fc54 97f37bac 876ce028 876ce0e0 87b46b30 usbhub!UsbhFdoPower_SetPower+0x6d
a268fc68 82c54d16 876ce028 87b46b30 00000016 usbhub!UsbhGenDispatch+0x63
a268fc80 82c854ae 00000004 876ce028 a268fc98 nt!IopPoHandleIrp+0x28
a268fc90 82c57049 a268fcc8 91db72fc 876ce028 nt!IofCallDriver+0x55
a268fc98 91db72fc 876ce028 87b46b30 00000000 nt!IoCallDriver+0x10
WARNING: Stack unwind information not available. Following frames may be wrong.
a268fcc8 91db4403 876170e0 87b46b30 82d89f40 libusb0+0x42fc
a268fcf8 82c54823 87617028 87b46b30 00000000 libusb0+0x1403
a268fd50 82e576d3 875140a8 90ea70e9 00000000 nt!PopIrpWorker+0x351
a268fd90 82d090f9 82c544d2 875140a8 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  libusb0+42fc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: libusb0

IMAGE_NAME:  libusb0.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a537d6e

STACK_COMMAND:  .cxr 0xffffffffa268f710 ; kb

FAILURE_BUCKET_ID:  0x7E_libusb0+42fc

BUCKET_ID:  0x7E_libusb0+42fc

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