What's so special about `hal.dll+12a3b`?
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?
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?
No comments:
Post a Comment