Extrange automatic reboot... No BSOD, just reboot

zbook · 16 Sep 2017

The dump files if present are useful but the other collected logs provide a lot of information for troubleshooting.
You can post mini dump and memory dump and we can look at both.
Many times there are crash dump failures and these don't appear in the dumps and only appear in the other logs. The logs then give information about the frequency of the unreported crashes.

1) mini dump files: %SystemRoot%\Minidump or c:\windows\minidump

2) memory dump file: %SystemRoot%\MEMORY.DMP or C:\Windows\MEMORY.DMP

Use file explorer > this PC > local C: drive > right upper corner search enter each of the above to find results.

Post using one drive or drop box share links.

We may need the full zip depending on the results.

FerchogtX · 16 Sep 2017

Here we go, There wasn't a Memory.DMP file I'm afraid (probably because I only get a rebopot and not a BSOD per se...

I hope this helps.

By now, I replaced Avast with AVG Free, let's see if that finally fixes the issues (I cross fingers)

zbook · 16 Sep 2017

Both of the new BSOD mini dump files dated 9/16/2017 when debugged displayed WHEA 0x124 which is highly indicative of a hardware problem.

When you are able to make the default language English additional hardware testing can be performed to troubleshoot the recurrent BSOD.

The drive was already tested.
These are the remaining hardware components to evaluate or stress test:
CPU
GPU
RAM / DIMM /Motherboard
PSU

Language - Add, Remove, and Change in Windows 10 Windows 10 General Tips Tutorials
BSOD - Posting Instructions - Windows 10 Forums

1) Please update the system specs: 'My Computer" with information about the PSU and anything attached to the computer by wireless or wired (printer, headset, xbox, etc.)

How To Fill Out Your System Specs
How To Fill Out Your System Specs
System Specs - Fill in at Ten Forums:
System Specs - Fill in at Ten Forums Windows 10 General Tips Tutorials
In the left corner below in your post you find 'My System Specs'.
After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
System Info - See Your System Specs - Windows 7 Help Forums

2) In the bios view the 3.5v, 5v, and 12v data. Using a camera or smart phone camera take pictures of the displayed results and post images into the thread.

Code:

BugCheck 124, {0, ffffa687bc7568f8, 0, 0}Probably caused by : AuthenticAMDFollowup: MachineOwner---------0: kd> !analyze -v********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************WHEA_UNCORRECTABLE_ERROR (124)A fatal hardware error has occurred. Parameter 1 identifies the type of errorsource that reported the error. Parameter 2 holds the address of theWHEA_ERROR_RECORD structure that describes the error conditon.Arguments:Arg1: 0000000000000000, Machine Check ExceptionArg2: ffffa687bc7568f8, 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.

Code:

0: kd> !errrec ffffa687bc7568f8===============================================================================Common Platform Error Record @ ffffa687bc7568f8-------------------------------------------------------------------------------Record Id     : 01d32a918fa337e6Severity      : Fatal (1)Length        : 928Creator       : MicrosoftNotify Type   : Machine Check ExceptionTimestamp     : 9/11/2017 0:04:42 (UTC)Flags         : 0x00000002 PreviousError===============================================================================Section 0     : Processor Generic-------------------------------------------------------------------------------Descriptor    @ ffffa687bc756978Section       @ ffffa687bc756a50Offset        : 344Length        : 192Flags         : 0x00000001 PrimarySeverity      : FatalProc. Type    : x86/x64Instr. Set    : x64Error Type    : BUS errorOperation     : GenericFlags         : 0x00Level         : 3CPU Version   : 0x0000000000660f51Processor ID  : 0x0000000000000000===============================================================================Section 1     : x86/x64 Processor Specific-------------------------------------------------------------------------------Descriptor    @ ffffa687bc7569c0Section       @ ffffa687bc756b10Offset        : 536Length        : 128Flags         : 0x00000000Severity      : FatalLocal APIC Id : 0x0000000000000000CPU Id        : 51 0f 66 00 00 08 04 00 - 0b 32 d8 7e 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 00Proc. Info 0  @ ffffa687bc756b10===============================================================================Section 2     : x86/x64 MCA-------------------------------------------------------------------------------Descriptor    @ ffffa687bc756a08Section       @ ffffa687bc756b90Offset        : 664Length        : 264Flags         : 0x00000000Severity      : FatalError         : BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4)  Status      : 0xfe00000000070f0f  Address     : 0x00000000f0d08700  Misc.       : 0xd00a0fff01000000

