You are viewing our Forum Archives. To view or take place in current topics click here.
How to fix your BSOD's!
Posted:

How to fix your BSOD's!Posted:

iThorHD
  • Ladder Climber
Status: Offline
Joined: Jun 20, 201112Year Member
Posts: 352
Reputation Power: 29
Status: Offline
Joined: Jun 20, 201112Year Member
Posts: 352
Reputation Power: 29
Today I'll be walking you through the process of fixing your BSOD's. This tutorial will be primarily concerned with software causing BSOD's, but it will include basic steps to solve hardware caused BSOD's.

Beginners:
Download [ Register or Signin to view external links. ] ( [ Register or Signin to view external links. ] ) ( [ Register or Signin to view external links. ] )
Install it and run it, then click the big analyze button, it'll give you a nice reading of what most likely caused your crash! However, it's not always 100%, but it does give a nice layout.

[ Register or Signin to view external links. ]

Advanced:
Part 1: BSOD's when you can get back into Windows

So if you can boot back into Windows you'll want to look here. First you'll need a bit of software called Debugging Tools for Windows, this will allow us to look at the dump files Windows makes. You can download it [ Register or Signin to view external links. ] ( [ Register or Signin to view external links. ] ).

Once you have that installed you'll want to go ahead and launch it. Go to File--> Open Crash Dump...

[ Register or Signin to view external links. ]

Next Navigate to C:\Windows\Minidump and open the most recent dump.

[ Register or Signin to view external links. ]

You'll be presented with a new screen with a lot of text. Scroll down all the way down to the bottom and you'll see a line that reads: Probably caused by:, followed by a filename. This is the problem file. You'll want to look into this file/program and see if there is a new updated version, or just uninstall it.

This isn't always 100% accurate, if the drivers are also a problem, this could take you in the wrong direction. So two suggestions, always keep your drivers updated, and even if it is your drivers, just Google what's causing the BSOD and there is a good chance someone else has already had the problem, and hopefully also already found a solution.

Part 2: BSOD's when you cannot get back into Windows

When you get a BSOD, there will be a STOP error that is this:
[ Register or Signin to view external links. ]

This means you need to see the blue screen and read the details from it. Unfortunately Windows will automatically reboot when a STOP error occurs. This way Windows can recover from the BSOD error.


  1. Go to Start menu and open the Control Panel.
  2. Go to System and Maintenance.
  3. Then, select System.
  4. Now click Advanced system settings in the task panel on the left-hand side.
  5. In the System Properties dialog box, under Startup and Recovery, click the Settings button.
  6. In the Startup and Recovery dialog box, clear the checkbox named Automatic restart under the System failure heading.
    [ Register or Signin to view external links. ]
  7. Click OK twice to close the dialog boxes and then close the Control Panel.


Now Windows won't longer restart when a STOP error happens, so you can see and analyze the STOP error being shown on the BSOD.

Here's a list of all stop errors:

