System Instability!

[Eric3988]

I know a variety of factors can cause one to have system instability but I am wondering if anyone can point me to some of the more common factors causing this. It's been happening for a week or two now that I've started using my PC for more than just browsing on the internet. It happens a lot when I exit out of Morrowind and sometimes randomly during the game.

It also is starting to happen infrequently when I'm browsing on Firefox too. In case if anyone asks, I have not overclocked any of my components and everything on my store bought machine is running stock. Just check my system specs for any specifics.

The one factor though I can definately identify is CompUSA. Ever since I took my computer to them to replace a faulty CD drive, its been acting screwy like this. They made me really suspicious when they srewed up my GPU and installed a fresh copy of windows on my system. It seems an awful lot just to replace a CD drive doesn't it? As always, thanks for the help in advance!

 

[Aevum]

ok, first of all, if you care for your computer, dont take it to those "computer supermarkets" for repair, they usualy hire the cheapest workers they can find and have them diagnose out of flow charts (if you dont know what a flow chart is, google it),
find a trusted shop around that can do things you cant do at home, learn to repair and replace simple parts yourself, replacing a CDrom is 4 screwes 2 cables and a jumper, easy as cake,

as for the instability diagnostics

you will need,
Ultimate Boot CD - http://www.ultimatebootcd.com/, its free, all you need to do is burn it and then boot from it,

3Dmark 2001 - www.futuremark.com the free version will suffice , 2001 is important becuase it pushes the CPU aswell as the GPU

3dmark 2003 or 2005, - put some high load on that mofo

ExcessGL - this benchmark detected my broken 6600GT when 3dmark03 and 05 ran fine,


now,
boot the ultimate boot CD,
run the fallowing tests

1st - Mersenne Prime Test, leave it for a few hours, best done before you go to bed, leave for work/school, if this fails, you have a cpu or motherboard problem,

2nd- memtest86, leave it for atleast 3-4 cycles, make sure its testing as highest level,
if this fails, your memory or motherboard is faulty, or your memory timmings are not correctly configured

3rd- start cycling the graphics tests, loop the 3dmarks for 3-4 passes each and then excess GL, if the prime and memtest86 came out clean, any problem caused here would be cuased by a driver conflict or a damaged video card,

and just remember to think, check voltages and temperatures in bios before and after the ultimate boot CD tests and try to find a utility that will check them during the testing you do in windows,

 

[Eric3988]

I didnt know that at the time cause my Dad told me to buy it from a store and get the warrenty, which is what I did. I took it there so I could get the cd drive replaced for free. Bastards...... if only they would of given me the cd drive. But I think the problem is motherboard related......the machine makes a weird noise that it didnt make before I took it to them. But hey, do you think they would replace the motherboard if my new graphics card doesn't work in the PCI-Ex slot? I think that would be evidence enough that the board is faulty. Thanks for the advice I'll try it out, but more suggestions are always welcome!

 

[infrared]

I think alot of us here started off in the same boat. The more you learn about computers, the more you realise how little the manufacturers seem to know, or at least the people putting them together.

Our first family pc went back 5 times because it would randomly crash after being on for a while... It was obvious to me that it was the PSU crapping out, and each time they tried replacing another part, sent it back and the same thing happened, over and over... In the end we gave up and got a full refund.

Custom building a PC is childs play, and you still have the warrantee on each component.

Anyway, i hope you get it sorted soon

 

[Eric3988]

I think alot of us here started off in the same boat. The more you learn about computers, the more you realise how little the manufacturers seem to know, or at least the people putting them together.

Our first family pc went back 5 times because it would randomly crash after being on for a while... It was obvious to me that it was the PSU crapping out, and each time they tried replacing another part, sent it back and the same thing happened, over and over... In the end we gave up and got a full refund.

Custom building a PC is childs play, and you still have the warrantee on each component.

Anyway, i hope you get it sorted soon

Yeah....
Thanks for sympathizing. Building your own PC from scratch is definately the way to go. Even if I have to warrentee every component by itself, it outweighs a store warrentee. I don't know for sure, but I'm still saying its the MOBO. The weird thing is I give them my whole PC to replace the CD drive and somehow my graphics card does not work when I pick it up. Not only that but the had to reinstall windows......

I should get my new X850XT tomorrow, so when I put that in the PCI-Ex slot and it does not work, I should be able to get a new MOBO from them. But this time I'm gonna have them boot up the machine while I'm there to prove it works and back up all my files before they fry it out.

 

