BSOC, 0x000000c4, gdrv.sys, DRIVER_POWER_STATE_FAILURE

Hello,

Hmm. Was windows reinstall after the upgrade?

Code:

Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Downloads\REBECA-PC-Mon_10_20_2014_124851_49\102014-34320-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`0300c000 PsLoadedModuleList = 0xfffff800`0324f890
Debug session time: Mon Oct 20 22:25:57.608 2014 (UTC + 6:00)
System Uptime: 0 days 0:13:21.794
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {f6, 5ac, fffffa800a7bd060, fffff8800729a809}

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

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

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

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 00000000000005ac, Handle value being referenced.
Arg3: fffffa800a7bd060, Address of the current process.
Arg4: fffff8800729a809, Address inside the driver that is performing the incorrect reference.

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


BUGCHECK_STR:  0xc4_f6

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  JBrowser.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff8000350e4ec to fffff80003081bc0

STACK_TEXT:  
fffff880`0773e5b8 fffff800`0350e4ec : 00000000`000000c4 00000000`000000f6 00000000`000005ac fffffa80`0a7bd060 : nt!KeBugCheckEx
fffff880`0773e5c0 fffff800`03523bf4 : 00000000`000005ac fffffa80`0a7bd060 00000000`00000002 fffff980`3328efe0 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`0773e600 fffff800`032db890 : 00000000`00000000 fffff880`0773e830 00000000`00000000 fffff980`3328ef00 : nt!VfCheckUserHandle+0x1b4
fffff880`0773e6e0 fffff800`0335b8c5 : fffff980`3328ef00 00000000`000f001f 00000000`00000000 fffff800`0335b800 : nt! ?? ::NNGAKEGL::`string'+0x2027e
fffff880`0773e7b0 fffff800`03523988 : fffff980`3328efe0 00000000`00000001 fffff880`0773e8a0 fffff800`0307d410 : nt!ObReferenceObjectByHandle+0x25
fffff880`0773e800 fffff880`0729a809 : 00000000`000f0000 00000000`00000001 fffff980`3328efe0 fffffa80`07c6f0d8 : nt!VerifierObReferenceObjectByHandle+0x48
fffff880`0773e850 00000000`000f0000 : 00000000`00000001 fffff980`3328efe0 fffffa80`07c6f0d8 fffff880`0773e8d8 : gdrv+0x1809
fffff880`0773e858 00000000`00000001 : fffff980`3328efe0 fffffa80`07c6f0d8 fffff880`0773e8d8 00000000`00000000 : 0xf0000
fffff880`0773e860 fffff980`3328efe0 : fffffa80`07c6f0d8 fffff880`0773e8d8 00000000`00000000 fffffa80`0796c2b0 : 0x1
fffff880`0773e868 fffffa80`07c6f0d8 : fffff880`0773e8d8 00000000`00000000 fffffa80`0796c2b0 fffff800`0339ee67 : 0xfffff980`3328efe0
fffff880`0773e870 fffff880`0773e8d8 : 00000000`00000000 fffffa80`0796c2b0 fffff800`0339ee67 fffffa80`07c6f0d8 : 0xfffffa80`07c6f0d8
fffff880`0773e878 00000000`00000000 : fffffa80`0796c2b0 fffff800`0339ee67 fffffa80`07c6f0d8 fffff800`03526cdc : 0xfffff880`0773e8d8


STACK_COMMAND:  kb

FOLLOWUP_IP: 
gdrv+1809
fffff880`0729a809 85c0            test    eax,eax

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  gdrv+1809

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: gdrv

IMAGE_NAME:  gdrv.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  49b9d175

FAILURE_BUCKET_ID:  X64_0xc4_f6_gdrv+1809

BUCKET_ID:  X64_0xc4_f6_gdrv+1809

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

0: kd> lmvm gdrv
start             end                 module name
fffff880`07299000 fffff880`072a2000   gdrv     T (no symbols)           
    Loaded symbol image file: gdrv.sys
    Image path: gdrv.sys
    Image name: gdrv.sys
    Timestamp:        Fri Mar 13 09:22:29 2009 (49B9D175)
    CheckSum:         000105CE
    ImageSize:        00009000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

A clean install is recommended on upgrades like this.

If considered, I would call my friend to help guide you.