Error volmgr 45

Добрый день. Имеется Windows Server 2019 Standard. Установлены все обновления.

Добрый день. Имеется Windows Server 2019 Standard. Установлены все обновления.

Установлено 2 NVMe диска Samsung Enterprise PM9A3

После добавления зеркала в управлении дисками при каждой перезагрузке генерируется 2 сообщения об ошибке

Volmgr 45 Не удалось загрузить драйвер аварийного дампа

и 1 сообщение

Volmgr 46 Не удалось инициализировать аварийный дамп

Файл дампа памяти не создается

Из того, что проверено:

1. память

2. chkdsk c: /f /r

3. sfc /scannow

Защита ресурсов Windows не обнаружила нарушений целостности.

4. DISM /Online /Cleanup-Image /ScanHealth

Повреждение хранилища компонентов не обнаружено

5. файл подкачки выставлен: «Автоматически выбирать объем файла подкачки» (пробовал разные варианты. вручную 10-20ГБ, по выбору системы и т.п. без изменений)

6. проверены все варианты дампов памяти: малый дамп, дамп памяти ядра и т.п. выставлен «Автоматический»

Дальнейшие действия:

1. разворачиваю резервную копию этого сервера на виртуальной машине с
дисками !! SCSI !!
ошибок нет.

2. если развернуть на виртуальной машине с NVMe дисками, снова ошибки и не создается дамп.

3. создал чистый сервер на виртуальной машине с NVMe диском. установил обновления. ошибок нет.

преобразовал диск в динамический и после перезагрузки те же самые ошибки. 2 Volmgr 45 и 1 Volmgr 46.

дампы памяти не создаются

судя из всего описанного, при использовании динамического NVMe диска в Server 2019 возникают проблемы с volmgr и созданием аварийного дампа.

в Server 2016 Standard такой проблемы не было. до этого использовался в похожей конфигурации. и проверил специально, как описано в п.3

конфигурация сервера на всякий случай, хотя, видимо дело не в железе:

Ryzen 9 5950X

Asus PRO WS 565-ACE

128 GB DDR4 ECC

2xNVMe Samsung Enterprise PM9A3

есть ли какое-то исправление для системы? может кто-то помочь?

P. S.

нашел аналогичную проблему вот здесь:

https://social.technet.microsoft.com/Forums/en-US/75f51056-f724-486e-8212-33c0ff94f168/windows-server-2019-crash-dump-initialization-failed-on-mirrored-disk?forum=ws2019

решение не нашел.

Ключевое слово 0x800000000000000
[ОраСистема] 2018-06-27T08: 01: 40.425584800Z

Устройство HarddiskVolume3

0000000001000000000000002D0004C003200000BB0000C00000000000000000000000000000000000

Дорожки:

В соответствии с

0000: 00000000 0000001 00000000 C004002D
0010: 00002003 C00000BB 00000000 00000000
0020: 00000000 00000000

Байт

0000: 00 00 00 00 01 00 00 00……..
0008: 00 00 00 00 2D 00 04 C0….- .. À
0010: 03 20 00 00 BB 00 00 C0 .. «.. UN
0018: 00 00 00 00 00 00 00 00……..
0020: 00 00 00 00 00 00 00 00……..

Проблема вроде решена, проблема была в моем третьем жестком диске, я предварительно отформатировал его с помощью утилиты Acronis. Сейчас отформатировал встроенной утилитой W10, вроде теперь все работает. Два дня в течении которых глюков не было.

Проблема снова горячая

Добрый день.
Попробуйте полностью выключить компьютер. Нажмите «Пуск», «Завершение работы» и «Shift», «Завершение работы.

Источник: https://answers.microsoft.com/ru-ru/windows/forum/all/pc/ef8b0487-3c36-461e-aad7-f3e010d8b358

Just to share my 3-day battle with Windows 7 32bit Pro after it was installed on the Kingston V+100E Self-encrypting SSD 64GB.

To be fair, the problem has little to do with the Kingston SSD actually. There may be incompatibility with Truecrypt 7.1 & Self-encrypting SSD, or it could be old registry entries left-over from my old encrypted HDD but I didn’t investigate further since I’ve solved my hibernation problem.

Update at the end of this article!

*******************************

System:

OS: Win7 32bit Pro (New install, not upgrade)

Laptop: Fujitsu T4215 with CPU upgraded to Intel T7200

HDD: WD Scorpio Black 320GB (Truecrypt 7.1 System FDE) -> Kingston V+100E 64GB (Self-encryption)

