MEMORY_MANAGEMENT D1

maki · Jun 24, 2020

The correct BSOD reason cannot be read if MiniDump is set.
After adding the DUMP file to the debugger (Windbg), it can't determine which driver caused the error, it always shows Process: taskhost.
Although my system is integral and functional.
BSOD can occur today, or in a month or two months, and again several times.
MEMORY_MANAGEMENT D1
is a complicated problem because the reason is not physical memory, because the expert has tested and never detected problems.
The new RAM doesn't solve any problems either.
I have 32 GB RAM and the full dump requires 48 GB + DUMP DISK size and then it will show the real process.
I don't have 48 GB of memory because I have a small SSD.

The problem is caused by the Chrome browser, BSOD always occurs only once a day, even when the computer works all the time.
This problem occurs when I have a lot of physical memory and the System does not have enough virtual memory.
The system automatically sets 16-30 GB pagefile.sys and no BSOD occurs.
But the system slows down.

32 GB RAM + 30 GB Virtual Memory (Auto) = 62 GB MEMORY

Memory increases when using pages with JavaScript - scrrol large page / wall = HIGH RAM (Facebook, Youtube)

maki · Jun 24, 2020

https://i.postimg.cc/Y250Y3R7/Screen-Shot-06-24-20-at-02-55-PM.jpg

x BlueRobot · Jun 24, 2020

Please follow these posting instructions - Blue Screen of Death (BSOD) Posting Instructions - Windows 10, 8.1, 8, 7 + Vista

maki · Jun 24, 2020

Thanks for fedback

Can you learn how to read DUMP files yourself.
I would like to gain knowledge myself ...
There are many guides ... but commands are missing.
!analyze -v
this is a modest command, which are advanced commands.
At Microsoft a few years ago a specialist in public gave a long command, it was very good! the program downloaded a few-gigabyte data folder, it took a long time, but then EVERY (!) DUMP file was read correctly!

and these SRVs don't download all the data.
Please, know how to download this multi-gigabyte folder with various files?

x BlueRobot · Jun 24, 2020

Please follow the posting instructions and we'll be able to help you.

If you want to learn how to debug yourself, then I would suggest that you enquire about our academy - Sysnative BSOD Academy

maki · Jun 24, 2020

I started collecting log, but each time the computer restarts before completion and shows BSOD.
Only this BSOD is strange. First it shows the blue screen and then there is no BSOD but the desktop with artifacts in the upper left corner!
Run again - the same problem...

maki · Jun 24, 2020

Sterowniki tego urządzenia nie są zainstalowane. (Kod 28)

Nie został wybrany sterownik dla zestawu lub elementu informacji o urządzeniu.

Aby znaleźć sterownik dla tego urządzenia, kliknij opcję Aktualizuj sterownik.

(ERROR BSOD)

ACPI\PNP0A0A
*PNP0A0A

AND

ASMedia USB3.0 eXtensible Host Controller (Error BSOD)

AND

6.1.7601.17514 21-06-06 Microsoft (Error) miniport WAN (Error BSOD)
Wyłączono sterownik (usługę) dla tego urządzenia. Możliwe, że tę funkcję zapewnia sterownik alternatywny. (Kod 32)

axe0 · Jun 24, 2020

maki said:
At Microsoft a few years ago a specialist in public gave a long command, it was very good! the program downloaded a few-gigabyte data folder, it took a long time, but then EVERY (!) DUMP file was read correctly!

and these SRVs don't download all the data.
Please, know how to download this multi-gigabyte folder with various files?

I suspect this command downloaded symbol installer files or packages. I've installed a couple of symbol installers for Windows 7, 8 and 10 a few years ago, I ended up with a symbols folder somewhere in the 70GB.

SRV allows you to point to the server where you want to download symbols from and it will download the symbols needed for you to look into the dump. It does not download all symbols because that's simply too much.

x BlueRobot · Jun 24, 2020

Google Translation:

Code:

