Solved startup problem with new(er) system

January 18, 2013 at 08:35:51
Specs: Windows 7, Amd Athlon 64 x2 dual core processor 6000+ 3.00GHZ, 5GB RAM
Frustrated! Sometimes windows starts up fine, other times it goes to just before the log on screen (with the windows emblem), then either the screen just turns black, and nothing further happens, or the system restarts and then is fine, or does the same bloody thing again. Sometimes when it do restart, it loads win7 without my gfx driver. So I updated drivers, same thing. The card is still fine, because it worked perfectly in my old PC, as soon as I put it in this one, trouble started. My specs: MSI K9N Platinum (MS-7250), Amd Athlon 64 x2 dual core processor 6000+ 3.00GHZ, Evga geforce GTX 470 1280MB. 5GB transcend RAM. I do also have a ntbtlog file but can't make out what is good and what not. This is really frustrating.

See More: startup problem with new(er) system

Report •

✔ Best Answer
January 28, 2013 at 14:00:59
Go to Control panel> Device Manager> View> Resources by connection.

This is a long shot.

You can check the BIOS to make sure the ACPI settings are not set for S3. I use S1 custom.



#1
January 18, 2013 at 08:41:11
I would have posted the ntbtlog file here, but I get an error: Entity too large.

Report •

#2
January 18, 2013 at 10:19:47
So, you changed out the graphics card or installed an add in card where you had been using an onboard graphics chip?

If this is the case you needed to remove the original drivers and then install the latest drivers for your card and OS.

From the link below it appears you don't have integrated graphics. What was the model of the old graphics card that you pulled?

http://www.motherboards.org/mobot/m...


Report •

#3
January 18, 2013 at 13:55:04
No I changed mother board and chip, fresh installation of win7, but used the same card from my old setup (which worked fine when it was still active)

I like to cook with wine...... .......sometimes I even add it to the food!


Report •

Related Solutions

#4
January 18, 2013 at 13:57:33
Could it be a bios setting that needs to be changed? Maybe a bios upgrade?

I like to cook with wine...... .......sometimes I even add it to the food!


Report •

#5
January 18, 2013 at 14:03:16
Windows 7 was installed to the old hardware. The new hardware may be different. I suggest you first attempt to correct the problems by installing all the drivers from the driver CD accompanying the new board.

If that doesn't fix things then perform a system repair. See the link below.

http://windows.microsoft.com/en-US/...


Report •

#6
January 22, 2013 at 07:13:30
i did a fresh installation. I always do when I change chipset.

I like to cook with wine...... .......sometimes I even add it to the food!


Report •

#7
January 22, 2013 at 09:44:44
Did you install the graphics drivers for the new card?

Post the model number of your power supply. The manufacturers site shows the following: "Minimum recommended power supply with +12 Volt current rating of 38 Amps".


Report •

#8
January 26, 2013 at 02:27:59
Corsair GS700. It has more than the recommended voltage on the GPU rail. I couldn't start my pc yesterday, So this morning I wanted to strip it and reassemble, but then I just decided to switch from one HD port to the other one. And the system started up without giving the two error sounds it usually did. So I think it might be a damaged port on the GFX card.

I like to cook with wine...... .......sometimes I even add it to the food!


Report •

#9
January 26, 2013 at 07:27:41
I am confused by your conclusions. If there is an issue with a hard drive connection how does that extrapolate to a damaged GFX card?

Report •

#10
January 26, 2013 at 16:11:35
Y-e-a-h.... If switching the hard drive port fixes the problem then the conclusion is that there is a problem with the hard drive (SATA) port or possibly the connector on the cable.

You have to be a little bit crazy to keep you from going insane.


Report •

#11
January 27, 2013 at 21:16:54
hehe no guys, I switched the HDMI port on the GFX card. But the solution was only temporary. When I start up, it either restarts by itself, or go into the old 800x640 (I think). In device mngr, under display devices, properties, I receive this error: Windows has stopped this device because it has reported problems. (Code 43). I googled some forums regarding this, turns out I'm not the only one. There's many others with the same problem, mostly running SLi, and their solution apparently, is the realtek nic network driver, they rolled it back, then all seems fine. Problem is, I don't have that network driver. I use Nvidia Nforce Network Controller. What I've found in the last day or so, if I boot up without my internet plugged, and without anything in the LAN ports and USB ports, everything works. Then after start-up I can replug my internet. Weird.

I like to cook with wine...... .......sometimes I even add it to the food!


Report •

#12
January 27, 2013 at 21:23:00

Report •

#13
January 28, 2013 at 04:14:09
Check Device Manager to see which IRQs are being shared. May be possible to reallocate.

Report •

#14
January 28, 2013 at 12:05:00
How do I go about doing that? Do I have to open each and everyone of everything in dvmngr, and select their properties?

I like to cook with wine...... .......sometimes I even add it to the food!


Report •

#15
January 28, 2013 at 14:00:59
✔ Best Answer
Go to Control panel> Device Manager> View> Resources by connection.

This is a long shot.

You can check the BIOS to make sure the ACPI settings are not set for S3. I use S1 custom.


Report •

Ask Question