I recently embarked on a new build. I've got an Asus P5KC mobo and an Asus ATI EAH3650 graphics card. I successfully installed windows and chipset drivers, but as soon as I installed the graphics card drivers, I got the following problem:
When using the DVI out, I get a blank screen when windows loads. Its still there in the background cause I can shut down using the keywboard shortcuts, but just a blank screen.
If I use a DVI to VGA adaptor, and use the vga input of the monitor, it works fine.
My other computer displays fine through DVI to my monitor so this rules out the monitor and DVI cable as problems.
I am running Windows XP with service pack 2 and the disk has 2004 on it. I don't want to do a windows update yet because this version of XP won't be on this computer (I'm getting XP Pro for this new computer but wanted to test all parts to make sure they work using this Home edition I've got).
1. Do you think there is some realease from MS since 2004 that could be giving me this issue?
2. Is this a driver issue? I've got the latest driver installed, but again, maybe its looking for something in Windows that isn't there. I've heard talk of .net Framework or perhaps Direct X?
3. Is the graphics card likely to be faulty?
Or is there anything else that could be causing this? I've got a 450W Corsair PSU (new) so would have thought power wasn't an issue.
Thanks
When using the DVI out, I get a blank screen when windows loads. Its still there in the background cause I can shut down using the keywboard shortcuts, but just a blank screen.
If I use a DVI to VGA adaptor, and use the vga input of the monitor, it works fine.
My other computer displays fine through DVI to my monitor so this rules out the monitor and DVI cable as problems.
I am running Windows XP with service pack 2 and the disk has 2004 on it. I don't want to do a windows update yet because this version of XP won't be on this computer (I'm getting XP Pro for this new computer but wanted to test all parts to make sure they work using this Home edition I've got).
1. Do you think there is some realease from MS since 2004 that could be giving me this issue?
2. Is this a driver issue? I've got the latest driver installed, but again, maybe its looking for something in Windows that isn't there. I've heard talk of .net Framework or perhaps Direct X?
3. Is the graphics card likely to be faulty?
Or is there anything else that could be causing this? I've got a 450W Corsair PSU (new) so would have thought power wasn't an issue.
Thanks
