Ghost ошибка 36000

Ghost executable fails with ‘Internal error 36000’ when enumerating volumes.

calendar_today

Updated On:

Products

Deployment Solution

Issue/Introduction

Ghost executable (Ghost64.exe or Ghost32.exe) fails with ‘Internal error 36000’ when enumerating volumes. This occurs at different points in the process where list of drives needs to be generated, even simply starting the executable and selecting: Local > Disk > To Image

Stack trace section in ghosterr.txt:

Thread #XXX Call Stack
VolumeContainer::VolumeContainer::getVolumesCount
LfoDeviceCommand::StartDriveEnumeration
LfoDeviceCommand::GetDriveInfo
OldGhostUI::OldGhostUI::getFirstDumpFile
OldGhostUI::OldGhostUI::selectSourceImage
OldGhostUI::OldGhostUI::attemptOperation
GhostClonerImpl::runMainScript
sub_main
main

Environment

Deployment Solution 8.5 RU2

Resolution

This issue is resolved in INFO5407 : CUMULATIVE POST 8.5 RU2 POINT FIXES.  Released as part of DS 8.5 POST_RU2 v1

Feedback

thumb_up
Yes

thumb_down
No

Step 1 – Solve Norton Ghost Internal Error 36000

Is Norton Ghost Internal Error 36000 appearing? Would you like to safely and quickly eliminate Ghost Internal Error which additionally can lead to a blue screen of death?

When you manually edit your Windows Registry trying to take away the invalid symantec ghost error 36000 internal inconsistency keys you’re taking a authentic chance. Unless you’ve got been adequately trained and experienced you’re in danger of disabling your computer system from working at all. You could bring about irreversible injury to your whole operating system. As very little as just 1 misplaced comma can preserve your Pc from even booting every one of the way by!

Troubleshooting lá»?i internal error 36000 Windows XP, Vista, 7, 8 & 10

Simply because this chance is so higher, we hugely suggest that you make use of a trusted registry cleaner plan like CCleaner (Microsoft Gold Partner Licensed). This system will scan and then fix any Norton Ghost Internal Error 36000 complications.

Registry cleaners automate the entire procedure of finding invalid registry entries and missing file references (including the Internal error) likewise as any broken hyperlinks inside of your registry.

Issue with symantec ghost internal error 8027

Backups are made immediately prior to each and every scan providing you with the choice of undoing any changes with just one click. This protects you against doable damaging your pc. Another advantage to these registry cleaners is that repaired registry errors will strengthen the speed and performance of one’s procedure drastically.

  • https://support.symantec.com/en_US/article.TECH106950.html
  • http://www.experts-exchange.com/questions/22114753/Norton-Ghost-Boot-Disk-gives-error-36000.html
  • http://www.experts-exchange.com/questions/24705332/Symantec-Ghost-Error-36000-Internal-Inconsistency-detected.html
  • http://community.norton.com/forums/norton-ghost-2003-internal-error-36000-boot

Cautionary Note: Yet again, for those who are not an state-of-the-art consumer it’s very encouraged that you simply refrain from editing your Windows Registry manually. If you make even the smallest error within the Registry Editor it can result in you some serious issues that may even call for a brand new set up of Windows. Not all difficulties attributable to incorrect Registry Editor use are solvable.

Fixed: an internal inconsistency has been detected 8027

Symptoms of Norton Ghost Internal Error 36000
“Norton Ghost Internal Error 36000” appears and crashes the energetic method window.
Your Personal computer routinely crashes with Norton Ghost Internal Error 36000 when running the exact same system.
“Norton Ghost Internal Error 36000” is shown.
Windows operates sluggishly and responds little by little to mouse or keyboard input.
Your computer periodically “freezes” for the number of seconds in a time.

Will cause of Norton Ghost Internal Error 36000

Corrupt obtain or incomplete set up of Windows Operating System software program.

Corruption in Windows registry from a new Windows Operating System-related application adjust (install or uninstall).

Virus or malware infection which has corrupted Windows method documents or Windows Operating System-related application data files.

Another method maliciously or mistakenly deleted Windows Operating System-related files.

Mistakes this sort of as “Norton Ghost Internal Error 36000” can be brought about by several different elements, so it really is important that you troubleshoot every of the achievable brings about to forestall it from recurring.

