Another BSOD at start-up:
An attempt was made to write to read only memory.
STOP 0X000000BE
USbuhci.sys -
Then:
The system has recovered from a serious error
Microsoft Windows Error Reporting
Troubleshoot a problem with a device driver
You received this message because a device driver installed on your computer caused Windows to stop unexpectedly. This type of error is referred to as a "stop error." A stop error requires you to restart your computer.
Steps to address this problem
Use Windows Update to check for updated drivers
(Already done - no essential updates necessary)Steps to work around this problem
Warning
These steps are designed to address a particular problem but might do so by temporarily disabling or removing some functionality on your computer.
If this problem occurred after you installed a new hardware device on your computer, the problem might be caused by the device driver. Go online to learn how to use the Dell Driver Reset Tool or uninstall the driver.
How do I disable or uninstall a device driver?
Click Start, and then click Control Panel. If you are using Classic View, click Switch to Category View.
Click Performance and Maintenance, and then click System.
Click the Hardware tab, and then click Device Manager.
Click the plus sign (+) next to the faulting device. You should now see the device listed.
Right-click the device, and then click Disable or Uninstall.
If this problem occurred after you installed new software, the software might have installed a driver that caused the problem. Try uninstalling the software. Could GMER Rootkit Scanner have installed a driver? Although we did use the 'Clean' tool. How do I uninstall a program?
If you don't know the specific driver or software, go online to learn more about performing a System Restore.
For information about your support options, go online to the Support.Dell.Com website.
I have emailed Dell Sales because attempts to contact Technical Support failed due to my service code not being found. I only want to ask about the test which is free for all though....it's not warranty related.
Will keep trying with Microsoft NET Framework 3.5 Service Pack 1
There's an email address for GMER Rootkit Scanner - maybe they'll have an idea of what might have sparked this issue off during the scan? Maybe the computer was already on the edge and it tipped it over?
You're supposed to be here for malware removal only....and I'm becoming a wreck.
