[BCCODE 124] Mouse freezes followed by a BSOD while browsing

Hi Sven24.

Your suspect may be absolutely right. Install the NVIDIA DRIVERS 314.22WHQL only.

• Uninstall All nvidia items in Control Panel > Programs and features
  
  • 3D Vision Control Driver
  • 3D Vision Driver
  • Graphics Driver
  • HD Audio Driver
  • PhysX
  • nvidia Update
  
  (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
• Now follow Drivers - Clean Left over Files after Uninstalling
• Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:
  
  

Let us know the results. If it BSODs again, Post it following the Blue Screen of Death (BSOD) Posting Instructions. A stray crash bump does not provide enough information.
_______________________________________________________________________________________

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80049508f8, 0, 0}

Probably caused by : AuthenticAMD

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80049508f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`031a86f0 fffff800`03124ca9 : fffffa80`049508d0 fffffa80`039fab50 00000000`0000000a 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`031a8c10 fffff800`03005ea7 : fffffa80`049508d0 fffff800`0307f2d8 fffffa80`039fab50 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`031a8c40 fffff800`02f6d275 : fffff800`030e0b40 00000000`00000001 fffffa80`04b40e70 fffffa80`039fab50 : nt!WheapProcessWorkQueueItem+0x57
fffff880`031a8c80 fffff800`02ee3261 : fffff880`011a2e00 fffff800`02f6d250 fffffa80`039fab00 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`031a8cb0 fffff800`031762ea : fffff8a0`126b7e38 fffffa80`039fab50 00000000`00000080 fffffa80`039e7040 : nt!ExpWorkerThread+0x111
fffff880`031a8d40 fffff800`02eca8e6 : fffff880`02f63180 fffffa80`039fab50 fffff880`02f6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031a8d80 00000000`00000000 : fffff880`031a9000 fffff880`031a3000 fffff880`02e92740 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

Followup: MachineOwner
---------

Well, I suggest it based on my personal experience. I have faced various issues with the display drivers other than 314.22 (and an earlier one, 306.23). And, a few of the driver versions later than 314.22 gave me such cursor issue, too.

So I stick with 314.22 and when people have issues with the later versions, suggest them to do it; as that particular version does not cause any disturb at all.