Simply click the beginning button.
Variety “command” inside the lookup box… Will not hit ENTER nonetheless!
Although keeping CTRL-Shift in your keyboard, hit ENTER.
You’re going to be prompted that has a authorization dialog box.
Click on Of course.
A black box will open having a blinking cursor.
Variety “regedit” and hit ENTER.
Within the Registry Editor, choose the symantec ghost error 36000 internal inconsistency connected key (eg. Windows Operating System) you wish to back again up.
Within the File menu, choose Export.
Inside the Preserve In list, pick out the folder in which you wish to save the Windows Operating System backup key.
Inside the File Title box, sort a reputation for the backup file, these types of as “Windows Operating System Backup”.
From the Export Vary box, ensure that “Selected branch” is selected.
Click on Help you save.
The file is then saved by using a .reg file extension.
You now use a backup within your lá»?i internal error 36000 related registry entry.

Solution to your ghost an internal inconsistency has been detected 25002 problem

There are actually some manual registry editing measures that can not be talked about in this article due to the high chance involved for your laptop or computer method. If you want to understand more then check out the links below.

Additional Measures:

One. Conduct a Thorough Malware Scan

There’s a probability the Norton Ghost 36000 Error Internal error is relevant to some variety of walware infection. These infections are malicious and ready to corrupt or damage and possibly even delete your ActiveX Control Error files. Also, it’s attainable that your Norton Ghost Internal Error 36000 is actually connected to some element of that malicious plan itself.

2. Clean Disk Cleanup

The a lot more you employ your computer the extra it accumulates junk files. This comes from surfing, downloading packages, and any sort of usual computer system use. When you don’t clean the junk out occasionally and keep your program clean, it could turn into clogged and respond slowly. That is when you can encounter an 36000 error because of possible conflicts or from overloading your hard drive.

Once you clean up these types of files using Disk Cleanup it could not just remedy Norton Ghost Internal Error 36000, but could also create a dramatic change in the computer’s efficiency.

Tip: While ‘Disk Cleanup’ is definitely an excellent built-in tool, it even now will not completely clean up Internal Error discovered on your PC. There are numerous programs like Chrome, Firefox, Microsoft Office and more, that cannot be cleaned with ‘Disk Cleanup’.

Since the Disk Cleanup on Windows has its shortcomings it is extremely encouraged that you use a specialized sort of challenging drive cleanup and privacy safety application like CCleaner. This system can clean up your full pc. If you run this plan after each day (it could be set up to run instantly) you are able to be assured that your Pc is generally clean, often operating speedy, and always absolutely free of any Error error associated with your temporary files.

How Disk Cleanup can help

1. Click your ‘Start’ Button.
2. Style ‘Command’ into your search box. (no ‘enter’ yet)
3. When holding down in your ‘CTRL-SHIFT’ important go ahead and hit ‘Enter’.
4. You will see a ‘permission dialogue’ box.
5. Click ‘Yes’
6. You will see a black box open up plus a blinking cursor.
7. Variety in ‘cleanmgr’. Hit ‘Enter’.
8. Now Disk Cleanup will start calculating the amount of occupied disk space you will be able to reclaim.
9. Now a ‘Disk Cleanup dialogue box’ seems. There will be a series of checkboxes for you personally to pick. Generally it will likely be the ‘Temporary Files’ that consider up the vast majority of your disk area.
10. Verify the boxes that you want cleaned. Click ‘OK’.

How to repair

3. System Restore can also be a worthwhile device if you ever get stuck and just desire to get back to a time when your computer system was working ideal. It will work without affecting your pics, paperwork, or other crucial information. You can discover this option with your User interface.

Internal Error

Manufacturer

Device

Operating System


Norton Ghost Internal Error 36000


5 out of
5

based on
90 ratings.

 

Ghost 2003 — General Exception 36000 — Restoring (Read 13424 times)

Christer

�bermensch
*****
Offline

Posts: 1344
Sweden

Back to top



Ghost 2003 — General Exception 36000 — Restoring
Feb 4th, 2007 at 3:59pm

 

Hello all!

Had a call from a friend whos computer I set up a few years ago. There were several problems. Very slow in general, WMP 10 not working OK, the screen going black for a second on an irregular basis and more to add … Undecided … but I won’t bore you with more details.