[Solaris17]

weird noise? explain. where does it come from and what isnt working your graphics you say? or something else? and

 

[zekrahminator]

I think alot of us here started off in the same boat. The more you learn about computers, the more you realise how little the manufacturers seem to know, or at least the people putting them together.

Our first family pc went back 5 times because it would randomly crash after being on for a while

I got into PC Building when I realized that Gateway/Dell/HP simply didn't have what I wanted (good thing too, I might have ended up with an overheating P4, and an X300 on a 300W power supply ) Darth Flatulence was actually retail, I modded her a ton, and owe her a lot of my experience. And yes, I know what you mean when you say manufacturers really don't know anything . Except for Gateway...Gateway support is the best support for a retail PC I've ever seen . They give me codes for Microsoft Office 2000 that I've lost a ton of times...these guys rock. If you're going to buy a retail PC, go Gateway FTW!!!!!

 

[Eric3988]

The noise comes from a place a little below the power button I believe. About the graphics, when I last put in my Powercolor X800GTO the machine would continually reboot itself right before into going into windows.
No matter what I did the computer would not start up and go into windows whenever the card was in the PCI-Ex slot. I didnt get the chance to see if it was the card, b/c my dad wouldnt let me test it out on his computer and he wouldnt let me put in his graphics card into my computer's slot. So I just RMA'd the card and got a new one.

 

[Solaris17]

so the card works now? and what is under your power button? also was the card pci-e or agp?

 

[Eric3988]

so the card works now? and what is under your power button? also was the card pci-e or agp?

I'm getting the card tomorrow. I'll crack open my PC, after dinner and tell you whats under there. Both cards are PCI-Ex.

 

[Solaris17]

ok dude please do here are my thoughts now

in order

Power supply dude 300v? when you crack your case tell us how many amps are on the 12v rail it will be next to or under +12v it will look like this.

+3.0v -12v +12v 5.0v
20a .5a 10a 15a or something like that.

also HEAT im thinking your getting a little hot look in your bios under system status cpu/volatage control or something and tell us how hot is.


fixes

new power supply 400w+
arctic silver5 on the cpu a couple new fans or just move the originals for better air flow.

 

[Eric3988]

ok dude please do here are my thoughts now

in order

Power supply dude 300v? when you crack your case tell us how many amps are on the 12v rail it will be next to or under +12v it will look like this.

+3.0v -12v +12v 5.0v
20a .5a 10a 15a or something like that.

also HEAT im thinking your getting a little hot look in your bios under system status cpu/volatage control or something and tell us how hot is.


fixes

new power supply 400w+
arctic silver5 on the cpu a couple new fans or just move the originals for better air flow.

Thanks and I'm going to try that now....

 

[Eric3988]

Okay heres what I found:

My CPU idle temp is 44 C
My System idle is 39 C

and on my generic 300 Watt PSU it says 15 amps on the +12 ramp

I dunno, I'm scanning it viruses, maybe thats it, even though all I've downloaded off the web was some mods for Morrowind off of www.planetelderscrolls.com.

 

[Eric3988]

Okay heres what I found:

My CPU idle temp is 44 C
My System idle is 39 C

and on my generic 300 Watt PSU it says 15 amps on the +12 ramp

EDIT: Sorry for posting twice, my mistake, lol!

 

[Alec§taar]

Things I Have Seen That Lead To System Instability Over Time

I know a variety of factors can cause one to have system instability but I am wondering if anyone can point me to some of the more common factors causing this.

It's usually 3 things imo & experience with PC's over 15 or so years now, such as it has been:

1.) Heat (usually due to poor cooling & trying overclocks)

