BSOD - Stop: C000021A {Fatal System Error}


  1. Posts : 7
    Microsoft Windows 7 Professional 32-bit (OEM)
       #1

    BSOD - Stop: C000021A {Fatal System Error}


    I have been having some issues with various BSOD's, I listed my most previous BSOD here on the forums and thought that I might have had this BSOD issue fixed (well, hopefully!) - it was related to AVG and possibliy conflicting with MSE, as no virus db was listed, you can see it here on the forum

    sevenforums.com/crashes-debugging/180151-bsod.html#post1528734

    Desktop System Details:

    System Manufacturer/Model Number: ACPI x86-based PC
    OS: Microsoft Windows 7 Professional 32-bit (OEM)
    CPU: Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz
    Motherboard: Intel Cold Lake DH67CL
    Memory: 4 GB (DDR3-1333 DDR3 SDRAM)
    Graphics Card(s): AMD Radeon HD 6700 Series
    Sound Card: N/A
    Monitor(s) Displays: LG Flatron W2343T
    Screen Resolution: 1920 x 1080 (recommended)
    Hard Drives: WDC WD2002FAEX-007BA0 (1863 GB, IDE)
    WD Ext HDD 1021 USB Device (931 GB, USB)
    PSU: N/A
    Case: Thermaltake Armor Jr
    Cooling: N/A
    Keyboard: Logitek K120 (generic)
    Mouse: Generic
    Internet Speed: Cable
    Other Info:
    OS Service Pack Service Pack 1
    DirectX DirectX 11.0
    DMI BIOS Vendor Intel Corp.
    DMI BIOS Version BLH6710H.86A.0076.2010.1115.1959

    BSOD Overview:

    On Friday (12/08/2011), I installed 'AIDA64 Extreme Edition', updated 'LG Flatron W234T' drivers and Microsoft completed an 'critical update' at which point this BSOD began to happen:

    autochk program not found - skipping AUTOCHECK

    Stop: C000021A {Fatal System Error}

    The initial process or system process terminated unexpectedly with status 0x00000000 (0xC0020034, 0x001004C8)

    The System has been shut down.
    I have been taking the following steps to get the system back up, but it only lasts so long before it either 'freezes' (when I am initiating a program like 'Windows NT6 BSOD jcgriff2') or gets another Bluescreen as it pops into screen saver, both requiring the system to be 'powered off' manually. The system is one I have purchased in the last 30-days and I am kind of thinking, my old faithful XP Pro box was definitely at lot more stable than my new Windows 7 box.

    The steps I have taken have been:

    (1.) Startup Repair, which gives me a 'windows cannot repair this computer automatically. ----> send information about this problem.

    The problem signature I am presented is the following:

    Problem Event Name: StartupRepairOffline
    Problem Signature 01: 6.1.7600.16385
    Problem Signature 02: 6.1.7600.16385
    Problem Signature 03: unknown
    Problem Signature 04: 21200478
    Problem Signature 05: AutoFailover
    Problem Signature 06: 2
    Problem Signature 07: BadDriver
    OS Version: 6.1.7601.2.1.0.256.1
    LocaleID: 1033

    Other problem signatures have included:

    Problem Signature 06: 3
    Problem Signature 07: NoRootCause

    Problem Signature 06: 4
    Problem Signature 07: NoRootCause

    Problem Signature 06: 5
    Problem Signature 07: NoRootCause;

    (2.) System Restore, which once completed gives the original 'autochk program not found - skipping AUTOCHECK' message and the BSOD C000021A;

    (3.) Restore from System Image Backup, by going back to an physical system image gets the box back up for an short period, until the next BSOD and I have to power down manually.

    If anyone can help I would be greatly appreaciate it, it is becoming a bit of a pain in the backside and I am starting to lose my mind Also, I am imagining that I am going to have to take the box back to the supplier and say, 'Oi mate, based on your recommendation, I've got a gift for you... bend over' (it does not paint a 'happy mental picture').

    Thanks in advance!
    Last edited by BigAnt; 13 Aug 2011 at 10:11. Reason: fixed grammar errors + added AIDA64
      My Computer


  2. Posts : 5,705
    Win7 x64 + x86
       #2

    Perfmon shows that you have networking issues and Microsoft Security Essentials (MSSE) issues. I suspect that the MSSE issues will fix themselves - but we'll uninstall/reinstall just to be sure.

    First, go to Device Manager...Network Adapters and right click on any of the following devices and select "Uninstall":
    - Teredo
    - ISATAP
    - 6to4
    - unknown
    Once that's done, reboot the system and the devices will automatically reinstall if needed (in most cases they aren't needed and they don't come back).

    Then, download a fresh copy of Microsoft Security Essentials (MSINFO32 says you're using ESET and not MSSE. Only use one antivirus and one firewall program at a time).
    Uninstall your current copy of Microsoft Security Essentials.
    Then install and immediately update the freshly downloaded copy.

    No memory dumps are present in the uploaded files. Please do the following:
    Upload Dump Files:
    Please go to C:\Windows\Minidump and zip up the contents of the folder. Then upload/attach the .zip file with your next post.
    Left click on the first minidump file.
    Hold down the "Shift" key and left click on the last minidump file.
    Right click on the blue highlighted area and select "Send to"
    Select "Compressed (zipped) folder" and note where the folder is saved.
    Upload that .zip file with your next post.

    If you have issues with "Access Denied" errors, try copying the files to your desktop and zipping them up from there. If it still won't let you zip them up, post back for further advice.

    If you don't have anything in that folder, please check in C:\Windows for a file named MEMORY.DMP. If you find it, zip it up and upload it to a free file hosting service . I recommend Windows Live SkyDrive - http://skydrive.live.com or another free, file-hosting service. Then post the link to it in your topic so that we can download it.

    Then, follow the directions here to set your system for Minidumps (much smaller than the MEMORY.DMP file): Set MiniDump
    The Windows Error Reporting section of MSINFO32 doesn't show any BSOD's also. It's possible that these are occurring too early to be recognized by the OS.

    So, I have to wonder if this is a hardware problem (because of your item (3.)) - or a software problem. Let's start by ruling out some stuff using these free diagnostics:
    I suggest starting all troubleshooting with the following diagnostic tests. They'll save you a lot of time and heartache if there is a hardware failure, and you'll have the disks on hand in case you need them in the future:
    H/W Diagnostics:
    Please start by running these bootable hardware diagnostics:
    Memory Diagnostics (read the details at the link)
    HD Diagnostic (read the details at the link) - Test ALL of the hard drives.

    Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Free Online AntiMalware Resources (read the details at the link)
    There are also free, bootable antivirus disks at this link: Free Online AntiMalware Resources
      My Computer


  3. Posts : 7
    Microsoft Windows 7 Professional 32-bit (OEM)
    Thread Starter
       #3

    Hi USASMA,

    Thanks, very much for your help and for the reply, couple of things:

    (i.) Completed first request (about to reboot) of 'Device Manager...Network Adapters ... "Uninstall":

    - Teredo
    - ISATAP
    - 6to4
    - unknown

    Note: unknown was not present see attached 'device manager image'

    (ii.) C:\Windows\Minidump

    Note: empty folder, see attached 'minidump folder image'

    (iii.) ESET is a bugbear, it was installed by 'suppliers technical staff' as part of Intel divers install, apparently it was on the disk, so they installed it. I requested it to be 'uninstalled', when I originally went to pick up the box - it had the wrong 'graphic card' installed... and ESET messages kept popping up stating 'motherboard something' was not protected from Malware, etc.

    Even though the tech un-installed ESET, I realise it has possibly left remnants of itself on the box, it is the reason I installed both AIDA64 and Glary Utilities - the ESET message in the taskbar was still occurring occasionally.

    To my knowledge there is only one AV installed on the box at the moment, that being MSE and I will follow your request to 'uninstall' it once I have rebooted. Although, I do have misgiving going into reboot, as the system seems to hang and become unresponsive, requiring physical intervention (hold the power button down, until it powers down) - so, I may be a short while completing tests and restoring from backup.

    Thanks, greatly appreciate it.
      My Computer


  4. Posts : 5,705
    Win7 x64 + x86
       #4

    The reports show that ESET is installed - and it doesn't show MSSE
    To remove remnants of ESET, try this free tool/procedure: How do I manually uninstall my ESET security product? - ESET Knowledgebase
      My Computer


  5. Posts : 7
    Microsoft Windows 7 Professional 32-bit (OEM)
    Thread Starter
       #5

    Hi USASMA,

    Thanks for the link to the ESET knowledgebase, was a 'pearler' (great resource).

    (i.) Minidump, I have reset Minidumps on the system, please see attached image 'Program Manager_2011-08-14_02-29-10';

    (ii.) AV issues, I have:

    (a.) 'uninistalled' ESET using 'ESETUninstaller.exe', it located and removed the 'ESS/EAV/EMSX' remnants, see attached text file '~ESETUninstaller'

    (b.) MSE has been re-installed and an full system scan reveals no viruses;

    (c.) completed an AV scan online using F-Secure after 'uninstalling' MSE, it found no malware, but seven (7) instances of 'spyware', see attached zip file 'F-Secure Online Scanner - Scanning Report';

    (iii.) Memory Diagnostics has been completed with no errors, I ran:

    (a.) MemTest86

    Intel Core Gen2 3293 MHz
    L1 Cache: 32K 109752 MB/s
    L2 Cache: 256K 49887 MB/s
    L3 Cache: 6144K 37415 MB/s

    Memory: RAM: 665MHz (DDR3 - 1330) / CAS: 9 - 9 - 9 - 24 / Single Channel

    Wall time - 0:21:42
    Cached - 4076M
    RsvdMem - 600K
    MemMap - e820
    Cache - on
    ECC - off
    Test - Std
    Pass - 2
    Errors - 0
    ECC Errs - nil

    (iv.) Hard Drive diagnostic, have attempted 'extended test' diagnostic twice, system goes into unresponsive hibernation and requires manual power down. All drivers has passed 'quick test' and have SMART status of 'pass'.

    I have disabled sleep and other services, such as screen saver and about to re-run diagnostic. Please find attached latest 'system health check' zip file.

    Regards and thanks.
    Last edited by BigAnt; 17 Aug 2011 at 07:04.
      My Computer


  6. Posts : 5,705
    Win7 x64 + x86
       #6

    It sounds like you've used the hard drive tests that work in Windows.
    Please rerun the test with a bootable CD. If there isn't a test for your hard drive, use the bootable SeaGate SeaTools test. If you have trouble getting it to work, then try the bootable Hitachi Drive Fitness Test.
      My Computer


  7. Posts : 7
    Microsoft Windows 7 Professional 32-bit (OEM)
    Thread Starter
       #7

    Hi USASMA,

    Yeah mate, that is correct. I have attempted to complete the hard drive diagnostics using an bootable CD, and I have got the following results:

    (i.) Bootable CD - Hard Drive diagnostics

    (a.) Western Digital, search for my hard drive model presents the result to download the Data Lifeguard Diagnostic for DOS (CD), Version 5.04f. When booting from CD I get the following message (also attached as image):

    NO DRIVE FOUND

    ERROR / STATUS CODE: 0120
    (b.) SeaGate's 'SeaTools for DOS' also results in an 'No Hard Drives Found' message and the suggestion to check 'cables, drive power connection and jumper settings', attached as image.

    (c.) Hitachi, also gets an error with option message to exit (unpacked ISO prior to burning to Bootable CD).

    (2.) BSOD's were presented as I attempted to boot up on the OS, these were:

    0x00000000 (0xC0020034, 0x001004C8) - original
    0xE0010002 (0x85947000, 0x0000040C, 0x0000011D, 0x00000912) - attached image

    I have to restore from 'system image backup' to get back up, and at the time of the last BSOD, I had just zipped up two files in the 'minidump' folder for you, but have lost them in the restoration process.

    I have run ADIA64 tests on hardware and have those results, including voltages and I can include them for review if you wish. I was thinking of running some hardware benchmarks using 'inquisitor' or 'Phoronix Test Suite' to benchmark the hardware and see 'if' it helps to troubleshoot the issues.
    Last edited by BigAnt; 16 Aug 2011 at 22:39. Reason: Added AIDA sentence.
      My Computer


  8. Posts : 5,705
    Win7 x64 + x86
       #8

    Interestingly enough, I've never seen either of your BSOD error messages:
    0x00000000 (0xC0020034, 0x001004C8) - original
    0xE0010002 (0x85947000, 0x0000040C, 0x0000011D, 0x00000912) - attached image
    I'd have dismissed the one with all 0's as fluke if you hadn't had the other one. I've found a couple of instances of the second error (in a web search) and both relate to the Renesas USB 3.0 drivers. I'd consider it essential that you attempt to capture future memory dumps of this sort as soon as they happen (so we'll have something to look at).

    From my experience, these "unusual" BSOD codes are from 3rd party drivers that have the ability to generate specific error codes (it's coded into some 3rd party drivers) - so I usually suspect the drivers/hardware that are named in the error as my first "guess".

    Meanwhile, I'd suggest uninstalling the Renesas software and then either physically removing the device from your system or disabling it in the BIOS (if you can't remove it). Also, if there's anything plugged into the USB 3.0 ports, it may also be a suspect - so remove them also. Since everything that's attached to the mobo is related in some way or another - test the hard drive(s) again after removing/disabling the device.

    In most cases when the hard drive isn't found - it's either due to one of the hard drives having issues, or that there's a motherboard problem. Also possible are cable issues, so it's best to remove them from the equation when testing. To troubleshoot which hard drive may be having the problem, disconnect one (both the power and data cables, and then remove the data cable from the mobo also) and try the test with the other hard drive in the system.

    Good luck!
      My Computer


 

  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 14:33.
Find Us