| |
| |
| |
|
Page: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
Comments:
<0> then go to the initialization tab and see if there's anything fishy running at startup
<1> hi
<1> i just put some new ram in and it taks about 3times as long to start up
<2> could be a bunch of different reasons for that
<2> most likely you haven't updated your settings in bios, so it's continously reading it
<2> during post
<2> just run bios, it'll update automatically
<2> if it still happens, you might have a hardware type problem
<2> possibly wrong type of memory for your board, or you're not useing it in the right configuration
<1> when the coputer get in to windows it fast
<3> so guys..i'm looking to upgrade my system and am wondering..should I go for socket 939 or wait for socket 940?
<2> sounds like it's taking it's time to read up the memory
<2> load bios and save your settings
<2> you shouldn't have to do anything... other than load it, let it refresh the memory settings, and then save it
<2> salec: socket939 venice is very nice
<1> i just think i also put a cdrw at the same time think might be that ?
<2> i have a clawhammer, the core before the venice, and i love it
<2> need to get a venice tho
<2> clawhammer isn't as stable as i'd like
<2> wts: possibly, but that would also go back to what i told you originally
<2> you've changed settings but failed to load and save your bios
<2> it's rereading those setting each time you bootup
<2> which is why it's so slow
<2> :P
<2> load bios, save it once you load it, and reboot
<2> bet you it'll load faster
<2> heh
<3> well that's my problem right now
<2> ok.. maybe i'm confuseing questions
<2> heh
<3> i'm running an nforce 2 motherboard w/ an athlon-xp 2400+ ..i'm having stability problem after stability problem!!
<1> thank _mre|666
<3> first it was memory issues..nforce 2 doesn't support ddr 400 on certain motherboards..now it's usb issues..BSOD on any device that needs power
<2> salec: check the core of your 2400+ and make sure it's not chip
<2> also pull hardware and test it in other systems
<2> to isolate the problem
<3> i have
<3> it's the mobo
<3> but i've tried multiple mobos and they all run into the same issues
<2> rma it
<3> these are old architectures
<2> what is the common component?
<3> no nforce 2 mobos are still supported anymore..
<2> it can't be all the boards are bad
<2> for what?
<3> the chipsets in that generation ****ed
<2> yeah, cant' disagree with you there
<1> i try my old ram see if it is that
<3> the nforce 2 chipset had horrible memory handling and the only mobo I have that finally ended up being stable has horrible usb handling
<2> i got a few different boards... mostly asus tho
<2> board at home with the clawhammer is a a8n-sli deluxe
<2> i'm sure once i get a venice chip on there, it'll be stable like a rock
<3> what's unstable about it now?
<2> spontaneous reboots after a few days of staying up
<3> this generation really hurt my perspective on amd machines :(
<2> i think it's a cpu issue
<3> the nforce 2 generation
<2> it's either cpu or motherboard
<2> i've limited it down to that
<2> both should be warrantied
<2> i need a venice to test my theory, but i don't have one
<3> well you might run into my issue
<4> nforce 2 was incredible stable pretty much across the board
<3> where the board isn't buggy at all
<4> heh
<3> it just doesn't support the stuff
<3> CosmicCat: not in terms of memory
<2> salec: indeed, another chip would tell me
<2> everything
<4> Salec: in your experience, not in everyone elses, apparently
<2> i'll get one, once i get back from vacation
<2> nice Venice 3500
<2> only $200
<2> heh
<3> not just mine..it's been documented and even nvidia has admited that their nforce 2 chipset doesn't support most ddr400 brands
<3> even though the board claimed to support it at first
<2> nforce2 did ****
<2> i remember the board i had that had that
<2> it was a decent board, but the chipset was ***
<5> hah I'm using an nforce2 atm
<3> problem was that nforce2 was MUCH more stable than the via **** that was out
<2> ppl were still useing via back then tho
<2> yep
<4> there was a transition to ddr400 during the nforce 2 lifetime. you just had to get the right board
<2> so it was pimp for it's time
<4> like the asus a7n8x supported it on the 2.0 boards
<2> phire-: partying like it's 1999?
<2> hehe
<5> will smith - will2k
<3> CosmicCat: i've tried 4 nforce2 boards over different generations...a7n8x-e boards claimed to support it..BUT they only support very specific brands
<2> in 1 week, mother****ers, i'm on my way to Daytona
<2> w00
<2> **** this computer ****
<2> heh
<3> i've tried 3 different dual channel ddr400 sets ranging from generic brand, avg brand (crucial) to performance ocx
<5> i only use very specific brands and what i use works everywhere
<4> i never had problems with any of the brands I tried, sorry :D
<2> salec: you're beating your head against a dead mobo, obviously
<2> been there, done that, throw the board away before you go crazy
<2> or rma
<2> it
<2> heh
<3> _mre: if only..like I said i tried those 3 sets on 4 diff boards
<2> you're doing something wrong
<4> you are *also* having usb issues on the same board right?
<2> maybe ESD
<3> well this was a while back..i finally got the memory issues solved when I used the performance ocx on my ABIT AN7 board
<6> hi
<3> i ran memtest86 and windows memory diagnostics
<2> hey psyche
<3> both p***ed 100%
<2> i've seen ppl fry perfectly good hardware, just because they didn't follow proper ESD procedures
<3> my new issue however..is with external drives..whenever I plug in my ipod or printer (printer has an external drive for card reader)
<3> blamo BSOD
<3> nah i'm good with grounding myself
<2> well... that's driver related
<3> not necessarily
<3> i've reinstalled windows several times
<3> tried different drivers and versions
<2> anything USB, 90% of the time is driver related
<3> as well as each SP
<3> ANY usb flash drive
<3> causes BSOD on occasion
<2> anything usb
<3> my ipod however
<3> is firewire
<2> other 9% of the time it's hardware related
<2> incompatibilities for one reason or another
<2> or just ****ty hardware
<2> like the early ipods
<3> i was reading that it's an issue with the amount of power supplied
<2> that would fry your computer
<3> mine's new
<2> from grounding issues
<7> thats the most retarded thing ive heard
<2> you're fortunate tho
<2> i've seen computers fried from older ipods
<2> Number17: believe it or not... i didn't until i saw it myself
<2> early ipods had alot of issues
<7> lies
<2> Number17: i own a computer repair/service business, what do you do for a living?
<8> http://www.hkepc.com/bbs/viewthread.php?tid=550178
<9> ipods have always had issues
<2> i had a client that fried his dell with an ipod through a firewire port. it was crazy... we traced the damage on the board right to his pci bus
<4> i spy for the goverment, driving fast cars, ****ing beautiful women, and shooting people.
<3> man i frickin love window's BSOD error reporting
<3> "System Error"
<3> that's all i got
<2> with a multimeter
<3> :(
<2> right to the firewire card installed
Return to
#computers
or
Go to some related
logs:
VBA listbox no itemdata
#politics
#nhl
#linuxhelp
she make my pee pee go boing...
#linuxhelp
#sex
#computers
#visualbasic
#redhat
|
|