I let Ad-Aware loose on it. Found a few tracking cookies which I deleted.

Next, I let Spybot S&D loose and it found the following:

TIBS with the executable C:Windowsms1.exe

Smithfraud-C with the executable C:WindowsSystem32paytime.exe and five executables C:Windowstool»n».exe where «n» is 1-5.

Torpig with the executable C:Windowskl.exe and a log file kl.log.

Spybot S&D could only fix paytime.exe but I could remove the other files manually.

My efforts made no difference. The computer still showed the same problems. I inserted Ghost Boot Disk #1 and booted to DOS. Next, Ghost Boot Disk #2 was inserted but it returned the below error log:

Quote:

*********************************
Date � : Sun Feb �4 20:15:09 2007
Error Number: (36000)
Message: A GeneralException occurred
Version: 2003.793 (Dec 17 2003, Build=793)
Command line arguments:
Active Switches :
� � � AutoName
ProgMode � � � � � �: no progmode
PathName � � � � � �:
DumpFile � � � � � �:
DumpPos � � � � � � : 0
File64 buffersize � : 0
FlagImplode � � � � : 0
FlagExplode � � � � : 0

Operation Details :
�Total size………0
�MB copied……….0
�MB remaining…….0
�Percent complete…0%
�Speed…………..0MB/min
�Time elapsed…….0:00 �
�Time remaining…..0:00 �

I have been running Ghost 2003 from GBDs on that copmuter ever since I set it up and it has worked flawlessly until now. My assumption is that whatever has infected the computer has written something to the system partition to cause the Ghost error.

Basic system specs are 2.0 GHz P4 with 512 MB RAM and two 120 GB Hitachi 7K250 PATAs.

Does this ring any bells?

Thanks for your time,
Christer


Old chinese proverb:

If I hear — I forget, If I see — I remember, If I do — I understand

IP Logged
 

Rad

Radministrator
*****
Offline


Sufferin’ succotash

Posts: 4090
Newport Beach, California

Back to top



Re: Ghost 2003 — General Exception 36000 — again
Reply #1 — Feb 4th, 2007 at 4:37pm

 

but you are not booting from the system partition, correct? .. when you boot from the ghost boot disk?

i mean, it sounds like you’re having problems *before* the hard disk is ever accessed.

what about defective hardware, such as bad memory?

i always like to blow a fan on the mobo, to make sure it’s not heat related, or affected. to rule that out. is mobo dusty? (which can act as heat insulator)

general exception .. that’s a crash, no? (memory related)

can you run memory diagnostics from a dos boot floppy?

can be difficult to troubleshoot bad memory.

WWW
 

IP Logged
 

Christer

�bermensch
*****
Offline

Posts: 1344
Sweden

Back to top



Re: Ghost 2003 — General Exception 36000 — again
Reply #2 — Feb 4th, 2007 at 5:16pm

 

Rad,
thanks for your suggestions!

I had to leave him hanging with no solution and will not have time to go back until mid week.

You’re right that the hard disk has not been accessed by Ghost but since I booted successfully to DOS from GBD #1, it was accessed by DOS. (I also booted from a Win98 startup disk and it went well.) It is not until Ghost loads (from GBD #2) that the error message appears. It is towards the end of the program load, just before the screen should come on, that it happens. It is possible that it happens while Ghost tries to detect the disks.

The next time I go there, I will bring a hard disk to substitute the current system disk. (He has two 7K250. One with C: for system and programs and D: for data. The other with E: for backups of D: and F: for Ghost Images. This is not network related as in the other thread.)

If Ghost does not load but return the same error with the other hard disk connected and the current one removed, I will do some more hardware related tests. The computer was cleaned out (from dust) by myself only a few weeks ago when I installed a new video card. Memory tests will be the first thing to do.

One vital issue that I failed to mention is that from «cold», the computer does not start on the first attempt. He has to do a «norwegian reset» (switch the power on/off) and the second time it boots.

Christer


Old chinese proverb:

If I hear — I forget, If I see — I remember, If I do — I understand

IP Logged
 

Rad

Radministrator
*****
Offline


Sufferin’ succotash

Posts: 4090
Newport Beach, California

Back to top



Re: Ghost 2003 — General Exception 36000 — again
Reply #3 — Feb 4th, 2007 at 9:16pm

 

