Jump to content

Welcome to Geeks to Go - Register now for FREE
Geeks To Go is a helpful hub, where thousands of friendly volunteers serve up answers and support. Get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute.
Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message and all ads will be removed once you have signed in.
Create an Account Login to Account

Volmgr Event ID: 46


  • Please log in to reply

#1
Darken1

Darken1

    Member

  • Member
  • PipPip
  • 28 posts
I don't know how long this has been happening but I get this error every time I turn on or off my computer.
I attached a screen shot of the error it self
It appears twice in Event viewer one after the other.

I did some searching online and someone keeps posting that the solution to this error is to enable an option in system properties.
in system/advanced system properties/startup and recovery
there is an option under system failure to "Write an event to the system log"
and checking this option off will remove this error but every time I check it off it unchecks itself.

Has anyone heard of this error and is this the solution to it.
If it is, how do I get the option to stay checked off.

any help is appreciated, thanks in advanced.


Hp Pavilion dv9207us laptop
Windows Vista Home Premium 32-bit
3 gb of RAM
250 gb 7200 rpm os drive
160 gb 5400 rpm secondary drive 7gb are partitioned for hp recovery
geforce go 7600
I just went through and updated all of my drivers.

Attached Thumbnails

  • error_screen.jpg

  • 0

Advertisement


#2
Jacee

Jacee

    Malware Expert

  • Expert
  • 992 posts
  • MVP
Type memory in the start search box. Then click on the memory diagnostic icon and check the memory (Ram)
  • 0

#3
Darken1

Darken1

    Member

  • Member
  • PipPip
  • 28 posts
Sorry for taking so long to reply i figured out what was causing the error for me I came across the solution you gave in another forum and had tried it before the post as well, when i say tried it I mean ran a memory test with no errors and tried swapping to two different sticks of ram altogether.

In the end the solution to the problem is checking off the box under control panel, system, advanced system options, startup and recovery, and then the box is called "Write an event to the system log"

The problem was with a program I use Advanced system care free and it's system optimizer will disable that functionality so all I had to do was undo the optimization and uncheck the box inside the program so it would not try to optimize it again and now I no longer get this error.

Thanks for your help and hope this helps someone else.
  • 0

#4
sylar2511

sylar2511

    New Member

  • Member
  • Pip
  • 1 posts
Hi, I have the same identical problem but I don't know exactly how to solve it. Using Advanced SystemCare, I do not know how to disable the system optimizer, once I optimized some fuctions I'm not able anymore to rollback to default. How can I do this?
  • 0

#5
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 33,982 posts
Direct to: sylar2511

Please start your own topic as this topic is almost a year old since the last reply.
Although your issue may seem similar there can be other factors that may need to be resolved.
By bumping on someone's topic it makes it confusing for the tech to understand who they are helping. This can in turn cause the wrong support to be given and can cause instability or worse to happen to your system.
Thank you for your cooperation.
  • 0

#6
SirChurchy

SirChurchy

    New Member

  • Member
  • Pip
  • 1 posts
I realise this is an old thread, however, it's also the #1 result on Google so I figured it deserved an answer for the benefit of other poor sods who got this error.

If you are getting this error, chances are you have your page file on a separate partition to your SYSTEM partition (note: don't confuse BOOT and SYSTEM, the naming is rather counter-intuitive)

Essentially, there are a variety of different ways you could partition your drive under Vista/7... for example, you could have your BOOT and SYSTEM partitions on the same partition, but the page file is not on the SYSTEM partition - in this instance, it will most likely prevent logging of crash dumps although I may be wrong, what I can say is that it will definitely prevent it if the BOOT partition has NTFS clusters > 4KB and it is also hosting your page file (4KB is the default, it will ONLY be larger if you specified it manually)

It should be noted that the SYSTEM partition can NEVER be formatted with > 4KB clusters or the machine will FAIL TO BOOT (indeed, if you want your main OS partition to use larger clusters for some reason such as using Volume Shadow Copy without defrag issues, then this way of doing things is pretty common)

under 7, you may well find that your BOOT partition (this is the partition that contains the OS files) is separate to your SYSTEM partition (this is the partition that the MBR will hand over to during boot) and it generally only contains the BCD database and bootmgr.

So, in order to rectify the problem you need to configure windows to have the page file on the SYSTEM partition, so you may well need to make this partition larger to accommodate it. If your computer still does not create a dump, consider configuring the location to make a dump to a folder on the SYSTEM partition. As always, do make sure you'll have enough free space for the dumps as well, or consider getting windows to only generate minidumps.

The other "solutions" posted here aren't really solutions, they're just telling windows not to bother trying to do crash dumps, which will make diagnosis difficult if you get a BSoD.
  • 0

Advertisement




Similar Topics: Volmgr Event ID: 46     x


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

featured