Windows 10: Strange automatic reboot... No BSOD, just reboot

Hi there!

Well... after thinking I had my reboot problems fixed, today I had this issue... I was just browsing using Firefox, and suddently, the mouse lagged, just before the system rebooted unexpectedly. This happened before... but strangely, just happens when I'm using Firefox... and not all the time... it's more like random... I can be safe during months, and then, BAM this happens, and only using Firefox.

Looking at the event viewer, I get a WHEA-Logger Error 20, Component AMD Northbridge, Exception in machine check, Error in watchdog in Hyper Transport with procesor ID 0.

The other is a Bugchek 1001 error, which I guess, is just product of the reboot itself.

I attach my file, according to the instructions, to see what is wrong. I have the latest Chipset drivers from AMD, as well as teh WHQL 17.4.4 VGA drivers installed. My Laptop specs below. BIOS version 1.13 Insyde, all defaults, nothing changed

This just seems to happen with Firefox... Photoshop, Clip Studio and even using OBS Studio don't trigger this, and haven't done ever...

Any ideas?

Thanks in advance for your help, guys *Biggrin

:)

 

Bsod problem

Bsod problem
Since I turn on my pc and just for Internet , YouTube , that's was no problem , after I start to play steam's games , almost 20-30 mins it's will automatic get a bsod , ok reboot for me and then the funny thing is after the bsod I continue to play my games
but won't get any bsod problem again at that day , until tomorrow I do the same things , on pc , YouTube then play games in steam , poop ! Bsod again ! Reboot and no problem no bsod again ... Everyday I need to reboot once . This really annoying !

 

Windows 10 constant BSOD/GSOD and reboots. Unable to boot from CD. Error in "Page fault in nonpaged area" in volsnap.sys.

Walked into my home office this morning and found my Windows 10 pc rebooting. No problem, it's set to automatically install updates and reboot. But then it BSODs. It automatically reboots, then GSODs (Green Screen of Death). The PC cycles between BSOD, reboot,
GSOD, reboot. The error on each SOD is "Page fault in nonpaged area" in volsnap.sys.

I tried to boot from my recovery disk, from a new Win10 DVD, and from a USB with no success. I receive a SOD before it can boot from any media.

What can I do now?

 

Hi FershogtX,

There was a bsod today:


Code: BugCheck 124, {0, ffffe787b93d88f8, 0, 0}Probably caused by : AuthenticAMD[/quote] The logs are in a foreign language. If you can change the default language to English and resubmit the logs we would be able to review the logs and provide more troubleshooting.

Open administrative command prompt and type or copy and paste:


1) winver (in the pop up about windows > view your windows version and build > type this information into the thread)


2) sfc /scannow


3) dism /online /cleanup-image /restorehealth


4) chkdsk /scan


When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on copy > paste into the thread


Open the Acer web site to find drivers by entering your computer's serial or product number and the operating system.

Use device manager and control panel to uninstall AMD drivers/applications.

Reinstall new or up to date drivers from the ACER web site.

 

Crap... this windows is single language only, and for worse... spanish... is there a way I can translate the logs for you?

About my version of Windows, it's 14393.1198 (AU Build 1607)

About the Acer drivers, I have tried them before keeping this combo (months ago), and with this latest drivers I have less problems than the ones they have on the site... not to mention the default drivers Windows came with... those were the worst (They just freezed windows without rebooting)

I'll run the tests you mention and post the results as soon as possible.

Thanks a bunch!

 

The logs we cannot read as they are very long. We use search to be able to find problems within the logs. If you can create logs in English then we would be able to use the logs for troubleshooting.

 

Results of the commands I executed in admin mode cmd:

Code: Microsoft Windows [Versión 10.0.14393] (c) 2016 Microsoft Corporation. Todos los derechos reservados. C:\WINDOWS\system32>sfc /scannow Iniciando examen en el sistema. Este proceso tardará algún tiempo. Iniciando la fase de comprobación del examen del sistema. Se completó la comprobación de 100%. Protección de recursos de Windows no encontró ninguna infracción de integridad. C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth Deployment Image Servicing and Management tool Version: 10.0.14393.0 Image Version: 10.0.14393.0 [==========================100.0%==========================] The restore operation completed successfully. The operation completed successfully. C:\WINDOWS\system32>chkdsk /scan El tipo del sistema de archivos es NTFS. La etiqueta de volumen es Acer. Etapa 1: Examen de la estructura básica del sistema de archivos... 389120 registros de archivos procesados. :52 Comprobación de archivos completada. 43537 registros de archivos grandes procesados. a: 0:05:37 .. 0 registros de archivos no válidos procesados. :37 ... Etapa 2: Examen de la vinculación de nombres de archivos... 459300 entradas de índice procesadas. 0:03:53 ... Comprobación de índices completada. 0 archivos no indizados examinados. :53 . 0 archivos no indizados recuperados en objetos perdidos. :53 .. Etapa 3: Examen de los descriptores de seguridad... Comprobación de descriptores de seguridad completada. 35091 archivos de datos procesados. 3:50 ... CHKDSK está comprobando el diario USN... 36810976 bytes de USN procesados. :00 ... Se ha completado la comprobación del diario USN. Se examinó el sistema de archivos sin encontrar problemas. No se requieren más acciones. 193577983 KB de espacio total en disco. 31932936 KB en 152015 archivos. 103888 KB en 35092 índices. 0 KB en sectores defectuosos. 522511 KB en uso por el sistema. El archivo de registro ha ocupado 65536 kilobytes. 161018648 KB disponibles en disco. 4096 bytes en cada unidad de asignación. 48394495 unidades de asignación en disco en total. 40254662 unidades de asignación disponibles en disco. C:\WINDOWS\system32>[/quote] Traducing this, sfc didnt find any integrity violations, dism didn't show any warnings or errors and completed successfully, and the chkdsk command ran without any problem, no defective sectors or problems in my file system... everything is just running fine... aparently.