«norwegian reset» .. never heard that term before. but i like it. �Smiley

definitely some weirdness going on, if the system does not boot on the first power-up.

and if it’s not booting on the first boot, then i think that rules out any heat issues.

what about ide controller issues? .. i thot of that when you mentioned it might be having trouble when trying to access drives. the primary drive typically gets the most work and therefore usually dies first.

does the unit have good cooling/fans/air-flow?
swapping out components would provide valuable insight.

perhaps you could run some disk utilities, to be if it detects any hard disk anomolies.

these are difficult problems to troubleshoot.

the good thing about having a back-up image on the 2nd hard drive is that it makes swapping out the primary drive fairly painless.

WWW
 

IP Logged
 

NightOwl

Radministrator
*****
Offline


«I tought I saw a puddy
tat…»

Posts: 5826
Olympia, WA—Puget Sound—USA

Back to top



Re: Ghost 2003 — General Exception 36000 — again
Reply #4 — Feb 4th, 2007 at 10:03pm

 

Christer

Two very interesting statements:

Quote:

One vital issue that I failed to mention is that from «cold», the computer does not start on the first attempt. He has to do a «norwegian reset» (switch the power on/off) and the second time it boots.

Quote:

The computer was cleaned out (from dust) by myself only a few weeks ago when I installed a new video card.

When did the last successful Ghost boot with image creation or restore occur?

Whenever a system problem occurs—I try to start listing everything I have done (system setting changes, software installations or uninstalls, hardware upgrades, software utility(s) run, etc.) recently in chronological order to the best of my memory?

Relative to any recent changes, when did the above symptoms first occur—i.e. where in the chronology of any recent changes do these symptoms first appear?

Depending on the answers, I would look for possible compatibility issues if the problems began after the video card was installed!

Possibly memory management conflict by the BIOS is occurring—many BIOS’s require that resource allocations be *manually* reset from within the BIOS—especially when it come to IRQ assignments—even though most newer systems are supposed to *play nice* with *Plug-n-Play* devices.

I had an IRQ conflict occur on my system when I attempted to install WinXP the first time—with all the PCI devices hooked up as I had been normally using them with Win98se—when I attempted to run the installation WinXP CD—I could not get the Windows PE to load without a IRQ conflict crash and system halted.  I removed the network card, the sound card, and the modem—I left only the video card hooked up.

I then booted to the BIOS, told it to reset the IRQ allocation of resources.  I was then able to boot the installation CD—installed WinXP without further problems.

I then went back and installed each device, one at a time—re-booting to let the BIOS allocated resources one device at a time, and also letting WinXP install the device drivers.  Once successful, I would shut down and added another device.

I added the network card first, then the sound card, and finally the modem.


____________________________________________________________________________________________

No question is stupid … but, possibly the answers are Wink !

IP Logged
 

Christer

�bermensch
*****
Offline

Posts: 1344
Sweden

Back to top



Re: Ghost 2003 — General Exception 36000 — again
Reply #5 — Feb 5th, 2007 at 3:28am

 

Rad,

«norwegian reset», well, there are many «norwegian stories» circulating in Sweden. Most of them focusing on how sweet and stupid they are. There are as many «swede stories» circulating in Norway. Brother nations they call us!

About the issue at hand, I don’t think it is heat related. The HDDs run at normal (low) temperatures in a well vented case but there is no HDD fan (except the small one in the mobile rack). If it is HDD failure, that will be confirmed in two steps: 1) substituting a different HDD and if Ghost loads without errors after that 2) reinstall the troublesome HDD and nuke it by DELPART which should rewrite everything on that HDD.

Having the images on a different HDD is important in situations like this. Regrettably, there is no Disk-to-Image but only Partition-to-Image which means that XP has to be installed on a new HDD, during which the HDD is partitioned prior to restoring the image. (That also will put the correct MBR on the new HDD which is lacking from a Partition-to-Image.)

NightOwl,

I said that I cleaned out the computer when installing a new video card a few weeks ago. I discussed this with my friend after posting and it actually was a few weeks before Christmas which makes it more like a few months ago.

The computer has been running flawlessly after the new video card was installed. He has been very satisfied with «Google Earth opening up a whole new world on the new hardware». There has not been a hint of any compatibility issue during the few months after the new video card was installed.

