Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Help with BSOD


  • Please log in to reply
6 replies to this topic

#1 mikerod4792

mikerod4792

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:01:48 AM

Posted 21 February 2018 - 11:29 AM

Hey all, 

 

I tried to download the application for the zip file, but my anti-virus software says that it is potentially malicious and removes it before I can finish installing it. My symptoms are that my rig BSOD's randomly mostly when I am gaming but it has happened once while I was writing a paper. They did not start after an update.

From the research I have done on the BUS_OBS_ERR_*_NOTIMEOUR_ERR error, the majority say that it is a hardware problem, as evidenced by the WHEA error, specifically either the board, GPU or CPU. However, I ran MEMTEST for 3 hours on the RAM with no issues. I also ran prime95 on the processor for 2 hours and 15 minutes with no warnings and no issues and I can Furmark GPU stress test for 2 hours with no issues either. I also monitored my temps on the CPU and GPU before the crash and they were all within normal range. Does this indicate a bad board? I just want to be sure before I go out and buy a bunch of parts and still have this issue. Thanks for any help or insight!

 

 

 

Here is a snapshot of my rig from Speccy:

http://speccy.piriform.com/results/mV2H8ZxRunAAPyXgStgcPka

 

So here is a copy and pasted form of the Windbg page:

 

Microsoft ® Windows Debugger Version 6.3.9600.17336 AMD64
Copyright © Microsoft Corporation. All rights reserved.
 
 
Loading Dump File [C:\Windows\Minidump\022118-33843-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
 
 
************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 8 Kernel Version 16299 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff802`38e88000 PsLoadedModuleList = 0xfffff802`391ef110
Debug session time: Wed Feb 21 11:04:34.571 2018 (UTC - 5:00)
System Uptime: 0 days 0:00:08.277
Loading Kernel Symbols
...............................................................
..
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
 
Use !analyze -v to get detailed debugging information.
 
BugCheck 124, {0, ffff808f654ab038, 0, 0}
 
Probably caused by : AuthenticAMD
 
Followup: MachineOwner
---------
 
5: 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: ffff808f654ab038, 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:  WIN8_DRIVER_FAULT
 
PROCESS_NAME:  System
 
CURRENT_IRQL:  0
 
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
 
STACK_TEXT:  
ffffa58d`476d65b0 fffff802`392beb15 : ffff808f`62961040 ffff808f`654ab010 ffff808f`62844330 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x7b
ffffa58d`476d6ae0 fffff802`3910d9e8 : ffff808f`654ab010 00000000`00001000 fffff805`00000000 ffff808f`62870180 : nt!WheapCreateTriageDumpFromPreviousSession+0x2d
ffffa58d`476d6b10 fffff802`3910e50b : fffff802`391dfee0 fffff802`391dfee0 ffff808f`62844330 fffff805`e80771e0 : nt!WheapProcessWorkQueueItem+0x48
ffffa58d`476d6b50 fffff802`38ec34d5 : ffff808f`62844330 ffff808f`62961040 fffff805`00000000 ffff808f`00001000 : nt!WheapWorkQueueWorkerRoutine+0x2b
ffffa58d`476d6b80 fffff802`38f9eb87 : ffff808f`62961040 00000000`00000080 ffff808f`6284b440 ffff808f`62961040 : nt!ExpWorkerThread+0xf5
ffffa58d`476d6c10 fffff802`39004be6 : ffffa901`a2020180 ffff808f`62961040 fffff802`38f9eb40 00000000`00000000 : nt!PspSystemThreadStartup+0x47
ffffa58d`476d6c60 00000000`00000000 : ffffa58d`476d7000 ffffa58d`476d1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
 
 
STACK_COMMAND:  kb
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: AuthenticAMD
 
IMAGE_NAME:  AuthenticAMD
 
DEBUG_FLR_IMAGE_TIMESTAMP:  0
 
IMAGE_VERSION:  
 
FAILURE_BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_BUS_PRV
 
BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_BUS_PRV
 
ANALYSIS_SOURCE:  KM
 
FAILURE_ID_HASH_STRING:  km:0x124_authenticamd_processor_bus_prv
 
FAILURE_ID_HASH:  {6fd7875b-9a1b-9e09-d6d6-816026a875c8}
 
Followup: MachineOwner
---------
 
5: kd> !errrec ffff808f654ab038
===============================================================================
Common Platform Error Record @ ffff808f654ab038
-------------------------------------------------------------------------------
Record Id     : 01d3ab2da5d1c593
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 2/21/2018 16:04:34 (UTC)
Flags         : 0x00000002 PreviousError
 
===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ ffff808f654ab0b8
Section       @ ffff808f654ab190
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   : 0x0000000000600f20
Processor ID  : 0x0000000000000000
 
===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ ffff808f654ab100
Section       @ ffff808f654ab250
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal
 
Local APIC Id : 0x0000000000000000
CPU Id        : 20 0f 60 00 00 08 06 00 - 0b 32 98 3e 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  @ ffff808f654ab250
 
===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ ffff808f654ab148
Section       @ ffff808f654ab2d0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal
 
Error         : BUSLG_OBS_ERR_*_NOTIMEOUT_ERR (Proc 0 Bank 4)
  Status      : 0xf2000010000b0c0f

Attached Files


Edited by mikerod4792, 21 February 2018 - 11:40 AM.


BC AdBot (Login to Remove)

 


#2 iancatalan

iancatalan

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:02:48 PM

Posted 21 February 2018 - 11:40 AM

did you check your event viewer? and check what could be the error why you get BSoD randomly.



#3 mikerod4792

mikerod4792
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:01:48 AM

Posted 21 February 2018 - 11:46 AM

Yes and it came back with event ID 20 WHEA Logger for AMD Northbridge Error Source: Machine Check Exception Error Type:11 Processor APIC ID:0  

Along with this:

  ErrorSource 3     ApicId 0     MCABank 4     MciStat 0xf2000010000b0c0f     MciAddr 0x0     MciMisc 0x0     ErrorType 11     Length 928

#4 mikerod4792

mikerod4792
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:01:48 AM

Posted 21 February 2018 - 11:50 AM

It also has something logged for an application error Event ID 1000, The WHEA error came first however. 

  WsAppService.exe       2.2.4.1       5784a857       KERNELBASE.dll       6.2.16299.248       4414ec23       e053534f       0000000000014008


Edited by mikerod4792, 21 February 2018 - 11:52 AM.


#5 mikerod4792

mikerod4792
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:01:48 AM

Posted 21 February 2018 - 12:11 PM

UPDATE: Apparently the AMD Northbridge error is common with AMD processors and can be fixed by disabling the fast boot up option in the power settings. I just changed that and restarted my PC so maybe that will fix my issues 



#6 iancatalan

iancatalan

  • Members
  • 13 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:02:48 PM

Posted 21 February 2018 - 12:16 PM

It also has something logged for an application error Event ID 1000, The WHEA error came first however. 

  WsAppService.exe       2.2.4.1       5784a857       KERNELBASE.dll       6.2.16299.248       4414ec23       e053534f       0000000000014008

I think this is your problem that cause you BSoD.

Check this article maybe it will help you

https://www.file.net/process/wsappservice.exe.html



#7 mikerod4792

mikerod4792
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:01:48 AM

Posted 21 February 2018 - 12:28 PM

Ok I check it out and it did look suspicious so I isolated it. Lets see if that stops the BSoD's






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users