Funny thing is that, I have done this before, I like to keep the health of my systems and updated... and more funny, I even use Edge or Chrome, and none of them causes this crashes, just Firefox... even the Photos App, which caused this with the default windows drivers stopped doing it, and intensitive applications like Photoshop just don0t trigger anything, I can work heavy files without crashes...

I assume Firefox is my problem in here, since anything else causes this problems...

But I leave the experts helping me... I hope I can get to the deeps of this problem XD

Thanks in advance *Biggrin

EDIT: I will look for a way to change display language in this windows... I'm sure I can do this without making a clean install...

 

I'm sorry... you are trying to be helpful, but this thing about language tricks me...

I tried to look for some tutorial about changing the language, but the only one I found seems too risky... I know I sound too idiotic but... what strings you need to search for? I can tell you the translation in spanish so you can see what is it and look for it.

I'm so sorry for this inconvenience... I woudl just reinstall Windows 10 full languages supported, but this would hurt what we are doing...

 

Thanks for the effort. Translating the search terms would not work either as there will a load of results that need to be quickly scanned and they will all be in a foreign language. So at this juncture there was a bsod that was related to AMD. If you can replace that driver with an updated one that may be the solution. We will just have to do without the logs unless you find the windows option to reboot with English and then create the logs.

 

Good news, I managed to install the english lang pack... but way too buggy (scrambled text and stuffs, and msinfo32 almost didnt work, I had to do some tricky stuff to get it working again), at least worked for the logs, so here they are again, but in english.

Also, searched for the most up to date drivers on AMD site, seems the 17.4.4 package is the latest for my APU by the moment and 17.10 for the chipset. That means I already have the latest drivers (which, seem to work better than the acer or default ones, that cause more frequent crashes)

Well, hope this helps, I trully wanna know the reason behind this XD

NOTE: If tehre is anything else, tell me, but I will translate stuff, installing language packs for single language OSes is a pain in the... brain... I reverted to my primary langpack to retrive functionality...

Thank you so much for your patience *Biggrin

 

Code: 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: ffffe787b93d88f8, 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.[/quote]
Have you been doing any overclocking?
Have you been using either hardware or software raid?



Open administrative command prompt and type or copy and paste:

1) msconfig (in the pop up system configuration > move the dot from normal startup to selective startup > uncheck load startup items > click service tab > in left lower corner check hide all Microsoft services > in the lower right side click disable all > click apply or ok > do not reboot)


2) taskmgr (in the pop up task manager > click on the start up tab > click on status so that the column sorts with enable rising to the top > right click on each row with enable and change to disable)


3) shutdown /r (you will reboot the computer so that it is in clean boot)


4) perform windows updates. Post any KB# that failed to update with error code,

Evaluate the performance on your computer in clean boot during typical use. Are the boots faster or slower? Are the shutdowns faster or slower? How have hangs changed? Are they more frequent, less frequent, or the same? How have bsod changed? Are they more frequent, less frequent or the same? Continue using clean boot indefinitely to monitor performance.



1) Run memtest86+ version 5.01 for at least 8 runs. This may take hours so plan to run it overnight.http://www.memtest.org/https://answe...f-ecc7b7ff6461
Please make sure that there are at least 8 runs. When the runs have completed please use the Windows snipping tool to post images into the thread.


2) Run one of these SMART tests on your drives and then use the Windows snipping tool to post images into the thread.
CrystalDiskInfo - Software - Crystal Dew World
HD Tune website
Hard Disk Sentinel - HDD health and temperature monitoring


3) Sometimes there are problems in the bios that produce bsod. The bios in your computer: BIOS Version/Date Insyde Corp. V1.13, 15/11/2016
Please check to see the lasted bios version and make sure the bios is up to date.