The last time Ghost started from the GBDs was after installing the new video card when the system was reimaged and the image checked for integrity.

Every «piece of evidence» indicate that the malware is the culprit. An additional «piece of evidence» is that he has analyzed his actions last week when things started to go wrong. He came to the conclusion that he may have picked up the infection when he wanted to join an association and pay the fee over the internet with his credit card. The transaction was not completed but an error due to technical difficulties was reported.

Torpig is a keylogger — password stealer. The strange thing is that it is over a year old and Norton should have detected it. I don’t remember which but one of the other malware has the ability to shut down AntiVirus software and/or «allow» themselves in the FireWalls. That may explain why Norton didn’t detect the malware and its actions.

I will do some more googling and share any information that I find.

Christer


Old chinese proverb:

If I hear — I forget, If I see — I remember, If I do — I understand

IP Logged
 

Christer

�bermensch
*****
Offline

Posts: 1344
Sweden

Back to top



Re: Ghost 2003 — General Exception 36000 — again
Reply #6 — Feb 5th, 2007 at 3:40am

 

I have also failed to mention that the computer runs in Safe Mode without screen issues (it does not intermittently go black). I thought it may be the video drivers but unless damaged, the don’t go bad «over night», right?

Christer


Old chinese proverb:

If I hear — I forget, If I see — I remember, If I do — I understand

IP Logged
 

NightOwl

Radministrator
*****
Offline


«I tought I saw a puddy
tat…»

Posts: 5826
Olympia, WA—Puget Sound—USA

Back to top



Re: Ghost 2003 — General Exception 36000 — again
Reply #7 — Feb 5th, 2007 at 9:19am

 

Christer

Quote:

Every «piece of evidence» indicate that the malware is the culprit.

Well, the sequence of events does not seem to support that the video card is the culprit.

But, I can not think of how malware could effect the initial POST of a system that requires the «norwegian reset»!  Even if the malware is infecting the Master Boot Record (MBR) on the HDD—accessing the MBR would be later in the process than when the system is initially powered on.

And, when booting from a floppy boot disk—the main system is essentially isolated being as the MBR that is read is that of the floppy disk—now the only system level issue would be the CMOS settings!

Failure of electronics is most likely early in its life cycle of a device…but,

Quote:

I have also failed to mention that the computer runs in Safe Mode without screen issues (it does not intermittently go black).

That tends to point a finger at a software issue—if it were hardware related—Safe Mode should not solve the problem!

The fact that you can boot to DOS with the boot floppy successfully, but the system reports an error when Ghost is being loaded usually means there’s a problem with device compatibility and accessing of HDD’s or optical drives:

How to troubleshoot the error: «Internal error 36000 . . . «

It will be interesting to hear your ongoing troubleshooting efforts and results!


____________________________________________________________________________________________

No question is stupid … but, possibly the answers are Wink !

IP Logged
 

Christer

�bermensch
*****
Offline

Posts: 1344
Sweden

Back to top



Re: Ghost 2003 — General Exception 36000 — again
Reply #8 — Feb 5th, 2007 at 10:57am

 

NightOwl,

Quote:

But, I can not think of how malware could effect the initial POST of a system that requires the «norwegian reset»!

I’m having a hard time getting that one straightened out too … Wink … !

I had already seen it but thanks for the link to the Symantec web page. If installing a different hard disk does not make a difference (Ghost 2003 does still not load from the GBDs), then some other hardware must be smoked. If it does make a difference, I will reinstall the original hard disk and try the suggestions in that article. Even if using switches works, I don’t regard that as a long term solution. I will nuke the hard disk using DELPART and see what gives after that. If still no luck, a new hard disk will be installed.

My thoughts on malware writing to the disk is that Ghost does write to the hard disk. I have no idea in which location Ghost 2003 «marks» a disk but malware may use the same location. It is a possibility … Lips Sealed … maybe … �Undecided … !

Christer


Old chinese proverb:

If I hear — I forget, If I see — I remember, If I do — I understand

IP Logged
 

NightOwl

Radministrator
*****
Offline


«I tought I saw a puddy
tat…»

Posts: 5826
Olympia, WA—Puget Sound—USA

Back to top



