No, BlueScreenView is not yet as thorough as Windows Debug; but it is coming along. If we have the actually dumps, we can use a variety of commands to look deeper. I did review what you posted; but it does not have what I am looking for. Most of us on the BSOD team use WinDebug.
Ok ill try WinDebug now. Let me say this...on the BlueScreenView....along the top it says caused by driver: US30XP.sys. Then it said File Name of the that driver: Universial Shield. It says that on both of the dumps. So either way...thats what caused the BSOD then though right? I deleted the Universial Shield. But ill try to get the full dump on here anyway. But at least i know what did it now.
My Computer
At a glance
Windows 7 Ultimate 64 bitIntel Pentium E5300 (W) 2.6 GHz (65W)6GB
- Computer Manufacturer/Model Number
- HP Pavillion a6767c Desktop
- OS
- Windows 7 Ultimate 64 bit
- CPU
- Intel Pentium E5300 (W) 2.6 GHz (65W)
- Motherboard
- Asus
- Memory
- 6GB
- Monitor(s) Displays
- 20 Inch Acer Monitor
- Screen Resolution
- 1680 x 1050
- Hard Drives
- 640GB
- Keyboard
- Logitech S510 Wireless Keyboard & Mouse
- Mouse
- Logitech S510 Wireless Keyboard & Mouse
- Other Info
- Also have the HP G60-235DX Notebook which i use mostly everyday.