PC freezes/BSOD randomly - not sure what more I can do.

Apr 4, 2018
7
0
10
Hello guys. The PC that I'm currently using usually freezes on me once a day, and the only thing that I can do from there is pressing the restart button. This problem or a similar one first occured back in December 2017. Instead of freezes the PC would randomly restart itself.

I've sent it back to where I bought it from for diagnostics/reparation two times. They've changed a few hardware components, but the issue never went away. I wanted to get a refund, yet they don't really seem to be like that idea, so they keep handing me suggestions regarding what I could do to "fix" the issue (and suggestions to what the cause of the issue might be). I really hope that some of you could give me a bit of insight in what I can do from here. Windows 10 came preinstalled with the machine.

My specs.

Operating System: Windows 10 Pro 64-bit
CPU: AMD FX-6300 17 °C, Vishera 32nm Technology
RAM: 8,00GB Single-Channel DDR3 @ 535MHz (7-7-7-19)
Motherboard: ASRock N68-GS4 FX R2.0 (CPUSocket)
Graphics: BenQ GL2450H (1920x1080@60Hz), 4095MB NVIDIA GeForce GTX 960 (Undefined)
Storage: 931GB TOSHIBA DT01ACA100 SCSI Disk Device (SATA)
Optical Drives: HL-DT-ST DVDRAM GH24NSD1 SCSI CdRom Device
Audio: NVIDIA High Definition Audio
________________________________________________________________________

The language installed is german, but I try my best to translate.
In event-viewer I always see this error after the restart, "Event ID 20 - WHEA-Logger, A fatal hardware error has occurred. Component: AMD Northbridge". I also got WHEA-Logger ID 18 once too. Sadly, I can't seem to find a dump file, but at times one gets created.

Other than that, I get DistributedCom errors which apparently shouldn't be the issue & Bugcheck error ID 1001.

I've tried... updating and re-installing several drivers, BIOS reset & update, Virus scan using Malwarebytes, Checking for issues using Memtest, some tools that windows already has, SeaTools, formating the whole machine/reinstalling windows 10 etc.

They told me to disable windows updates too after a fresh windows 10 installation, but this didn't help either. The only two updates that currently are installed can't be deleted.

1. Security update for Adobe Flash Player
2. Security update for Microsoft Windows (KB4054517)

I'm currently running another harddrive check, and I plan on doing a longer Memtest scan and running FurMark. But I fear that there won't be any errors, just like last time and the times I handed my PC over to the seller to get it fixed.
________________________________________________________________________

I'd really need some advice from you guys. This whole thing is extremely frustrating...

- Tommy

 
Solution
if windows 10 was activated on the motherboard before, when you do a clean install you can skip the serial number and when the activation process checks the motherboard signature it should activate. Major problem is often the hack programs block access to the activation server even if you have a valid key.

I think you can still join the windows 10 insider preview program and get a copy of windows that will update itself.
generally the builds are good for a year (so you can delay updates if you need to )

ragnar-gd

Reputable
You have two years after buying for being able to force them to fix that, so if they can hold you back some time longer, you loose your leverage... Check that...

Ignore the Distributed ComErrors, they are a common nuisance, but not related to your problems.
Given your description and error-message from the log, i supect the MoBo to be the culprit (the Northbridge-error is talking).
The ASrock N68 boards are not the best thing ASRock ever built, it is kind of cheap bulk-ware.
What they tell about the windows updates is b*s*.

Tell your shop to exchange the MoBo, pointing at the error you found. They won't like that, but, heck...

 
You need to provide the actual memory dump file from c:\windows\minimums directory.

The generic first attempt fix for this type of problem is to update the bios and motherboard drivers from the motherboard vendors website. And remove any overclocking drivers
Beyond that you need to provide the memory dump file so it can be looked a with the Windows downs debugger.
 
Apr 4, 2018
7
0
10


Might be that the motherboard is responsible. The strange thing is that they've changed it, yet the only thing that changed was that the PC just froze instead of restarting. BIOS should be fine, and I already have the driver for the MoBo too.
 
Apr 4, 2018
7
0
10


There's no dump file to be found, for whatever strange reason. The folder is empty. But it's possible for me to look up some things using the "Reliability History" in Windows.

