Additional menu

4 BSOD Errors That Can Kill Your PC and their Solutions

4 BSOD Errors That Can Kill Your PC and their Solutions

Blue Screen of Death (BSOD) error can reduce the lifespan of your PC if proper action is not taken.

The screen turns blue, and you get some message with an error code.

BSOD can be caused by both software and hardware. If the root cause is the first one, you just have to apply some tweaks. Otherwise, you may need to reformat the system.

Those are less freaky.

One standard way to solve BSOD error in Windows 10 is explained here.

But what if RAM, Hard Disk, CPU, Power Unit, Motherboard, South Bridge are the cause for these BSOD errors.

In this post, we are going to see such errors which may kill your PC and how to take necessary action.

1. INVALID_DATA_ACCESS_TRAP (Error Code 0x00000004)

This is one of the several BSOD errors we have. It can occur in the latest Windows 10 to XP.

This can happen when you install new hardware or driver. The INVALID_DATA_ACCESS_TRAP appears during program installation. This can be a conflict between various things.

For example, your app is installing; a driver is being loaded, Windows is starting up or shut down simultaneously. There are many causes for the INVALID_DATA_ACCESS_TRAP error.

Some of them are corrupted device drivers, corruption in Windows registry, driver conflict, Error 0x4 caused by a broken hard disk, RAM corruption, etc.

Solution

The following troubleshooting steps can be tried to get out of this error code INVALID_DATA_ACCESS_TRAP.

  1. You can use software like CCleaner and delete registry entries to remove the Error 0x00000004. This will then remove this error.
  2. Use prominent anti-virus like BitDefender, McAfee, and anti-malware like Malwarebytes to remove any infection on your computer.
  3. Update all your PC drivers including the system drivers like.Net package etc.
  4. Uninstall any new software and reinstall it and update the drivers for it, if necessary.
  5. Check hardware corruption using the command chkdsk /f or any other interface tool.

  1. Remove the RAM from the slot and clean the golden edges with a dry clean cloth and reinsert it and see.

2. NTFS_FILE_SYSTEM (Error Code 0x00000024)

This BSOD error can cause the system to crash suddenly after a stop error. It becomes difficult to even to note down the error code. The main reason is that it is a bug check value error code problem.

It indicates a possible disk file-system corruption and most likely caused by failing sectors of your hard-disk. This is related to the NTFS file system. To further not kill your PC, the automatic mechanism shutdowns your computer.

The problem occurs in the NTFS.SYS file. This is a driver file that allows the PC to read and write from the NTFS file system. Even if you have FAT32 or FAT16 systems, you can get a read error.

Solution

  1. You can use Windows Defender and Security Essentials to recheck your PC for virus/malware and clean them.
  2. Check hard disk corruption using the command CHKDSK /F command mentioned earlier, answering the prompt messages.
  3. Check for outdated drivers using any Driver Updater tool. These tools check all the drivers on your PC and automatically update them to the latest ones.
  4. Run a disk defragmentation tool available inside Windows. You can also try repairing individual slots on your Hard Disk using the software.

3. NMI_HARDWARE_FAILURE (Error Code 0x00000080)

This type of error code can crop up while playing a game and system suddenly crashes.

You can send the dump files to an MVP expert or post in Microsoft forums.

The main two reasons for this kind of error are –

  1. Driver error
  2. Memory error

So first you need to check whether all your drivers are updated if you were using the latest version of Windows 10. If that doesn’t work out, you can try the generic drivers given by Windows 10 itself.

Generally, by now manufacturers would have provided the latest drivers. But if it’s an old PC, you may have trouble finding it. Then you can Google for the particular driver file and see if it fits in.

If that doesn’t work out, you need to do a Memory test. This like checking whether your hard disk or RAM are working properly are not.

You can use this free link to test it –

http://www.mersenne.org/freesoft/

  1. You can use “Just stress testing” option.
  2. Then use the “Blend” test.
  3. The number of torture test threads should be equal to the number of CPU cores.
  4. Run the test for 6 to 24 hours or until you get errors.

Then you get a log of what hardware is killing your PC.

4. DATA_BUS_ERROR (Error Code 0x0000002E)

This BSOD error code gives a little more of information in the form of 4 parameters. These parameters mean –

Parameter 1 – The hexadecimal value of the virtual address that causes the error.

Parameter 2 – The value of the physical address that causes the error.

Parameter 3 – The PSR (processor status register which says whether your CPU is okay or not)

Parameter 4 – Finally the error in the registry

In general cases, the error could be due to –

  • corrupted hardware
  • Compatibility problem of hardware devices and OS.
  • faulty configuration

The main causes could be –

  • BAD RAM
  • L2, L3, etc. kind memory cache errors
  • flash drive, SSD, USB card kind of errors.

Also, if a fault occurs in the driver code, it tries to access the not available range of memory.

Solution

  1. First, remove the newly installed hardware devices and restart. See if that removes it. Then you need to avoid that hardware or repair it.
  2. Also, make sure RAM, etc. fit correctly in the connectors. Check the loose cables etc.
  3. If it’s a new PC, then install the latest version of BIOS and updates for the SCSI controller.
  4. Also, check for faulty hard-drive.

Conclusion

As I said before, there are many BSOD error codes which show the cause of blue screen. But we have discussed those who are more likely to cause death to your PC and how to resolve them.

If you find a different cause or solution for the above BSOD errors, please comment.

Reader Interactions

Guest Author
About Guest Author
This post is submitted by Guest Author. Would you like to contribute to Geek Flare? Send your article here.

Comments

  1. BSOD Errors are difficult to decipher. I had a BSOD error during installation and the cause was really difficult to find out. It’s always better to create a restore point from time to time and also use the repair option from the installation disc, if it helps. The error code also helps in finding a solution. Thanks for an informative post.

Leave a Reply

Your email address will not be published. Required fields are marked *