BSoD on Wake/Overnight

Windows 7 Ultimate, OEM, 64 Bit, Hand built, Days old.

Had 2 BSoDs. First one was overnight. Second one was after I woke the computer up from sleep after sitting overnight.

I was having a hanging issue but I resolved it:
https://www.sevenforums.com/crashes-d...ml#post1334733

The problem there was that my PSU was not adequate to power 2 of my graphics cards. I took one of the card out for now until I can purchase a bigger PSU. (I can't run xfire anyways because the xfire cables are not long enough, but that's another issue altogether).

The driver that it complains about the last time was copperhd I believe. Is that my Razer Copperhead Mouse?

Any ideas on how to fix? TIA

I attached the zipped folder from the "BSOD Dump & System File Collection app", and in the folder is the perf mon report .html as well.

BSODs caused by your Diamondback USB Optical Mous, please update the driver since it is no Windows 7 certified. The software it uses dates back to 2006. Remove that device if no updates are found

Code:

copperhd.sys    copperhd.sys+28e0    fffff880`06cc4000    fffff880`06cc7600    0x00003600    0x4473d831    24/05/2006 07:51:13

Turn off Driver Verifier

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck C9, {224, fffff88006cc68e0, fffff98011414af0, 2}

Unable to load image copperhd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for copperhd.sys
*** ERROR: Module load completed but symbols could not be loaded for copperhd.sys
Probably caused by : copperhd.sys ( copperhd+28e0 )


DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 0000000000000224, An IRP dispatch handler has returned a status that is inconsistent with the
    IRP's IoStatus.Status field.
Arg2: fffff88006cc68e0, The address in the driver's code where the error was detected.
Arg3: fffff98011414af0, IRP address.
Arg4: 0000000000000002, Expected status code.

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


BUGCHECK_STR:  0xc9_224

DRIVER_VERIFIER_IO_VIOLATION_TYPE:  224

FAULTING_IP: 
copperhd+28e0
fffff880`06cc68e0 53              push    rbx

FOLLOWUP_IP: 
copperhd+28e0
fffff880`06cc68e0 53              push    rbx

IRP_ADDRESS:  fffff98011414af0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800031533dc to fffff80002cc8740

