Random Reset Problem

Scroll down to option two: Driver Verifier - Enable and Disable

nilank said:

You tried what I asked you to do? Maybe you could figure out the problem that way.

@ OP, delete these things from startup. As it is guided twice by two different posters, there must be some reason behind it.
No code has to be inserted here.None of those are supposed to be there for any real need, but they often cause problems. Moreover, I we are suspecting one of these drivers are buggy.

@ Nilank, well found :)

RussWalker said:

Looks like I had already disabled it, it said no settings were changed.

Sounds bad. Very bad. It must be some driver bug then, that is making the computer feel that Driver Verifier is enabled; whereas it is actually not. Earlier we noticed some buggy drivers, which also behaved in the same way, but never generated this Bucket ID:

Code:

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

It made me think that you have DV enabled, plus the Bugcheck code C9, DRIVER_VERIFIER_IOMANAGER_VIOLATION.

Now, have another look:

Code:

0: kd> !irp bb7ce438 9
Irp is active with 8 stacks 7 is current (= 0xbb7ce580)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
Flags = 40000000
ThreadListEntry.Flink = bb7ce448
ThreadListEntry.Blink = bb7ce448
IoStatus.Status = c0000010
IoStatus.Information = 00000000
RequestorMode = 00000000
Cancel = 00
CancelIrql = 0
ApcEnvironment = 00
UserIosb = 00000000
UserEvent = 00000000
Overlay.AsynchronousParameters.UserApcRoutine = 00000000
Overlay.AsynchronousParameters.UserApcContext = 00000000
Overlay.AllocationSize = 00000000 - 00000000
CancelRoutine = 00000000   
UserBuffer = 00000000
&Tail.Overlay.DeviceQueueEntry = bb7ce478
Tail.Overlay.Thread = 00000000
Tail.Overlay.AuxiliaryBuffer = 00000000
Tail.Overlay.ListEntry.Flink = 00000000
Tail.Overlay.ListEntry.Blink = 00000000
Tail.Overlay.CurrentStackLocation = bb7ce580
Tail.Overlay.OriginalFileObject = 00000000
Tail.Apc = 00000000
Tail.CompletionKey = 00000000
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  2 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 c0000010
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
 [ 17,ff]   0  2 bb7adbe0 00000000 00000000-00000000    
          bb7adbe0: Could not read device object or _DEVICE_OBJECT not found

            Args: bb796020 00000000 00000000 00000000
>[ 17,ff]   0 e0 bb7adbe0 00000000 83372d1c-bb7ce5a4 Success Error Cancel 
          bb7adbe0: Could not read device object or _DEVICE_OBJECT not found
    nt!IovpInternalCompletionTrap
            Args: bb796020 00000000 00000000 00000000
 [ 17,ff]   0 e0 bb797ee0 00000000 83371bff-80e449b0 Success Error Cancel 
          bb797ee0: Could not read device object or _DEVICE_OBJECT not found
    nt!ViIrpSynchronousCompletionRoutine
            Args: bb796020 00000000 00000000 00000000
Extra information not available.

IoStatus.Status = c0000010 means, The specified request is not a valid operation for the target device. So it behaves as same as a normal DV enabled crash dump.

Now time for a conclusion, the crash dump says that the probable cause of the crash is somehow USB/ Input (Keyboard & Mouse) related.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck C9, {220, badeaa8c, bb7ce438, bb796020}

Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpMajorHandler+0 )

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

So, let us first update Renesas Electronics Corporation USB 3.0 Host Controller Driver from Filesystem/Device Drivers Downloads | Renesas Electronics America

Next step, Uninstall these programs

Code:

Start Menu\Programs\Logitech
Start Menu\Programs\Logitech\Logitech Harmony Remote
Start Menu\Programs\Logitech\Mouse and Keyboard
Start Menu\Programs\Logitech\Unifying

and use some other Keyboard and mouse those does not need any third party programs or drivers to be installed to use those. You do it, at lease as a test.

Finally, a driver bug often caused by a real bug. Scan the system for possible virus infection using these two programs only.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

Let us know the results.

Russ, unfortunately in remote assistance we have to depend on the data you supplied, and the supplied data said you use Logitech Keyboard-mouse.

Removing stuff from startup does not loss any functionality at all, but cause problems.

RussWalker said:

So far so good!

Take your time :) Report us the situation back.