Two Errors

[Jim]

I have been trying to resolve two errors with no success. Tried
everything I could find from Google but nothing seems to work.

I get these two errors each time I boot:

Event 45, volmgr
Crash dump initialization failed!

(5 seconds later)

Event 46, volmgr
The system could not sucessfully load the crash dump driver.



Windows 7 Ultimate x64 16gb ram
Small memory dump (256k) Tried:Kernel, Complete.
Hyberfil.sys -off (tried on and off no difference)
2Gb page file (tried every page file setting)
1 Hard drive with two partitions: 1-System and Programs, 2- Data

I read that this problem had something to do with 'Mirroring' but no
raid driver enabled.

Bios - everthing seems to be set properly.


If you have an idea on how to fix this I would greatly appeciate your
input.

Thanks!
Jim

 

[Jason]

I have been trying to resolve two errors with no success. Tried
everything I could find from Google but nothing seems to work.

I get these two errors each time I boot:

Event 45, volmgr
Crash dump initialization failed!

(5 seconds later)

Event 46, volmgr
The system could not sucessfully load the crash dump driver.



Windows 7 Ultimate x64 16gb ram
Small memory dump (256k) Tried:Kernel, Complete.
Hyberfil.sys -off (tried on and off no difference)
2Gb page file (tried every page file setting)
1 Hard drive with two partitions: 1-System and Programs, 2- Data

I read that this problem had something to do with 'Mirroring' but no
raid driver enabled.

Bios - everthing seems to be set properly.


If you have an idea on how to fix this I would greatly appeciate your
input.

Thanks!
Jim

I believe that a large dump goes into the page file. If it's only 2GB and
you have 16GB of memory that might be the problem, except you said you
tried every setting (including letting Windows manage it?).

 

[Jim]

I believe that a large dump goes into the page file. If it's only 2GB and
you have 16GB of memory that might be the problem, except you said you
tried every setting (including letting Windows manage it?).

Yes, I let Windows manage it but it didn't help. I think it is related
to the 16gb of memory but I'm not sure how though.

Jim

 

[Jim]

Yes, I let Windows manage it but it didn't help. I think it is related
to the 16gb of memory but I'm not sure how though.

Jim

I get the same error even with memory dump set to 'none'

Jim

 

[Paul]

Yes, I let Windows manage it but it didn't help. I think it is related
to the 16gb of memory but I'm not sure how though.

Jim

Any chance you made a registry change somewhere related to this ?

Note that there is some option, where you can do a crash dump
to disk, rather than a crash dump elsewhere.

So rather than being a solution, I'm showing this as a potential workaround.
Who knows, maybe you'll find something interesting in the registry, near
this key...

http://blogs.msdn.com/b/ntdebugging...rive-when-capturing-a-system-memory-dump.aspx

"This feature is enabled by setting the following registry value:

Location: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CrashControl

Name: DedicatedDumpFile

Type: REG_SZ

Value: A dedicated dump file together with a full path, such
as D:\dedicateddumpfile.sys

HTH,
Paul

 

[Jim]

Any chance you made a registry change somewhere related to this ?

Note that there is some option, where you can do a crash dump
to disk, rather than a crash dump elsewhere.

So rather than being a solution, I'm showing this as a potential workaround.
Who knows, maybe you'll find something interesting in the registry, near
this key...

http://blogs.msdn.com/b/ntdebugging...rive-when-capturing-a-system-memory-dump.aspx

"This feature is enabled by setting the following registry value:

Location: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CrashControl

Name: DedicatedDumpFile

Type: REG_SZ

Value: A dedicated dump file together with a full path, such
as D:\dedicateddumpfile.sys

HTH,
Paul

I fixed the problem. I took a good look at the registry and found that
HKLM\SYSTEM\CurrentControlSet\Control\CrashControl had an entry
'Truecrypt.sys'. I remembered that several months ago I tried out
Truecrypt OS encryption for a few days but it was a pain so I removed
the encryption. I guess Truecrypt left that entry which probably
refers to a Truecrypt volume that no longer exists. I deleted the
entry and the errors are now gone. Finally!

 

[Ed Cryer]

I fixed the problem. I took a good look at the registry and found that
HKLM\SYSTEM\CurrentControlSet\Control\CrashControl had an entry
'Truecrypt.sys'. I remembered that several months ago I tried out
Truecrypt OS encryption for a few days but it was a pain so I removed
the encryption. I guess Truecrypt left that entry which probably
refers to a Truecrypt volume that no longer exists. I deleted the
entry and the errors are now gone. Finally!

Well done. Have you got any disk volume labelled as True crypt-type? If
so I don't think it's been changed back after the uninstall. You'll have
to do it manually now.

Ed

 

[Jeff Barnett]

Jim wrote, On 3/24/2013 5:06 PM:

I have been trying to resolve two errors with no success. Tried
everything I could find from Google but nothing seems to work.

I get these two errors each time I boot:

Event 45, volmgr
Crash dump initialization failed!

(5 seconds later)

Event 46, volmgr
The system could not sucessfully load the crash dump driver.



Windows 7 Ultimate x64 16gb ram
Small memory dump (256k) Tried:Kernel, Complete.
Hyberfil.sys -off (tried on and off no difference)
2Gb page file (tried every page file setting)
1 Hard drive with two partitions: 1-System and Programs, 2- Data

I read that this problem had something to do with 'Mirroring' but no
raid driver enabled.

Bios - everthing seems to be set properly.


If you have an idea on how to fix this I would greatly appeciate your
input.

Thanks!
Jim

For the information of all of you who swing a bat at this post: check
the ACPI spec includes a method to specify affinity/closeness of
processors. In other words, such things as hyper-threading, multi-core,
multi chips on a motherboard, multi-motherboards, etc., can be
distinguished! The OS has the option to use this information and process
intercom information in making processing dispatch decisions that
determine where processes will execute. Whether any of our popular home
hobby-kit systems play the game I do not know. The reason I point this
out is that having the information available and using it properly can
make an enormous difference.

 

[Jeff Barnett]

Jeff Barnett wrote, On 3/26/2013 1:02 PM:

Jim wrote, On 3/24/2013 5:06 PM:
For the information of all of you who swing a bat at this post: check
the ACPI spec includes a method to specify affinity/closeness of
processors. In other words, such things as hyper-threading, multi-core,
multi chips on a motherboard, multi-motherboards, etc., can be
distinguished! The OS has the option to use this information and process
intercom information in making processing dispatch decisions that
determine where processes will execute. Whether any of our popular home
hobby-kit systems play the game I do not know. The reason I point this
out is that having the information available and using it properly can
make an enormous difference.

Whoops - this was meant for the "Dual CPU's vs. Single?" thread below.
Sorry for the mispost.