Here's what I found, I hope this helps. I will be translating this to some extent. It should be noted that some of the descriptions, regarding the (same?) problem differ from the one out of a few that I will post below.
________________________________________________________________________

Source
Windows

Summary
Unexpected Shutdown

Date
‎02.‎04.‎2018 21:14

Status
The report got sent.

Problemsignature
Problemname: BlueScreen
Code: 124
Parameter 1: 0
Parameter 2: ffff9a0a80625038
Parameter 3: 0
Parameter 4: 0
Operating system version: 10_0_16299
Service Pack: 0_0
Produkt: 256_1
Operating system version: 10.0.16299.2.0.0.256.48
Area schema-ID: 1031

More information about the issue
Bucket-ID: 0x124_AuthenticAMD_PROCESSOR_BUS_PRV
Serverinformation: a59b8b6f-0c81-4775-8829-d242fd525d42
________________________________________________________________________

I will be posting a dump file when it's created (hopefully after the next freeze encounter). I will check the BIOS again, and see if it's up to date. A driver for the MoBo, doesn't really exist... All I got and all what there is to find were/are things related to the system, such as a sound driver and other utilities/software.

Edit: BIOS is up-to-date.
 
dump should be at c:\windows\minidump directory or c:\windows\memory.dmp file if you have the system set to save memory dumps and you have a pagefile on drive c: with proper space.

the bugcheck in the log indicates that the CPU called a bugcheck because of an internal error. you need the system uptimer to know if this bugcheck is useful or not. if the system up timer is under 15 second then most likely the motherboard reset the CPU because of a power problem but the PSU allowed the CPU to restart before the power was stable. This happened when too much power is being used by the GPU slot, the motherboard resets the CPU. Then some power supplies fake the power_ok signal and the CPU restarts with unstable power and generates a internal error the the CPU memory controller detects and calls a bugcheck to shut down the system.

you might want to google "how to use a keyboard to force a memory dump" make the registry settings and force a memory dump to confirm you system is set tow save one.

bugcheck 0x124 are panic memory dumps (system going down now) sometimes you only get a partial memory dump.
if your system has a large hardware cache it might not make it to the hard drive before the system shuts down.

if you make a memory dump of a working system I can take a quick look to see if there is anything really wrong before it crashes.




 
8,00GB Single-Channel DDR3 @ 535MHz (7-7-7-19)

This statement indicates you have the wrong memory for an AMD FX CPU. Although it doesn't identify the actual memory you have., it tells what it is running at.

You likely also don't know how to properly set the memory parameters in the BIOS.
1) Memory Clock Speed
2) DRAM Timings
3) DRAM voltage
 
Apr 4, 2018
7
0
10
Here's a memory dump that I created a few minutes after the PC started & a dump file that got created after the system crashed on its own: https://mega.nz/#!vP5gFboD!0GGsQ1YH-TiOAK_LU7UKT4rGM41Uvz0GcS905noP9WQ

I will also add what I could see in WinDbg for both files.
Below is the memory dump

BugCheck E2, {0, 0, 0, 0}

