Error Volmgr Event Id 46
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Sat, 15 Oct 2016 02:36:17 GMT by s_wx1131 (squid/3.5.20)
Monitor an unlimited number of servers with $49/year With the current low prices for servers and the need for processing power, even a small company event id 46 time service may end up with quite a few of them. If ten crash dump initialization failed windows 2012 r2 years ago it was still common to see an entire company using just one server, these days that's event id 46 the time service encountered an error no longer the case. New computers are added to the network with the understanding that they will be taken care of by the admins. Keeping an eye on these http://answers.microsoft.com/en-us/windows/forum/windows_7-performance/event-log-entry-system-volmgr-event-id-46-crash/6fd6f205-7bd2-40db-b985-544092a6609f servers is a tedious, time-consuming process. Even with 5 minutes per server (to check the logs and other parameters), it may take an hour to make sure that everything is ok and no "red lights" are blinking on any of the servers. read more... Event ID: 46 Source: volmgr Source: volmgr Type: Error Description:Crash dump initialization failed! English: http://www.eventid.net/display-eventid-46-source-volmgr-eventno-10647-phase-1.htm Request a translation of the event description in plain English. Comments: Anonymous Launch sysdm.cpl and go to Advanced system settings / Perfs / Settings / Advanced / Modify Unselect automatic setting Select the drive where to create your swap (c:\ ) and define minimum size > size of your memory. For example, if you have 4096 MB of memory put the minimum size at 4100 and maximum at 4101 Click on set / OK Restart Computer Goto Control Panel\System and Maintenance\System Click on "Advanced System Settings" on the left panel Under "Startup and Recovery" select "Settings" Make sure you have a check mark beside "Write and event to the system log" Put the link of folder on C: The problem should be fixed now. x 74 Private comment: Subscribers only. See example of private comment Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (1) - More links... Custom search for *****: Google - Bing - Microsoft - Yahoo Feedback: Send comments or solutions - Notify me when updated Printer friendly Subs
Javascript Disabled Detected You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality. Error volmgr Started by Dukislav , Nov 11 2010 04:55 AM Please log in to reply 7 replies to this https://forum.piriform.com/?showtopic=30559 topic #1 OFFLINE Dukislav Dukislav Newbie Members 2 posts Posted 11 November 2010 - 04:55 AM After Defraggler boot time defrag (2.00.230 - 64), in Event Viewer got: Error Event id: 46 Source: volmgr Crash dump initialization failed! http://www.eightforums.com/bsod-crashes-debugging/19795-crash-dump-initialization-failed.html ... My System: Win7/64 Hard Disks: 2 (C,D) Pagefile: System managed Write Debugging information: Small Memory Dump ... Back to top #2 OFFLINE Coffee4Joe Coffee4Joe Advanced Member Members 247 posts Gender:Not Telling Location:Earth Sometimes Posted 14 November event id 2011 - 01:32 PM I get this after running a full defrag then rebooting. This error will show every reboot unless I: Right click my computer > properties > advanced system settings > Advanced tab > Startup and recovery settings > and check Write event to system log. That fixes the error until I run a defrag and reboot again, Then "Write event to system log" becomes unchecked. Previously I changed Volume Shadow Copy service to event id 46 automatically start. That fixed it until the latest version of Defraggler 2.08.373 System: Win7 Professional x86 (32bit) Back to top #3 OFFLINE Alan_B Alan_B Super Hero Members 4,295 posts Gender:Male Location:Lancashire, England Posted 14 November 2011 - 02:33 PM Today's announcement includesAdded Volume Shadow Service (VSS) compatible mode.Perhaps you need to alter this new mode of use. Back to top #4 OFFLINE Coffee4Joe Coffee4Joe Advanced Member Members 247 posts Gender:Not Telling Location:Earth Sometimes Posted 14 November 2011 - 02:56 PM I completely missed that when I read the change log. Thanks! That seems to have fixed the error Back to top #5 OFFLINE Coffee4Joe Coffee4Joe Advanced Member Members 247 posts Gender:Not Telling Location:Earth Sometimes Posted 15 November 2011 - 07:11 PM Volmgr Error Happens after selecting Boot Time Defrag then rebooting.When "Run Once" or "Run Every Time" is clicked it unchecks "Write event to system log" in "my computer >properties > advanced system settings > Advanced tab > Start up and recovery settings"Leaving "Run Every Time" option in defraggler checked doesn't seem to uncheck "Write event to system log", Just happens when you initially click a option from Boot Time DefragIf I go into Start up and Recovery settings and check the Write Event box before rebooting the volmgr doesn't appear. Back to top #6 OFFLINE Dukislav Dukislav Newbie Members 2 posts Posted 26 November 2
Lodder View Profile View Forum Posts Junior Member Netherlands, Groningen, Zevenhuizen Posts : 3 MS Windows 8 Pro Crash dump initialization failed Hi! I have installed Win8 Pro now several times, and have been debugging it since with the help of suggestions from this forum. Currently the machine works great. It is fast, and does not use too much system resources. Unfortunately it was rather unusable after the previous installations. The 1st serious problem I ran into was running the SF Diagnostic Tool. Initially I was unable to find the generated info, or to be able to click the OK button. I have 1 system error left, and I am open to suggestions as whether no to care, or where to look for appropriate suggestions. The error exists since the 1st startup of Win8. Apart from UEFI etc there are no installation choices I have made (so far). The MS Systernals tool "psloglist -f e" reports: System log on \\LABBIE-HANS: [2789] volmgr Type: ERROR Computer: Labbie-hans Time: 4-2-2013 07:06:44 ID: 46 Crashdumpinitialisatie is mislukt! This translates nicely into" Crash dump initialization failed", and gives me the creeps. Looking for solutions I found that people increased their page file. I did that, but the problem remained, and even worse,the Win8 startup time and shutdown time increased both considerably. I intend to reduce the page file again, but have not done so yet. The error message is only displayed during a cold or warm (reboot) startup. 2 questions: 1. How to solve? 2. How to test that dumping indeed does not work? Kind regards, and thanks in advance, Hans Lodder My System Specs You need to have JavaScript enabled so that you can use this ... System Manufacturer/Model Number HP Pavillion g7 Notebook PC OS MS Windows 8 Pro CPU AMD A8 4500M Motherboard B1L54EA#ABH Memory 6 G Graphics Card Radeon HD Graphics Screen Resolution 1600x900 Quote 06 Feb 2013 #2 usasma View Profile View Forum Posts Mr. Cranky Pants Posts : 5,139 Win8.1Pro - Finally!!! First, here's a start on how crash dumps are generated: BSOD Crash Dump Generation Next is my experience. I've been doing BSOD analysis for at least 9 years and have come to the