I got BSOD repeatedly today. This is the first:
BugcheckCode 244
BugcheckParameter1 0x3
BugcheckParameter2 0xfffffa8018e63b10
BugcheckParameter3 0xfffffa8018e63df0
BugcheckParameter4 0xfffff800035e2b70
Zip file attached if someone knowledgeable could assist with deciphering.
Thank you.
Last edited by Gadgety; 09 Jan 2017 at 20:29. Reason: File removed because Windows 7 Pro mixes languages in the text, not all English. Fantastic software...
Hello Gadgety mate very hard to help until we get the BSOD dump files so can you please follow these
Dump Files - Configure Windows to Create on BSOD
&
Blue Screen of Death (BSOD) Posting Instructions
Thank you for your reply ICIT2LOL. I had it removed, as explained in the editing commentary, because the text file was a mix of English, and my native language. I tried to change the language and reload, but apparently this is non changeable with Windows7 Pro, which is what I'm using. In Windows7 Ultimate enables changing the lanuage. Amazing company, Microsoft. They wouldn't sell me the English version of Windows Pro, when I bought it. Who would have thought that dump files would be written in a mix of languages? I can repost, of course, if you could give it a shot.
Sorry late reply and I have to say I was wondering about the different languages as axe has stated the dumps are universal.
So just go ahead and follow those links without the results we cannot go ahead.
OK, thank you! Late replying = no worries, I'm later. NSW, different time zones. I will repost.
Last edited by Gadgety; 18 Jan 2017 at 02:47.
Okmate now looking the dumps again in the last one there is a reference to a bug check 124 which is almost certainly a hard ware problem.
So take a look at this - it is a reference from a Google search and is a part of a Microsoft articleCode:BugCheck 124
Generic "Stop 0x124" Troubleshooting Steps:
1) Ensure that none of the hardware components are overclocked. Overclocking means pushing the components beyond what they were designed for. If you do not know what that is you probably are not overclocking so go to the next step
2) Ensure that the machine is adequately cooled. If this is a laptop use compressed air to carefully blow out the heat pipe and fan when the computer is turned off. If a desktop take the side cover off and blow a fan on the components
3) Update all hardware-related drivers: video, sound, RAID (if any), etc. Do not rely on windows when it says the most recent driver is installed. It may be the most recent but it may also be corrupt.
4) Update the motherboard BIOS according to the manufacturer's instructions and clear the CMOS. Check with the computer maker for directions on this procedure and as usual it is always a good idea to back up your data.
5) Update ALL OS Windows updates
6)Stress test the major components. Start with RAM, CPU, HD, etc. (see other wikis for how to)
For RAM, use Memtest. Instructions for which can be found here.
Computers are extremely sensitive to problematic ram so any errors on memtest should be considered an issue and even a clear report for less than 8 passes can give a false negative.
For CPU use Prime95
For hard drives, use CHKDSK /F finds any problems on the drive(s), notably "bad sectors". You should also go to the HD maker and download and run their HD checking utility
7)-Perform a "vanilla" (clean) re-installation of Windows: Install nothing that is not from the OS (not even Malware) until you have seen that the computer is not crashing in this state.
When the vanilla installation has run long enough that you are convinced it is OK, start installing updates and applications a few at a time, and wait until you are again convinced it is OK. If the crashes resume it is obviously the last group of installations that is the issue and remove them.
8)- Re-seat all connectors, ram modules, etc. You can use the same can of compressed air to clean out the RAM DIMM sockets as much as possible.
Only attempt this if you are FULLY knowledgeable about the procedures.
9)- If all else fails, start removing items of hardware one-by-one in the hope that the culprit is something non-essential which can be removed.
Should you find yourself in the situation of having performed all of the steps above without a resolution of the symptom, unfortunately the most likely reason is because the error message is literally correct - something is fundamentally wrong with the machine's hardware.
For the moment I think we should ignore the BIOS stuff and concentrate on the hardware issues.
Now I think it might be as well to start with a memtest see this please and follow it exactly as put down.
MEMTEST
Now to make absolutely we are on the same page the memtest linked here is the*only*one we recommend and it MUST be run for at least 8 passes or you may as well not bother. It is rather lengthy and best left for a downtime for that machine - overnight is good. Having said that you can stop the test if errors show up while you are around and then it is a matter of tracking down the bad stick of RAM.* RAM - Test with Memtest86+
Great, thank you, ICIT2LOL. Good to know that it's most likely hardware related. I'll work through the list. The problem with this BSOD is it's been intermittent (I'm assuming it's the same culprit), and 30 days or so between occurrences until the last week. This makes Microsoft's recommendation to, for example, remove hardware items one-by-one impractical... it'll take forever. Stage 7, the Windows reinstallation, I guess is to ascertain whether this is hard/or software? Otherwise, if it is hard- and not software, how could a reinstall of Windows help? Memtest, should be done one stick at a time?
Ok mate now you don't need to go through every tiny bit of the hardware that you can disconnect and/or re-seat mainly it is stuff such as the GPU and cables to it the monitor cables will automatically disconnected if you take it right out (and then might be a good time to clear any crud from it)
The SATA drive cables should also be taken out inspected and reinserted any cables that look suspect - renew. That is at each end of them for example the drives and optical drive etc..
RAM sticks again check each thing for any signs of scorching, in some instances some folks will redo the thermal compound on the CPU. The 24 pin plug and any other cables supplying all spots on the board and finally any plug in cards I have missed an audio card if you have one.
Now doing this is important because the problem is intermittent and that smacks of a lose or dirty connection strips.
While you are going around the board it is well worth checking out the caps on the board for bulging or leakage in which case that cap will have to be replaced. Some of the caps may be hidden by larger components but do the best you can because just one cap being bad can cause the machine to malfunction.
Now wanting to make out you don't know what they look like but I have attached a pic or two of what they can look like. I meant mention above check the actual board for scorchig too if it has been hot at anytime there can be quite an acrid resinous smell.
The memtest mate is best done first with all sticks in and if errors do come up then of course it means a tedious rerun of the test with each stick. Now sometimes albeit not that often a slot on the board can be the issue but as I said not a common thing. I wrote up this little ditty and the wording is not aimed at you as I was answering someone else but kept it because I use the thing quite a bit
MEMTEST
Now to make absolutely we are on the same page the memtest linked here is the*only*one we recommend and it MUST be run for at least 8 passes or you may as well not bother. It is rather lengthy and best left for a downtime for that machine - overnight is good. Having said that you can stop the test if errors show up while you are around and then it is a matter of tracking down the bad stick of RAM.* RAM - Test with Memtest86+
There are a lot of instructions and info on what to do with errors in that link. However if you have problems please post back.
Quote