The drivers for this device are not installed. (Code 28)

No driver selected for the device information set or item.


To find a driver for this device, click Update Driver.


(ERROR BSOD)

ACPI \ PNP0A0A
* PNP0A0A

AND

ASMedia USB3.0 eXtensible Host Controller (Error BSOD)


AND

6.1.7601.17514 21-06-06 Microsoft (Error) miniport WAN (Error BSOD)
The driver (service) for this device has been disabled. It is possible that this feature is provided by an alternative driver. (Code 32)

Where did this message come from?

Could you please zip any files found in this directory:

Code:

%systemroot%\Minidump

maki · Jun 24, 2020

Shows two unknown devices, cannot find drivers.
I have all the drivers downloaded from the manufacturer's website ASUS.COM
Z97-PRO

Minidump 0 bytes / No files

xilolee · Jun 24, 2020

Try the sfc and dism tools.

maki · Jun 24, 2020

I have always used sfc /scannow and SFCFix and Windows Repair
Repair Reparse Poind
Not require reapir - ZERO ERRORS
Repair Environment Variables - ZERO ERROS
but it always shows that the system does not require repair.
ZERO ERRORS
The system is stable, does not freeze.

maki · Jun 24, 2020

Drivers are missing from the manufacturer's website:
Z97-PRO Driver & Tools | Płyty główne | ASUS Polska
Windows 7 64-bit

ACPI PNP DRIVER
Z97-PRO

maki · Jun 24, 2020

I found the drivers here:
ASUS Z97-PRO Probe II Sense Драйвер v.1.0.1.0 скачать бесплатно для Windows 8.1 (32/64-bit), 8 (32/64-bit), 7 (32/64-bit)
I installed the drivers, I had to restart my computer.
I checked again and it still shows [error 28]

maki · Jun 24, 2020

xilolee · Jun 24, 2020

Try the command

Code:

Dism /online /cleanup-image /restorehealth

Post its result.

maki · Jun 24, 2020

Microsoft Windows [Wersja 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Wszelkie prawa zastrzeżone.

C:\Windows\system32>Dism /online /cleanup-image /restorehealth

Wersja narzędzia do obsługi obrazu wdrażania
i zarządzania nim: 6.1.7601.24499

Wersja obrazu: 6.1.7601.24499

Błąd: 87

Opcja restorehealth nie została rozpoznana w tym kontekście.
Więcej informacji można znaleźć w pomocy.

Plik dziennika narzędzia DISM można znaleźć w folderze C:\Windows\Logs\DISM\dism.log

C:\Windows\system32>

maki · Jun 24, 2020

On Windows 7 and earlier, the DISM command isn’t available.

xilolee · Jun 25, 2020

Yup, sorry, I didn't re-read your 13th post.

maki · Jul 4, 2020

For a long time there was no BSOD.
One driver cannot be installed fully.
After installation, "restarting computer required", except that it always asks after each startup my PC (infinite installation loop without success).

Code:

na System zgodny ze standardem Microsoft ACPI
AMDA00 Interface
Vers. 1.0.1.0 17-03-14
ASUSTeK Computer Inc.

System Windows nie może zainicjować sterownika urządzenia dla tego sprzętu. (Kod 37)

Aby zmiany dokonane dla tego urządzenia zostały wprowadzone, musisz ponownie uruchomić komputer.

This is the only driver on the internet, there is no other.

Code:

: Kontroler osadzony zwrócił dane mimo braku żądania danych. Być może system BIOS próbuje uzyskać dostęp do kontrolera osadzonego bez synchronizacji z systemem operacyjnym. Te dane zostaną zignorowane.

MEMORY_MANAGEMENT D1

Member

Member

Administrator

Member

Administrator

Member

Member

Administrator, BSOD Academy Instructor, Security Analyst

Administrator

Member

Moderator

Member

Member

Member

Member

Moderator

Member

Attachments

Member

Moderator

Member

Administrator,
BSOD Academy Instructor,
Security Analyst