0x000000c4

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

My install of windows was acting funny after adding a 2nd video card. After
repeted driver installs and uninstalls i decided to run a "repair"
installation to see if this would help. Setup runs fine until it gets to the
detecting devices, when the green bar is approx 85% through i get a BSD with
a Stop Error: 0x000000C4 (0x00000060, 0x00000000, 0x00000084, 0x00000001)

Windows then restarts the install and it hangs agaain, over and over.....any
suggestions?
 
Matt L. said:
My install of windows was acting funny after adding a 2nd video card.
After
repeted driver installs and uninstalls i decided to run a "repair"
installation to see if this would help. Setup runs fine until it gets to
the
detecting devices, when the green bar is approx 85% through i get a BSD
with
a Stop Error: 0x000000C4 (0x00000060, 0x00000000, 0x00000084, 0x00000001)

Windows then restarts the install and it hangs agaain, over and
over.....any
suggestions?
Turn off automatic restart.
Then search the internet for stop error xC4. At least then, you will have
some idea about what is happening.

Jim
 
I understand the error to an extent...my trouble is that the "reapir" install
will not get past this point. So I can not boot back into windows or
continue with the install. This is what I need help with getting past.
 
Remove all unnecessary external devices or hardware and try again. You
should only have the Keyboard, Mouse and monitor when you install
Windows. Disconnect printers, scanners, external hard drives...
disconnect every thing except the items mentioned above. If the error
persists you may have to pull unnecessary internal cards.

John
 
Do you get a file name along with the 0xc4 error message, something like
filename.sys perhaps?

John
 
Matt L. said:
There was no filename listed...
Most of the reference I have found on the internet indicate that this error
code is generated by a driver verification program which is usally used for
debugging of a driver.
So, it seems likely that there is a driver somewhere on his system that
flunks whatever test this program provides.

I don't understand why this code shows up from a production system...

Jim
 
Back
Top