PDA

View Full Version : Problems continue


Invalid
23rd April 2005, 21:09
Ok I had problems with my new motherboard so I put my old one while I RMA it.

Everything was fine until I stuck in the new memory. Upon booting up my screen is blank, no signal to the display. However, if I just wait once windows loads my screen turns on.

So in a nutshell the problem is that there is no video signal sent to the display until windows loads since upgrading the memory.

But when I stick the old memory back in the problem does not revert, it stays the same. I am going to clear the cmos and try again but wtf is going on?

The memory is supported the motherboard is a Soyo KT400 Dragon Ultra Platinum and the memory is PC3200 Corsair Value Select.

Any help is appreciated. Its been 2 weeks now without a computer trying to fix all this. =(

Invalid
23rd April 2005, 21:25
Ok I just cleared the cmos and put in all the new memory and it loaded fine. So I guess I just had to clear it for the different memory.

At least I am getting somewhere! Now I am going to try one last time with the brand new motherboard and see what happens. But I am not getting my hopes up. :mad:

Invalid
23rd April 2005, 21:44
Ok. I am now on the new motherboard with all 4 memory chips in place.... I don't get this! All I did this time was cleared the cmos again and put everything together and booted. And it worked flawlessly. So weird!!

I am going to test this out for a few days and look for anything weird but it seems to be working fine for now...


I do have one new question. My system properties shows something I never saw before and do not know what it means. It says "Physical Address Extension". What does this mean?

Here is a sshot:
http://www.voomo.com/pa.jpg

I searched google and only found things pertaining to 4g of ram in win2000 and such. So I don't understand.

Fibbles
23rd April 2005, 22:17
Isn't WinXP based on 2000? That could just be left over.

ỒĊBłůē
23rd April 2005, 23:28
PAE is automatically enabled on computers running Windows Server 2003 with Service Pack 1 (SP1) and Windows XP with Service Pack 2 (SP2) when DEP is enabled on a computer with a processor that supports the no-execute page protection feature.
Try googling info on pagefile, virtual memory, etc...

Invalid
24th April 2005, 00:23
What does it do though? I don't get it. Is it basically because the cpu is 64bit?

Starbuck3733T
24th April 2005, 03:28
It's a feature that keeps stuff in "data" memory from being executed. Kind of an anti-buffer overflow device. I don't understand it fully but I think that's the gist of it.

fillip
24th April 2005, 03:31
It's a feature that keeps stuff in "data" memory from being executed. Kind of an anti-buffer overflow device. I don't understand it fully but I think that's the gist of it.
Ahhhh, that'd be the architecture AMD built into there cpu's because of MS being too lazy to write software that wasn't so vunerable then?
Will look out for that when I upgrade this summer.

Starbuck3733T
24th April 2005, 03:43
Not so much MS as EVERY POSSIBLE VENDOR. EVeryone get's sploited!

fillip
24th April 2005, 03:47
Not so much MS as EVERY POSSIBLE VENDOR. EVeryone get's sploited!
Really? so it affects any OS, hmmm, i'm sure the articles I read only mentioned microsoft, maybe they were just having their usual dig at them.
But it is a fix for a problem inherent in software and not pc hardware yes?

Invalid
24th April 2005, 03:56
The reason I am so confused is because before when I was having all these problems with this computer this was not there. Now ever since this has been there I have had none of the problems.

So for some reason whatever this means is important for my machine for some reason.

fillip
24th April 2005, 04:25
Maybe the CMOS just wasnt clearing properly before and as such the necessary hardware changes weren't taking effect, or at least there was some confusion between what you had installed and what was stored in the CMOS. :unsure: