Need help to analyze BSOD (dmp attached)

[pxL]

Hi,

Everything was working fine during 2 weeks or so, and now it's hell again.

Here are the new dump files if you guys can analyze them and tell me if you see what's wrong (and fixable). I've already call the After-sale service but if I can fix it manually that woud save me some time without any computer :/

Thanks a lot

 

[CarlTR6]

Hi,

Everything was working fine during 2 weeks or so, and now it's hell again.

Here are the new dump files if you guys can analyze them and tell me if you see what's wrong (and fixable). I've already call the After-sale service but if I can fix it manually that woud save me some time without any computer :/

Thanks a lot

I looked at the latest three dumps. All three indicate hardware problems. Since your computer is under warranty, I would let the techs sort it out.

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

Use !analyze -v to get detailed debugging information.

BugCheck 122, {a, 4, 0, 0}

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

Use !analyze -v to get detailed debugging information.

BugCheck 124, {4, fffffa8005d7e038, 0, 0}


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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff880057dc000, 1, fffff88010322762, 0}

 

[Jonathan_King]

See this article: http://www.sevenforums.com/crash-lockup-debug-how/35349-2-int-stop-0x124-what-means-what-try.html

Especially note over clocking and heat.