That they have done the same tests over and over and they didn't had any bsod.And that the hardware is working perfectly.But they have no idea what those bsod are and why are happening..They also run tests on with a different HDD ..
So the only think that is left from me to do is to format another hdd and clean install Windows there and not on my primary to check if there is a problem with that..
The testing here was interrupted by the return of the computer.
See the prior post.
The next step is windows driver verifier to find misbehaving drivers.
Please post an updated dm log zip: BSOD - Posting Instructions - Windows 10 Forums
1) create a brand new restore point
2) backup files to another drive
2) create a backup image using Macrium:
Macrium Software | Your Image is Everything
3) place the backup image onto another drive
4) read the information in the links below
5) learn the 3 commands to turn off windows driver verifier
6) practice the commands using the administrative command prompt command: shutdown /r /o /f /t 00
7) make sure system recovery has bsod mini dump automatic restart unchecked so that you have time to view the bsod window
8) When all of the above is complete use link 2 for the customized settings for testing
9) windows driver verifier will repetitively produce bsod until all misbehaving drivers are fixed or until it is turned off. Each time you return to the desktop you will run both bluescreenview and whocrashed.
10) download and install bluescreenview: Blue screen of death (STOP error) information in dump files.
11) download and install whocrashed: http://www.resplendence.com/whocrashed
12) post a new zip after each bsod so that we can guide you through the process:
BSOD - Posting Instructions - Windows 10 Forums
13) when there are no more bsod using windows driver verifier it will be run for an additional 36 hours while the computer is under typical use. If there are no more bsod the troubleshooting will be completed using windows driver verifier.
1) https://answers.microsoft.com/en-us/...d-e95ee5d8669d
2) https://answers.microsoft.com/en-us/...3-c48669e4c983
3) Enable and Disable Driver Verifier in Windows 10 Windows 10 Performance Maintenance Tutorials
Hello, i uploaded the new bsod files and will do ti again once i've finished the rest tests you asked
Please fill in your system specs.
Please follow this tutorial and download the tool.
The tool will give you detailed information about your system specs, please fill in your system specs more completely including PSU, cooling and other used stuff like mouse, keyboard, monitor, case, etc.
The PSU, cooling and other stuff are NOT mentioned in the tool.
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
System Specs - Fill in at Ten Forums Windows 10 General Tips Tutorials
i uploaded a photo cause i am using 2 pcs so i wont lose the other ones info.
cooler master 620m plus 80 psu
keyboard roccat isku fx
mouse roccat kiro
case phanteks p400 eclipse
monitors asus vs247hr and LG flatron m2094d
no other cooling than the one from the cpu box that came with and the ones that are on the case in default
i used BSODAnalyzer and run it for 10 straight hours i hope this might give you some more info
info WHEA_UNCORRECTABLE_ERROR (124)
Caused by GenuineIntel .
This is the Log.
Opened log file 'c:\BasicAnalysis.txt'
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*c:\Symbols*https://msdl.microso...ownload/symbols
Microsoft ® Windows Debugger Version 10.0.15063.0 AMD64
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\081317-22671-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*c:\Symbols*https://msdl.microso...ownload/symbols
Symbol search path is: SRV*c:\Symbols*https://msdl.microso...ownload/symbols
Executable search path is:
Windows 10 Kernel Version 15063 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 15063.0.amd64fre.rs2_release.170317-1834
Machine Name:
Kernel base = 0xfffff801`67a8a000 PsLoadedModuleList = 0xfffff801`67dd65c0
Debug session time: Sun Aug 13 15:28:15.143 2017 (UTC + 3:00)
System Uptime: 0 days 0:48:25.822
Loading Kernel Symbols
.
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..............................................................
................................................................
.................................................
Loading User Symbols
Loading unloaded module list
.......
GetContextState failed, 0x8007001E
CS descriptor lookup failed
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get program counter
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, ffffdd05bc2a2028, bf800000, 124}
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Probably caused by : GenuineIntel
Followup: MachineOwner
---------
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
1: kd> !analyze -v;r;kv;.logclose;q
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get program counter
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
*******************************************************************************
* *
* 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: ffffdd05bc2a2028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000124, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.15063.540 (WinBuild.160101.0800)
SYSTEM_MANUFACTURER: ASUS
SYSTEM_PRODUCT_NAME: All Series
SYSTEM_SKU: All
SYSTEM_VERSION: System Version
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: 3003
BIOS_DATE: 10/28/2015
BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.
BASEBOARD_PRODUCT: MAXIMUS VII RANGER
BASEBOARD_VERSION: Rev 1.xx
DUMP_TYPE: 2
BUGCHECK_P1: 0
BUGCHECK_P2: ffffdd05bc2a2028
BUGCHECK_P3: bf800000
BUGCHECK_P4: 124
BUGCHECK_STR: 0x124_GenuineIntel
CPU_COUNT: 4
CPU_MHZ: c7e
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 3c
CPU_STEPPING: 3
CPU_MICROCODE: 6,3c,3,0 (F,M,S,R) SIG: 1E'00000000 (cache) 1E'00000000 (init)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: Dauntless-Win64-Shipping.exe
CURRENT_IRQL: f
ANALYSIS_SESSION_HOST: DESKTOP-5LVHCU4
ANALYSIS_SESSION_TIME: 08-15-2017 14:17:08.0007
ANALYSIS_VERSION: 10.0.15063.0 amd64fre
STACK_TEXT:
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: GenuineIntel
IMAGE_NAME: GenuineIntel
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_CACHE
BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_CACHE
PRIMARY_PROBLEM_CLASS: 0x124_GenuineIntel_PROCESSOR_CACHE
TARGET_TIME: 2017-08-13T12:28:15.000Z
OSBUILD: 15063
OSSERVICEPACK: 540
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-08-01 04:23:25
BUILDDATESTAMP_STR: 160101.0800
BUILDLAB_STR: WinBuild
BUILDOSVER_STR: 10.0.15063.540
ANALYSIS_SESSION_ELAPSED_TIME: 7cb
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x124_genuineintel_processor_cache
FAILURE_ID_HASH: {4c8f3f5e-1af5-ed8b-df14-d42663b1dfa7}
Followup: MachineOwner
---------
GetContextState failed, 0x8007001E
Unable to get current machine context, Win32 error 0n30
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
Unable to get program counter
GetContextState failed, 0x8007001E
Unable to retrieve register information
nt!KeBugCheckEx:
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
fffff801`67bf6560 48894c2408 mov qword ptr [rsp+8],rcx ss:00000000`00000008=????????????????
GetContextState failed, 0x8007001E
GetContextState failed, 0x8007001E
^ Unable to get program counter '!analyze -v;r;kv;.logclose;q'
We are working up the bsod WHEA 124 which is typically a hardware problem.
The information in the above link is available in the prior bsod mini dump debugging.
What is the link for that application?
The notable findings are in the code section in post #9.
What are the BIOS 3.3, 5 and 12 voltage values?
What are the CPU voltage and frequency?
https://www.sevenforums.com/tutorials/301799-psu-test-dc-output-voltage.html
When you are comfortable with the methods to turn off windows driver verifier you can start it with the custom settings in post # 22.
For any new bsod please post a new zip:
https://www.tenforums.com/bsod-crashes-debugging/2198-bsod-posting-instructions.html
When you posted images of HD sentinel there was no error scan image.
Please post an error scan of the drive.
this is the link of the application
https://raw.github.com/Gi0tis/BSODAn...ODAnalyzer.exe
this is the link to the site but it is in greek.
BSODAnalyzer v0.9.9.0
the next thing i will do is to complete your request at post #22.
will check for the voltage values
can you please explain the error scan of the drive you want? i had no error on the hd sentinel. sorry for the trouble
Disk > surface test
If that is not part of the trial or free edition the use HD tune: http://www.hdtune.com/
Hello sorry for taking so long to reply but there is a lot of workload.
I used the settings provided for the verifier and starting doing the tests for the hdd.i got a bsod at that time that i can only give you a screenshot of it.after restart verifier kicked in and after second reboot pc went into repair mode and went to an earlier state.so i have not the files to upload. i will do the verifier from post #22 as soon as possible and provide them to you. thank you and sorry for taking so long from my behalf.
Quote