FerchogtX · 20 Sep 2017

Sorry for being late.

I'm going to run Memtest as soon as I can. Meanwhile, Bios has nothing about the voltages, probably an screenshot from AIDA64 might help, if you want it, I can post. About the PSU, I dunno if this apples to a laptop, but the charger is a 45 watt one, I always work with the AC line (Unless I need to move or do anything with the battery).

By the other hand, the only things attached to the laptop are my Wacom tablet, an acteck wireless mouse with USB dongle, my laptop cooler and nothing else...

Hope this helps

zbook · 20 Sep 2017

Okay. For a laptop you will test CPU, GPU, RAM/DIMM/MB

Once the Memtest86+ version 5.01 has completed at least 8 passes please use a camera or smart phone camera to take a picture and post an image into the thread.
The more the passes the better.

Microsoft Community

MemTest86+ - Test RAM Windows 10 BSOD Tutorials

For CPU and GPU please read these links and let us know when you may be ready to start testing.
Prime95 - Stress Test Your CPU Windows 10 Performance Maintenance Tutorials
FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials
Download and install one of the temperature monitoring software applications such as HWinfo or Speecy or speedfan..
HWiNFO - Download
Speccy - System Information - Free Download
SpeedFan - Access temperature sensor in your computer

FerchogtX · 23 Sep 2017

Well... as I bought a new HDD, I tried my luck and went for a clean install, I will see how this works, if anything, I will post back, and update the info package, since I installed windows in english to avoid problems with cortana and other localized stuff.

Will it be correct if I open another thread later if I face a problem or I leave this one and necro bump in case of need?

Thank you so much for all your help, and sorry XD

FerchogtX · 29 Sep 2017

Weird question, I just came up with this... can a faulty BIOS (poorly programmed) cause this WHEA reboots with a particular software?

I will run memetest this night, as I have some time for it, I'll post results tomorrow, hopefully.

Another question... seems memtest doesn't test the whole memory by default, I need to configure it, right?

Cya!

FerchogtX · 30 Sep 2017

Good news, I ran memtest since very early today, took a while, but seems it worthed it, no errors so far, also I'm attaching a new zip with updated info of my system, if that helps, includes the dump from this 28th of september.

I pass from the prime95 test, as I did that a while ago while testing temps of the PC, and the thing is still alive XD.

I'm really beggining to suspect that Firefox is the only culprit here... I even ran Super Mario Sunshine on emulator for hours and the thing don't crash at all, and the game is quite intensive for being a simple mario game... (I have a gamecube, so no harm done here)

I tend to stream sometimes using GPU codecs, no crashes. I tend to run even Windows 7 and 8.1 at the same time in my hardware, no crashes...

This really leaves me with just Firefox... (I even changed my AV solution to AVG... or even went with Defender alone)

Probably the new servo engine will finally stop this weird crashes on certain systems...

Unless there is something else to see... XD

Thanks a bunch

https://i.imgur.com/IAquUgN.jpg

Added a link because the file was too big XD

zbook · 30 Sep 2017

The Memtest86+ displays 15GB RAM.
Msinfo32 displays 16GB RAM.
What accounts for that discrepancy?

Perform windows updates.
Post any failed KB# with error code.
In the left lower corner search type winver.
Post the current windows version and build into the thread.

Open device manager > click view > show hidden devices > post an image into the thread.
Take Screenshot in Windows 10 Windows 10 General Tips Tutorials

