This problem has been going for a while (ever since I installed Windows 7 on this PC): Every once in a while (randomly, with any application), when I use the mouse to left-click & drag (move window, scroll down, etc.), my PC crashes with the following problem signature:
Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7601.2.1.0.256.1 Locale ID: 1033 Additional information about the problem: BCCode: 124 BCP1: 0000000000000000 BCP2: FFFFFA8007D3D028 BCP3: 00000000B2000040 BCP4: 0000000000000800 OS Version: 6_1_7601 Service Pack: 1_0 Product: 256_1 Files that help describe the problem: C:\Windows\Minidump\062412-16187-01.dmp C:\Users\andeve\AppData\Local\Temp\WER-1301015-0.sysdata.xml
I consulted this Generic "Stop 0x124" Troubleshooting Strategy but nothing helped.
Using BlueScreenView, this was the only information that's available about this BSOD:
Dump File Crash Time Bug Check String Bug Check Code Parameter 1 Parameter 2 Parameter 3 Parameter 4 062412-16187-01.dmp 6/24/2012 6:28:29 PM 0x00000124 00000000`00000000 fffffa80`07d3d028 00000000`b2000040 00000000`00000800
Caused By Driver Caused By Address File Description Processor Crash Address Processors Count Major Version Minor Version Dump File Size hal.dll hal.dll+12a3b x64 ntoskrnl.exe+7f1c0 4 15 7601 284,136
Filename Address In Stack From Address To Address Size Time Stamp Time String hal.dll hal.dll+12a3b fffff800`02c0d000 fffff800`02c56000 0x00049000 0x4ce7c669 11/20/2010 9:00:25 AM ntoskrnl.exe ntoskrnl.exe+18cb03 fffff800`02c56000 fffff800`0323e000 0x005e8000 0x4fa390f3 5/4/2012 4:18:59 AM
As you can see, having the problem reported in the core system (hal + ntoskrnl) is not helpful at all because it doesn't point to a specific driver (mouse? display?) that I can update (if there is one) but rather to the system which is 100% up-to-date.
So it seems that my only hope is to find someone who actually recognizes this problem as having a very specific solution.
Any idea how to fix this problem once and for all?
UPDATE, MONTHS LATER: The problem still persists and it starts to annoy me. So far, it looks like only @Chiyou is in the right direction, so I am posting snapshots from the hardware monitoring driver that I installed specifically for troubleshooting this problem (I don't overclock, nor do I normally need the information provided extra CPU cycles it eats). My system is built around ABIT IP35-PRO:
Which results in what seems to be safe temperatures:
And voltages as well:
Any idea what to tweak?