locked
System ID Error 46, Volmgr RRS feed

  • Question

  • I seem to be getting ID error 46, Crash Dump Initialization failed, every 2-3 days.  In the past I rarely saw it, but it seems more frequent.  It may be tied to sleep mode but I'm not sure.  The only major changes I've made to the OS is the installation of an HP printer which had a minor glitch in the "Solution Center" screen. HP recommended I uninstall and reinstall the MS NET Framework (4.0) which I did without a problem and fixed the glitch.  I also upgraded Norton Internet Security from the 2011 to 2012 version.  The C:\Win\MiniDump file is locked but empty.

    Here's a copy of the ID error:

    Log Name:      System
    Source:        volmgr
    Date:          11/29/2011 5:20:00 AM
    Event ID:      46
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      Chuck-PC
    Description:
    Crash dump initialization failed!
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="volmgr" />
        <EventID Qualifiers="49156">46</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2011-11-29T12:20:00.212424100Z" />
        <EventRecordID>255219</EventRecordID>
        <Channel>System</Channel>
        <Computer>Chuck-PC</Computer>
        <Security />
      </System>
      <EventData>
        <Data>\Device\HarddiskVolume3</Data>
        <Binary>0000000001000000000000002E0004C001100000010000C000000000000000000000000000000000</Binary>
      </EventData>
    </Event>

    Any ideas why this error may be occurring?

    Tuesday, November 29, 2011 6:04 PM

Answers

  • Believe I have corrected the problem.  The system settings under startup & recovery >system failure had become unchecked. I checked the box to "write an event to the system log."
    • Marked as answer by Bart9 Wednesday, November 30, 2011 5:13 PM
    Wednesday, November 30, 2011 5:13 PM

All replies

  • Believe I have corrected the problem.  The system settings under startup & recovery >system failure had become unchecked. I checked the box to "write an event to the system log."
    • Marked as answer by Bart9 Wednesday, November 30, 2011 5:13 PM
    Wednesday, November 30, 2011 5:13 PM
  • Hi,

     

    I’m glad to hear that your problem has been solved. We really appreciate your time and efforts. Hope your experience will help other community members facing similar problems.

     

     

    Regards,

    Leo   Huang

     

     


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Thursday, December 1, 2011 6:18 AM
  • had same error with an old disk with bad sectors ...
    Sunday, June 3, 2012 8:44 AM