STACK_TEXT:  
fffff880`031a11d8 fffff800`031533dc : 00000000`000000c9 00000000`00000224 fffff880`06cc68e0 fffff980`11414af0 : nt!KeBugCheckEx
fffff880`031a11e0 fffff800`0315d47a : fffff800`031519f0 fffff880`06cc68e0 fffff980`11414af0 00000000`00000002 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`031a1220 fffff800`0315e3f3 : fffff880`06cc68e0 fffffa80`070b8bb8 00000000`00000002 00000000`ffffffff : nt!ViErrorFinishReport+0xda
fffff880`031a1270 fffff800`03169759 : fffffa80`070b8b00 fffffa80`070b8b00 fffffa80`070b8bb8 00000000`00000240 : nt!VfErrorReport4+0x83
fffff880`031a1360 fffff800`03169b63 : fffffa80`070b8b00 00000000`00000002 fffffa80`06f9b3d0 fffff880`05a593a8 : nt!IovpCallDriver2+0x179
fffff880`031a13c0 fffff800`0316fc2e : fffff980`11414af0 fffff980`11414af0 00000000`00000002 fffffa80`06f9b3d0 : nt!VfAfterCallDriver+0x353
fffff880`031a1410 fffff800`031724da : fffff980`11414f68 fffffa80`06f9b3d0 fffffa80`06fa5040 fffffa80`070b8b00 : nt!IovCallDriver+0x57e
fffff880`031a1470 fffff800`0316fc16 : fffff980`11414af0 00000000`00000002 fffffa80`06fa5040 fffffa80`05f12f40 : nt!ViFilterDispatchPnp+0xea
fffff880`031a14a0 fffff880`05a47875 : fffffa80`06fa5f00 fffff980`11414af0 fffffa80`06fa5b40 fffffa80`05f12f40 : nt!IovCallDriver+0x566
fffff880`031a1500 fffff880`05a473f8 : 00000000`00000000 fffffa80`06fa5b40 fffffa80`06fa5f00 fffffa80`06fa5f00 : hidusb!HumRemoveDevice+0x81
fffff880`031a1540 fffff880`05a5f8c0 : fffffa80`06fa5cb0 fffff880`05a5fc10 ffffffff`ffffffb0 fffff980`11414af0 : hidusb!HumPnP+0xbc
fffff880`031a15b0 fffff880`05a5cc52 : 00000000`00000001 fffff980`11414af0 00000000`00000000 00000000`00000002 : HIDCLASS!HidpRemoveDevice+0x104
fffff880`031a1600 fffff880`05a5c64a : fffff880`05a59300 fffffa80`06fa5c90 fffffa80`06fa5c90 fffff880`031a16c8 : HIDCLASS!HidpFdoPnp+0x192
fffff880`031a1630 fffff880`05a4e90d : fffff880`05a593a8 fffff880`05a583c0 fffffa80`06fa5c90 fffffa80`00000001 : HIDCLASS!HidpIrpMajorPnp+0x8a
fffff880`031a16a0 fffff800`0316fc16 : fffff980`11414af0 fffff980`11414af0 00000000`00000002 fffff880`031a1828 : HIDCLASS!HidpMajorHandler+0xf5
fffff880`031a1710 fffff800`02f33a09 : fffffa80`06fa5b40 00000000`c00000bb fffff880`031a1828 fffffa80`066513f0 : nt!IovCallDriver+0x566
fffff880`031a1770 fffff800`030b3161 : fffffa80`06f89060 00000000`00000000 fffffa80`06f89730 00000000`00000801 : nt!IopSynchronousCall+0xc5
fffff880`031a17e0 fffff800`02dc9c13 : fffff8a0`0150c130 fffff8a0`0150c130 00000000`00000000 00000000`00000000 : nt!IopRemoveDevice+0x101
fffff880`031a18a0 fffff800`030b2cb4 : fffffa80`06f89730 00000000`00000000 00000000`00000002 00000000`00000018 : nt!PnpRemoveLockedDeviceNode+0x1a3
fffff880`031a18f0 fffff800`030b2dc0 : 00000000`00000000 fffffa80`06f5e000 fffff8a0`0a588d80 fffff800`02ecc300 : nt!PnpDeleteLockedDeviceNode+0x44
fffff880`031a1920 fffff800`030b2eb9 : fffffa80`06fbe002 fffffa80`06fbe0e0 00000000`00000001 00000000`00000000 : nt!PnpDeleteLockedDeviceNodes+0xa0
fffff880`031a1990 fffff800`030b3031 : fffffa80`06fbe0e0 00000000`00000000 fffffa80`06fbe0e0 00000000`00010286 : nt!PnpDelayedRemoveWorker+0x79
fffff880`031a19e0 fffff800`02dc9e39 : 00000000`00000004 fffffa80`062fce20 00000000`00000001 00000000`00000001 : nt!PnpChainDereferenceComplete+0x131
fffff880`031a1a20 fffff800`03143690 : 00000000`00000000 fffffa80`06f7ed00 fffff8a0`09096db0 00000000`00000001 : nt!PnpIsChainDereferenced+0xc9
fffff880`031a1aa0 fffff800`0314392c : fffff880`031a1c78 00000000`00010200 fffff880`031a1c00 00000000`00000000 : nt!PnpProcessQueryRemoveAndEject+0xff0
fffff880`031a1be0 fffff800`0302ea1c : 00000000`00000000 fffffa80`066d99d0 fffff8a0`09124010 fffff800`02e6d500 : nt!PnpProcessTargetDeviceEvent+0x4c
fffff880`031a1c10 fffff800`02cd5961 : fffff800`02f334f0 fffff8a0`09096db0 fffff800`02e6d5f8 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x58b2b
fffff880`031a1c70 fffff800`02f6b7c6 : ff7fe0f9`ff7ee0fa fffffa80`039f5680 00000000`00000080 fffffa80`039d8890 : nt!ExpWorkerThread+0x111
fffff880`031a1d00 fffff800`02ca6c26 : fffff880`02f64180 fffffa80`039f5680 fffff880`02f6efc0 ff84e1f8`ff83e1f9 : nt!PspSystemThreadStartup+0x5a
fffff880`031a1d40 00000000`00000000 : fffff880`031a2000 fffff880`0319c000 fffff880`031a1370 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

SYMBOL_NAME:  copperhd+28e0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: copperhd

IMAGE_NAME:  copperhd.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4473d831

FAILURE_BUCKET_ID:  X64_0xc9_224_copperhd+28e0

BUCKET_ID:  X64_0xc9_224_copperhd+28e0

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

Thanks for your help. I would have thought that windows 7 would've pulled the correct driver on that mouse since it correctly detected it. I updated the driver from the manufacturer's website and it fixed the problem for me so far. Thank you for your help.