BleepingComputer.com: Bluescreen Information

Hello,

I am using a Sony Vaio laptop with Windows XP. I have had a couple of bluescreens in the last week and want to check, if possible, what the cause might be. I have looked in the eventviewer but cannot seem to see any error messages around the time that they occurred.

Would someone be able to let me know how I can see this information and if it is possible from the message to get an idea of what may have caused these, such as a device like a specific USB dongle or other item. When the screen flashed briefly I think it mentioned something about 'caught in loop'.

I have scanned with AVG with no malware found.

Thanks for any help or feedback,
James

Download BlueScreenView:
http://www.nirsoft.net/utils/blue_screen_view.html
unzip downloaded file and double click on BlueScreenView.exe to run the program.
when scanning is done, go to EDIT - Select All
Go to FILE - SAVE Selected Items, and save the report as BSOD.txt
Open BSOD.txt in Notepad, copy all of the content, and paste it into your next reply

Additionally you could prevent that Blue Screen from flashing by so quickly by Right Clicking 'My Computer' select Properties, select the Advanced Tab & click on Settings under 'Startup and Recovery.' Uncheck the box for Automatically Restart under 'System Failure.'

Yes, we're aware of that thank you. I'm trying to get a history of the bsod's.

Perhaps I should have stated it, "In addition to installing BlueScreenView & posting its results, as recommended by Allan,....etc."

My post was only meant to inform James1000 of the setting which would allow him to Lock the BlueScreen in place. Not meant as an 'either do this or that' type option.

He certainly should post the history results of BlueScreenView regardless.

Apologies for any possible misunderstanding or the appearance of 'Taking Over.'

James1000 is in highly capable hands. Best wishes to you Allan.

SAW101

No problem at all - it's just the bluescreen view will provide all the info needed. However, I always disable "restart on error" so I agree with you