Just for my own knowledge; what is the key to figuring out what a bsod is pointing to? I mean how does one determine what the cause of a bsod is. I am trying to learn more about this so i can try and help more in this section more. Thanks.
Well it varies completely on the type of bugcheck and where to look.
In your case you were having 0x124 errors, you don't really need to look a them at all, just stress test components.
The two main causes of BSODs are drivers and failing hardware.
Sometimes you have to take the more generic troubleshooting approach when analysing BSODs as they don't always give you a clear cause.
For example,
I could be analsying a 0xD1 bugcheck which is DRIVER_IRQL_NOT_LESS_OR_EQUAL this indicates a driver tried to access paged out memory at an IRQL above Dispatch.
What this means is that to access pageable memory the IRQL must be at dispatch or below.
The IRQLs vary from system to system, it depends whether it's 32bit or 64bit.
On 64bit architecture there are 16 IRQLs.
An IRQL is an interrupt that diverts to CPUs operation for more important reasons.
When the IRQL is too high and a driver tries to access pageable memory the system cannot respond because the IRQL is above dispatch, it becomes a vicious circle if you like.
The system can't lower the IRQL until it's completed it's request but a driver has created a page fault so that needs it's attention first but you can't lower the IRQL until the request is completed.
Hence a bugcheck is initated.
Now that's a lot different from a 0x124 error as that mostly involves the CPU finding a fault with the system and bug checking.
Back to what I was saying, sometimes windows can't find the driver responsible so it points to other windows code like ntoskrnl.exe which is the kernel implemented in a .exe module.
Now obviously that's not the cause so you'd have to dig deeper for a root cause.
Looking at the thread stack is one of the best ways.
If that finds nothing then the raw stack should find the driver responsible, if you still can't find anything then driver verifier should find the culprit, in this case (0xD1) the best option is Forxe IRQL checking which will bugcheck when the system finds the driver.
With this option when the driver is in a spin lock or raises the IRQL to dispatch or higher verifier monitors it and if it access memory it should the system bugchecks with that driver behind bars.
So that method would be completely different to a different bugcheck.
Most of use Windbg which you can download with the Windows Debugging Tools part of the Windows Software development kit.
Sorry for all the text I just like to go on a lot when asked to explain things.
Take a deep breath and slow down a bit.
The CPU may not require replacing - first you need to:
1. Check that the CPU cooler is clean & working properly
2. Check and reapply the thermal paste medium
3. Reset any overclocks back to the default settings in the BIOS
4. Rerun IBT
There is no substitute for using MemTest86+....all other memory testers are inferior. Go buy a USB thumbdrive, install MemTest86+, boot from the USB and run a minimum of 8 passes.
Always reply to suggestions in a clear & concise manner. A reply like "the tests failed" is useless to us. Which tests? At what point did it fail? The devil is in the detail.
Well golden; the thing is i havent done any overclocking that i can recall. As for the cooling; all my fans are working fine. for the thermal paste; i have not done any changes to the thermal paste. What is on there now is what its been using all along; so with that in mind; i would think if there was a overheating issue; it would have come up a long long time ago; and it hasnt. I also just recently cleaned out all the dust etc. from my case. So Im sorta inclined to believe it is the cpu at this point unless some other experts want to chime in on this one. And oh yes; as for buying a thumbdrive; that is out as i can not afford any other new computer hardware right now. I am on a extremely extremely tight budget; and therefore just cannot justify spending anymore on this system right now. As for running; memtest; that is out as i do not have discs to burn it to and right now I need what little funds i have left for other things.
Change the thermal paste anyway....you have nothing to lose. Anyway, if you decide to change the CPU yiu will need to do it anyway. Thermal paste can degrade over time, or maybe you knocked the CPU whilst cleaning...
Test RAM before you change CPU....thumbdrives cost a few dollars....you only need a cheap small one. Run MemTest from the thumbdrive...forget discs! You dont need DVD's....get a cheap $2 thumbdrive.
Well; i did already test the ram using the built in windows tester and it showed no errors; but what else can i test it with other than memtest just to be sure; as i just want to get it done doing it a easier way like running a file from the system instead. As for knocking the cpu while cleaning; that is highly unlikely as I just used a electric powered air pump to blow out all the dust; so i highly doubt its that.
Plus from what TheDoctor was mentioning above; the bug check looked to him like the cpu was faulty due to the fact that i couldnt even run any stress tests without getting bsod's. Also; by thumbdrive you mean a flash drive?
Last edited by matts6887; 23 May 2014 at 11:47.
With respect, I don't think you are ready for tackling BSOD's.
You have been around long enough to have noticed that MemTest86+ is the only reliable RAM testing software - nothing else comes close. Let me make it very clear : there is nothing else you can use to give a reliable test result.
Google USB thumb drive...see what you come up with.
Read my previous reply about thermal paste.
If you aren't willing to try anything, mark this thread solved and purchase a new CPU if you so choose.
I honestly suggest listening to Golden as he knows what he's talking about.
A USB flash drive and thermal paste isn't a lot of money, in fact it could save you money in the long run by not replacing the CPU.
There's nothing else I can suggest apart form what's already been said, the rest is up to you.
Well. I believe my brother has some thermal paste I can steal from him when the time comes. As for the cpu; after much persuasion and discussions with the personnel at intel; they finally agreed to send me a replacement without charging me. Hopefully; this will solve the bug check 0x124 bsod's Ive been getting suddenly. As for the thermal paste etc. Well yes that will get new paste once i put the new processor in and put the heatsink in place.
Quote