Multiple accounts of display error. BCCode: 124

[adrenalinerush1]

I've been having these issues with the display of my Dell studio 15 laptop since the last couple of months. The display just goes blank or displays random lines and eventually restarts.

At times the system manages to recover and gives and error "Display Driver Stopped functioning and recovered". I've tried updating my driver and even reinstalling it, but the problem persists.

Graphic Card: ATI Mobility Radeon HD 5400

I'm copy pasting the error code I received and am also attaching the .dmp file mentioned in the error.

Any help will be greatly appreciated. Please let me know if I need to attach any other file.

Thanks,

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 16393

Additional information about the problem:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA8004E478F8
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\012914-18111-01.dmp
C:\Users\XX\AppData\Local\Temp\WER-46628-0.sysdata.xml

 

[Arc]

Hi adrenalinerush1.

Its hard to debug a stop 0x124 BSOD based on a stray crash dump, but suggesting you some steps.

Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings.

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: http://www.sevenforums.com/tutorials/311593-speccy-publish-snapshot-your-system-specs.html .

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

But, the essence of the issue is, apparently, this part of your post:

At times the system manages to recover and gives and error "Display Driver Stopped functioning and recovered". I've tried updating my driver and even reinstalling it, but the problem persists.

Something like this?

If so, and if altering the driver version dis not stop it, it sounds bad. This is so random in nature that Furmark may not catch it. So the temperature records as per Speccy will be vital here, to determine the next step.

So let us know the results.
___________________________________________________________________________________________

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

Use !analyze -v to get detailed debugging information.

BugCheck [COLOR="Red"]124[/COLOR], {[COLOR="Red"]0[/COLOR], fffffa8004e478f8, 0, 0}

Probably caused by : GenuineIntel

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