Ghost Error 37013
PKI Service Identity Access Manager Shop Online Cyber Security Services Managed Security Services DeepSight Intelligence Incident Response Security Simulation Website Security SSL Certificates Complete Website Security Code Signing Certificates Norton Shopping Guarantee Buy SSL Products A-Z Services Services Home Business Critical Services Consulting Services Customer Success Services Cyber Security Services Education Services Solutions Solutions Home Topics Encryption Everywhere Internet of Things Next Generation Endpoint Office 365 Industries Automotive Cyber Insurance Education Financial Services Global Service Providers Industrial Control Systems Healthcare Retail Government Federal Government State & Local Support Center Technical Support Symantec Connect Buying Programs Upgrades Maintenance & Renewals Training Security Center Security Center Home Blogs ISTR Threats Virus Definitions and Security Updates Removal Tools Partner Find a Partner Become a Partner Login Required Login into Partner Portal Partner Licensing Partner Renewals Partner Training Margin Builder Opportunity Registration Financial Benefits English 中文(简体) 中文(繁體) Česká English Français Deutsch Magyar Italiano 日本語 한국어 Polski Português Pусский Español Site: Symantec Enterprise Small Business Norton United States Search Support Home Support Home MySymantec Licensing Products A-Z SYM16-015 Security Advisory Login Profile Subscriptions Logout Login Forgot Password? Don't have a SymAccount? Create a SymAccount now!' Errors: "37013: An internal inconsistency has been found" and "37013: Out of memory" while using Ghost TECH107399 January 14th, 2007 http://www.symantec.com/docs/TECH107399 Support / Errors: "37013: An internal inconsistency has been found" and "37013: Out of memory" while using Ghost Did this article resolve your issue? Thank you for your feedback! Provide feedback on this article Request Assistance Print Article Subscribe to this Article Manage your Subscription
of the error: Windows Windows Internal Error 37013 are caused by misconfigured system files. So, from my experience, If you received a Windows Internal Error 37013 message then there is a 97.5% chance that your computer has registry problems. The Windows Windows Internal Error 37013 are easy to repair. By downloading and running the registry repair tool RegCure Pro, you can quickly and effectively fix this problem and prevent others from occuring. Simply click the links below for your free download. To Fix the problem https://support.symantec.com/en_US/article.TECH107399.html you need to follow the 3 steps : STEP 1: Download & Install RegCure Pro for Free. NOTE: If the download link doesn't work you may need to Download it Directly from a Mirror Here. STEP 2: Click "Quick Scan" Button to Scan Your Computer. STEP 3: Click the "Repair All" Button to Repair Your PC! That's All! Scott Chan Technical http://computerfixerrorsfree.com/windows-internal-error-37013.php Description of System Error(for Experts only): Microsoft Windows [Version 5.2.4630] (C) Copyright 1985-2014 Microsoft Corp. C:\Documents and Settings\Administrator>RegCure Pro.exe Windows Windows Internal Error 37013 may caused by some of the following errors Windows Explorer ErrorsJavascript ErrorsHardware MalfunctionError Symptom include:Can not printing fileBlue ScreenIO errorShutdown problemsHttp error Tags: Windows Windows Internal Error 37013 4 Response to “RegCure Pro ” WandaSays: at 9:22 PM Thank you so much! After spending countless hours on this stupid windows internal error 37013 problem I almost gave up. RegCure worked like a charm on the first try. It took a bit longer than 10 minutes, closer to 30, but by the time it was finished my PC worked great again. Kelsie Says: at 3:47 AM Just ran this on my wife's computer and for the first time in a long time, it finally works again! Regcure found over 2500 errors including the Windows Internal Error 37013 and fixed them all. I'm not a PC guru by any stretch, but this was a godsend. Cheers! Tyler Says: at 4:48 AM worked just like it said. no more errors and officially back in action
I am trying to ghost a hard drive but I do not know if I am doing this right. I am intalling the good http://www.velocityreviews.com/threads/ghosting-a-hd-from-windows-nt-using-norton-ghost.211220/ HD on top and setting the jumpers to master, intalling the bad one on bottom and setting the jumpers to slave. I boot from floppy, start the Ghosting process, select source 1 http://www.techimo.com/forum/archive/index.php/t-17861.html destination 2, click ok to start ghosting... then it gives me an error message: "Internal Error 37013" An internal inconsistency has been detected. What am I doing wrong?- What can I ghost error do to fix this problem and ghost my drive?- Please I need help asap.........Veronica Hernandez Veronica Hernandez, Nov 1, 2004 #1 Advertisements TheRedCat Guest On 1 Nov 2004 09:22:27 -0800, (Veronica Hernandez) wrote: >I am trying to ghost a hard drive but I do not know if I am doing this >right. >I am intalling the good HD on top and setting the ghost error 37013 jumpers to master, >intalling the bad one on bottom and setting the jumpers to slave. I >boot from floppy, start the Ghosting process, select source 1 >destination 2, click ok to start ghosting... then it gives me an error >message: > >"Internal Error 37013" >An internal inconsistency has been detected. > >What am I doing wrong?- >What can I do to fix this problem and ghost my drive?- > >Please I need help asap.........Veronica Hernandez > Hi Veronica It sounds as if you are going about things the right way, so what's going wrong. Firstly, you say a 'bad drive'. If the drive is faulty in some way, or the file tables are corrupt then this may explain why Ghost isn't. Ghost will copy a drive bugs and all and will not repair errors. A second reason may be the version of Ghost. Ghost 2000 had severe limitations on ntfs drives which have been happily overcome in Ghost 2003. Perhaps some more detail may help to nail the problem down. TheRedCat, Nov 1, 2004 #2 Advertisements Stevo Guest Veronica Hernandez wrote: > I am trying to g
may come across rather.........pi$$ed:mad: :mad: . I spent $100+ for Norton System Works 2002 back in September. The main reason buying it was Ghost. I have successfully ghosted my drive on an Asus A7A266 mobo. Since, I've swapped out the mobo for a Soyo Dragon+ and the freakin' thing keeps giving me "error 12020":confused: . A search at the Symantec site shows that it's a "general error" - what the hell does that mean??? I followed all of thier "fixes", reset the BIOS to minimal and underclocked. I've got over 10 coasters in the trash right now with a computer soon to follow (pay attention to my handle:) ). I'm SO very mad right now that I can't think. Before I ever post a problem, I try everything - locally and through the internet. I had to post back in October because of this and it still does it:(. Any help would be great 'cuz if not, I'm gonna take that $100 cd and the $1500 box and have a bonfire tomorrow - without a doubt. I've had it with wasting hard earned cah on cr@p software. Sorry, I try to conduct myself a little more professionally but I'm WAY beyond being rational - 12 wasted hours today and I still have both my business and personal taxes to start - *I'll edit here*:) . Mike GroundZero3April 4th, 2002, 11:12 PMhttp://service2.symantec.com/SUPPORT/ghost.nsf/pfdocs/2000103010201025 will this help? when do you get the error message? like what are you trying to do? SocalgalApril 4th, 2002, 11:15 PMHi Taz, sorry about your hardship :( I can sympathize. I just read the "solutions" offered by Symantec, and you did not mention if you had tried ======= IDE controller With some CD writers such as the Iomega CDZIP 12x4x32 CDR/W drive, this problem sometimes happens when the CD writer is on the same IDE controller as the hard disk that Ghost is cloning. To resolve the problem, attach the CD writer and hard disk to different IDE controllers. Typically, this results in making the disk drive the Primary Master and the CD writer the Secondary Master. ======== Error12020 (http://216.239.33.100/search?q=cache:lqBBRCbE2d8C:service4.symantec.com/SUPPORT/ghost.nsf/docid/2000103010201025+error+12020&hl=en) ? I wish I could be more helpful. I had a consistent 'Error 37013' with Ghost and used their suggested Ghost.exe -ws- -wd- (http://service2.symantec.com/SUPPORT/ghost.nsf/e44a397a948bb43e85256952006d83d1/941b4810f3b1204d8825697100620067?OpenDocument) and it did work.. but now I use Drive Image 5.0, which I like alot better as it easily allows me to hide system