Sign in with
Sign up | Sign in
Your question

Urgent help required. Windows 7 does not install :(

Tags:
  • New Build
  • Windows 7
  • Systems
Last response: in Systems
Share
July 17, 2010 2:10:47 PM

It's been over a week and I'm still struggling to install Windows 7 and really not sure what else I can do now. Please help.

SYSTEM
Motherboard: Gigabyte EX58-UD5
Graphics Card: NVIDIA Quadro CX
CPU: Intel i7 980x
RAM: Corsair 24GB Dominator
HDD: Corsair P256 SSD
OS: Windows 7 Ultimate x64

Peripherals plugged in: Monitor (HP LP2475w), Mouse (Logitech G9 Laser) and Keyboard (Microsoft Ergonomic 4000).

INSTALLATION APPROACH

1. Boot into BIOS, select "load optimised defaults" and then ensure USB keyboard and mouse are enabled as this is disabled by default.

2. Boot using Ultimate Boot CD v5.02 and run HDD Erase 4.0 on the SSD.

3. Boot using Windows 7 installation disc and step through the installation.

PROBLEM

After copying files, expanding them and installing some features, Windows then reboots. After rebooting, it starts to complete the installation at which point I get a BSOD and the computer crashes and reboots.

TROUBLESHOOTING I'VE DONE

- Checked the hardware cables etc are snug and connect solidly.

- Swapped out the SSD for a Western Digital 1TB Caviar Black HDD and re-performed the install as above but came across the same issue.

- Run MemTest 4.0 with no errors reported.

- Ordered another copy of Windows 7 Ultimate x64 and performed the installation again using the above procedure without luck.

- Flashed the BIOS to the latest version (F12) and still I get the same issue.

- Enabled AHCI mode in the BIOS and performed the installation again (ensuring the Intel SATA RAID drivers are loaded by copying the files to a FAT formatted USB and loading them at the relevant stage of the Win7 installation). Still same problem.

I'm now at a loss as to what else I can do. Help, guidance and advice would be much appreciated.

More about : urgent required windows install

July 17, 2010 6:04:11 PM

Have you updated windows?

Nice computer by the way.
July 17, 2010 7:16:52 PM

Thanks GoalGuy. Although at the moment this super-beast is clearly being a little useless LOL.

You see, the thing is, I'm not able to log into windows to be able to run the update. But yes, that would be the first thing I'd so if I only I could get past the BSOD.

So I went through the installation procedure again and this time I had a camera ready to capture the BSOD :) 

Picture is here:

http://www.flickr.com/photos/37746517@N04/

I then booted into a Linux recovery environment and couldn't find the minidump which the BSOD is allegedly writing. Regardless, as least we have some "STOP" numbers and Error codes to investigate.

Additional Troubleshooting:

