0X00000050 BSODS, have tried the usual fixes, games are now unstable.

MSINFO32:

Please upload your msinfo32.txt file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Export -> Save as msinfo32.txt and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .txt file, click send to compressed (zipped) folder -> Upload the .zip file here.

Driver Issues:

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.

Many use MagicISO - Convert BIN to ISO, Create, Edit, Burn, Extract ISO file, ISO/BIN converter/extractor/editor as well, which is free.

Analysis:

All crashes were due to your TP-LINK Wireless USB Adapter. USB wireless network adapters are inherently unstable. USB ports do not provide adequate power for such devices to operate reliably. Please replace yours with a PCI wireless network adapter that is compatible with Windows 7.

@writhziden

Thanks for your advice.

I've removed Daemon tools. And run thesptd.sys uninstaller.

I haven't removed the TP-LINK Wireless USB Adapter yet as I need it to reply to you. I have a couple of questions:

1. Would plugging the adapter into a usb 2.0 help at all (more power)?

2. I have opened up my case And it looks like it would be really tight to reach a PCI slot due to the heat fins and fan on my card. Is this a common problem and is it likely that most PCI adapters would fit?

I've attached the report as requested.

Thank you for your help so far,

Adrian

I would not put a PCI card in if it has the potential to block the display card fan or increase heat for the card.

The problem is likely your Netgear Neutral Wireless Solution driver that is out of date. Do you have a Netgear device or have had one in the past?

The driver may be part of the driver set that came with the TP-LINK device. If so, updating its drivers may help or finding a USB device that is up to date may help. If you do decide to go with another USB device, keep in mind that it is not guaranteed to be stable, but an up to date device will have better results than an older one.

@writhziden

Hi there,

I have now replaced the USB adapter with an internal PCI card. (I checked that it would not interfere with the fans.)

I am still experiencing BSODs however, but now with a different code, 0X00000024. I wonder if I have caused another issueby installing the new hardware?

Incidentally I have removed the old drivers for my previous devices, including hidden ones. Could you please take a look for me? I've included the usual files.

Thank you,

Adrian

You really need to install your Windows Updates... I see none installed past Service Pack 1.


Your crashes primarily indicate hard disk problems. This could mean hard disk corruption, bad sectors, a failing hard disk, Windows files or registry corruption, viruses, or memory problems.

• If you are overclocking any hardware, please stop.
  
  
• Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log (you may need to search for wininit instead of chkdsk).
  For any drives that do not give the message:
  
  Windows has checked the file system and found no problems
  run disk check again as above. In other words, if it says:
  
  Windows has made corrections to the file system
  after running the disk check, run the disk check again.
  
  
• Run all Basic tests with SeaTools: S.M.A.R.T. Check, Short Drive Self Test, Drive Information, Short Generic, and Long Generic. Run the tests for all HDDs.
  SeaTools for Windows
  
  SeaTools for DOS
  
  
• If you have an SSD, make sure the following are up to date:
  • SSD firmware
  • BIOS Version
  • Chipset Drivers
  • Hard disk controller drivers/SATA drivers
  • If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.
  
  
  
• 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.
  
  
• Download and install Malwarebytes, update it, do not start the free trial, and then run a full scan. Also run a full scan with your antivirus software installed on your system. If you do not have antivirus software installed, see the Good and Free system security combination. for better security steps and scanning tools. Make sure to update the security software before running the full scan.
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
     Warning

  Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. WARNING: The steps that follow can void your warranty!!!
  
  For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
  
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
  
  Once these steps have been followed, it is safe to remove and replace components within your computer.

Hi there,

apologies for break in response, have been crazy busy. I am still experiencing random BSOD. Which is probably down to the following which I hope you can help with.

I am having problems installing Windows updates: My recent history shows several failed attempts and manual attempts have brought error messages like: Code 8007065E and Code 9C48. I have been successful with some Microsoft updates however.

I have run DiscCheck, SeaTools, MalWareBytes etc, showing nothing.

I have run SFC/SCANNOW from the command and it does say there are corruptions it hasn't fixed. However I cannot find the report, it said windir\Logs\CBS\CBS.log

I wonder if this and not being able to update are the problem?

Additional, I have found the report file and have attached.

I would really appreciate any help you could give with this please.

Any takers?