Computer crashes with "DPC Watchdog Violation" since upgrading to VC 1.21
Open source disk encryption with strong security for the Paranoid
Brought to you by:
idrassi
Menu
▾
▴
Hello!
A few days ago I've upgraded my two computers from Veracrypt 1.19 (I think) to 1.21. While one of them works like a charm the other one crashes after each wake up from suspend to RAM with "DPC Watchdog Violation". This is reproducible. Since it is a HTPC with not many programs on it and no changes except automatical Windows 8.1 updates (ccrudial only) I suspect Veracrypt. I've updated all drivers I could lay my hands on but it didn't help.
Configuration:
Gigabyte 880GA-UD3'H Rev. 2.1 Board
AMD Athlon II X4 640 4x 3.00GHz Processor
2 x 4 GB Kingston Value RAM
Samsung 830 SSD, 128 GB, Windows 8.1 Pro, encrypted system disk
3WARE 9650-12-ML Controller with
7 x WD HDD (4-6 TB), all completely encrypted, NTFS, all system favorites
Everything worked before changing to Veracrypt 1.21. Since then reproducable watchdog crashes immediately after waking up from STR or during longer copy sessions.
Has anyone got an idea what is wrong?
wafranyofl
Last edit: wafranyofl 2017-08-08
Hi,
The first thing to do on the machine that has the problem is to upgrade to the latest version 1.22-BETA3 available at https://sourceforge.net/projects/veracrypt/files/VeraCrypt%20Nightly%20Builds/: some changes has been done at the driver level for some special cases and we can see if it the issue is caused by them or not.
If the issue persists, we will need the Windows kernel-mode memory dump that is generated by Windows for this crash. Usually it is created by default but it can be configured as described here: https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/enabling-a-kernel-mode-dump-file. You can encrypt it using VeraCrypt PGP key and then send it by email or post it here.
Thank you for your help.
Thanks for your quick answer, Mounir. VC 1.22beta3 didn't solve my problem. To which e-mail address shall I send the memory.dmp? It has about 85 MB even compressed with Winrar - over 400 uncompressed. That's usually rejected as an e-mail attachment.
wafranyofl
You can encrypt the file with VeraCrypt PGP key (using gpg4win for example) and upload it to any cloud service.
Otherwise, you can contact me by email on veracrypt@idrix.fr and I will give you details on how to share it privately.
Meanwhile I was able to straighten some things out:
My memory most likely didn't serve me well when I stated that Veracrypt 1.19 ran seamlessly on my HTPC with a 3ware 9650-12-ML. After I'd installed this controller I had to copy/move/verify many TB of data so that automatic stand by was disabled for a long time. Veracrypt ran properly on my 2nd PC without 3ware controller then.
Meanwhile I had installed Windows 10 Pro on this 2nd PC. Stand by worked like a charm with Veracrypt 1.21. After installing a 3ware 9650-12-ML and driver on this computer, too, I have the same problem like on my HTPC. Both PCs show a BSOD with "DPC Watchdog Violation" and sometimes other error messages after waking up from STR or STD and even during copy actions. To make sure the problem results from the combination Veracrypt/3ware 9650 I reinstalled Windows 8.1 Pro and Veracrypt 1.19. The same result. It seems that the BSODs narrow down to the combination Veracrypt with 3ware 9650, driver version 3.00.05.056 - 9.5.4 and Firmware 9.5.4.
Now I've got 2 Computers with over a dozen Veracrypt-encrypted HDDs here which crash everytime after waking up from stand by and sometimes even during work. Mounir sent me an e-mail that my memory dump was received on their cloud server. But he didn't answer my emails anymore since I've uploaded the wanted memory.dmp which was more than half a year ago. I don't know what to do now. It would be really great if one of the staff could have a look at my memory dump and tell me how to solve my problem which has become rather serious in the meantime.
wafranyofl
Hello? Is someone here and can help me?
wafranyofl
Last edit: wafranyofl 2018-03-21
Obviously not. Thanks for leaving me alone with 14 encrypted HDDs/SSDs and 2 computers that crash each time when waking up from stand by.
I know veracrypt is free software and I don't expect support as if I had paid for it. But first telling me "this is serious" and asking for a memory dump (which I uploaded) and then doing exactly nothing is not what I had in mind when asking for help.
wafranyofl
I wouldn't presume to speak for anyone on the development team, but as a slightly more than casual observer, I quickly discovered a couple of things. Firstly, one of the most common causes I've seen cited for "DPC Watchdog Violation" errors (independent of VeraCrypt) is outdated device drivers. This is significant because the drivers you are using (v3.00.05.056-9.5.4) are dated 08-11-2011, pre-dating the initial release of Windows 8 by over a year, and the OS compatibility list on the Broadcom website (who bought LSI and 3ware) does not include Windows 8. So you're already running on borrowed time, just as I am with a couple of my own devices and drivers. Compatibility with your version of Windows isn't even officially claimed by Broadcom, and cross-compatibility issues with other software such as VeraCrypt introduce further unknowns into the mix. In case your information conflicts with mine, here's my source:
https://www.broadcom.com/support/knowledgebase/1211161497882/9.5.4-codeset
That said, you might have one last hope to extend your usage of this relatively old product even further, and it concerns something that has occasionally caused problems with VeraCrypt in certain contexts, and it caught my attention when I read a little about fixing DPC Watchdog Violation errors. Have a look at Fix 2 on this page:
http://www.incrediblelab.com/dpc-watchdog-violation-fixed/
Enigma2Illusion occasionally prescribes disabling fast startup as a potential fix for certain types of problems with VeraCrypt, so that item caught my eye when mentioned in the context of DPC Watchdog Violations completely unrelated to VeraCrypt. Try it if it applies, and otherwise consider getting hardware with drivers that are more up to date.
Dear Gary, thanks for your answer.
I know the drivers are old justs like the controllers. But they work seamlessly even with Windows 10 Pro. I've installed new drivers which are compatible with Windows 8 meanwhile. The codeset is 9.5.5.1 instead of 9.5.4, the firmware is v4.10.00.027, the driver v5.01.00.058. They were released during 2012-2013 and are compatible with Windows 8.
https://www.broadcom.com/site-search?q=9650+firmware - Zip-Files 3 and 4
Fix 2 (fast startup off) leads to shut down instead of stand by - at least one of the computers booted from scratch at the first try. The other I haven't tested yet. Since both computers need to wake up from stand by without me having to enter the password for Veracrypt each time this isn't a solution. My computers shut down only if I tell them to. The default action for them is to go into stand by (Suspend to RAM) when the idle time of 15 minutes is expired.
I bought two 3ware/LSI 9650SE-12ML used for under 200 US$. They do everything I need and more under Windows 8.1 and 10 except the described problem with waking up from stand by in combination with Veracrypt. If I'd buy newer versions of this controller (which I technically don't need) I'd have to pay estimated additional 1000 US$ or more. That's more than I can afford. Thus it would be better to change the disk encryption. But Veracrypt, too, does exactly what I need and I'm used to it coming from True Crypt. Recrypting 14 HDDs (50% 3 TB, 50% 6 TB) additionally would cost months of encrypting, copying and verifying.
I guess I'm stuck as long as nobody has a look at my memory dump and finds a solution.
wafranyofl
Last edit: wafranyofl 2018-06-11
wafranyofl -- I'm glad you were able to find newer drivers, but it's a shame that it still didn't cure your problem. I agree that with the price of replacement hardware of this class, finding a way to extend the life of your current controller card is a worthy enough objective. So with that in mind, I do have a couple of suggestions that might help. As you probably know, there's quite a bit of granularity accessible in the advanced power settings for Windows, and I suggest taking advantage of it. There are a couple of settings directly relating to your disk subsystem, which seems to be the likely source of conflict between Windows sleep mode and VeraCrypt. Since your controller uses the PCI Express bus, I'm thinking that if you leave the PCI Express link fully powered, even while the rest of the computer goes asleep, this might eliminate those nasty DPC Watchdog Violation errors. You might also have to leave the drives spinning (another setting) during sleep mode. Even if you have to leave the drives and controller fully powered, obviously it reduces the power savings of sleep mode, but it might be an acceptable tradeoff if it actually works.
My other suggestion is sort of the flip side of my first suggestion, that is, disabling sleep mode entirely but using some of the individual settings to shut down various parts of the computer after an idle period. I hope one of these methods helps you get some of the power savings you're shooting for. In the words of the great Kermit the Frog, it's not easy being green :)
Hello Gary. I'm really glad that finally someone tries to help me because I've run out of ideas. I'll test your suggested settings an let you know the result. As far as I remember there is a way to exclude a single device from power saving, too. I wouldn't mind if PCI express or the controller resumes power. Better than having two computers running 24/7.
wafranyofl
Last edit: wafranyofl 2018-06-13
Meanwhile I've tried everything you suggested and made a clean install of Windows 10 on my HTPC. As soon as Veracrypt and the driver of the 9650SE-12ML controller come together the computer crashes with a BSOD and "DPC watchdog violation". I give up. As soon as I can afford it I'll dump the two 9650 and buy up-to-date controllers. A costly experience.
Thanks again for your help, Gary. At least one glimpse of hope - other than the nonexistent "support" of Idrix.
wafranyofl