crcdisk.sys STOP 7B/xx/00/00 and BSOD

Hello, a good afternoon from Germany.
I'm new to this. My name is Manfred. And - of course - I have a problem.

My new notebook (MEDION, Multimedia Notebook MD 96543 (WAM2070), Original Windows Vista® Home Premium, AMD Turion™ 64 TL-64 Prozessor (2.2 GHz),
15,4” WS TFT, 2048 MB DDR-II RAM, 250 GB S-ATA, GeForce® 6150 Go, NVIDIA nForce Go 430) isn't working for me as needed. Especially video editing is now some limited.

I purchsed a 2nd 2.5" HDD, formatted it using one of my desktop PCs and replaced the original VISTA drive by this drive.
Then I installed Windows XP Professional SP2 from CD.
All fine.
The original drive is detected when connected using a special case and USB.
Using XP I can realize all my intentions, and I'm very satisfied.

The problem:
If I try to boot from the original and now external HDD I get a BSOD.
Booting in safe mode I can detect that the boot process stops at loading "crcdisk.sys".
The BSOD:
"STOP: 0x0000007B (0x********, 0xC0000034, 0x00000000, 0x00000000)".
(******** means several numbers at several boot processes.)

There are no informations in the WEB which I can understand and use for solving this special problem.
While the drives are reverted to their original positions VISTA is booting and working.
But VISTA doesn't detect the external 2.5" USB drive with NTFS and installed XP.
It's asking for several "bridge" drivers which it cannot find on the driver/tool CD that came with the new machine.
(See here some infos.
With one certain USB mouse VISTA is also asking for the appropriate USB mouse driver.
With another USB mouse it is flawlessly working.)

So I'm requesting some advice. I may be happy if I can understand it an convert it into success.
If I could also boot from the external (original VISTA) drive I could also use (sometimes) the built-in DVB-T TV device.

Give a "Kraut" a chance.
At present is the best of all that I detected this forum. Really amazing stuff.

Best regards,
Manfred

