a.k.a.

Hello everyone,

FIRST: Actually, there's no Process Explorer error. That was my fault -- That was from an older bootlog file.

Here's the error code I've just gotten this morning. Google turned up nothing, so it could be that I mistranscribed something.

0x0000007B (0xFFFFFA60005AF9D0, 0xFFFFFFFFC0000034, 0x0000000000000000, 0x0000000000000000)

It suggessted checking for viruses, HDD controlers, HDD configuration & termination, and running CHKDSK /F for corruption.

I ran a bootlog from F8 on startup, but the only one that I can find is a month old (ntbtlog.txt).

Booting from last good configuration seems to bypass the bluescreen problem. When I get to the desktop, however, Windows tells me it needs to search for a driver for an unknown device, then looks online and finds nothing.

The only other relevant hardware/driver events preceding this error that I can think of are:

(1) hooking up to a new printer. The driver installed fine under a 'guest' user account. Could it be that it's been looking for a trace of the driver under the normal user accounts? Does a guest login erase any installed driver (perhaps incompletely)?

(2) Using a USB thumb drive on an on-campus networked machine to print a document, and reinserting the USB key into my laptop afterwards.

Would be grateful to hear your advice about this one.

Cheers,
a.k.a.