BSOD Win 7 Pro 32bit VLK Image BUGCHECK_STR: 0xC5_2

Page 2 of 3 FirstFirst 123 LastLast

  1. Posts : 13
    windows 7 pro 64bit and 32bit
    Thread Starter
       #11

    You are correct, images are first fully updated by windows and than company applications are installed afterwards, HP drivers are then downloaded and added to the baseline image so whatever hardware the image is installed on the appropriate drivers will be selected and used (this has been my process and has never failed me). I'm hoping the issue stems from Symantec and is going to be resolved after updating to the newest version.

    Thanks again!
      My Computer


  2. Posts : 17,322
    Win 10 Pro x64
       #12

    You're welcome. Let us know how it goes. :)
      My Computer


  3. Posts : 13
    windows 7 pro 64bit and 32bit
    Thread Starter
       #13

    I thought I had my BSOD under control because I tested the image without drivers added and with just upgraded Symantec. I guess I got cocky because it was fine testing for a day so I added my driver packages today for all hardware and deployed the image, now I have BSOD on two different hardware computers.
    The .dmp files are attached, any ideas?
    thanks,
      My Computer


  4. Posts : 17,322
    Win 10 Pro x64
       #14

    Those are both the same Bugcheck C5,

    The earlier one is blaming Symantec again,

    Code:
    Unable to load image \SystemRoot\system32\Drivers\SEP\0C010FAD\0FAD.105\x86\SYMEFA.SYS, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for SYMEFA.SYS
    *** ERROR: Module load completed but symbols could not be loaded for SYMEFA.SYS
     SYMEFA+0x1e3a
    The other one wasn't flagging a specific driver, just pool corruption.

    Code:
    BugCheck C5, {4, 2, 1, 82d27943}
    
    Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+2e3 )
    
    Followup: Pool_corruption
      My Computer


  5. Posts : 13
    windows 7 pro 64bit and 32bit
    Thread Starter
       #15

    Thanks again for checking those, how are you able to get the below from the .dmp files? when I run WinDbg I don't ever see that, again I'm not a pro at system debugging by any means, usually I just press the analyze button and then if I'm lucky it will tell me a specific driver at fault, or in this case it just keeps giving me c5 bugcheck which all seems to point to Symantec and 32bit windows. Very Frustrating, it appears to be maybe the capturing of the image with Symantec and re-deployment of the software that sometimes it crashes on a clean deployment. I have two image files, one seems to work, and another with all my drivers installed that gives the BSOD. Very very annoying especially when I need to get the ball rolling on deployment. I guess I will use the image that doesn't crash and install hardware drivers after the fact.

    "Unable to load image \SystemRoot\system32\Drivers\SEP\0C010FAD\0FAD.105\x86\SYMEFA.SYS, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for SYMEFA.SYS
    *** ERROR: Module load completed but symbols could not be loaded for SYMEFA.SYS
    SYMEFA+0x1e3a"
      My Computer


  6. Posts : 17,322
    Win 10 Pro x64
       #16

    Try using this method,

    Debugging A BSOD - My way

    That's how I got that info about SYMEFA.SYS

    When you get to step 2, it's dps (limit) (base) enter.
      My Computer


  7. Posts : 13
    windows 7 pro 64bit and 32bit
    Thread Starter
       #17

    thank you for all your help with my problem, I just tried using that !thread myself and was able to see what you were referring to. Very nice! it will be awesome to have this going forward for bugging and troubleshooting things.
      My Computer


  8. Posts : 17,322
    Win 10 Pro x64
       #18

    You're welcome, good luck, hope you get that figured out.
      My Computer


  9. Posts : 13
    windows 7 pro 64bit and 32bit
    Thread Starter
       #19

    I've got a new one on a machine that was BSOD win windows XP 64x, now re-imaged with windows 7 x86 and it is still BSOD. Any ideas from this .dmp file? I could not see anything.
      My Computer


  10. Posts : 13
    windows 7 pro 64bit and 32bit
    Thread Starter
       #20

    Hi again, I was hoping you could troubleshoot this log with me derekimo; See attached.

    I was unable to find a driver issue after running the !thread and dps commands. Apparently the user just launched IE and the next thing the computer BSOD crashed. Any ideas?

    Thanks so much!
      My Computer


 
Page 2 of 3 FirstFirst 123 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 05:25.
Find Us