Jump to content
AIDA64 Discussion Forum
facboy

BugCheck in Windows 1803 (Asus Maximus X Hero) [Win10 1803 timer collision]

Recommended Posts

since Windows 1803 my machine has rebooted randomly twice.  WinDbg seems to be pointing to something in AIDA64 as the culprit:

Quote

KEY_VALUES_STRING: 1


TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING:  17134.1.amd64fre.rs4_release.180410-1804

SYSTEM_MANUFACTURER:  System manufacturer

SYSTEM_PRODUCT_NAME:  System Product Name

SYSTEM_SKU:  SKU

SYSTEM_VERSION:  System Version

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  1301

BIOS_DATE:  04/09/2018

BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT:  ROG MAXIMUS X HERO

BASEBOARD_VERSION:  Rev 1.xx

DUMP_TYPE:  1

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: 0

BUGCHECK_P3: 8

BUGCHECK_P4: 0

CPU_COUNT: c

CPU_MHZ: e70

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: a

CPU_MICROCODE: 6,9e,a,0 (F,M,S,R)  SIG: 84'00000000 (cache) 84'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  aida64.exe

CURRENT_IRQL:  0

 

Share this post


Link to post
Share on other sites

Do you have Asus AI Suite installed?  What video card(s), HDD(s) and SSD(s) do you have?

Share this post


Link to post
Share on other sites

sorry, since i stopped using it i forgot to follow this up.

no i don't have any Asus software installed because their software is awful.

nvidia gtx980, 2 WD blacks, a WD red, a samsung 850evo and a crucial mx100.

Share this post


Link to post
Share on other sites

i've had AIDA64 running again for the last couple of days, somebody has fixed something because i don't seem to be getting the errors anymore.  there's been a couple of Nvidia driver releases since then so perhaps that sorted it out.

Share this post


Link to post
Share on other sites
2 hours ago, facboy said:

i've had AIDA64 running again for the last couple of days, somebody has fixed something because i don't seem to be getting the errors anymore.  there's been a couple of Nvidia driver releases since then so perhaps that sorted it out.

This is good news. Driver updates can fix such issues. Let us know if the issue comes back.

 

Share this post


Link to post
Share on other sites

This issue is occurring in the nvidia kernel driver, your isn't hasn't been fixed its just gone into a really random occurance cycle.

