On Sat, 12 Jan 2008 18:34:02 +0530, willgimmence wrote:
> I have a Dell XPS M1330 and have exactly the same issue.
>
> I have installed it on my custom built desktop and not had a problem.
Using
http://support.microsoft.com/common/international.aspx I reported
this. In reply there were some more detailed questions which I answered and
now I hope some Microsoft folks are sitting on that bug. To give it a
possibly higher priority, do the same.
Some more info from my side:
1) The content of the bluescreen flshing after stucking on
\Windows\system32\drivers\crcdisk.sys, before restart
<cite>
A problem has been detected and windows has been shut down to prevent
damage
to your computer.
If this is the first time you've seen this Stop error screen, restart your
computer. If this screen appears again, follow these steps:
Check for viruses on your computer. Remove any newly installed hard drives
or hard drive controllers. Check your hard drive to make sure it is
properely configured and terminated. Run CHKDSK /F to check for hard drive
corruption, and then restart your computer.
Technical information:
*** STOP: 0x0000007B (0x80603BA0, 0xC0000034, 0x00000000, 0x00000000)
</cite>
Of course I have no viruses, no new hardware in laptop and the disk is ok.
2) Log after "repair you computer" confirms the disk is ok. Most
interesting parts:
Number of repair attempts: 1
Number of root causes = 1
Root cause found:
A patch is preventing the system from starting.
Repair action: System restore
Result: Completed successfully. Error code = 0x0
Time taken = 77034 ms
3) I tried several options of booting ("Safe Mode", "Safe Mode with
networking", "Safe Mode with Command Prompt", "Enable Boot Logging",
"Enable low-resolution video (640x480)", "Debugging Mode", "Disable Driver
Signature Enforcement", "Start Windows Normally") after F8 numerous times.
After about 15 attempts of "Safe Mode" my comp once didn't hang/reboot but
managed to proceed. Windows was running. It finished configuring the
pluggin and other initial actions, I had no idea what to do more so I
restarted. The issue hadn't gone out.
--
Marcin Balcerzak