- Took out the 24GB RAM and replaced with a 3 x 2GB Corsair Platinum kit incase there was "too much" RAM for the installer to handle. Still no luck :( 

I'm now of the opinion that all my hardware is perfectly fine. This is perhaps a driver issue where the retail DVD has really outdated graphics driver. Currently I'm in the process of trying to slipstream the latest graphics drivers for my NVIDIA Quadro CX into the retail CD and create an updated installation DVD.
Related resources
July 17, 2010 8:19:11 PM

Do you have another video card?
Can you get into safe mode so you can remove the video drivers?
July 17, 2010 8:34:28 PM

Unfortunately not. No alternative graphics card available. Really do need to get this all working with the Quadro CX though as I use it heavily for graphics work. But yes, wish I did have a backup card for debugging purposes.

After the BSOD crash, when the system restart and tries logging into windows I get the following come up in a dialogue box (both when starting windows normally and in safe mode):

The computer restarted unexpectedly or encountered an unexpected error. Windows installation cannot proceed. To install Windows, click "OK" to restart the computer, and then restart the installation.


Clearly that BSOD was fatal :( 
a b $ Windows 7
July 17, 2010 8:51:57 PM

Can you try installing the graphics card in a different pcie slot?
July 17, 2010 9:07:59 PM

Your issue does seem to be microsoft/nvidia driver related but I found this on another site ... might have to use Linux disk to find it and it may be a hidden file but it makes sense ... in a perverted way. Just depends on how brave you are.

Hey yeah this method of deleting the nvlddmkm.sys in windows\system32\drivers directory works, then after i deleted the nvlddmkm.sys file i downloaded and installed the latest nvidia driver which replaced the nvlddmkm.sys with the newest version.

So you don't need to download the nvlddmkm.sys file just delete the nvlddmkm.sys file and download the latest nvidia driver version. (which was 195.62), and i have a nvlddmkm.sys file created on the 21/11/09 now (file version 8.17.11.9652)


I had the same issue when installing Win 7 and finally figured out it was my ATI card/drivers. Tried reinstalling win7 but got the same thing. Finally removed the partition, let Win 7 make and format new partition and do fresh install. Then I went into safe mode and uninstalled video drivers, ran driver sweeper and reinstalled ATI/AMD drivers I'd downloaded. so far so good. This is all assuming your video card is good.
July 18, 2010 4:20:34 AM

Tried re-installing again and stilling getting the same BSOD, but this time we've got a memory dump file now :)  Analysis below, seems to be confirming the problem resides with graphics card drivers.

@puterfx: I also deleted the nvlddmkm.sys file and rebooted. Installation is so badly corrupted anyway after BSOD it can't get into windows to reinstall the drivers.

@geofelt: OK you're next now :)  Going to try switching PCIe slots for the graphics card. But before I do that, I've realised I've got an eSATA bracket plugged in which I'm going to take out as it's superflous for now. Just in case.

--------------------------------------------------------------

BugCheck 116, {fffffa8014ade010, fffff88006da56c0, 0, 2}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+d06c0 )

Followup: MachineOwner
---------

10: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8014ade010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88006da56c0, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.

Debugging Details:
------------------


FAULTING_IP:
nvlddmkm+d06c0
fffff880`06da56c0 803db1899c0000 cmp byte ptr [nvlddmkm+0xa99078 (fffff880`0776e078)],0

DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT

BUGCHECK_STR: 0x116

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`060ae9c8 fffff880`05312ef8 : 00000000`00000116 fffffa80`14ade010 fffff880`06da56c0 00000000`00000000 : nt!KeBugCheckEx
fffff880`060ae9d0 fffff880`05312c02 : fffff880`06da56c0 fffffa80`14ade010 fffffa80`14ac6d50 fffffa80`14ac8010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`060aea10 fffff880`053b9f07 : fffffa80`14ade010 00000000`00000000 fffffa80`14ac6d50 fffffa80`14ac8010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`060aea40 fffff880`053e3b75 : 00000000`ffffffff 00000000`00001fa5 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`060aeb20 fffff880`053e22bb : 00000000`00000102 00000000`00000000 00000000`00001fa5 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`060aeb50 fffff880`053b52c6 : ffffffff`ff676980 fffffa80`14ac8010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`060aebf0 fffff880`053e1e7a : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`14c73b88 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`060aed00 fffff800`0296e166 : 00000000`1861dbf7 fffffa80`14ab2b60 fffffa80`12782b30 fffffa80`14ab2b60 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`060aed40 fffff800`026a9486 : fffff800`02843e80 fffffa80`14ab2b60 fffff800`02851c40 fffff880`01a30534 : nt!PspSystemThreadStartup+0x5a
fffff880`060aed80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nvlddmkm+d06c0
fffff880`06da56c0 803db1899c0000 cmp byte ptr [nvlddmkm+0xa99078 (fffff880`0776e078)],0

SYMBOL_NAME: nvlddmkm+d06c0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a0c8387

FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys

Followup: MachineOwner
---------
!