Drivers: (All updated to latest from manufacturer)

********************************

Everything seems to work well until I run Easy Transfer to transfer my account from my old HDD to the new SSD. My old WD Scorpio Black was encrypted using Truecrypt 7.1 so there were active Truecrypt registry entries which I’m not aware of & few people seem to know about. Google it & you would’t find many entries if any.

Hibernation will always fail with black screen. When KB/Mouse is touched, the login screen is shown. Event Viewer will show Event ID 45 Error caused by volmgr on deviceharddiskvolume2 (which is my C:). What’s cryptic is the error is a crash dump driver error. What has crash-dumping in volmgr.sys got to do with hibernation?

A lot in fact, after kernel-mode drivers had crashed or unloaded, the only way the NT Kernel could do stuff is through special filters apparently. So to activate Hibernation, the Kernel has to unload everything & dump everything in RAM to HDD. What if you’re running Bitlocker or Truecrypt, which are software-based encryption?

The Kernel has to filter the RAM data thru these small programs so the Hibernation or Crash dumps are encrypted as well, else there’ll be a security risk. dumpfve.sys for Bitlocker & truecrypt.sys for Truecrypt 7. Unfortuntately I don’t see this documented anywhere. (I did not search SourceForge though.) I found out when I was hunting in the registry.

This registry key is where I found the offending entry.

HKLMSYSTEMCurrentControlSetControlCrashControl -> DumpFilters

In it, I found “dumpfve.sys” & “truecrypt.sys”. Now I did not install Truecrypt in the new system so the only way is thru’ Easy Transfer.

OK, fine, so I install Truecrypt 7.1 to make sure the proper files are installed. But after rebooting, Windows BSOD & I couldn’t see any crash dump! It may be that active Truecrypt registry is still there thinking the SSD was encrypted. Well I can’t have that! So I did a System Restore & booted up. I then remove the truecrypt.sys entry in all Registry keys, adjust my pagefile size, enabled crash dump 128KB & enabled hibernation with “-size 100”.

Hit the Hibernation button & it WORKS!!!

After that, whatever changes I did to pagefile.sys & crash dump size did not affect Hibernation.

So for those of you who have hibernation problems with Event ID 45 from volmgr. Check your crashdump filter.

Now I still need Truecrypt to access the old encrypted WD Scorpio Black, so what I did was to install Truecrypt in “Portable” mode & run the .exe files instead of an installation. Done!

Update (19/3/2012):

Recently I cleaned the registry of all entries with Truecrypt & install the latest 7.1a version & Windows did not BSOD so I’m a happy camper again. Seems like Truecrypt doesn’t leave many entries in Windows itself, which is a GOOD thing!

Windows 10: hibernate problem event 45 volmgr

Discus and support hibernate problem event 45 volmgr in Windows 10 Performance & Maintenance to solve the problem; whenever I try to hibernate my PC, I get the event 45 volmgr error in event logger, and the system returns to lock screen.