Run FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials

Please make note of the importance of temperature monitoring and aborting the test in the GPU link.

FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials:
FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials

Make sure that the bios has been reset and that there is no over clocking.

Please record maximum temperatures and duration of testing.

Aim for 45 minutes testing duration using FurMark.

And please make sure that you use the Microsoft snipping tool to post images of each into the thread.

Take Screenshot in Windows 10 Windows 10 General Tips Tutorials

Code:

9/29/2017 2:52 AM    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 124
P2: 0
P3: ffffa807f627d8f8
P4: 0
P5: 0
P6: 10_0_15063
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\092817-22734-01.dmp
\\?\C:\Windows\Temp\WER-24562-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER33BE.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER33BF.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER33FE.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_124_4dc02ec4676d1ae564b11f4544387dd9b965fa69_00000000_cab_217d4a91

Analysis symbol: 
Rechecking for solution: 0
Report Id: a861a8ad-a1d3-4302-a4d0-ae641525d075
Report Status: 2049
Hashed bucket:9/29/2017 2:52 AM    Windows Error Reporting    Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 124
P2: 0
P3: ffffa807f627d8f8
P4: 0
P5: 0
P6: 10_0_15063
P7: 0_0
P8: 768_1
P9: 
P10: 

Attached files:
\\?\C:\Windows\Minidump\092817-22734-01.dmp
\\?\C:\Windows\Temp\WER-24562-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER33BE.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER33BF.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER33FE.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_124_4dc02ec4676d1ae564b11f4544387dd9b965fa69_00000000_036933fb

Analysis symbol: 
Rechecking for solution: 0
Report Id: a861a8ad-a1d3-4302-a4d0-ae641525d075
Report Status: 4
Hashed bucket:

Code:

9/30/2017 5:43 AM    Application Error    Faulting application name: Project64.exe, version: 2.3.1.9999, time stamp: 0x57da99f5
Faulting module name: XAudio2_7.dll_unloaded, version: 9.29.1962.0, time stamp: 0x4c0641e5
Exception code: 0xc0000005
Fault offset: 0x0003a5e0
Faulting process id: 0x870
Faulting application start time: 0x01d339ac4b226f83
Faulting application path: D:\Programs\Emuladores\Systems\Project64 2.3\Project64.exe
Faulting module path: XAudio2_7.dll
Report Id: 92f5ea51-d8fc-4a59-b433-10ec346afd16
Faulting package full name: 
Faulting package-relative application ID:9/29/2017 3:27 AM    Application Error    Faulting application name: Project64.exe, version: 2.3.1.9999, time stamp: 0x57da99f5
Faulting module name: XAudio2_7.dll_unloaded, version: 9.29.1962.0, time stamp: 0x4c0641e5
Exception code: 0xc0000005
Fault offset: 0x0003a5e0
Faulting process id: 0x1a64
Faulting application start time: 0x01d338d02a4d1157
Faulting application path: D:\Programs\Emuladores\Systems\Project64 2.3\Project64.exe
Faulting module path: XAudio2_7.dll
Report Id: e82feb1c-57f7-43f6-b5d3-58aa90394934
Faulting package full name: 
Faulting package-relative application ID:
9/28/2017 11:51 PM    Application Error    Faulting application name: Project64.exe, version: 2.3.1.9999, time stamp: 0x57da99f5
Faulting module name: XAudio2_7.dll_unloaded, version: 9.29.1962.0, time stamp: 0x4c0641e5
Exception code: 0xc0000005
Fault offset: 0x0003a5e0
Faulting process id: 0x2190
Faulting application start time: 0x01d338b244eb5b81
Faulting application path: D:\Programs\Emuladores\Systems\Project64 2.3\Project64.exe
Faulting module path: XAudio2_7.dll
Report Id: f6e4772f-9ad9-4fe4-b232-16ed9bf1ea44
Faulting package full name: 
Faulting package-relative application ID:
10/1/2017 3:03 AM    Windows Error Reporting    Fault bucket , type 0
Event Name: PnPDriverNotFound
Response: Not available
Cab Id: 0

