New
#11
That's so weird. I've uninstalled and reinstalled that thing so many times. I don't want to be a bother, but is there anything else I could try? I guess I'll try your instructions in the meantime, though.
That's so weird. I've uninstalled and reinstalled that thing so many times. I don't want to be a bother, but is there anything else I could try? I guess I'll try your instructions in the meantime, though.
I do note you have sptd.sys installed on the system:
- Please remove any CD/DVD virtualization software, such as Daemon Tools/Alcohol 120%, as they use a driver called sptd.sys that is known to cause BSODs. Use add/remove programs to remove the software. After removing the software, use the sptd.sys uninstaller to remove sptd.sys from the system.
I prefer TotalMounter as my CD/DVD virtualization software as it allows me to burn images to a virtual CD/DVD if I just want an ISO file instead of a disc, and it is free.
Many use MagicISO - Convert BIN to ISO, Create, Edit, Burn, Extract ISO file, ISO/BIN converter/extractor/editor as well, which is also free.
I don't think I have one. I had Daemon installed once, but it's no longer on here. Would Nero fall in that category? If not, I'll go right ahead and use that uninstaller.
You're correct. The software itself is no longer installed. The driver is still loaded, though, so the uninstall tool for sptd.sys would be a good idea.
Also, in regards to the network related crashes, you could also try uninstalling and re-installing Microsoft Security Essentials. Sometimes corrupted antivirus software can cause network adapter related crashes. I have seen it happen with pretty much all the big names: Norton, Kaspersky, Microsoft, etc. not because they are bad programs but because they are popular and corruption can occur with any software.
I didn't get to using the uninstaller yet, but I thought I should mention something. Even though I've updated Ralink, when I go into the properties of it in Device Manager - the date of the driver version hasn't changed. I thought that may help somehow. :) Perhaps it's not installing correctly?
Wireless network adapter drivers can be a pain to update. They do not always stick. That is why I recommended the steps I did. Instead of restarting after uninstalling the drivers and making sure to delete the driver software when given the option, do not restart your computer even if asked. I know my previous instructions said to restart if asked, but sometimes that prevents the new drivers from sticking.
So uninstall the drivers through Device Manager, delete the driver software when asked, and then install the latest drivers without restarting your computer in between. After installing the latest drivers, then you should restart your computer.
I was just about to finally do that, but I came to this computer to find it had had an 'a' BSOD. I'm not sure what that one means - it's a first. Should I get the files together again?
EDIT: I was uninstalling and reinstalling in safe mode (because the installer doesn't work right in regular mode) and it's like the driver in driver manager and the installer are seperate things, because I have to use the setup to uninstall, and in Device Manager I have to uninstall (They don't affect each other). Every time I uninstall in device manager, the next driver seems to be older than the other.
Last edited by shadedgrey63; 10 Jun 2012 at 18:28.
Strange. Check Windows for corruption. Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations. Use OPTION THREE of SFC /SCANNOW Command - System File Checker to provide us with the sfcdetails.txt file if errors occur.
The first run came back with no integrity violations. I don't know what to do.
A BugCheck A crash can indicate hardware problems. Hard to say without the .dmp, though. Can you upload the latest?