There are two ways to…
Discussion in ‘Windows 10 Performance & Maintenance’ started by XavierXing, Dec 29, 2019.

  1. hibernate problem event 45 volmgr

    whenever I try to hibernate my PC, I get the event 45 volmgr error in event logger, and the system returns to lock screen.

    There are two ways to reproduce:
    1. Manually clicking «hibernate» in power menu;

    2. Automatically as usually happens after the system sleeps for the prespecified time. This is more serious, since normally it will go to hibernation atuomatically after sleeping for a while, but now it wakes to try to hibernate and remains awake until battery is depleted.

    Below is the error information

    -<Event xmlns=»http://schemas.microsoft.com/win/2004/08/events/event«>
    -<System>
    <Provider Name=»volmgr» />
    <EventID Qualifiers=»49156«>45</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreatedSystemTime=»2019-12-29T07:49:43.012772800Z» />
    <EventRecordID>1011</EventRecordID>
    <Channel>System</Channel>
    <Computer>XavierMiBook</Computer>
    <Security />
    </System>
    -<EventData>
    <Data>DeviceHarddiskVolume4</Data>
    <Binary>0000000001000000000000002D0004C003200000100000C000000000000000000000000000000000</Binary>
    </EventData>
    </Event>

    :)

  2. Cannot sleep/hibernate because of Error 45 Volmgr

    Hello,

    I’m having an irritating problem on Windows 10 x64 version 1803 since a couple of months (I can’t remember exactly when it started). It often fails to sleep/hibernate, the screen turns black but sleep/hibernation fails and I find myself back to the lockscreen.

    It turns out that every time this happens I can see the following error in the event viewer : Event 45, volmgr, The system could not successfully load the crash dump driver.

    My online researches led me to problems linked to Truecrypt full-disk encryption. I use Veracrypt but not its full-disk encryption feature and I don’t have any key other than dumpfve.sys in HKLMSYSTEMCurrentControlSetControlCrashControl.

    If I kill most of the programs that seem to consume resources the computer will eventually sleep/hibernate but I couldn’t find any obvious pattern (like killing this program and that program would do the trick).

    Any ideas?

    Thanks!

  3. Windows 10 Hibernate problems

    I suggest you to follow the methods provided below and check if it helps.

    I suggest you to run the Power troubleshooter by following the steps below and check if for any power components change status.

    • Press Windows logo key on the keyboard, type troubleshooting and select the top most search result.
    • Click on View All from the left side panel of the window.
    • Select Power from the options, click on Advanced option and check Apply repairs automatically option.
    • Follow the on screen instructions and wait for the troubleshooting to complete.
    • Check for the missing/corrupted power component status of the troubleshooter, close the window and check if the issue is resolved.

    You can follow the step by step guide to
    enable hibernate option in windows 10.

  4. hibernate problem event 45 volmgr

    Windows 10 1809 — slow shutdowns / volmgr errors (Event ID 161) since update

    Here’s some more info —

    Without making any changes, the machine has just quickly shut down three times. There were no volmgr events logged after I rebooted the machine.

    However, I went to reboot (as opposed to shutdown) the machine and it took ages to shut down and then
    did not reboot.

    I also got the volmgr event again during the boot up process.

Thema:

hibernate problem event 45 volmgr

  1. hibernate problem event 45 volmgr — Similar Threads — hibernate problem event

  2. BSoD: Error volmgr Event ID: 161, Error volmgr Event ID: 162, Critical Kernel-Power Event…

    in Windows 10 Gaming

    BSoD: Error volmgr Event ID: 161, Error volmgr Event ID: 162, Critical Kernel-Power Event…: My pc has suddenly begun getting BSoD. I’ve tried updating all my drivers, running memory diagnostics, and I’ve done a fresh install of Windows, but the problem persists.Log Name: System Source: volmgr Date: 01/02/2023 17.17.40 Event ID: 161 Task Category: None Level: Error…
  3. BSoD: Error volmgr Event ID: 161, Error volmgr Event ID: 162, Critical Kernel-Power Event…

    in Windows 10 Software and Apps

    BSoD: Error volmgr Event ID: 161, Error volmgr Event ID: 162, Critical Kernel-Power Event…: My pc has suddenly begun getting BSoD. I’ve tried updating all my drivers, running memory diagnostics, and I’ve done a fresh install of Windows, but the problem persists.Log Name: System Source: volmgr Date: 01/02/2023 17.17.40 Event ID: 161 Task Category: None Level: Error…
  4. Hibernate/sleep problem, external hdd, event 45 volmgr

    in Windows 10 Gaming

    Hibernate/sleep problem, external hdd, event 45 volmgr: So google tells me this problem has existed for like 15 years. Neato.Firstly: This problem has something to do with external harddrives! Every internet forum seems to be baffled by what the root of this is. This started for me after I replaced/upgraded my external harddrive!!…
  5. Hibernate/sleep problem, external hdd, event 45 volmgr

    in Windows 10 Software and Apps

    Hibernate/sleep problem, external hdd, event 45 volmgr: So google tells me this problem has existed for like 15 years. Neato.Firstly: This problem has something to do with external harddrives! Every internet forum seems to be baffled by what the root of this is. This started for me after I replaced/upgraded my external harddrive!!…
  6. Hibernate/sleep problem, external hdd, event 45 volmgr

    in Windows 10 BSOD Crashes and Debugging

    Hibernate/sleep problem, external hdd, event 45 volmgr: So google tells me this problem has existed for like 15 years. Neato.Firstly: This problem has something to do with external harddrives! Every internet forum seems to be baffled by what the root of this is. This started for me after I replaced/upgraded my external harddrive!!…
  7. Volmgr 45 on Dell xps 9500

    in Windows 10 Gaming

    Volmgr 45 on Dell xps 9500: I’m getting volmgr 45 error on my pc,When i checking error details, it says error volume2 parttion on hdd. It was getting this error on my pc running Windows 10 pro, I updated pc to Windows 11 pro. but this same error going on. I searched many topic on internet but not fixed…
  8. Volmgr 45 on Dell xps 9500

    in Windows 10 Software and Apps

    Volmgr 45 on Dell xps 9500: I’m getting volmgr 45 error on my pc,When i checking error details, it says error volume2 parttion on hdd. It was getting this error on my pc running Windows 10 pro, I updated pc to Windows 11 pro. but this same error going on. I searched many topic on internet but not fixed…
  9. event 161, volmgr

    in Windows 10 Ask Insider

    event 161, volmgr: I bought this asus GL502VSK a few years ago and out of the box it had issues where during gaming it would freeze and the restart. As of the new Path of Exile league it is doing it even more. I did some research and pulled this event code. I flashed the bios as mine was…
  10. Windows keeps crashing (Volmgr event 161)

    in Windows 10 BSOD Crashes and Debugging

    Windows keeps crashing (Volmgr event 161): Hello everyone,

    Since a few days I have a lot of issues with my Windows 10 PC. When I’m using my PC it randomly restarts out of nowhere. I get no warning and I don’t do heavy tasks when the error occurs. I don’t think that there is a consistency either. For example I just…