A process cannot cause a bsod,  a driver would have been flagged that was loaded by the process but it might be wrong too (as different utilities can be more or even less correct about analysing dump files with the symbols available.

 

397.55 or earlier are not affected by this, so if you're on 397.64 or .93, theres your culprit.

Share this post


Link to post
Share on other sites

I'm also affected by this, I've killed AIDA64 off for now to see if it fixes it, but I tend to get a BSOD every day or so at this stage.

Driver is 397.93 - and it's only been doing this for a few days, so pretty sure that's when I updated to .93.

My minidump from an hour ago:

 

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 17134 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17134.1.amd64fre.rs4_release.180410-1804
Machine Name:
Kernel base = 0xfffff801`cd612000 PsLoadedModuleList = 0xfffff801`cd9cf1d0
Debug session time: Sat Jun  2 00:44:44.287 2018 (UTC - 4:00)
System Uptime: 0 days 1:27:49.164
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000008, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP: 
+0
00000000`00000000 0000            add     byte ptr [rax],al

EXCEPTION_PARAMETER1:  0000000000000008

EXCEPTION_PARAMETER2:  0000000000000000

WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
 0000000000000000 

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

BUGCHECK_STR:  0x1e_c0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  aida64.exe

CURRENT_IRQL:  0

EXCEPTION_RECORD:  000000000010a1c0 -- (.exr 0x10a1c0)
Cannot read Exception record @ 000000000010a1c0

TRAP_FRAME:  ffffb4863a8e54a8 -- (.trap 0xffffb4863a8e54a8)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=ffffb4863a8e55d0 rsp=0000000004029000 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=00000000c0000005 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0     vif nv up di ng zr na pe nc
0001:55d0 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff801cd622b5d to fffff801cd7a9670

STACK_TEXT:  
ffffb486`3a8e4d18 fffff801`cd622b5d : 00000000`0000001e ffffffff`c0000005 00000000`00000000 00000000`00000008 : nt!KeBugCheckEx
ffffb486`3a8e4d20 fffff801`cd7bc902 : 00000000`0010a1c0 00000000`00000001 ffffb486`3a8e54a8 fffff806`7e8d0964 : nt!KiDispatchException+0x58d
ffffb486`3a8e53d0 fffff801`cd7b8aac : ffff8a80`7c4e2000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
ffffb486`3a8e55b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x4ac


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiDispatchException+58d
fffff801`cd622b5d 90              nop

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiDispatchException+58d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5ae3f148

FAILURE_BUCKET_ID:  X64_0x1e_c0000005_nt!KiDispatchException+58d

BUCKET_ID:  X64_0x1e_c0000005_nt!KiDispatchException+58d

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

 

Share this post


Link to post
Share on other sites
On ‎5‎/‎27‎/‎2018 at 10:39 PM, Squall Leonhart said:

This issue is occurring in the nvidia kernel driver, your isn't hasn't been fixed its just gone into a really random occurance cycle.

A process cannot cause a bsod,  a driver would have been flagged that was loaded by the process but it might be wrong too (as different utilities can be more or even less correct about analysing dump files with the symbols available.

Just a sidenote: a process can load a DLL (in this particular case the one for NVAPI) which can issue kernel driver calls (exactly what happens in this case) which can then cause a BSoD.  Sometime it's difficult to go through that chain of calls to find the culprit :( 

Share this post


Link to post
Share on other sites

yes, i've just had a bugcheck again (first time since i last posted).  i'm on 398.11.

i first started seeing this in early may, when 397.64 wasn't out yet, so i'm pretty sure it affects 397.55 as well, and possibly earlier versions.

Share this post


Link to post
Share on other sites
On ‎6‎/‎10‎/‎2018 at 7:45 PM, facboy said:

yes, i've just had a bugcheck again (first time since i last posted).  i'm on 398.11.

i first started seeing this in early may, when 397.64 wasn't out yet, so i'm pretty sure it affects 397.55 as well, and possibly earlier versions.

We believe we've found the root cause of the issues concerning Windows 10 April 2018 Update (Version 1803 / Build 17134) based systems.  The timer that AIDA64 uses for BCLK measurement is also used by a new Win10 component.  Most likely that component is used for GPU profiling.  And when AIDA64 and Win10 both use the timer for their own purposes in the same time, the system could become unstable.  We've had to disable polling for BCLK, so from now on AIDA64 will only measure BCLK once, and then use the last value until AIDA64 gets restarted.  Here's the new AIDA64 beta build that includes the workaround:

https://www.aida64.com/downloads/latesta64xebeta

Share this post


Link to post
Share on other sites

I am having exactly the same problem. I'm using latest version. (5.98.4800)
My hardware:
Maximus X Hero, 8086K@5GHz, 16GB RAM, 2xGTX970, M2 Samsung MZ-V7E1T0BW 1TB

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000008, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP: 
+0
00000000`00000000 0000            add     byte ptr [rax],al

EXCEPTION_PARAMETER1:  0000000000000008

EXCEPTION_PARAMETER2:  0000000000000000

WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
 0000000000000000 

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

BUGCHECK_STR:  0x1e_c0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  aida64.exe

CURRENT_IRQL:  0

EXCEPTION_RECORD:  000000000010a1c0 -- (.exr 0x10a1c0)
Cannot read Exception record @ 000000000010a1c0

TRAP_FRAME:  ffffae8166b39000 -- (.trap 0xffffae8166b39000)
Unable to read trap frame at ffffae81`66b39000

LAST_CONTROL_TRANSFER:  from fffff803a5c6bcdd to fffff803a5db3490

STACK_TEXT:  
ffff8186`5f17dc18 fffff803`a5c6bcdd : 00000000`0000001e ffffffff`c0000005 00000000`00000000 00000000`00000008 : nt!KeBugCheckEx
ffff8186`5f17dc20 fffff803`a5dc4142 : 00000000`0010a1c0 00000000`00000001 ffffae81`66b39000 fffff800`9bfaa854 : nt!KiDispatchException+0x58d
ffff8186`5f17e2d0 fffff803`a5dc0cbf : ffffae81`6835ba00 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
ffff8186`5f17e4b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x3ff


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiDispatchException+58d
fffff803`a5c6bcdd 90              nop

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiDispatchException+58d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5b93419b

FAILURE_BUCKET_ID:  X64_0x1e_c0000005_nt!KiDispatchException+58d

BUCKET_ID:  X64_0x1e_c0000005_nt!KiDispatchException+58d

Followup: MachineOwner

 

 

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×