AIDA64 throws a Blue Screen when closing it with the OSD Panel open

[Selim Gürsu]

I disabled low-level sensor operations and it worked fine, but when I disabled low-level SMBus operations, it gave me a blue screen.

[Selim Gürsu]

I tried again, when the 2 options you mentioned are selected, it gives a blue screen.

I think versions after 5.99 are not compatible with my motherboard and processor.

[Fiery]

29 minutes ago, Selim Gürsu said:

I tried again, when the 2 options you mentioned are selected, it gives a blue screen.

I think versions after 5.99 are not compatible with my motherboard and processor.

Thank you!  We have tons of new features and improvements implemented since AIDA64 v5.99 (which was released almost 7 years ago) so it's very difficult to narrow it down just based on that info  However, we can continue with your USB devices: in AIDA64 please press Ctrl+D --> System Debug --> USB Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post.

Thank you in advance!

[Selim Gürsu]

I really don't want to do that right now, so I uninstalled the program. If I reinstall and close it, it will give me a blue screen again. I'm worried that Windows will crash because of this blue screen.

[Selim Gürsu]

2 hours ago, Fiery said:

Thank you!  We have tons of new features and improvements implemented since AIDA64 v5.99 (which was released almost 7 years ago) so it's very difficult to narrow it down just based on that info  However, we can continue with your USB devices: in AIDA64 please press Ctrl+D --> System Debug --> USB Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post.

Thank you in advance!

In fact, if you look at the changes you made in the transition from version 5.99.4900 to version 6.00.5100, you may be able to find the problem more easily.

[Fiery]

23 minutes ago, Selim Gürsu said:

In fact, if you look at the changes you made in the transition from version 5.99.4900 to version 6.00.5100, you may be able to find the problem more easily.

So you mean you've actually tried it with v6.00.5100 and it failed to work?

[Selim Gürsu]

2 saat önce, Fiery şöyle dedi:

Yani v6.00.5100 ile denediniz ve işe yaramadı mı?

Yes, I tried all versions after 5.99.

[Fiery]

3 minutes ago, Selim Gürsu said:

Yes, I tried all versions after 5.99.

Thank you.  It must not be related to your motherboard since AIDA64 v7.35 works fine with another owner of the same motherboard you've got (MSI Z270 Tomahawk).

[Selim Gürsu]

13 minutes ago, Fiery said:

Thank you.  It must not be related to your motherboard since AIDA64 v7.35 works fine with another owner of the same motherboard you've got (MSI Z270 Tomahawk).

Dear admin, I'm a conscientious PC user and pay close attention to both hardware and software. I've tried every method possible; I really, really love AIDA64. That's why I've tried every possible solution. I'd be very grateful if you could solve this problem. Best regards.

[Selim Gürsu]

Dear Admin, I took the kerneld.x64 file from version 5.99 and deleted the kerneld.x64.sys file from version 7.70. I added .sys to the end of the kerneld.x64 file from version 5.99, and the file became kerneld.x64.sys. I copied it to the program's main folder and it's fine now. What I don't understand is that the kerneld.x64 file from version 5.99 doesn't have an extension. In short, is there any harm in using it this way or could it cause the program to malfunction?

By the way, although there is only one nvme driver in version 7.70, there are 2 of them, for your information.

[Fiery]

52 minutes ago, Selim Gürsu said:

Dear Admin, I took the kerneld.x64 file from version 5.99 and deleted the kerneld.x64.sys file from version 7.70. I added .sys to the end of the kerneld.x64 file from version 5.99, and the file became kerneld.x64.sys. I copied it to the program's main folder and it's fine now. What I don't understand is that the kerneld.x64 file from version 5.99 doesn't have an extension. In short, is there any harm in using it this way or could it cause the program to malfunction?

By the way, although there is only one nvme driver in version 7.70, there are 2 of them, for your information.

By using that method you effectively disabled the kernel driver of AIDA64.

As for your NVMe drive, #2 in that context means the secondary thermal diode of the single NVMe SSD you've got.

[Selim Gürsu]

19 minutes ago, Fiery said:

Bu yöntemi kullanarak AIDA64'ün çekirdek sürücüsünü etkin bir şekilde devre dışı bırakmış olursunuz.

 

Wouldn't Aida64 work properly in this case?

Also, it turns out that the problem is the "kerneld.x64.sys" file. Could you please help me find a solution? Thanks.

[Selim Gürsu]

As of now, I got a blue screen error again, and the kerneld.x64 file didn't work either

[Fiery]

19 hours ago, Selim Gürsu said:

Wouldn't Aida64 work properly in this case?

Also, it turns out that the problem is the "kerneld.x64.sys" file. Could you please help me find a solution? Thanks.

The problem is the sensor module of AIDA64 that you can effectively disable by fiddling around with the AIDA64 kernel driver, e.g. by renaming its file   But, since the sensor module consists of a code over 130 thousand (!) lines, it's very difficult to find the exact place that causes the issue, especially since the bug doesn't come up with the issue occurs, but rather it only rears its ugly head when you close AIDA64.  That makes it a _lot_ more difficult to find.

We'd need to reproduce the issue on our own test systems.  But, first we'd need to know which hardware or software component in your system causes the troubles.  And that's where we're stuck since none of the apparent candidates seems to be the one.  Not your motherboard, not the video card.  It could be an external device like an USB-connected peripheral, but we'd need to find out which one first.

BTW, do you have the latest BIOS installed for your motherboard?

[Selim Gürsu]

The BIOS is up to date, and there are no external devices like USB peripherals. Not even speakers.

Keyboard: Razer Cynosa
Mouse: HyperX Pulsefire
That's all.

Can you check what you did when you upgraded from the 5.99 to the 6x version?

I also changed the ram sticks.

[Selim Gürsu]

Installed Programs;

 

[Selim Gürsu]

USB Dump

 

usbdump.rar

[Fiery]

13 hours ago, Selim Gürsu said:

The BIOS is up to date, and there are no external devices like USB peripherals. Not even speakers.

Keyboard: Razer Cynosa
Mouse: HyperX Pulsefire
That's all.

Can you check what you did when you upgraded from the 5.99 to the 6x version?

I also changed the ram sticks.

We've done a lot of changes and improvements between v5.99 and v6.00.  It looks like a minor update, but it wasn't.

[Fiery]

11 hours ago, Selim Gürsu said:

USB Dump

 

usbdump.rar 2.3 kB · 0 downloads

Thank you!  You're right, there're no "interesting" or "suspicious" USB devices connected to your system.

[Fiery]

13 hours ago, Selim Gürsu said:

Installed Programs;

Thank you!

Please try the following:

1) Disable OSD.  If you have it enabled already, you can do that without starting AIDA64 and so triggering the BSoD.  Just navigate to the installation folder of AIDA64 and edit the file you can find there named AIDA64.INI using e.g. Notepad.  Find the following line in the file:

HWMonEnableOSD=1

And update it to:

HWMonEnableOSD=0

Save the file.

2) Start AIDA64.  Press Ctrl+D --> HWMon Modules --> uncheck (untick) ACPI there.

3) Now try to enable OSD and close AIDA64.  See if it triggers the BSoD.

[Selim Gürsu]

I followed your instructions exactly, but unfortunately, I got a blue screen again. It seems there's no other option. I guess I won't be able to use newer versions of AIDA64 anymore.