|
| ||||||||||
| Tags: bsod, eamonm, eset antivirus, sys file, truecrypt, windows vista |
![]() |
| | Thread Tools | Search this Thread |
|
#1
| |||
| |||
| In Windows Vista Eset 4.2.64 shows BSOD with Truecrypt
|
|
#2
| |||
| |||
| Re: In Windows Vista Eset 4.2.64 shows BSOD with Truecrypt
What you have to do is organize Windows to produce absolute memory dumps per the instructions here and replicate BSOD. When completed, condense it and express it to ESET for inspection. You need to suggest the error occurred in your system so that they can develop a patch to fix it either in your system or in other system. I hope that you know how to achieve it. |
|
#3
| |||
| |||
| Re: In Windows Vista Eset 4.2.64 shows BSOD with Truecrypt
As I can say that I didn’t get any issue while using TrueCrypt along with Eset 4.2.58 on Windows Vista. Another thing to say that half of my primary hard drive has been encrypted. But I got the BSOD in .64 version of Eset. I have tried many things like I send it to Eset laboratory for inspection but they didn’t helped at all. Right now I am definitely waiting for an update to Truecrypt hoping that may be it could solve the problem. But my suggestion is trying to mount Truecrypt volumes as removable media. Turn of the Scanning feature to off on both the removal storage as well as networks drives, may be it could stop BSOD. |
|
#4
| |||
| |||
| Re: In Windows Vista Eset 4.2.64 shows BSOD with Truecrypt
As far as I know from the source of Microsoft the Complete memory dump preference does not exist on computers that are operating a 32-bit OS like in your situation Vista and that contain 2 GB or more RAM. A total memory dump accounts each and every one of the contents of machine memory when your computer impedes unpredictably. A whole memory dump possibly will enclose data as of processes that were operating when the memory dump was composed. If you pick the memory dump choice, you ought to encompass a paging file on the boot volume that is adequate to embrace the entire substantial RAM bonus 1 megabyte (MB). |
|
#5
| |||
| |||
| Re: In Windows Vista Eset 4.2.64 shows BSOD with Truecrypt
If you are continuously getting BSOD then I urge you that install the latest version of Eset again and update the new virus signature database. The primary reason behind the BSOD is the cause of enabled verifier. To check it open the command prompt in your Windows vista and type "Verifier /reset". I have been informed BSOD in coincidence with TrueCrypt where dumps piercing to a bug in truecrypt.sys. Lest of continue problems, I'd recommend telling TrueCrypt support on this issue. |
![]() |
|
| Thread Tools | Search this Thread |
| |
Similar Threads for: "In Windows Vista Eset 4.2.64 shows BSOD with Truecrypt" | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Truecrypt hangs due to ESET NOD32. | Jaques Strapp | Windows Security | 4 | 15-03-2012 10:40 AM |
| Why ESET NOD32 Antivirus 5 causes BSOD on reboot. | AliaShaikh | Networking & Security | 6 | 23-11-2011 10:03 AM |
| With ESET EAV 4.2.64 and Truecrypt 7, I get BSOD. | Jagjeet-J | Networking & Security | 10 | 22-11-2011 03:54 PM |
| Windows 7 BSOD after upgrade from Vista | RockeЯ | Operating Systems | 3 | 08-12-2009 12:56 PM |
| Vista BSOD, am unable to shutdown without BSOD, logoff OK | Adele2 | Vista Help | 3 | 29-01-2007 07:59 AM |