Jump to content

AIDA64 crashes when shutting down


Selim Gürsu
 Share

Recommended Posts

 

First of all I'm sorry I don't know English, I am using the latest version of Aida64.I get a blue screen when turning off Aida64.
I renewed my old processor I got the i5-7600k.Could the problem be with the new processor?Please help me, thank you.
My crash report;

==================================================
Dump File      : 121420-7593-01.dmp
Crash Time  : 14.12.2020 17:29:25
Bug Check String: PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code: 0x00000050
Parametre 1       : ffff8580`00000000
Parametre 2       : 00000000`00000000
Parametre 3       : 00000000`00000000
Parametre 4       : 00000000`00000006
Caused By Driver : ntoskrnl.exe
Caused By Address  : ntoskrnl.exe+3f5780
File Description  : 
Product Name          : 
Company           : 
File Version      : 
Processor           : x64
Crash Address : ntoskrnl.exe+3f5780
Stack Address 1    : 
Stack Address 2    : 
Stack Address 3    : 
Computer Name    : 
Full Path           : C:\Windows\Minidump\121420-7593-01.dmp
Processors Count    : 4
Major Version        : 15
Minor Version        : 19041
Dump File Size: 798.604
Dump File Size    : 14.12.2020 17:30:07
==================================================

Link to comment
Share on other sites

On 12/14/2020 at 7:46 PM, Selim Gürsu said:

 

First of all I'm sorry I don't know English, I am using the latest version of Aida64.I get a blue screen when turning off Aida64.
I renewed my old processor I got the i5-7600k.Could the problem be with the new processor?Please help me, thank you.
My crash report;

==================================================
Dump File      : 121420-7593-01.dmp
Crash Time  : 14.12.2020 17:29:25
Bug Check String: PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code: 0x00000050
Parametre 1       : ffff8580`00000000
Parametre 2       : 00000000`00000000
Parametre 3       : 00000000`00000000
Parametre 4       : 00000000`00000006
Caused By Driver : ntoskrnl.exe
Caused By Address  : ntoskrnl.exe+3f5780
File Description  : 
Product Name          : 
Company           : 
File Version      : 
Processor           : x64
Crash Address : ntoskrnl.exe+3f5780
Stack Address 1    : 
Stack Address 2    : 
Stack Address 3    : 
Computer Name    : 
Full Path           : C:\Windows\Minidump\121420-7593-01.dmp
Processors Count    : 4
Major Version        : 15
Minor Version        : 19041
Dump File Size: 798.604
Dump File Size    : 14.12.2020 17:30:07
==================================================

What motherboard, CPU and video card(s) do you have?  Are you using the latest version of AIDA64, 6.32?

Link to comment
Share on other sites

121920-6250-01.dmp    19.12.2020 1:06:01    PAGE_FAULT_IN_NONPAGED_AREA    0x00000050    ffffd480`00000000    00000000`00000000    00000000`00000000    00000000`00000006    ntoskrnl.exe    ntoskrnl.exe+3f5780    NT Kernel & System    Microsoft® Windows® Operating System    Microsoft Corporation    10.0.19041.685 (WinBuild.160101.0800)    x64    ntoskrnl.exe+3f5780                    C:\WINDOWS\Minidump\121920-6250-01.dmp    8    15    19041    1 078 500    19.12.2020 1:06:37    
 

Link to comment
Share on other sites

  • 3 weeks later...
  • 1 month later...
On 12/21/2020 at 3:30 PM, Selim Gürsu said:

All versions above 5.99.4900 have a bsod.

Maybe you are right. I have the same problem and deeper investigation of the dump files lead me to kerneld.x64 causing the BSODs, I compared all of the last versions of that file as a size and seems like after the version you mentioned there has been a change and the file is bigger and seems like the same size in all the versions from 6 and above. Really annoying problem guys, please fix it. I would try and use 5.99 but it doesn't detect the NVM drive so I needed a newer version but seems like all of them have that annoying bug.

Link to comment
Share on other sites

  • 2 weeks later...
On 2/13/2021 at 11:08 AM, scorpion_87 said:

Maybe you are right. I have the same problem and deeper investigation of the dump files lead me to kerneld.x64 causing the BSODs, I compared all of the last versions of that file as a size and seems like after the version you mentioned there has been a change and the file is bigger and seems like the same size in all the versions from 6 and above. Really annoying problem guys, please fix it. I would try and use 5.99 but it doesn't detect the NVM drive so I needed a newer version but seems like all of them have that annoying bug.

So far we haven't been able to reproduce the issue on our test systems here :( 

Link to comment
Share on other sites

  • 8 months later...
  • 5 months later...
  • 3 months later...
  • 3 months later...
On 2/25/2021 at 2:09 AM, Fiery said:

So far we haven't been able to reproduce the issue on our test systems here :( 

it requires some (3 days minimum) uptime without reboot.

 

kernel memory dump blames MiMappingHasIoTracker trying to read from zero'd memory.

I can reproduce it across multiple windows 10 systems, but so far not windows 7.

 

All dump files across multiple user systems that i have seen so far are all sharing vary similar stacks.

 

have seen it on i3 second gen in a toshiba aio touchsystem, and x79 on rampage iv with xeon  v2's.

rst driver doesn't matter, smart/raid access doesn't matter

all that matters is moving from the 4xKB driver in 5.99.4800 to the 67KB driver in 5.99.49xx beta's and later.

 

Here is a list of affected configurations,  there is no correlating hardware or driver apart from kerneld.x64 and windows own drivers.

 

Msi Z270 Tomahawk - i5-7600K - Asus GTX 1050TI.

MSI B150 Gaming M3 I7 6700 GTX 770

i7-9700K RTX 2080Ti Z390 chipset MB

Ryzen 5 3600, MSI B450-A PRO MAX, 16GB DDR4 Vengance 3200 Mhz, 550W PSU, RTX 2070

i3 10105f, Gigabyte B560M DS3H V2, GT 1030

H97m-e ASUS whit an i5 4460 and rx 480

Quosmio DX730. i5 2450, GT 540, 16GB. Single SSD.  Almost an untouched install of windows on it, it only runs some dedicated servers. RST 12.9.4.1000

Rampage IV Extreme, 1680v2, GTX 1060, 32GB. RSTe 6.3.0.1022, iaNVME 5.3.0.1005, Samsung nvme 3.3.0.2003

 

My suspicion is a core windows driver is responsible.

 

Windows 11 does not seem affected?

 

I do have a suspicion that the Microsoft XVDD driver is  involved, as the bsod can trigger any point after the event log registers a disk surprise removed event

 

  

On 11/16/2021 at 4:32 AM, Aayk said:

Exactly the same problem, constant reboots with aida64 enabled,

newer versions of the program did not solve the problem, still the screen and restart.

Ryzen 9 5900X, ROG STRIX B550-XE GAMING WIFI, DDR4 32GB, 6900XT

 

you appears to be confused and mixing some idle bsod issue into this one.

Link to comment
Share on other sites

  • 2 weeks later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...