BSOD - computer has rebooted from a bugcheck: 0x0000007e

tda43 · 03 Jul 2014

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e (0xc0000005, 0x929c7fd5, 0x900f98b4, 0x900f9490). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 070214-5304-01.

This is a new Dell PC.

The PC blue screens about twice a week.

I have 1 powered USB device connected. Yesterday, I went to device manager and located the device in the Ports list (COM4). I did a 'update driver'. Device manger said there was a better driver available and downloaded it over the internet. The PC requested a restart. Upon restart, windows went right into system repair mode. System repair did not succeed after 1 hour so I cancelled out of all windows and did a hard reboot. As soon as the PC powered back on, it instantly had a BSOD.

I then unplugged the USB cable in question and the PC booted up fine.

I haven't had time to continue troubleshooting, my guess is I will have to do a system restore to address this driver issue.

Thanks in advance!

Arc · 03 Jul 2014

Hi tda43.

Do you have any USB to Serial converter? If so, remove it, and see if the BSOD stops.

It is causing the BSODs.

Code:

BugCheck 1000007E, {c0000005, 929c7fd5, 900f98b4, 900f9490}

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

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

Code:

ftdibus    USB Serial Converter Driver    c:\windows\system32\drivers\ftdibus.sys

And the driver is extremely old, so the device is, too.

Code:

    Image name: ftdibus.sys
    Timestamp:        Tue Apr 20 14:34:55 2004 (4084E7B7)

Let us know the situation after removing it.

tda43 · 07 Jul 2014

Arc - you nailed it. Thanks a million!

Arc · 08 Jul 2014

You are welcome mate. :)

Let us know for any further issue.