2.) Drivers + hardwares of unfinished, or, lower quality (these lead to the infamous "BlueScreen/BSOD" stopcodes (like IRQL_DRIVER_LESS_THAN_OR_EQUAL) on Windows, but for good reason - protection when a driver's "touchy")).

Fact is, here? I lean FIRST to the driver... why? Because the OS "views" your hardware thru them & its "HAL" (hardware abstraction layer).

3.) DLL versioning mismatches (of which Windows System File Protection & 'side-by-side assemblies loading' helps to "offset/stop" nowadays since XP/Server 2003 models, as well as better installation routines/programs (ala Microsoft MSI &/or InstallShield) which can load DLL versions into the app's local folder, instead of public %WinDir\System32%) & also OLEServer DLL & ActiveX OCX lib types, marshalled/loaded by GUID, rather than just by name of file!

Since an app typically looks inside its OWN folder first for DLL's it loads (unless LoadLibrary API is called with a hardcoded pathway), first, prior to checking the system %PATH% & other areas in the registry? This aids in stability, & lets you keep diff. version builds of DLL's in the app's folder to load, instead of publicly viewable %PATH% ones.

(There is an ENTIRE logical "ruleset" (fairly long & complex but readable) for this DLL search & load ordering that I can supply, if you need it, with ALL locations that libs are loaded from & in what order).



* There ARE others too, like virus/malware/spyware!

(However, software tools like a DECENT AntiVirus (Norton/AntiVir/AVG are my top 3 picks personally) AND tools like AntiSpyware products (Spyware Blaster, SpyBot &/or AdAware are my top 3 picks here) are your pals, use them!))

However, I would point to those 3 first assuming no malware/spyware/virus infestation is present on your rig...

APK

 

[Alec§taar]

Supplement To My Last Post #3 Possible Regarding Dll Hell

HOPE THIS HELPS SOME (& that it is NOT the cause of your instability), & FOR YOUR REFERNCE(S):

=================================================================

HOW DYNAMIC LINK LIBRARIES ARE SEARCHED FOR & CALLED RULES:
------------------------------------------------------------------------------------

"DLL HELL" may occur on Win32 OS when 2 of SAME named "Dynamic Link Libraries" (.dll extension, executable with no loader header that cant self initialize) exist on a system and are accessible to a program. Since same name it can cause a program to "grab hold" of wrong version build to init for call functions it uses from it!

Can be problem that causes crash in programs because program expects function it calls to return integer return from a function but latest build of DLL of same name sends back pointer data instead!

Microsoft overcame a great deal of "DLL Hell" using ActiveX controls (OLE Servers, which have .DLL extensions also), that have .OCX extensions too. These are "marshalled" (loaded) not by name, as is done with older .DLL file types using the LoadLibrary call, but via a thing called a "GUID" (Globally Unique Identifier).

This is a 32-bit UNIQUE generated number in the registry that summons the CORRECT build the calling program requires by internally checking the .ocx or .dll file being called for its internal version information (using the functions this program uses on Version checking no doubt, std. Win32 API call method).

Microsoft has also put in "Side-by-Side" loading in their newer Operating Systems (2000/XP/2003) which can load the older type DLLs technically by name but into RAM separately, where they can be accessed separately by programs (the program that calls and finds the one it loads) so no "collisions" occur.

This is a GOOD move, but still can be problematic if the program finds the wrong version build of the .DLL it is calling, first

Order of seeks used by Win32 Portable .exe files for finding DLLs to load -

NT based Os by default, use different approaches for 32-bit vs. 16-bit apps:

1.) For 32-bit apps, NT/2000/XP/2003 search for implicitly loaded DLLs at:

a. .exe location folder
b. Current folder
c. %SystemRoot%\SYSTEM32 folder
d. %SystemRoot% folder
e. %Path% environment variable

* BUT if a DLL is listed as a KnownDLLs here in registry:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager

As REG_SZ entry type & Value of DLL name w/out the extension + data value of DLLname w/ .DLL extension, then search order becomes:

aa. %SystemRoot%\SYSTEM32.
bb. .exe file folder.
cc. Current folder.
dd. %SystemRoot% folder.
ee. %Path%.

KnownDLLs are mapped at boot time. Rernaming or moving during a session has no effect.

You can alter this behavior by including the 8.3 DLL name in the ExcludeFromKnownDlls entry, a REG_MULTI_SZ value, & one per line in that comma delimited listing.

(This makes NT believe that the DLL is not listed in KnownDLLs.)

2.) For 16-bit apps, Windows NT uses KnownDLLs for both implicitly and explicitly load DLLs. The value is at:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\WOW.

Here in that key, KnownDLLs is a REG_SZ value that lists 8.3 DOS formatted DLL names, & is separated by spaces. Without a KnownDLLs entry, WOW searches:

a. The current directory.
b. The %SystemRoot% directory.
c. The %SystemRoot%\SYSTEM directory.
d. The %SystemRoot%\SYSTEM32 directory.
e. The .exe file directory.
f. The directories in your Path.

With a KnownDLLs entry, WOW only searches for them in the %SystemRoot%\SYSTEM32 directory.

