Blue Screen Crash

Mroctober · 04 May 2011

I was transferring files from a dvd-r to a Verbatim protable hard drive, when I got a blue screen then a reboot. The drive was bought yesterday and this was the first time using it on this pc.

0x0000007f (0x00000000, 0x00000000, 0x00000000, 0x00000000 That's the error in the event viewer

Attached is the memory dump file

SledgeDG · 04 May 2011

Hi Mroctober and welcome to SF
Your dump identifies as probable cause the driver fnetthjm_152D.sys

Code:

fnetthjm_152D.sys Wed Jul 22 05:55:17 2009 (4A66E205)

Which could well be the driver for your portable drive. I would check with verbatim if there's a working driver available
Support Center | Verbatim

Or does the drive have to be formatted before it can be used?
If you can't find a solution, assume a shotty drive and exchange it for a good one

Code:

.............................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {0, 0, 0, 0}

Unable to load image \SystemRoot\system32\drivers\fnetthjm_152D.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for fnetthjm_152D.sys
*** ERROR: Module load completed but symbols could not be loaded for fnetthjm_152D.sys
Probably caused by : fnetthjm_152D.sys ( fnetthjm_152D+1ca2 )

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

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

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000000, EXCEPTION_DIVIDED_BY_ZERO
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR:  0x7f_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  wmpnetwk.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from a2f9aca2 to 8305304b

STACK_TEXT:  
807e2de0 a2f9aca2 badb0d00 00000000 807e2e34 nt!KiTrap00+0x8b
WARNING: Stack unwind information not available. Following frames may be wrong.
807e2e50 85c64c3b 85c64b38 807e2ea0 8308c933 fnetthjm_152D+0x1ca2
807e2e5c 8308c933 85bdfaa8 85c64b38 85f321d4 0x85c64c3b
807e2ea0 9098b30d 8304f0e8 85b45690 00000000 nt!IopfCompleteRequest+0x128
807e2ed0 9098bf55 875d49f8 85c64b38 85f32170 USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x6e0
807e2efc 9098c6f6 862e3028 862e30f0 862e3a98 USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x33b
807e2f24 909889ce 862e3028 862e3a98 862e3002 USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xbc
807e2f48 8308c1b5 862e3aa4 862e3002 00000000 USBPORT!USBPORT_Xdpc_Worker+0x173
807e2fa4 8308c018 807c2120 87d81290 00000000 nt!KiExecuteAllDpcs+0xf9
807e2ff4 8308b7dc a51c9ce4 00000000 00000000 nt!KiRetireDpcList+0xd5
807e2ff8 a51c9ce4 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c
8308b7dc 00000000 0000001a 00d6850f bb830000 0xa51c9ce4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
fnetthjm_152D+1ca2
a2f9aca2 ??              ???

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  fnetthjm_152D+1ca2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: fnetthjm_152D

IMAGE_NAME:  fnetthjm_152D.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a66e205

FAILURE_BUCKET_ID:  0x7f_0_fnetthjm_152D+1ca2

BUCKET_ID:  0x7f_0_fnetthjm_152D+1ca2

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

1: kd> lmvm fnetthjm_152D
start    end        module name
a2f99000 a2f9ef80   fnetthjm_152D T (no symbols)           
    Loaded symbol image file: fnetthjm_152D.sys
    Image path: \SystemRoot\system32\drivers\fnetthjm_152D.sys
    Image name: fnetthjm_152D.sys
    Timestamp:        Wed Jul 22 05:55:17 2009 (4A66E205)
    CheckSum:         00011945
    ImageSize:        00005F80
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

-DG

Mroctober · 04 May 2011

After the pc restarted, the drive was not recognized anymore. I uninstalled it, unplugged and plugged it back in. The driver installed, but in the device manager there's a yellow triangle with an exclamation mark. Verbatim support said I should contact Microsoft for a driver problem.