•
•
•
•
What is DaniWeb IT Discussion Community?
You're currently browsing the Troubleshooting Dead Machines section within the Tech Talk category of DaniWeb, a massive community of 427,684 software developers, web developers, Internet marketers, and tech gurus who are all enthusiastic about making contacts, networking, and learning from each other. In fact, there are 4,287 IT professionals currently interacting right now! Registration is free, only takes a minute and lets you enjoy all of the interactive features of the site.
Please support our Troubleshooting Dead Machines advertiser: Programming Forums
Views: 4595 | Replies: 51
![]() |
•
•
Join Date: Jul 2006
Location: a few 1000 miles east of the east coast
Posts: 277
Reputation:
Rep Power: 3
Solved Threads: 10
Yes download that. Do you know somebody who has already flashed a BIOS and knows what to do if something goes wrong? Would be a good help, since otherwise you'll have to read a bunch about that first. Basically, you download a self-extracting *.exe file and put its contents on a bootable floppy or CD in order to run the flash program from a clean DOS. The Gigabyte file contains an Autoexec.bat that starts the flash program automatically with the BIOS image after booting from the floppy or CD.
In the manual for the GA-8I848P/775 I found this interesting passage: "Some advanced options are hidden in the new BIOS version. Press Ctrl and F1 together after entering the BIOS menu and you will able to see these options". Maybe your BIOS has a similar feature?
In the manual for the GA-8I848P/775 I found this interesting passage: "Some advanced options are hidden in the new BIOS version. Press Ctrl and F1 together after entering the BIOS menu and you will able to see these options". Maybe your BIOS has a similar feature?
Last edited by Xpenetrator : Nov 7th, 2006 at 1:36 am.
•
•
Join Date: Jul 2006
Location: a few 1000 miles east of the east coast
Posts: 277
Reputation:
Rep Power: 3
Solved Threads: 10
•
•
Join Date: Jul 2006
Location: a few 1000 miles east of the east coast
Posts: 277
Reputation:
Rep Power: 3
Solved Threads: 10
•
•
Join Date: Jul 2006
Location: a few 1000 miles east of the east coast
Posts: 277
Reputation:
Rep Power: 3
Solved Threads: 10
50/50... since there is a big gap between the current and the latest BIOS, this should be done anyway and if it harms, you can revert it. If your board has the dual BIOS feature, it is even harmless if something goes bad. Solving issues with certain new hardware is what BIOS updates do, so it will be a good thing to try.
•
•
Join Date: Jul 2006
Location: a few 1000 miles east of the east coast
Posts: 277
Reputation:
Rep Power: 3
Solved Threads: 10
•
•
Join Date: Nov 2006
Posts: 26
Reputation:
Rep Power: 2
Solved Threads: 0
hey, Ive been thinking about the MB/GC compatibility problem. To me it just doesn't add up. (although you know way more htan me, and i'm probably wrong). If it was caused by not being compatible or whatever wouldn't it do it in all games? ok, it only freezes in these games, COD2, BF2 , FSX. FS9 and oblivion. From my observations I have seen that in oblivion it only happens when I use magic, and in FSX it normally only happens when closer to the ground.
It doesn't freeze in all games, such as AO3, AO2, IL2 and heaps of others. The times when it does crash, for instance when using magic in Oblivion it is normally during graphically intyense periods. Tjis makes me wonder if it may be the graphics card itself or some other hadware or even dust related issue. Anyway, sorry for the long post and your probably correct, but I just want to make sure..it just seems weird! Oh, I also forgot to say earlier that when I first got my computer it WAS NOT having this problem, it has recently been appearing and is now at its worst with freeze appearing every 15-30 mins or so.
It doesn't freeze in all games, such as AO3, AO2, IL2 and heaps of others. The times when it does crash, for instance when using magic in Oblivion it is normally during graphically intyense periods. Tjis makes me wonder if it may be the graphics card itself or some other hadware or even dust related issue. Anyway, sorry for the long post and your probably correct, but I just want to make sure..it just seems weird! Oh, I also forgot to say earlier that when I first got my computer it WAS NOT having this problem, it has recently been appearing and is now at its worst with freeze appearing every 15-30 mins or so.
Last edited by flyboysu27 : Nov 8th, 2006 at 12:47 am. Reason: forgot some data
•
•
Join Date: Jul 2006
Location: a few 1000 miles east of the east coast
Posts: 277
Reputation:
Rep Power: 3
Solved Threads: 10
Ok if these freezes occur (and can be reproduced) at certain situations, I think "Fastwrites" is somewhat less suspect. It was "freeze - Geforce6 - AGP" that made me think about the Fastwrite issue and try that shot into the blue. There are so many reasons for freezes. But I still suspect the AGP/chipset to be the cause of the problem. Since the BIOS appears to be so simple, the only way to influence this is still via a new BIOS file. The developers may or may not have improved the AGP implementation to support new graphics cards or improve stability. Issues with GF6 on AGP with older boards are pretty common and I had stable running games (i.e. IL-2 PF!) on my personal fastwrites issue, too. (I guess you run IL-2 in OpenGL, too - this maybe explains the difference...)
But you're plain right, it can also be a faulty graphics card. You should test it in another machine. If the other machine is already nVidia equipped, this should be no big deal. Maybe you can test it at the store where you got it from.
Answering another unanswered question, while sitting on the desktop or drawing boring windows your card is running close to idle power in almost all parts. Only when a game requires complex rendering operations and huge memory transfers, all the juice is drawn and things run close to their limits and get hot.
BTW: Your PSU should deliver at least 20A on the +12V rail (you find a sticker at the side of your PSU) for your 6600GT and your Pentium. But if it's too weak this would be more likely restarting your computer.
The next thing you can check is to provoke a freeze and to look into the Event Viewer of XP, if something useful has been recorded about the error. Note the system time at which the lockup occurs. After reboot, go Start-->Run, type eventvwr.msc and hit Enter. A window pops up and on the left tree view, select "System". In the main window you see the logged events - search for red X errors that match with the time of the freeze. If any, doubleclick them and click on the button with the two tiny sheets of paper - this will copy the message into the clipboard and you can paste it into your next post. Unfortunately, freezes occur mostly before the system can log something...
But if your 6600 overheats sometimes, this would be logged there, too and this would be one more possible cause for your problem to check.
Reproducible freeze means to me "memory could be involved, too" and should be checked if all other measures and tests fail. Also, if this problem gets worse as you described, this could point to a memory (or other chip) going bad. Troubleshooting this kind of woes isn't easy, but there is much to try before giving up. A different kind of computergame. :mrgreen:
But you're plain right, it can also be a faulty graphics card. You should test it in another machine. If the other machine is already nVidia equipped, this should be no big deal. Maybe you can test it at the store where you got it from.
Answering another unanswered question, while sitting on the desktop or drawing boring windows your card is running close to idle power in almost all parts. Only when a game requires complex rendering operations and huge memory transfers, all the juice is drawn and things run close to their limits and get hot.
BTW: Your PSU should deliver at least 20A on the +12V rail (you find a sticker at the side of your PSU) for your 6600GT and your Pentium. But if it's too weak this would be more likely restarting your computer.
The next thing you can check is to provoke a freeze and to look into the Event Viewer of XP, if something useful has been recorded about the error. Note the system time at which the lockup occurs. After reboot, go Start-->Run, type eventvwr.msc and hit Enter. A window pops up and on the left tree view, select "System". In the main window you see the logged events - search for red X errors that match with the time of the freeze. If any, doubleclick them and click on the button with the two tiny sheets of paper - this will copy the message into the clipboard and you can paste it into your next post. Unfortunately, freezes occur mostly before the system can log something...
But if your 6600 overheats sometimes, this would be logged there, too and this would be one more possible cause for your problem to check. Reproducible freeze means to me "memory could be involved, too" and should be checked if all other measures and tests fail. Also, if this problem gets worse as you described, this could point to a memory (or other chip) going bad. Troubleshooting this kind of woes isn't easy, but there is much to try before giving up. A different kind of computergame. :mrgreen:
Last edited by Xpenetrator : Nov 8th, 2006 at 2:31 am. Reason: Forgot some things, too
![]() |
•
•
•
•
•
•
•
•
DaniWeb Troubleshooting Dead Machines Marketplace
•
•
•
•
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
- C++ is dying a slow death (C++)
- 100% CPU Usage - No Virus, No gaming (Windows NT / 2000 / XP / 2003)
- Links and Banner advertisement available on Gaming site (Ad Space for Sale)
- will this come be 1337 for gaming (Windows NT / 2000 / XP / 2003)
Other Threads in the Troubleshooting Dead Machines Forum
- Previous Thread: HP Pavilion Boot Problem
- Next Thread: Computer wont boot.. sometimes


Linear Mode