2 things to check.
1/In bios did you check the sata/ide settings?
2/ Insert your Vista DVD to repare the system, when it blocks, wait at least 10 to 20 minutes (i know it's quite long) By chance you'll get the install menu, repare (another 5 minutes) and cross fingers.

Hi Manfred,

Here is some info from the Micrsosoft Database about the BSOD 0x0000007B..

0x78: PHASE0_EXCEPTION
The PHASE0_EXCEPTION bug check has a value of 0x00000078.
This bug check occurs when an unexpected break is encountered during HAL initialization. This break can also occur if you have set the /break parameter in your boot settings but have not enabled kernel debugging.


It also Means the HAL or Hardware Access Layer has changed since you installed Vista, unfortunately you have to Clean reinstall Vista to fix this error because the HAL settings are automatically set during install and are permanently locked afterwards...


We have a Tutorial here: Clean Install with a Full Version of Vista

Let me know
Cheers
Steven

Thanks, @ Steven,
but... ...what I get is "seven-Bravo"...
M$ tells a lot on this 7B and 34 issue. It's only hard to understand.

Another issue:
That I must swap the drives between external and built-in each time if wanting to use VISTA e.g. for repairing it.
Not really much work coz the notebook case is easily to open at the buttom side. 5 screws and done. Nevertheless: Carefully doing this needs around half an hour.
Additionally: I'm not sure what I really can do. The notebook is OEM stuff with a recorvery DVD and a Microsoft VISTA DVD. I do not know (at present) what the VISTA DVD can do or not.
Important may be to know what happens if I insert the DVD, boot from optical drive and try to repair a VISTA system on an external HDD that is not C:\ ...
Yes, I'd like to find a way to "repair" VISTA on the external drive...

What I found now is something on "wrong" drive number in a "group" that is noticed in the registry. There may be something to delete by using regedit. I didn't have the time to study all items but I'll do it this night and see...

So long many thanks to all who repied.

Best regards,
Manfred - the "Kraut"...

Did you try what i suggested above?
I know it works on some issues having the EXACT same problem and error.
If it doesn't work there is another issue but we have to be sure 1st that test N°1 doesn't work.

Hey Manfred,

Sorry my bad..Here are the correct Error codes...


Bug Check 0x7B: INACCESSIBLE_BOOT_DEVICE

The INACCESSIBLE_BOOT_DEVICE bug check has a value of 0x0000007B. This bug check indicates that the Microsoft Windows operating system has lost access to the system partition during startup.

Cause
The INACCESSIBLE_BOOT_DEVICE bug check frequently occurs because of a boot device failure. During I/O system initialization, the boot device driver might have failed to initialize the boot device (typically a hard disk). File system initialization might have failed because it did not recognize the data on the boot device. Also, repartitioning the system partition or installing a new SCSI adapter or disk controller might induce this error.
This error can also occur because of incompatible disk hardware. If the error occurred at the initial setup of the system, the system might have been installed on an unsupported disk or SCSI controller. Some controllers are supported only by drivers that are in the Windows Driver Library (WDL). (These drivers require the user to do a custom installation.)

Resolving the Problem

This error always occurs while the system is starting. This error frequently occurs before the debugger connection is established, so debugging can be difficult or impossible.
Resolving a failed boot device problem: If a boot device is at fault, you must edit the boot options.For more information about these options, see Boot Options for Driver Testing and Debugging .
Resolving an incompatible disk hardware problem: If Setup autodetects the controller, you might have to skip detection and use a specific manufacturer's disk to load the driver. Also, check the availability of updates for the system BIOS and SCSI controller firmware. Updates of this kind are typically available on the Web site or BBS of the hardware manufacturer.
Remove any recently added hardware, especially hard disk drives or controllers, to see if the error is resolved. If the problematic hardware is a hard disk drive, the disk firmware version might be incompatible with your version of the Windows operating system. Contact the manufacturer for updates. If you removed another piece of hardware and the error is resolved, IRQ or I/O port conflicts likely exist. Reconfigure the new device according to the manufacturer's instructions.
Confirm that all hard disk drivers, hard disk controllers, and SCSI adapters are listed in the Microsoft Windows Marketplace Tested Products List.
If you recently added a driver, restart your computer, and press F8 at the character-based menu that displays the operating system choices. In the Advanced Options menu, select the Last Known Good Configuration option. This option is most effective when you add only one driver or service at a time.
In addition, check your computer for viruses by using any up-to-date, commercial virus scanning software that examines the Master Boot Record of the hard disk. All Windows file systems can be infected by viruses.
This error can also occur because of hard disk corruption. Run Chkdsk /f /r on the system partition. You must restart the computer before the disk scan begins. If you cannot start the computer because of the error, use the Recovery Console and run Chkdsk /r.
If you cannot start the system in the last known good configuration, you should try to start off the Windows CD. Then, you can run Chkdsk from the Repair Console.
Warning If your system partition is formatted with the FAT file system, the long file names that the Windows operating system uses might be damaged if you use Scandisk or another MS-DOS-based hard disk tool to verify the integrity of your hard disk drive from MS-DOS. Always use the version of Chkdsk that matches your version of Windows.
If your system has SCSI adapters, contact the adapter manufacturer to obtain updated Windows drivers. Try disabling sync negotiation in the SCSI BIOS, checking the cabling and the SCSI IDs of each device, and confirming proper termination. For IDE devices, define the onboard IDE port as Primary only. Also check each IDE device for the proper master/subordinate/stand alone setting. Try removing all IDE devices except for hard disks. Finally, check the System Log in Event Viewer for additional error messages that might help identify the device or driver that is causing the error.
To analyze this error: Run an lm (List Loaded Modules) command in the debugger. Verify that the following drivers were loaded: disk, classpnp, ftdisk, partmgr, and FAT or NTFS.
kd> lm

start end module name
80001000 80016000 hal (deferred)
80016000 80018c40 bootvid (deferred)
80019000 8001dfc0 pciidex (deferred)
8001e000 8001ff60 dmload (deferred)
80086000 80086980 pciide (deferred)
802c1000 802cc000 pci (deferred)
802cc000 802d39a0 isapnp (deferred)
802d4000 802ed000 ftdisk (deferred)
802ed000 802f3820 mountmgr (deferred)
802f4000 802fad40 fdc (deferred)
802fb000 802fdc20 partmgr (deferred)
802fe000 802fef00 wmilib (deferred)
8039b000 803b8000 dmio (deferred)
803b8000 803cb000 atapi (deferred)
803cb000 803d1560 disk (deferred)
803d2000 803d8e80 classpnp (deferred)
803d9000 803fa000 fastfat (deferred)
80400000 80540000 nt (pdb symbols) \\localsymbols\symbols\exe\ntoskrnl.dbg
80540000 80546f20 ksecdd (deferred)
80547000 80554620 cnss (deferred)
80555000 80579000 ndis (deferred)

You probably have pci or isapnp loaded. Also make sure your controller drivers are loaded. That is, make sure Atapi.sys is loaded with the channel drivers (pciide and pciidex or intelid) or scsiport.sys is loaded with the appropriate miniport driver.
It is helpful to know as much as possible about the boot device that Windows is installed on. For example, you can investigate the following items:

• Find out what type of controller the boot device is connected to (SCSI, IDE, 1394, etc). Find the manufacturer of non-IDE controllers (Adaptec, Symbios, and so on).
• Note the SCSI ID of the boot device if you are using SCSI.
• Indicate if other devices are attached to the same controller that the boot device is on (CD-ROM drives, zip drives, and so on).
• Note the file system that is used on the drive.

The !devnode extension gives you more information, if you know what your boot devices are.
Typically Plug and Play cannot assign resources to the boot device. You can verify this restriction by finding an entry for the service. If the status flags include DNF_INSUFFICIENT_RESOURCES or do not include DNF_STARTED or DNF_ENUMERATED, you have found the problem. Try !devnode 0 1 scsi or !devnode 0 1 atapi to save some time instead of dumping the whole device tree.

Bug Check 0x34: CACHE_MANAGER

The CACHE_MANAGER bug check has a value of 0x00000034. This indicates that a problem occurred in the file system's cache manager.


Cause

One possible cause of this bug check is depletion of nonpaged pool memory. If the nonpaged pool memory is completely depleted, this error can stop the system. However, if the amount of available nonpaged pool memory is very low, another kernel-mode driver requiring nonpaged pool memory can also trigger this error.
Resolving the Problem

To resolve a nonpaged pool memory depletion problem: Add new physical memory to the computer. This will increase the quantity of nonpaged pool memory available to the kernel.

Like sidney1st has mentioned...You need to follow this repair tutorial here: Repair Install For Vista

Steven

Sorry, forgot to report that there is no adequate option in the BIOS.
Guys, Steven, your assistance is overwhelming!

What to do?
For avoiding any misunderstanding I'll state:

• The external drive with VISTA on it is running fine while working inside the notebook as C:\.
• The disadvantage is only that a certain video editing tool is not working properly under VISTA.
• The advantage of using the VISTA drive may be that also DVB-T receiver works and allows saving of broadcastings.
• The best performance of the whole system (notebook and OS) I get using it with XP.

Using XP I can

• access the external (VISTA) notebook drive and use it in a normal way

but I cannot

• boot from this drive with an installed VISTA.

Now I made a decision:
I'll try to recover this drive as VISTA drive using the OEM recovery tool. Then I have a "factory new" drive and system.
After this I'll remove it from the notebook and connect it to an USB port.
Let's see what happens (with no drive inside the notebook!!!).

• IF it fails to boot in the known way I'll try to use the Windows VISTA DVD and to start the repair function.
• IF I have success I'll move the new XP drive back to its place in the notebook.
• IF it will boot in the known way I'll try to access the external (VISTA) drive and test it as data drive.
• IF now all is running well I'll try to boot from the VISTA drive using the boot manager (F12).

It's a game now.
I may also take one of my many unused video data drives, format it and connect it to an USB port of the notebook while no other drive is active. If this drive is recognized I'll try to install an enterprise version of XP from CD on this drive. This because I'm some familiar with XP.
After this I'll put the internal XP drive back to the notebook and see whether it will boot normally. Then I may try to boot from the fresh XP on the external drive.
A game.
All remarkable issues I'll write down and report here.

D'accord?
Thank you, thank you, but I didn't understand much of it.
My "game" is now a bypass. What I do is what I understand even if it may not work.

Here (Europe) a new day has started. I'll do my best to make it successful for me.

Best regards,
Manfred (the "Kraut" )

No problem and if you have some, just ring the bell
I made running a Dell Inspiron with no drive using only an USB flash drive.

All the best,
Sid.