Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I have a BSOD/STOP 0x124 problem that keeps haunting me for a very very long time: It always happens at address hal.dll+12a3b.

In my searches for an explanation/solution, I found suggestions that this crash may be a result of either overclocking or bad RAM.

Since I don't overclock my system, bad RAM could have been a possibility but... my system never crashes when running Ubuntu (under much more demanding memory conditions: multiple VMWare VMs running simultaneously, including Windows 7 64-bit VMs).

So, other than a bug in Windows 7, I have no other explanation for the phenomenon but I am still curious:

What's there in that special hal.dll+12a3b address?

share|improve this question
1  
HAL - Hardware Abstraction Layer. Also look into bad or seriously out of date drivers. It's probably the main difference between the two OS's in this instance. –  Fiasco Labs May 27 '13 at 3:13
    
upload the dmp fiels so that we can look at them with Windbg. –  magicandre1981 May 27 '13 at 3:51
1  
Bug Check 0x124 is WHEA_UNCORRECTABLE_ERROR. Please post at least parameters of bugchecks you got (either recorded from bluescreens, or found in the System event log). MCi values can be analyzed, e.g., according to this guide. You can also check for a BIOS update (I have seen unexplainable MCEs on a server which had gone away after updating the BIOS). –  Sergey Vlasov May 27 '13 at 4:19
    
any news? have you uploaded the dumps? –  magicandre1981 Jun 2 '13 at 6:24

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.