Sign in with
Sign up | Sign in
Your question

Win7_Driver_Fault Need help fixing BSOD

Tags:
  • Blue Screen
  • Components
  • Computers
Last response: in Components
Share
September 9, 2014 12:04:33 PM

I am sorry if this is in the wrong part of the forums but I recently have been recently getting the BSOD while I use my computer. I have recently changed my graphics card and PSU. I would be very thankful If you can help solve my problem as I am a bit of a noob at computers. I will be posting the Windows Debugging of the minidump I get.

Computer Specs:

AM3+ FX-4100 X4 Retail
Samsung 1TB Sata2 32MB Spinpoint F3 HD103SJ
ASUS M5A78L-M USB3 DDR3 760 AM3+ SATA II
Ballistix Sport 8GB x 4
Windows Ultimate 64bit
Corsair CP-9020062-UK RM Series RM1000 80 Plus Gold 1000W ATX/EPS Fully Modular Power Supply Unit
XFX Radeon R9 290 DD Edition Graphics Card (4GB, GDDR5)

  1. Microsoft (R) Windows Debugger Version 6.3.9600.17237 AMD64
  2. Copyright (c) Microsoft Corporation. All rights reserved.
  3.  
  4.  
  5. Loading Dump File [C:\Windows\Minidump\090914-66706-01.dmp]
  6. Mini Kernel Dump File: Only registers and stack trace are available
  7.  
  8.  
  9. ************* Symbol Path validation summary **************
  10. Response Time (ms) Location
  11. Deferred SRV*c:\debug_symbols*http://msdl.microsoft.com/download/symbols
  12. Symbol search path is: SRV*c:\debug_symbols*http://msdl.microsoft.com/download/symbols
  13. Executable search path is:
  14. Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
  15. Product: WinNt, suite: TerminalServer SingleUserTS
  16. Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
  17. Machine Name:
  18. Kernel base = 0xfffff800`02e61000 PsLoadedModuleList = 0xfffff800`030a4890
  19. Debug session time: Tue Sep 9 16:58:35.841 2014 (UTC + 1:00)
  20. System Uptime: 0 days 0:00:12.902
  21. Loading Kernel Symbols
  22. .
  23.  
  24. Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
  25. Run !sym noisy before .reload to track down problems loading symbols.
  26.  
  27. ...................................................
  28. Loading User Symbols
  29. Mini Kernel Dump does not contain unloaded driver list
  30. *******************************************************************************
  31. * *
  32. * Bugcheck Analysis *
  33. * *
  34. *******************************************************************************
  35.  
  36. Use !analyze -v to get detailed debugging information.
  37.  
  38. BugCheck 124, {0, fffffa801a7eb038, 0, 0}
  39.  
  40. Probably caused by : AuthenticAMD
  41.  
  42. Followup: MachineOwner
  43. ---------
  44.  
  45. 2: kd> !analyze -v
  46. *******************************************************************************
  47. * *
  48. * Bugcheck Analysis *
  49. * *
  50. *******************************************************************************
  51.  
  52. WHEA_UNCORRECTABLE_ERROR (124)
  53. A fatal hardware error has occurred. Parameter 1 identifies the type of error
  54. source that reported the error. Parameter 2 holds the address of the
  55. WHEA_ERROR_RECORD structure that describes the error conditon.
  56. Arguments:
  57. Arg1: 0000000000000000, Machine Check Exception
  58. Arg2: fffffa801a7eb038, Address of the WHEA_ERROR_RECORD structure.
  59. Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
  60. Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
  61.  
  62. Debugging Details:
  63. ------------------
  64.  
  65.  
  66. BUGCHECK_STR: 0x124_AuthenticAMD
  67.  
  68. CUSTOMER_CRASH_COUNT: 1
  69.  
  70. DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
  71.  
  72. PROCESS_NAME: System
  73.  
  74. CURRENT_IRQL: 0
  75.  
  76. ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
  77.  
  78. STACK_TEXT:
  79. fffff880`031b65b0 fffff800`03121cb9 : fffffa80`1a7eb010 fffffa80`18da4b50 00000000`00000007 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
  80. fffff880`031b6ad0 fffff800`03002ea7 : fffffa80`1a7eb010 fffff800`0307c2d8 fffffa80`18da4b50 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
  81. fffff880`031b6b00 fffff800`02f6a275 : fffff800`030ddd00 00000000`00000001 fffffa80`1a05a840 fffffa80`18da4b50 : nt!WheapProcessWorkQueueItem+0x57
  82. fffff880`031b6b40 fffff800`02ee0261 : fffff880`01128e00 fffff800`02f6a250 fffffa80`18da4b00 0e070d0f`070e1008 : nt!WheapWorkQueueWorkerRoutine+0x25
  83. fffff880`031b6b70 fffff800`0317273a : 00000000`00000000 fffffa80`18da4b50 00000000`00000080 fffffa80`18c489e0 : nt!ExpWorkerThread+0x111
  84. fffff880`031b6c00 fffff800`02ec78e6 : fffff880`02fd7180 fffffa80`18da4b50 fffff880`02fe1fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
  85. fffff880`031b6c40 00000000`00000000 : fffff880`031b7000 fffff880`031b1000 fffff880`037e9730 00000000`00000000 : nt!KxStartSystemThread+0x16
  86.  
  87.  
  88. STACK_COMMAND: kb
  89.  
  90. FOLLOWUP_NAME: MachineOwner
  91.  
  92. MODULE_NAME: AuthenticAMD
  93.  
  94. IMAGE_NAME: AuthenticAMD
  95.  
  96. DEBUG_FLR_IMAGE_TIMESTAMP: 0
  97.  
  98. IMAGE_VERSION:
  99.  
  100. FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
  101.  
  102. BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
  103.  
  104. ANALYSIS_SOURCE: KM
  105.  
  106. FAILURE_ID_HASH_STRING: km:x64_0x124_authenticamd_processor_bus_prv
  107.  
  108. FAILURE_ID_HASH: {78c2f422-5335-4ef3-5cef-a28518da5023}
  109.  
  110. Followup: MachineOwner
  111. ---------

More about : win7 driver fault fixing bsod

September 9, 2014 12:05:44 PM

I am sorry for the long post but I dont know how to use the forums way of shortening things
m
0
l
Related resources
September 12, 2014 9:24:30 AM

Sorry for taking a long time to respond I couldn't access the internet. In reply to price I don't oc and when I uninstall my AMD drivers it works fine how ever I cant play any games. When i do install my drivers again it crashes with same error.
m
0
l
September 12, 2014 11:57:03 AM

authenticAMD.sys is a windows driver that uploads microcode changes for various bugs in AMD CPUs.

Best places to get the changes are to update your BIOS if your vendor keeps it up to date.

your bugcheck was from the CPU and you can use the command
!errrec fffffa801a7eb038
in the windows debugger to see what the CPU is complaining about.

I would treat this as a standard overclocking failure and check voltages, clocks, and cooling (make sure fans are working)
reset BIOS to defaults or update the BIOS to get better defaults.
Some BIOS versions will automatically overclock so make sure that is turned off.
You can use the command
!sysinfo smbios
to dump the machine info and clock rates that were active at the time of the bugcheck.

m
0
l
September 12, 2014 12:10:40 PM

Common Platform Error Record @ fffffa801a7eb038
-------------------------------------------------------------------------------
Signature : *** INVALID ***
Revision : 0.0
Record Id : 0000000000000000
Severity : Recoverable (0)
Length : 0
Creator : {0047bd58-0000-0000-38dc-f90200000000}
Notify Type : {0047bd58-0000-0000-38dc-f90200000000}
Flags : 0x00000000

2: kd> !errrec fffffa801a19b7b8
===============================================================================
Common Platform Error Record @ fffffa801a19b7b8
-------------------------------------------------------------------------------
Record Id : 01cfc607a97d17a6
Severity : Fatal (1)
Length : 928
Creator : Microsoft
Notify Type : Machine Check Exception
Timestamp : 9/1/2014 17:10:53 (UTC)
Flags : 0x00000002 PreviousError

===============================================================================
Section 0 : Processor Generic
-------------------------------------------------------------------------------
Descriptor @ fffffa801a19b838
Section @ fffffa801a19b910
Offset : 344
Length : 192
Flags : 0x00000001 Primary
Severity : Fatal

Proc. Type : x86/x64
Instr. Set : x64
Error Type : BUS error
Operation : Generic
Flags : 0x00
Level : 3
CPU Version : 0x0000000000600f12
Processor ID : 0x0000000000000000

===============================================================================
Section 1 : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor @ fffffa801a19b880
Section @ fffffa801a19b9d0
Offset : 536
Length : 128
Flags : 0x00000000
Severity : Fatal

Local APIC Id : 0x0000000000000000
CPU Id : 12 0f 60 00 00 08 04 00 - 0b 22 98 1e ff fb 8b 17
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0 @ fffffa801a19b9d0

===============================================================================
Section 2 : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ fffffa801a19b8c8
Section @ fffffa801a19ba50
Offset : 664
Length : 264
Flags : 0x00000000
Severity : Fatal

Error : BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4)
Status : 0xfe00000000070f0f
Address : 0x0000000782fe3a10
Misc. : 0xc00a0fff01000000

I am not very good with this stuff so could you please tell me what this means and also when I try the !sysinfo smbios it comes up with:

2: kd> !sysinfo smbios
sysinfo: could not find necessary interfaces.
sysinfo: note that mssmbios.sys must be loaded (XPSP2+).
m
0
l
September 12, 2014 12:47:09 PM

basically the CPU core 0 tried to access some cache memory inside the CPU and did not get a response from the internal cache memory controller so the CPU called a bugcheck.

the second command failing is also common with bugcheck because the CPU indicated a failure and you are lucky to get the partial memory dump.

So, what you really need to do is update your BIOS or reset your BIOS to defaults and make sure your CPU is not overheating. Then run some CPU tests to confirm the CPU works as expected.

you can also get this failure with power fluctuations to the CPU. The voltage may be low enough to cause cache failures but not low enough to cause the CPU to reset and go back to BIOS. This is very common when you update a graphics card and don't connect the supplemental power connections to the power supply. (or connect only one power connection rather than both, or connect them to only one lead of a power supply and you have a multi rail power supply)




m
0
l
September 13, 2014 2:47:31 AM

johnbl said:
basically the CPU core 0 tried to access some cache memory inside the CPU and did not get a response from the internal cache memory controller so the CPU called a bugcheck.

the second command failing is also common with bugcheck because the CPU indicated a failure and you are lucky to get the partial memory dump.

So, what you really need to do is update your BIOS or reset your BIOS to defaults and make sure your CPU is not overheating. Then run some CPU tests to confirm the CPU works as expected.

you can also get this failure with power fluctuations to the CPU. The voltage may be low enough to cause cache failures but not low enough to cause the CPU to reset and go back to BIOS. This is very common when you update a graphics card and don't connect the supplemental power connections to the power supply. (or connect only one power connection rather than both, or connect them to only one lead of a power supply and you have a multi rail power supply)






So I updated my BIOS but after installing the drivers it crashed while watching YouTube. I then tried plugging my graphics card into another socket and yet again it crashed I don't think it is over heating because after it crashed the first time is opened up my computer and felt the CPU and it was not that hot. If needed I can post pics here of what the inside of my PC looks like.
m
0
l
September 13, 2014 3:06:12 AM

I also have to say when I go onto the BIOS setup and under jumper free configuration in advanced settings CPU over clocking is set t auto and there are 3 more options called : Manual, Overclock Profile and Test Mode. There is also PCI over clocking set to auto and can be changed to manual could you please tell me what to do with these
m
0
l
September 13, 2014 8:34:58 AM

set the pci bus to 100 MHz, the newer graphics cards tend to fail if the bugs. In particular, factory overclocked graphics cards fail. on some systems auto will set the PCI bus to 103MHz. Just to get 3% potential advantage in benchmarks.

for your CPU I would set it to manual and put it at the rated clock speed for my CPU.

Simon8198 said:
I also have to say when I go onto the BIOS setup and under jumper free configuration in advanced settings CPU over clocking is set t auto and there are 3 more options called : Manual, Overclock Profile and Test Mode. There is also PCI over clocking set to auto and can be changed to manual could you please tell me what to do with these


m
0
l
September 14, 2014 11:00:01 AM

Can you please tell me what the rated clock speed for my CPU is because when I set over clocking to 200 mhz it still crashed in also set PCIe overclocking to 100
m
0
l
September 15, 2014 8:16:23 AM

I think you cpu AM3+ FX-4100 X4
is rated to run at 3.6 GHz

the 100Mhz is the clock speed for standard PCI cards inserted into a slot on you motherboard not the CPU speed.

Simon8198 said:
Can you please tell me what the rated clock speed for my CPU is because when I set over clocking to 200 mhz it still crashed in also set PCIe overclocking to 100


m
0
l
September 15, 2014 11:36:01 AM

I tried the suggestion you gave me but it still crashed but on starting it up again there was no error log. However there was a mini crash dump file still.
m
0
l
September 15, 2014 1:30:27 PM

does your system pass a memtest86 run?
m
0
l
September 16, 2014 1:40:23 PM

johnbl said:
does your system pass a memtest86 run?


It passes with no errors
m
0
l
September 20, 2014 1:22:34 AM

Please Help
m
0
l
September 20, 2014 7:39:05 AM

with this error all you can do is confirm your hardware is working with various tests.
memtest86 (done)
prime95 to check the CPU for errors and overheating

-on a older system you can blow out any dust, and check for overheating or fans that are not spinning.
check for power supply problems, power starting to fail.
-make sure your BIOS is as up to date or reset it to defaults with no overclocking, no overvoltages to memory or the CPU.

if all else fails you might try underclocking your system to get it stable.


m
0
l
September 28, 2014 7:46:50 AM

I have tries doing a Prime 95 check but the computer crashes after a few hours I dont know when because i normally had my screen turned off or was not near by and when I check the results all it says are the things that passed. iI have also set my BIOS to default and underclocked it but it will still crash and when it does it will say overclocking failed.
m
0
l
September 28, 2014 8:15:44 AM

if you get a message that says overclocking failed, it means your BIOS is set to automatically overclock. go into your BIOS and disable any memory overclocking or CPU overclocking. If you are running a overclocking utility. Disable it
m
0
l
!