I don't see a driver mentioned there, but maybe we can find one:
I can run a debugging utility on the dump files if you do this:
1 > create a new folder on the desktop and call it "dumpcheck" or whatever you like
2 > navigate to %systemroot%\minidump and copy the last few minidump files to that folder.%systemroot% is normally c:\windows. They are numbered by date. You can paste that address in address bar to get there.
3 > close the folder and right click on it and select Send to Compressed (zipped) Folder
4 > use the "manage attachments" in the "add" reply window to upload that zip file here as an attachment.
This might point us to a 3rd party driver causing the error, if one exists for it.
Windows has a built in driver tester that may find something.
Before using it you must ensure that you can start in Safe Mode and return from it. If verifier issues a STOP screen, rebooting in Safe Mode is the only way to reset it.
In its default configuration verifier tests "unsigned" drivers, but you should have it test all drivers under maximum conditions.
There's less to it than meets the eye in this MS article:http://support.microsoft.com/default.aspx?...kb;en-us;244617
To run verifier simply go to Start > run and enter:verifier.exe
and select "standard configuration" and follow the prompts.
It will run on the next reboot. If it finds something you will get a Blue Screen STOP message.
Ignore the STOP parameters -- they are specific to verifier. The only thing important is the driver file name if it finds one.
If you get a STOP screen you will have to reboot to Safe Mode and run verifier again and have it "delete existing settings"
If you do not get a STOP message you can run it again checking all drivers; driver verifier will continue to run on every boot up until you run:
or use the graphical interface to delete existing settings.
Edited by Rollin' Rog, 08 October 2007 - 02:54 AM.