3.) Windows 2000 Service Pack #3 (at least, & thus probably XP/2003 also) has instituted the SafeDllSearchMode Value Name, a REG_DWORD data type, at this hive key folder:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager

A value of 0 keeps the current search order, & a value of 1 makes Win2k & programs search for DLLs & programs in this order:

a. Their own folder first
b. %SystemRoot%\System32
c. %SystemRoot%
e. The current directory
f. The folders in your %PATH% environment variable.

All that said: IF you follow those rules and realze that SOMETIMES, multiple .DLL versions are required on your system where they are located so programs can call the CORRECT VERSION of a .dll build, you will be ok!

Sometimes programmers DO stash a .DLL file inside the folder where their .exe program is located for GOOD REASON:

It takes up more diskspace, but assures the program will find the correct version build of the .dll called FIRST, since 2/3 times (w/out registry hacks shown previously (defaults only)) it's the first place a program looks for .dll it is instancing.

MAIN POINT:

BUT, inside the code itself, this can be made to happen thru hardcoded paths!

(Ordinarily this is frowned upon, but not in this case (to avoid .dll hell is why)).

The program can call the LoadLibrary API function to look for a file @ a certain location or can declare it @ program startup to look for the DLL to load in a certain location also!

* Application Hardcode of DLL Location Example

Examples in Delphi code (form creation instancing, not LoadLibrary call stated above):

Function CopyFileW(lpExistingFileNameointer;lpNewFileNameointer;bFailIfExists:Boolean):Boolean;stdcall; external "kernel32.dll"

* Note the end, "kernel32.dll" doesnt have path in front of it like "C:\Windows\system32\kernel32.dll

That is NOT hardcoded above is why and uses the rules we stated.

* Hardcoded example used to avoid DLL hell:

Function CopyFileW(lpExistingFileNameointer;lpNewFileNameointer;bFailIfExists:Boolean):Boolean;stdcall; external "c:\myprogram folder\kernel32.dll"

=================================================================



APK

 

[Eric3988]

I did'nt quite understand all of that stuff about DLL that you tried to explain, it was a little above my understanding of computers . Anyways, I don't think its either of the three you listed. I also ran Norton last night and came up with no viruses. I also browse using Firefox, combined with noscript and adblock. I think if heat was getting to my system I would of noticed it six months ago when I got the PC. I have not updated any of my drivers b/c I as of right now I have no graphics card so I felt no need. I can't comment about the dynamnic link libraries, but I will say that I haven't screwed around with any of my computers code or anything. Haven't even gone inside the windows folder in fact.

 

[Alec§taar]

I did'nt quite understand all of that stuff about DLL that you tried to explain, it was a little above my understanding of computers .

It is for many folks. I made it as simple as I can for "normal folks" to read above as I could...

Anyways, I don't think its either of the three you listed. I also ran Norton last night and came up with no viruses.

This is good, because collaring these or outright removing them CAN be a nightmare (Win32 Pinfi being the worst I ever saw)...

The "problem" with AntiVirus & AntiSpyware technology? It's REACTIVE... not really PROACTIVE!

And, it's only as good as its set of DB 'mugshots' of known offenders really... oh, heuristics help some, but not totally!

Anyhow - pulling viruses manually?

LOL, it is up there with understanding & managing DLL diff.'s!

I wrote a program that can check for duplicate files on your system, & in executables & help here!

I trimmed out many mb of space by pulling ABSOLUTELY duplicates - checked by CRC32, size, time/date stamp (not reliable enough imo because copying/moving files changes it sometimes), internal version build stamp detect via API calls (GetFileVersion iirc)...

(The program finds TRUE dups, of all kinds, including DLL's, but not .SYS drivers files, they don't keep ver info.)

I also browse using Firefox, combined with noscript and adblock.

Good, it's a start on that end too!

I think if heat was getting to my system I would of noticed it six months ago when I got the PC.

Right, I agree - if this was a heat issue it would have showed sooner (provided you did not buy the system in the winter & your home internal ambient is lower in the winter time & it is now SUMMER over there & warmer).

Could be that something JUST broke, but I would not go THAT far... not until you (for instance) try another HDD & FRESH OS INSTALL... & if that runs well?

I would lean to DLL mismatch mostly!

I have not updated any of my drivers b/c I as of right now I have no graphics card so I felt no need.

That cannot hurt to do, & I would myself to see if it "cures" it.

