BSOD HELP! Please!

[Beban96]

Past 3-4 months i get repeatedly BSOD.With one tool i saw that was problem with 3 drivers.Nvidia gforce driver,audio driver, and Nvidia nforce networking controller was problem.I installed just two of them.I get BSOD again and again.I think that third driver problem doesn't make BSOD,but in Bluescreen View,i always see NT Kernel System problem.What is it Kernel,and how to fix it,or i need to download third driver that occur my computer?

here is .zip dumpfiles
Windows_NT6_BSOD_jcgriff2.zip

 

[FredeGail]

Hello Beban96 & Welcome to SevenForums!

:ar: BSOD Summary

*******************************************************************************
*                                                                             *
*                        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: 00000000, Machine Check Exception
Arg2: 85cab4dc, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000000, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
8af2bcc4 82b21105 85cab4c0 82bb9c48 82bb9c40 nt!WheapCreateTriageDumpFromPreviousSession+0x32
8af2bce4 82b21f2f 82bb9c40 85cab4c0 82bb9c70 nt!WheapProcessWorkQueueItem+0x56
8af2bd00 82ac008b 82bb9c40 00000000 84ad7a70 nt!WheapWorkQueueWorkerRoutine+0x1f
8af2bd50 82c60a55 00000001 aa0d17ce 00000000 nt!ExpWorkerThread+0x10d
8af2bd90 82b12239 82abff7e 00000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_BUS_PRV

Followup: MachineOwner

Your latest crash caused your hardware. It's likely that it's your memory sticks. Please follow the tutorial below to get the perfect test. The test will be running in DOS. We usually recommend to run the test for 7, 8 passes. Anyway, more information in the link.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Best Regards,
FredeGail

 

[Beban96]

thank you!

Well,thanks i will look link,and if i have some questions,i will post them.

 

[FredeGail]

Well,thanks i will look link,and if i have some questions,i will post them.

Defiantly

Best Regards,
FredeGail

 

[Beban96]

Ok.I done everything and there were no errors or something like that.Does that means that my computer will not giv me BSOD or what.Thanks.

 

[FredeGail]

Ok.I done everything and there were no errors or something like that.Does that means that my computer will not giv me BSOD or what.Thanks.

No, defiantly not. Upload any new incoming .dmp - Maybe they'll give us more details. Otherwise we can do more hardware analyses. But for now, if you have some new .dmp, upload them.

Best Regards,
FredeGail

 

[Beban96]

Ok.I had 2 BSOD's while posting main thread,and 1 BSOD after Memtest86.

Here are 3 dump files:
.zip.zip

 

[zigzag3143]

Ok.I had 2 BSOD's while posting main thread,and 1 BSOD after Memtest86.

Here are 3 dump files:
.zip.zip

Your .dmp file shows a stop error of 0x124 which is a general hardware error .

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.

Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.

You can read more on this error and what to try here... Stop 0x124 - what it means and what to try http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html