Stop 0?00000003 UNSYNCHRONIZED_ACCESS
Stop 0x0000000A IRQL_NOT_LESS_OR_EQUAL
Stop 0x0000001E KMODE_EXCEPTION_NOT_HANDLED
Stop 0?00000023 FAT_FILE_SYSTEM
Stop 0?00000024 NTFS_FILE_SYSTEM
Stop 0x0000002E DATA_BUS_ERROR
Stop 0x0000003F NO_MORE_SYSTEM_PTES
Stop 0?00000044 MULTIPLE_IRP_COMPLETE_REQUESTS
Stop 0?00000050 PAGE_FAULT_IN_NONPAGED_AREA
Stop 0x0000006B PROCESS1_INITIALIZATION_FAILED
Stop 0?00000073 CONFIG_LIST_FAILED
Stop 0?00000074 BAD_SYSTEM_CONFIG_INFO
Stop 0?00000076 PROCESS_HAS_LOCKED_PAGES
Stop 0?00000077 KERNEL_STACK_INPAGE_ERROR
Stop 0?00000079 MISMATCHED_HAL
Stop 0x0000007A KERNEL_DATA_INPAGE_ERROR
Stop 0x0000007B INACCESSIBLE_BOOT_DEVICE
Stop 0x0000007E SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Stop 0x0000007F UNEXPECTED_KERNEL_MODE_TRAP
Stop 0x0000008E KERNEL_MODE_EXCEPTION_NOT_HANDLED
Stop 0x0000009C MACHINE_CHECK_EXCEPTION
Stop 0x0000009F DRIVER_POWER_STATE_FAILURE
Stop 0x000000BE ATTEMPTED_WRITE_TO_READONLY_MEMORY
Stop 0x000000C2 BAD_POOL_CALLER
Stop 0x000000C4 DRIVER_VERIFIER_DETECTED_VIOLATION
Stop 0x000000CA PNP_DETECTED_FATAL_ERROR
Stop 0x000000CB DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS
Stop 0x000000CE DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
Stop 0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL
Stop 0x000000D5 DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL
Stop 0x000000D8 DRIVER_USED_EXCESSIVE_PTES
Stop 0x000000DA SYSTEM_PTE_MISUSE
Stop 0x000000EA THREAD_STUCK_IN_DEVICE_DRIVER
Stop 0x000000ED UNMOUNTABLE_BOOT_VOLUME
Stop 0x000000F2 HARDWARE_INTERRUPT_STORM
Stop 0x000000FC ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
Stop 0x000000FE BUGCODE_USB_DRIVER
Stop 0xC0000218 UNKNOWN_HARD_ERROR
Stop 0xC000021A STATUS_SYSTEM_PROCESS_TERMINATED
Stop 0xC0000221 STATUS_IMAGE_CHECKSUM_MISMATCH
Stop 0xC0000244 STATUS_AUDIT_FAILED

Go ahead and google, the cause of the problem because of the STOP error, and hopefully you can then fix it. (For me it was once a SATA cord was kinked)

Part 3 : The OverClockers BSOD code list

BSOD codes for overclocking
0x101 = increase vcore
0x124 = increase/decrease vcore or QPI/VTT...have to test to see which one it is
0x0A = unstable RAM/IMC, increase QPI first, if that doesn't work increase vcore
0x1E = increase vcore
0x3B = increase vcore
0x3D = increase vcore
0xD1 = QPI/VTT, increase/decrease as necessary, can also be unstable Ram, raise Ram voltage
0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances
0x50 = RAM timings/Frequency or uncore multi unstable, increase RAM voltage or adjust QPI/VTT, or lower uncore if you're higher than 2x
0x109 = Not enough or too Much memory voltage
0x116 = Low IOH (NB) voltage, GPU issue (most common when running multi-GPU/overclocking GPU)
0x7E = Corrupted OS file, possibly from overclocking. Run sfc /scannow and chkdsk /r


I hope I helped, you and if you have any questions just ask.

The following 1 user thanked iThorHD for this useful post:

xxAmazing1 (04-19-2012)
#2. Posted:
Resolute
  • TTG Senior
Status: Offline
Joined: May 30, 201112Year Member
Posts: 1,947
Reputation Power: 82
Status: Offline
Joined: May 30, 201112Year Member
Posts: 1,947
Reputation Power: 82
I never experience a BSOD on my pc.
Is this a good thing?
How to prevent them in the near future?
#3. Posted:
System32
  • TTG Senior
Status: Offline
Joined: Nov 03, 201013Year Member
Posts: 1,553
Reputation Power: 60
Status: Offline
Joined: Nov 03, 201013Year Member
Posts: 1,553
Reputation Power: 60
Playstation wrote I never experience a BSOD on my pc.
Is this a good thing?
How to prevent them in the near future?


It is a very good thing and the best thing you can possibly do is never install anything lol. But considering that's pretty unrealistic, you need to keep in mind stuff like only installing trusted software and when you update something with a downloaded update ( just a newer version of the program's installer ) ALWAYS do a clean install.
#4. Posted:
QWOP
  • TTG Senior
Status: Offline
Joined: Feb 10, 201113Year Member
Posts: 1,738
Reputation Power: 80
Status: Offline
Joined: Feb 10, 201113Year Member
Posts: 1,738
Reputation Power: 80
You are sexy sexy sexy
Jump to:
You are viewing our Forum Archives. To view or take place in current topics click here.