I can't comment about the dynamnic link libraries, but I will say that I haven't screwed around with any of my computers code or anything. Haven't even gone inside the windows folder in fact.

The problem is, OLDER INSTALLERS CAN & DO, from older softwares, causing or contributing to "DLL HELL"...

Even though the OS counters for it with its %WinDir%\Driver Cache (& Libraries cache iirc, under %WinDir%\System32\dllcache also) + Service Pack files subfolder as well?

It can't stop a "bum" older installer from overwriting some DLL's sometimes...

APK

P.S.=> I hope it's NOT your hassle, the DLL stuff, because it is time consuming HELL to overcome manually, let alone finding them (which is why I wrote a dup file finder that works on 5 diff. algorithms for detection of file diff.'s)... apk

 

[Eric3988]

Okay, what drivers would I need to update exactly? I'm not entirely sure what to update and where to get it from. I'd also being willing to try out that program to see if it works. But would you think that I should take back my computer to CompUSA and tell them that the motherboard is not working properly? The warrentee would cover repairs and the reason I think its the motherboard is b/c when my old graphics card was in the PCI-Ex slot, the machine would continually reboot and never go into windows. Only when the slot was empty would the machine boot normally. If all else fails I guess I'll wipe the hard drive and install a fresh copy of windows....

P.S.
I like your quote, I'm glad I'm not the only one here who watches that show!

 

[Alec§taar]

Okay, what drivers would I need to update exactly? I'm not entirely sure what to update and where to get it from. I'd also being willing to try out that program to see if it works.

See my last block quote below... prior to the P.S./P.S.S.! Thanks...

But would you think that I should take back my computer to CompUSA and tell them that the motherboard is not working properly? The warrentee would cover repairs

You can try that - you do have warranty. Thing is, you don't LEARN by having others do it for you (same reason many harley riders won't BUILD you your first bike, but WILL show you how to put one together, yourself... so you KNOW how it's done & how it ALL works!)

and the reason I think its the motherboard is b/c when my old graphics card was in the PCI-Ex slot, the machine would continually reboot and never go into windows. Only when the slot was empty would the machine boot normally.

This could be AGP vs. PCI-e init. order, & that is settable in MOST bios... & did you disable the onboard graphics in your BIOS, first, & THEN try your new PCI-e vidcard?

Afaik? THIS MATTERS!

If all else fails I guess I'll wipe the hard drive and install a fresh copy of windows....

What I would do, after I backed up ANY personally created data (documents like resumes, or other stuff you cannot just reinstall, sourcecode, etc.)?

Wipe your disk, reinstall the OS (plus, doing "Windows Update" to it), & then latest drivers for your equipment & wares for it too, + then??

See how she runs!



* That will eliminate any "virus" (hopefully none of your installers are infested) or malware possibles, as well as assuring you that you have an ABSOLUTELY fresh OS install + driverset for your equipment/peripherals!

APK

P.S.=> Now, IF it runs well after that? It was a DLL hell or other system file type mismatch, or bum drivers of somekind... rather than hardware failure!

This IS the way to eliminate it down to THAT set of possibles imo... apk

P.S.S.=>

P.S.
I like your quote, I'm glad I'm not the only one here who watches that show!

Good to see another "Trekkie" here as well (no, I am not the kind that goes to conventions or wears "spock ears" while watching the show lol, I just like Sci-Fi!)... apk

 

[Eric3988]

See my last block quote below... prior to the P.S./P.S.S.! Thanks...



You can try that - you do have warranty. Thing is, you don't LEARN by having others do it for you (same reason many harley riders won't BUILD you your first bike, but WILL show you how to put one together, yourself... so you KNOW how it's done & how it ALL works!)



This could be AGP vs. PCI-e init. order, & that is settable in MOST bios... & did you disable the onboard graphics in your BIOS, first, & THEN try your new PCI-e vidcard?

Afaik? THIS MATTERS!



What I would do, after I backed up ANY personally created data (documents like resumes, or other stuff you cannot just reinstall, sourcecode, etc.)?

Wipe your disk, reinstall the OS (plus, doing "Windows Update" to it), & then latest drivers for your equipment & wares for it too, + then??

See how she runs!



* That will eliminate any "virus" (hopefully none of your installers are infested) or malware possibles, as well as assuring you that you have an ABSOLUTELY fresh OS install + driverset for your equipment/peripherals!

APK

P.S.=> Now, IF it runs well after that? It was a DLL hell or other system file type mismatch, or bum drivers of somekind... rather than hardware failure!