Problem signature:
P1: x64
P2: BTHENUM\{00001801-0000-1000-8000-00805f9b34fb}_VID&0001001d_PID&1200
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3A19.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_x64_a814057e235f3daacf372613f4edb76e22df38_00000000_04103c5b

Analysis symbol: 
Rechecking for solution: 0
Report Id: 112d5402-aebd-4249-8d73-0bd1b74fb9ae
Report Status: 2147491840
Hashed bucket:
10/1/2017 3:03 AM    Windows Error Reporting    Fault bucket , type 0
Event Name: PnPDriverNotFound
Response: Not available
Cab Id: 0

Problem signature:
P1: x64
P2: BTHENUM\{00001132-0000-1000-8000-00805f9b34fb}_VID&0001001d_PID&1200
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_x64_a2d15b623cb9221c6ab0f74c56cccb7655be5e0_00000000_1a543a29

Analysis symbol: 
Rechecking for solution: 0
Report Id: 5c22db80-f6ec-4625-8355-ae8bf0ae796d
Report Status: 4
Hashed bucket:
10/1/2017 3:03 AM    Windows Error Reporting    Fault bucket , type 0
Event Name: PnPDriverNotFound
Response: Not available
Cab Id: 0

Problem signature:
P1: x64
P2: BTHENUM\{00001801-0000-1000-8000-00805f9b34fb}_VID&0001001d_PID&1200
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_x64_a814057e235f3daacf372613f4edb76e22df38_00000000_14183825

Analysis symbol: 
Rechecking for solution: 0
Report Id: 112d5402-aebd-4249-8d73-0bd1b74fb9ae
Report Status: 4
Hashed bucket:
10/1/2017 3:03 AM    Windows Error Reporting    Fault bucket , type 0
Event Name: PnPDriverNotFound
Response: Not available
Cab Id: 0

Problem signature:
P1: x64
P2: BTHENUM\{00001800-0000-1000-8000-00805f9b34fb}_VID&0001001d_PID&1200
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER27F9.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_x64_2ae29069b68e22aa84fc5b14314983f3fc3df6d0_00000000_21a033d0

Analysis symbol: 
Rechecking for solution: 0
Report Id: b09bb573-777a-4409-9f3e-ca215a9c5a7a
Report Status: 2147491840
Hashed bucket:
10/1/2017 3:02 AM    Windows Error Reporting    Fault bucket , type 0
Event Name: PnPDriverNotFound
Response: Not available
Cab Id: 0

Problem signature:
P1: x64
P2: BTHENUM\{00001800-0000-1000-8000-00805f9b34fb}_VID&0001001d_PID&1200
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_x64_2ae29069b68e22aa84fc5b14314983f3fc3df6d0_00000000_1418226b

Analysis symbol: 
Rechecking for solution: 0
Report Id: b09bb573-777a-4409-9f3e-ca215a9c5a7a
Report Status: 4
Hashed bucket:

FerchogtX · 01 Oct 2017

Oh... the discrepancy probably accounts for the reserved 555 MB the system has for the GPU, I believe Memtest rounds down to 15 GB... during the test, I could see that it could actually reach to the 16GB range when the testing part showed numbers like 14G - 16G. Windows can see the 16 GB, as well as the BIOS...

My current Windows 10 build is this one: 15063.632 I have all updates installed, none have failed, and well, as you can see, all my devices are installed and working properly, the 99% of them come from windows update, the Wi-Fi, VGA and Sound are updated manually (specially the VGA, so I can use the latest stable version for my GPU and gain some speed improvements XD).

I'll try to run the fumark test as soon as possible, ah... no overclock on this system, it's a laptop, and the BIOS doesn't let me do that (nor I'm interested

) Thanks

Attachment 155930