Probably caused by : kbdhid.sys ( kbdhid!KbdHidProcessCrashDump+1e0 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

MANUALLY_INITIATED_CRASH (e2)
The user manually initiated this crash dump.
Arguments:
Arg1: 0000000000000000
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 402

BUILD_VERSION_STRING: 16299.15.amd64fre.rs3_release.170928-1534

SYSTEM_PRODUCT_NAME: To Be Filled By O.E.M.

SYSTEM_SKU: To Be Filled By O.E.M.

SYSTEM_VERSION: To Be Filled By O.E.M.

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: P1.00

BIOS_DATE: 10/05/2015

BASEBOARD_MANUFACTURER: ASRock

BASEBOARD_PRODUCT: N68-GS4 FX R2.0

BASEBOARD_VERSION:

DUMP_TYPE: 0

BUGCHECK_P1: 0

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BUGCHECK_STR: MANUALLY_INITIATED_CRASH

CPU_COUNT: 6

CPU_MHZ: dbc

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 15

CPU_MODEL: 2

CPU_STEPPING: 0

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 2

ANALYSIS_SESSION_HOST: DESKTOP-8NN8EQ2

ANALYSIS_SESSION_TIME: 04-06-2018 16:09:31.0024

ANALYSIS_VERSION: 10.0.16299.91 amd64fre

LAST_CONTROL_TRANSFER: from fffff808175c3a0c to fffff800e5393510

STACK_TEXT:
fffff800`e4da5e18 fffff808`175c3a0c : 00000000`000000e2 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff800`e4da5e20 fffff808`175c3410 : ffffdb8c`4da3a5d0 fffff800`e54cd057 ffff6b8c`25c31e87 fffff800`e5320bcd : kbdhid!KbdHidProcessCrashDump+0x1e0
fffff800`e4da5e60 fffff808`175a4d49 : ffffdb8c`4b811c80 ffffdb8c`4b846a1c ffffdb8c`00000000 fffff808`175a8110 : kbdhid!KbdHid_InsertCodesIntoQueue+0xb0
fffff800`e4da5ec0 fffff808`175a4eb9 : ffffdb8c`000000c6 00000000`00000000 00000000`00000000 00000000`00000000 : HIDPARSE!HidP_KbdPutKey+0x45
fffff800`e4da5ef0 fffff808`175a502e : ffffdb8c`4b846a1c 00000000`0000000e 00000000`00000000 ffffdb8c`4ae34b60 : HIDPARSE!HidP_ModifierCode+0xa9
fffff800`e4da5f20 fffff808`175a512e : ffffdb8c`4b846ae8 00000000`00000000 ffffdb8c`4b776c10 fffff808`175a3e2a : HIDPARSE!HidP_TranslateUsage+0x86
fffff800`e4da5f70 fffff808`175c315f : 00000000`00000001 ffffdb8c`4b811f02 00000000`00000000 00000000`00000000 : HIDPARSE!HidP_TranslateUsageAndPagesToI8042ScanCodes+0xbe
fffff800`e4da5fe0 fffff800`e52db5f7 : ffffdb8c`4b776c10 00000000`00000001 ffffdb8c`00000000 fffff808`00000001 : kbdhid!KbdHid_ReadComplete+0x2ef
fffff800`e4da6060 fffff800`e52db4c7 : 00000000`00000000 ffffdb8c`4ba79706 00000000`00000009 ffffdb8c`4b809bd0 : nt!IopfCompleteRequest+0x117
fffff800`e4da6190 fffff808`1757133c : ffffdb8c`4b809bc0 fffff808`13642f02 fffff800`e4da6240 ffffdb8c`4b809be0 : nt!IofCompleteRequest+0x17
fffff800`e4da61c0 fffff808`175693ac : ffffdb8c`4ba79790 ffffdb8c`4ba79702 ffffdb8c`4b4ae960 ffffdb8c`4ba79620 : HIDCLASS!HidpDistributeInterruptReport+0x1e0
fffff800`e4da6280 fffff800`e52db5f7 : ffffdb8c`4b81fc10 ffffdb8c`4b81fc10 fffff800`e4da6401 ffff9781`050700f8 : HIDCLASS!HidpInterruptReadComplete+0x5c8c
fffff800`e4da6320 fffff800`e52db4c7 : ffffdb8c`4adcd301 ffffdb8c`4cc6c000 ffffdb8c`48c3d840 fffff800`e4da6580 : nt!IopfCompleteRequest+0x117
fffff800`e4da6450 fffff808`150d2aad : ffffdb8c`47e6d000 ffffdb8c`4cc6c1ac ffffdb8c`00000bed ffffdb8c`70627375 : nt!IofCompleteRequest+0x17
fffff800`e4da6480 fffff808`150d382e : 00000000`00000002 ffffdb8c`4cc6c01c 00000000`ffffffff ffffdb8c`47e6d050 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x15dd
fffff800`e4da67d0 fffff808`150d526e : 00000000`00000000 ffffdb8c`47e6e2c8 fffff780`00000320 fffff800`e5231004 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x2de
fffff800`e4da6830 fffff808`150d4e24 : ffffdb8c`47e6d1a0 00000000`00000002 ffffdb8c`4bb7c002 ffffdb8c`47eb7190 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0x3ee
fffff800`e4da68a0 fffff800`e52e3f62 : fffff800`e4da6a20 ffffdb8c`47eb5000 fffff800`e4d33180 00000000`00000002 : USBPORT!USBPORT_Xdpc_Worker_IocDpc+0x204
fffff800`e4da6920 fffff800`e52e365f : 00000000`00000010 00000000`00002b01 00000000`00346472 fffff800`e4d33180 : nt!KiExecuteAllDpcs+0x1d2
fffff800`e4da6a60 fffff800`e5396dfa : 00000000`00000000 fffff800`e4d33180 00000000`001a6f89 fffff800`e5637380 : nt!KiRetireDpcList+0xdf
fffff800`e4da6c60 00000000`00000000 : fffff800`e4da7000 fffff800`e4da1000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


THREAD_SHA1_HASH_MOD_FUNC: 0e21e666385dd0456ebf84b09e1ee762dd8d6886

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 7c027c0657d93db489cf01df663bde269533646e

THREAD_SHA1_HASH_MOD: 755ba025b120e105d7b412a68d37679b14d4d1ca

FOLLOWUP_IP:
kbdhid!KbdHidProcessCrashDump+1e0
fffff808`175c3a0c cc int 3

FAULT_INSTR_CODE: c08545cc

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: kbdhid!KbdHidProcessCrashDump+1e0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: kbdhid

IMAGE_NAME: kbdhid.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 30e4f78a

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 1e0

FAILURE_BUCKET_ID: MANUALLY_INITIATED_CRASH_kbdhid!KbdHidProcessCrashDump

BUCKET_ID: MANUALLY_INITIATED_CRASH_kbdhid!KbdHidProcessCrashDump

PRIMARY_PROBLEM_CLASS: MANUALLY_INITIATED_CRASH_kbdhid!KbdHidProcessCrashDump

TARGET_TIME: 2018-04-05T19:00:09.000Z

OSBUILD: 16299

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2018-03-01 06:36:55

BUILDDATESTAMP_STR: 170928-1534

BUILDLAB_STR: rs3_release

BUILDOSVER_STR: 10.0.16299.15.amd64fre.rs3_release.170928-1534

ANALYSIS_SESSION_ELAPSED_TIME: a29

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:manually_initiated_crash_kbdhid!kbdhidprocesscrashdump

FAILURE_ID_HASH: {a90fbd35-7a19-bced-0f76-fa89d249d332}

Followup: MachineOwner
---------

& here is the random crash report.

BugCheck 124, {0, ffffce0ae75da038, 0, 0}

Probably caused by : AuthenticAMD

Followup: MachineOwner
---------

0: 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: ffffce0ae75da038, 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:
------------------


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.16299.125 (WinBuild.160101.0800)

DUMP_TYPE: 2

BUGCHECK_P1: 0

BUGCHECK_P2: ffffce0ae75da038

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BUGCHECK_STR: 0x124_AuthenticAMD

CPU_COUNT: 6

CPU_MHZ: dbc

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 15

CPU_MODEL: 2

CPU_STEPPING: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: DESKTOP-8NN8EQ2

ANALYSIS_SESSION_TIME: 04-06-2018 16:11:27.0037

ANALYSIS_VERSION: 10.0.16299.91 amd64fre

STACK_TEXT:
ffff890b`a70ed5b0 fffff802`626b9635 : ffffce0a`e6d76040 ffffce0a`e75da010 ffffce0a`e4853480 fffff802`00000000 : nt!WheapCreateLiveTriageDump+0x7b
ffff890b`a70edae0 fffff802`62509348 : ffffce0a`e75da010 ffffe407`4698cb00 00000000`00000000 fffff802`62856120 : nt!WheapCreateTriageDumpFromPreviousSession+0x2d
ffff890b`a70edb10 fffff802`62509e6b : fffff802`625dad80 fffff802`625dad80 ffffce0a`e4853480 00000000`00000202 : nt!WheapProcessWorkQueueItem+0x48
ffff890b`a70edb50 fffff802`622c4e05 : ffffce0a`e4853480 ffffce0a`e6d76040 ffffce0a`e4853400 ffffce0a`e78624d8 : nt!WheapWorkQueueWorkerRoutine+0x2b
ffff890b`a70edb80 fffff802`622b0f87 : ffffba01`7c28cc40 00000000`00000080 ffffce0a`e48c9040 ffffce0a`e6d76040 : nt!ExpWorkerThread+0xf5
ffff890b`a70edc10 fffff802`623f1676 : ffffba01`7c280180 ffffce0a`e6d76040 fffff802`622b0f40 00000000`00000000 : nt!PspSystemThreadStartup+0x47
ffff890b`a70edc60 00000000`00000000 : ffff890b`a70ee000 ffff890b`a70e8000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


THREAD_SHA1_HASH_MOD_FUNC: 26acd050bd9f055d0a04825d57b9e0e6be9c1a07

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: e1ca14ad460db17fee32f4b133c79439b72309bb

THREAD_SHA1_HASH_MOD: 30a3e915496deaace47137d5b90c3ecc03746bf6

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: AuthenticAMD

IMAGE_NAME: AuthenticAMD

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: .thread ; .cxr ; kb

FAILURE_BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID: 0x124_AuthenticAMD_PROCESSOR_BUS_PRV

PRIMARY_PROBLEM_CLASS: 0x124_AuthenticAMD_PROCESSOR_BUS_PRV

TARGET_TIME: 2018-04-05T17:37:22.000Z

OSBUILD: 16299

OSSERVICEPACK: 125

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2017-12-07 22:55:32

BUILDDATESTAMP_STR: 160101.0800

BUILDLAB_STR: WinBuild

BUILDOSVER_STR: 10.0.16299.125

ANALYSIS_SESSION_ELAPSED_TIME: 832

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x124_authenticamd_processor_bus_prv

FAILURE_ID_HASH: {6fd7875b-9a1b-9e09-d6d6-816026a875c8}

Followup: MachineOwner
---------
 
Apr 4, 2018
7
0
10


Hm, I wasn't aware of that. I hoped the guys from where I bought the PC from would do it right. I will look into the BIOS part.

 
DriverBooster.exe could indicate you did not get the proper drivers from the motherboard vendor.
Azureus.exe bittorrent client
old version of this driver:
nVidia nForce network driver
\SystemRoot\System32\drivers\nvmf6264.sys Wed Apr 20 15:49:36 2011
(I would expect problems with this driver)
------
hacked ntkernel file, Several other windows files have the checksum codes removed
normally, you would want to reinstall using a known good windows images downloaded from Microsoft servers.

looking at internal logs now.

machine info:
BIOS Version P1.00
BIOS Starting Address Segment f000
BIOS Release Date 10/05/2015

Manufacturer ASRock
Product N68-GS4 FX R2.0
Processor Version AMD FX(tm)-6300 Six-Core Processor
Processor Voltage 8dh - 1.3V
External Clock 200MHz
Max Speed 3500MHz
Current Speed 3500MHz
 
Apr 4, 2018
7
0
10


I'm going to reinstall windows now. I downloaded a file a while ago, to activate windows since I didn't have the whole serial key, and the old one that I had didn't work because of a new Mobo. I did try to activate windows following several guides and different methods, but nothing worked. I hoped that this program would show me the full key for the new motherboard (after I got the pc back). All I had were the first letters (I believe, or just a small part of the whole) but instead it "cracked"/hacked the system, basically giving me a free activation. I was able to activate windows again with the original serial key (which I got days later) for the new MoBo , after I used the software. The new reinstall will be a clean one, with that key.

 
if windows 10 was activated on the motherboard before, when you do a clean install you can skip the serial number and when the activation process checks the motherboard signature it should activate. Major problem is often the hack programs block access to the activation server even if you have a valid key.

I think you can still join the windows 10 insider preview program and get a copy of windows that will update itself.
generally the builds are good for a year (so you can delay updates if you need to )



 
Solution
Apr 4, 2018
7
0
10


I made a fresh install using a USB. Luckily windows was activated right after I installed it (digital license), just as you said. I got all the updates too, so I think it should be fine regarding the operating-system. It might take a few days for the crashes to happen again. At least, that's what I noticed the last times. Before the MoBo got switched I installed windows again (twice I think) to see if it would solve anything and right after I got a new MoBo, 3-7 days passed almost each time and suddenly it started happening again almost daily.

Also, thank you for taking time out of your day trying to help me. The struggle has been going on for quite a while :)