This IS the way to eliminate it down to THAT set of possibles imo... apk

P.S.S.=>

Good to see another "Trekkie" here as well (no, I am not the kind that goes to conventions or wears "spock ears" while watching the show lol, I just like Sci-Fi!)... apk

Ok, I'll try a fresh copy of windows first, but a question if I may. I have a boot CD that came with my computer and it reinstalls windows and stuff and I believe it deletes everything on the hard drive. But do I need to use any other utilities to make sure my hard drive is clean?

Oh yeah, last time when I installed my X800GTO I didnt disable onboard graphics. All I did was uninstall all drivers like the directions said. Then I installed the card. Booted my system up and it worked like a charm until I took to CompUSA and they screwed everything up. Check out my earlier posts on that if you didnt already.

 

[Alec§taar]

Ok, I'll try a fresh copy of windows first

Be SURE you collect up any important PERSONALLY created data (you can never get it back again in the same shape if you format your system, or, not easily)... you can't just "install that" from Cd-DvD, you know?

but a question if I may. I have a boot CD that came with my computer and it reinstalls windows and stuff and I believe it deletes everything on the hard drive. But do I need to use any other utilities to make sure my hard drive is clean?

Good question - no, that ought to do it well enough.

Oh yeah, last time when I installed my X800GTO I didnt disable onboard graphics.

That might mess you up good... especially on entry to Windows.

(ALSO - Do CHECK your BIOS as to the ORDER of PCI vs. AGP initialization of display slots over one another, as well as disabling that onboard video BEFORE installing your new PCI-e vidcard!)

All I did was uninstall all drivers like the directions said. Then I installed the card. Booted my system up and it worked like a charm until I took to CompUSA and they screwed everything up. Check out my earlier posts on that if you didnt already.

Well, I must admit, I did not (fully, only skims) but did by talking with you directly...

I figure, you try this? This will cover you @ COMPUSA, because you'll have done ALL the things they pretty much will do!

APK

P.S.=> If ANYONE sees any "holes" in what I wrote? Please, DO correct me, but I don't think I "missed a trick" here, & Eric is on his way to doing his OWN pc-repair work too, bonus! apk

 

[Eric3988]

Be SURE you collect up any important PERSONALLY created data (you can never get it back again in the same shape if you format your system, or, not easily)... you can't just "install that" from Cd-DvD, you know?



Good question - no, that ought to do it well enough.



That might mess you up good... especially on entry to Windows.

(ALSO - Do CHECK your BIOS as to the ORDER of PCI vs. AGP initialization of display slots over one another, as well as disabling that onboard video BEFORE installing your new PCI-e vidcard!)



Well, I must admit, I did not (fully, only skims) but did by talking with you directly...

I figure, you try this? This will cover you @ COMPUSA, because you'll have done ALL the things they pretty much will do!

APK

P.S.=> If ANYONE sees any "holes" in what I wrote? Please, DO correct me, but I don't think I "missed a trick" here, & Eric is on his way to doing his OWN pc-repair work too, bonus! apk

Yeah, I won't forget to copy that stuff on to my flash drive. Ok, I'll remember to disable onboard graphics. Do I need to worry about the PCI-e and AGP initialization if my computer only has a PCI-e and PCI slots? But, thanks again for all of the advice and everything. I REALLY APPRECIATE IT!!

 

[Alec§taar]

Yeah, I won't forget to copy that stuff on to my flash drive.

GOOD, because backup's VERY important (unless you like doing your work AGAIN, & next time without even a roughdraft to begin with!)

Ok, I'll remember to disable onboard graphics.

This might be part of the problem you had, who knows, but should be done prior to installation of your new graphics card on PCI-e imo @ least!

Do I need to worry about the PCI-e and AGP initialization if my computer only has a PCI-e and PCI slots?

Nope! A "non-issue" for you in your case (no agp)...

But, thanks again for all of the advice and everything. I REALLY APPRECIATE IT!!

I just hope it works out & you don't have to go thru the HASSLE of proving whether COMPUsa techies may have messed up your rig, or that you somehow did (it happens, both cases!).

APK

 

[Eric3988]

Yes, thanks again for all of the help! Right now I'm backing up all of my necessary files onto my Sony MP3 player, which doubles as a flashdrive. It's pretty nice, except that you have to use their software to put music on it. But it does have a gig of memory and super long battery life.