Re: Ghost 2003 — General Exception 36000 — again
Reply #9 — Feb 6th, 2007 at 9:06am

 

Christer

Quote:

My thoughts on malware writing to the disk is that Ghost does write to the hard disk. I have no idea in which location Ghost 2003 «marks» a disk but malware may use the same location. It is a possibility … �… maybe … � … !

Well, that’s a thought! �My experience with modifying absolute sector 62 where Ghost 2003 *marks* each HDD—as well as placing its *fingerprint* data—has shown that Ghost does access that code on each Ghost load, if a single data point is altered prior to the Ghost load—you get the opening screen stating that Ghost needs to *mark* the drive again (so there must be a *check-sum* for the data Ghost places in sector 62 that must pass testing).

I’ve written a number of different thing to that sector—Ghost simple over-writes anything there when it *marks* the HDD again, if you allow it to during that load when it reports finding an un-marked HDD. �So, I don’t know if a virus or malware could place data there that can protect itself from another program overwriting data in that sector. �And I’ve never had Ghost fail to load because of changes in that sector—but maybe malware could effect that!??????

Here’s a Windows based *sector editor* (

Roadkil’s Sector Editor

) that would allow you to look at that sector 62—or any other sector for that matter—see here for discussion:

Invalid Partition Offset Error during Integrit

And here’s another discussion about using a DOS based *disk editor* (

PTS Disk Editor

):

Erase DiskID on external USB drive

You can use these tools to just *look* if you wish—you don’t have to actually edit or modify anything!


____________________________________________________________________________________________

No question is stupid … but, possibly the answers are Wink !

IP Logged
 

El_Pescador

�bermensch
*****
Offline


Thumbs Up!

Posts: 1605
Bayou Country, USA

Back to top



Re: Ghost 2003 — General Exception 36000 — again
Reply #10 — Feb 6th, 2007 at 11:31am

 

Christer wrote on Feb 5th, 2007 at 10:57am:

«… My thoughts on malware writing to the disk is that Ghost does write to the hard disk. I have no idea in which location Ghost 2003 «marks» a disk but malware may use the same location. It is a possibility … Lips Sealed … maybe …  Undecided … ! …»

CLICK HERE for reference to ancient malware that at the time could — and did — deny access to Windows Update and to

all

the Symantec products (a full Norton SystemWorks 2003 Professional suite) on my PC.  I wonder if it did so in a manner consistent with Christer’s musings.

BTW,

BugBear

failed to stymie my active Roxio GoBack which luckily made for an instant recovery.

EP

Cry

WWW
 

IP Logged
 

Christer

�bermensch
*****
Offline

Posts: 1344
Sweden

Back to top



Re: Ghost 2003 — General Exception 36000 — again
Reply #11 — Feb 6th, 2007 at 3:29pm

 

NightOwl and El_Pescador,
I’m a little short on time right now but I will take your thoughts/suggestions in consideration. As you may remember, I do not have the computer to hand. If I find the time, I will probably go there tomorrow.

Thanks,
Christer


Old chinese proverb:

If I hear — I forget, If I see — I remember, If I do — I understand

IP Logged
 

Christer

�bermensch
*****
Offline

Posts: 1344
Sweden

Back to top



Re: Ghost 2003 — General Exception 36000 — Restori
Reply #12 — Feb 7th, 2007 at 3:13pm

 

I was at my friends tonight and did some harware swapping.

1) Removed his infected HDD and substituted another HDD — same error when launching Ghost 2003 from Ghost Boot Disks. Put his HDD back.

2) Removed new video card and installed the old video card — same error. Put new video card back.

3) Thought I would remove one RAM module and run on a single module one after the other. Not possible since it was RAMBUS and it seems to be necessary to fill all the slots, either with memory sticks or «bridges» (or whatever they are called). I did remove and reseat. (Never worked with RAMBUS before!)

4) Removed the BIOS backup battery and checked the voltage — OK. I jumpered to clear CMOS and jumpered back. Reseated the battery.

When I tried to restart, I had long (2-3 seconds) BIOS beeps in 2-3 seconds interval. Nothing happened. I tried to find out what that means but found no BIOS beep code fitting that description other than «all other BIOS beep codes indicate RAM problems». I removed the RAMBUS modules and tried to start without them and had the same BIOS beeps. (I knew that it wouldn’t start … Lips Sealed … but did it to find out if the BIOS beeps were different but they were the same.)