Users found this page by searching for:

  1. volmgr error 45


Windows 10 Forums

(As per the advice on the submission form I posted this on /r/techsupport/ a month ago, but did not receive any replies so am trying here, I hope that’s OK!)


If I attempt to hibernate my computer the screen switches off but the computer keeps running. If I move the mouse the screen wakes up and the computer has locked but not shut down. If I look in event viewer, an error is logged in volmgr, event ID 45, «The system could not sucessfully load the crash dump driver» for DeviceHarddiskVolume2 (C:).

If I reboot the computer but do not log in I can hibernate. After logging on, the problem arises.

Having read lots and lots of articles covering this error message online (going back as a far as XP in some cases!) I’m not really sure what might be causing this issue. It was fine prior to installing the 2004 update.

I can also trigger the error without hibernating by going into «Start-up and Recovery» and changing the «System Failure», «Write debugging information» dropdown (changing this to any setting other than «(none)» causes the error to be logged).

For what it’s worth I’m running a Core 2 Quad machine with spinning rust hard disk drives. I have set my page files to use a separate hard disk drive D: as otherwise Windows 10 nearly constantly pegs C: at 100% HDD usage. With the page file on a separate drive it seems to perform much better.

Things I have tried:

  • Run the Power troubleshooter.

  • sfc scannow and DISM /Online /Cleanup-Image /CheckHealth

  • Reinstalled Windows with an in-place upgrade.

  • Reset virtual memory settings to «System managed» on all drives.

  • Checked DumpFilters in HKLMSYSTEMCurrentControlSetControlCrashControlto make sure truecrypt.sys wasn’t listed (it wasn’t, I’ve never encrypted the drive).

  • Added a value to set IgnorePagefileSize to 1 under the above registry key.

  • Recreated the hiberfile.sys with powercfg hibernate off then powercfg hibernate on, sometimes with an explicitly-set size to ensure it’s large enough for my 4GB RAM.

  • Reinstalled Intel Rapid Storage Technology (I’m not using RAID/mirroring but as there was an old version installed I thought it worth updating to the latest version).

  • Disabled as many startup applications as possible (though with this not fixing the issue I’ve switched the ones I used back on: 7+ Taskbar Tweaker, Catalyst Control Center Launcher, Cortana, CrossHair.exe, Intel’s «Delayed launcher» (for Intel Rapid Storage Technology), Microsoft OneDrive, Windows Security notification icon and AudioScrobbler).

Interestingly after installing Version 2004 and having this problem for a while I thought I’d reinstall to see if it would fix the issue, but it then refused to install due to a compatibility issue with my system. Digging through the compatibility testing logs this indicated OneDrive was to blame so I uninstalled OneDrive (and still had the hibernation problem) before installing 2004 again. With OneDrive removed it installed fine but the hibernation problem remained.

As the issue seems to relate to a disk drive then the only known issue I have with the drive is that it has a 3TB capacity however as my PC is older and uses a traditional BIOS rather than UEFI I can only use the first 2TB of it as it’s formatted for MBR instead of GPT. This hasn’t been a problem in the past beyond being a bit of a waste of available space, though!

This is a pretty long shot in the dark but I’ve tried everything I could find online and was wondering if someone else might have had the same issue and found a way to resolve it…

Понравилась статья? Поделить с друзьями:
  • Error void type not allowed here
  • Error void is not a pointer to object type
  • Error vocaloid текст
  • Error vocaloid lyrics
  • Error vmerror принтер