To ensure that there are no improper bios settings please reset the bios.
Sometimes there can be failure to boot after resetting the bios. So please make sure your files are backed up. Please make a backup image with Macrium: Macrium Software | Macrium Reflect Free
And please create a restore point.


How to Clear Your Computers CMOS to Reset BIOS Settings
3 Ways to Reset Your BIOS - wikiHow

If the above tests indicate no problems the next testing will be stress testing the CPU and GPU.

 

@zbook Looking at the error record for the hardware failure is a very useful step. The Machine Check Exception reveals why the CPU triggers the crash. In this case it was because of too much delay in the BUS.

Code: 1: kd> !errrec ffffe787b93d88f8 =============================================================================== Common Platform Error Record @ ffffe787b93d88f8 ------------------------------------------------------------------------------- Record Id : 01d2ec534e01d1c5 Severity : Fatal (1) Length : 928 Creator : Microsoft Notify Type : Machine Check Exception Timestamp : 6/23/2017 19:02:51 (UTC) Flags : 0x00000002 PreviousError =============================================================================== Section 0 : Processor Generic ------------------------------------------------------------------------------- Descriptor @ ffffe787b93d8978 Section @ ffffe787b93d8a50 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 : 0x0000000000660f51 Processor ID : 0x0000000000000000 =============================================================================== Section 1 : x86/x64 Processor Specific ------------------------------------------------------------------------------- Descriptor @ ffffe787b93d89c0 Section @ ffffe787b93d8b10 Offset : 536 Length : 128 Flags : 0x00000000 Severity : Fatal Local APIC Id : 0x0000000000000000 CPU 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 00 Proc. Info 0 @ ffffe787b93d8b10 =============================================================================== Section 2 : x86/x64 MCA ------------------------------------------------------------------------------- Descriptor @ ffffe787b93d8a08 Section @ ffffe787b93d8b90 Offset : 664 Length : 264 Flags : 0x00000000 Severity : Fatal Error : BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4) Status : 0xfe00000000070f0f Address : 0x00000000f0d08700 Misc. : 0xd00a0fff01000000[/quote] Let's wait and see what answers the OP gives to your questions on overclocking etc. Stress testing the system would be a good next step.

 

Thank you so much for your support, guys.

About BIOS settings and overclocking, I don't overclock this system (in fact, it's a laptop, so overclock isn't really possible without killing the MoBo, too much heat) and I haven't changed any settings in the BIOS (It's so mutilated that entering there is a waste of time... nothing to do there. Also. I don't think I'm doing any hardware Raid in here... I?m not sure what does that means anyway (at least for harware, I know about disk raid setups, but this is a laptop still, so, only one physical disk available) The only thing related to an "overclocking" is AMD Turbo CORE, which makes the processor get up to 3.4 Ghz (instead of the max 2.5 Ghz stock) But that is a default design... (I believe) and again, because of all the missing options in BIOS, I cannot disable that to test if that is the problem...

I have made some tests in the past (when I was using build 1511) stressing the GPU and CPU, using AIDA64 and GPU-Z and Prime95... but not even a single crash, no BSODs, nothing... it's supposed a hardware failure might arise during those tests... but nothing happened. Windows updated itself this weekend tho, I'm now in build 14393.1358, hope this doesn't alter things...

I've tested the clean boot thing... the PC works barely faster than it normally does... startup is the same as well as shutdown (which is rather fast, like 20 secs or less until I reach the dsktop, I don't use hybrid boot, waste of HDD space XD) In general, tehre is no change at all using clean boot, the system works blazingly fast, as it does currently with only the AV software and KeyboardLEDs app enabled (only that is enabled... I hate having useless stuff sitting in memory, even if I have 16 gig of RAM)

About Updating the BIOS, that is a step I cannot do, because latest revisions have the RAM crippled (They cut your RAM from 15.5 GB to 7.5 GB...) I ignore if they have aditional problems so, I avoid upgrading it...

I can try running the stress tests again this weekend, with the programs you sugest, and running memtest... unfortunately, I need to get job done here so, until then, I cannot run extensive tests *Sad

The analysys you do, @philc43 is the same (or almost the same) you said about an intel processor you were analysing as well in other thread... weird question, could this be because of faulty drivers? I hope it is, because, if it's hardware, that means I have to RMA this thing once again, and this time, getting a whole new system...

Thank you so much for your help, I'll try to get back at you this weekend, when I do all the tests.

 

Yes, the CPU is triggering and reporting the reason for the crash but this does not mean that it is the CPU which is the problem. Overclocking is a common reason as is overheating, drivers sending bad instructions, motherboard failure, etc. There is great difficulty in analysing x124 WHEA BSOD events because the real cause is rarely revealed. Troubleshooting is a matter of trial and error and gradually eliminating possible causes. If the problem never happens in safe mode that can be a good indicator that the problem is not a hardware one.

 

By Safe Mode you mean clean boot or are different things?
And... is normal that there can pass months without a crash, and still be a hardware issue?