My friend will take the memory modules to a computer shop tomorrow and have them checked.

My conclusions:

The infection and Ghost not launcing are not connected.

The computer was infected and had hardware problems simultaneously.

The hardware problem is either memory module(s) or motherboard. (The motherboard is a possibility since I have mechanically disturbed it by removing/reseating the memory modules.)

What do you think?

Christer


Old chinese proverb:

If I hear — I forget, If I see — I remember, If I do — I understand

IP Logged
 

Christer

�bermensch
*****
Offline

Posts: 1344
Sweden

Back to top



Re: Ghost 2003 — General Exception 36000 — Restori
Reply #13 — Feb 9th, 2007 at 2:36am

 

One of the local computer shops was closed for «stock taking» and the other had no means for testing RAM or RAMBUS. My friend needs his computer and decided to buy a new motherboard and memory modules. Two 256 MB RAMBUS modules would be twice as expensive as a new motherboard and a 512 MB PC3200 RAM module! The difference is made up for by me installing the new hardware and reinstalling the software. If possible, a repair installation will be done.

Christer


Old chinese proverb:

If I hear — I forget, If I see — I remember, If I do — I understand

IP Logged
 

El_Pescador

�bermensch
*****
Offline


Thumbs Up!

Posts: 1605
Bayou Country, USA

Back to top



Re: Ghost 2003 — General Exception 36000 — Restori
Reply #14 — Feb 9th, 2007 at 10:07am

 

Christer wrote on Feb 9th, 2007 at 2:36am:

«… Two 256 MB RAMBUS modules would be twice as expensive as a new motherboard and a 512 MB PC3200 RAM module!…»

In the event those surplus RAMBUS sticks eventually prove fully functional, they can be auctioned on eBay and should draw handsome bids. �I recently bought two 128MB sticks that way and I had to bid almost 65% of the new ‘street’ price Shocked

EP

Cry

WWW
 

IP Logged
 

I’m trying to load an image onto a Seagate 1gb HD, the image is very small, we’ve used it many times before.  We’re using Symantec 8.0 for PCDOS.  I’ve run a killdisk utility on the drive to completely wipe it.  It begins to install the image and will stop at different points each time giving the same error:
«Internal Error 36000
An internal inconsistency has been detected»

I’ve tried running the Ghost.exe with the -ws- -wd- flags, this has not resolved the issue.  Anyone have any other ideas?  This is a very old machine, so please dont suggest using a newer version of ghost.

Ghost 2003 Internal Error 36000

After running chkdsk /f on all drives in the system,
I started an image backup of a Windows Small Business Server (SBS) 2003 system
from a Norton Ghost 2003 boot CD. I was attempting to backup an internal
IDE drive to a double-layer DVD in the system’s internal DVD writer.
When I attempted to backup drive C (the second partition to a double-layer DVD,
I got a «File Name ? (546)» error message. The backup aborted shortly after
it started with the current file being backed up listed as «0 $MFT».

When I hit enter for «OK», I then received the following error message:

Internal Error 36000

An internal inconsistency has been detected
If this problem persists, contact Symantec Technical Support
at http://service.symantec.com


		[  OK  ]

When I hit enter, I saw the following:

ABORT: 12020, Write to CD/DVD disc failed

ABORT: 36000, A generalException occurred

I rebooted and hit F8 prior to the system booting from the Ghost boot
disc to choose what entries in config.sys and autoexec.bat should be
processed. I chose not to execute «Ghost.exe» from autoexec.bat. When
I got a command prompt, I entered ghost -fni instead, as suggested
by
How to troubleshoot the error: «Internal error 36000 . . . «.
I then proceeded with the backup of the second partition, excactly as before.
This time the backup completed succcessfully.

[/os/windows/utilities/backup/ghost]
permanent link

Понравилась статья? Поделить с друзьями:
  • Ghost recon breakpoint ошибка подключения к серверам ubisoft
  • Ghost recon breakpoint ошибка uplay
  • Ghost recon breakpoint ошибка mountain 01100 решение
  • Ghost recon breakpoint ошибка infinity 00100
  • Ghost recon breakpoint неизвестная ошибка mountain 01100