• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About mongo66

  1. It seems I've come across a stumbling block, something I had carelessly overlooked earlier on. Both LEGACY and drivers share one common denominator: RAID Controller. As I mentioned in an earlier post, two driver integration is made possible by editing the relevant INF/OEM files. This is all fine and dandy, but when it comes to RAID Controller id's, *_NVRAIDBUS and *NVRAIDBUS, omitting them from either package will result in mismatched drivers being installed: nvgts.sys + nvraid.sys, or nvatabus.sys + nvrd32.sys Whereas keeping them won't eliminate the mismatched driver issue (on the LEGACY side of things) and may cause conflicts during Windows Setup due to the duplicate entries in TXTSETUP.SIF. Whatever the case, it doesn't look too promising for SATA RAID systems. Not exactly what I was hoping for, so it's a no go P.S. - What is it with NVIDIA and their drivers? Intel is so much easier to work with.
  2. Thanks for your input! Quite some time ago, I created a BartPE live CD which included both your LEGACY and 9.99.09 driver sets: Intel_textmode_drivers_v8.7.0.1007_mod_by_Fernando nForce IDE 99909 for XP 32bit mod by Fernando nForce LEGACY 699 for XP 32bit built by Fernando Although it was a half-baked effort and purely experimental, I've had no problems using this CD on legacy or newer systems (so far). Unfortunately, I didn't go on to create a similar XP installation disc at the time. Over the past 2-3 years, I have created several XP discs with integrated drivers, none of which was an All-In-One solution. TBH, I'm fed up with having to sift through all these discs whenever I needed to use one. Therefore, I'm hoping to create a new disc based on what I had achieved with BartPE. textmode: - Intel WHQL (or should I use your modded package? please advise) - nForce LEGACY - nForce (sataraid) pnp drivers: - nForce (sata_ide) About the hardware IDs -- it only makes sense to remove duplicate entries; if only for the reasons you've mentioned. In creating the BartPE CD, the LEGACY inf/oem files were edited to "exclude" HWID's already present in the package. While the only change made to the configuration files was the removal of *_NVRAIDBUS and *NVRAIDBUS hardware ID's. Everything else was left intact. BTW, I messed around with the DriverPacks Method before, but never got it to work properly.
  3. Hi Fernando, I want to build an XPSP3 installation disc which can support a wide variety of nForce-based systems. Ideally, I would like to integrate both LEGACY and the drivers onto a single disc. Apart from me having to edit the INF/OEM files accordingly (to eliminate dupe entries), are there any drawbacks? I would like your thoughts/opinion on this. Thanks.
  4. Adblock Plus Firefox Showcase Fission Hide Menubar Stylish
  5. I wasn't running CHKDSK on the system partition; it would require a reboot (like you mentioned). I was doing a routine disk check on my data partitions. I have three hard drives; one used for OSes, the other two for storage. Maybe there's something wrong with my Vista configuration, perhaps a conflict somewhere. I've been using Vista on this machine for a year, never had any issues until yesterday. Everything else is working normally. No luck so far in isolating the problem though...
  6. Windows Explorer hangs after running CHKDSK with the "Automatically fix file system errors" option in Vista SP1. This occurs only on NTFS volumes. The disk check completes normally (without errors), but after I close the message box, Explorer stops responding for 15-20 seconds and then resumes. I don't experience this with FAT32 partitions. I ran into this problem while doing a routine disk check. As far as I can remember, this has never occurred before. I've checked the event viewer logs, but have come up empty handed. I'm hoping someone can shed some light on this. Any ideas?
  7. I don't see how overclocking RAM is going to do you any good. If your goal is to improve performance, won't you be better off leaving the RAM as it is and overclock the CPU instead? Just a thought... The limitation you're seeing can be caused by a number of things - type of RAM, CPU, motherboard, FSB, etc. Limitations in overclocking varies from system to system. Just because you can achieve a certain speed, doesn't necessarily mean someone else can (with the same motherboard). Another thing, run Prime95 and/or Memtest for at least 8 hours to ensure (overclock) stability.
  8. Thanks for the links! I found the "TabshutdownDelay" to be very useful. Yet another tweak to add to my long list of tweaks...
  9. Here are two potential solutions to the slow file copy problem... 1. Disable Receive Window Auto Tuning in Vista; 2. Uninstall the "Remote Differential Compression" feature in Vista (Control Panel > Programs and Features) This worked for me, so it might do the same for you as well.
  10. Hi folks, It all began one evening... While viewing videos on YouTube, I experienced a loss of ADSL sync. After a several subsequent connection dropouts, sync-up could not be established. So I switched off the ADSL modem and unplugged the power adapter. After letting the device 'rest' for half an hour, I was back in business. However, connectivity issues persisted and got worse as time went by. I also tried plugging the modem directly into the wall socket, but to no avail. This 2-Mbit ADSL connection has served me well since day one. Good ADSL service is hard to come by in South East Asia. I've been using it for over a year without any problems. I contacted my ISP, they told me everything on their end was "fine" and suggest I do a hard reset on the ADSL modem. I told them it didn't work as I had already reset the device beforehand... The technician then changed my connection profile to 1024/512. When I informed him there still was no sync, he asked me to leave the phone "off-hook" and try again. To my surprise, the phone off-hook trick worked on both connection profiles... The technician explained I might be experiencing a "high open" issue and suggested I contact my telephone company. Now I'm thinking, what the hell is a "high open" ? After Googling, I came across this article. So without further delay, I proceeded to test NID the modem. With ADSL modem connected directly to the NID, 2048/512 sync was achieved in less than a minute. Next, I connected the splitter (modem > splitter > NID) also with positive results. But upon reconnecting the phone (to wall socket), I could hear "static" through the handset. I quickly came to the conclusion - faulty internal wiring. So I rewired my home over the weekend. It was long overdue, the old phone wiring in this house has been around since the mid-1990's. Rewiring got rid of the static. Connecting the modem to the new wiring I was able to achieve and maintain full ADSL connection with the phone on-hook. But after a while, dropouts started to occur and (re)sync took longer and longer. Reluctantly, I took the phone "off-hook", now the connection seems to be stable once again. Some observations... With phone "on-hook", I lose sync within a half hour. After connection dropout, ADSL (re)sync is VERY slow... sometimes it won't sync at all (ADSL light flashes continuously). When sync is achieved, the data rate varies from full speed (2048/512) to xxx/512. Downstream SNR margin is also very low -- anywhere from 5.0 to 8.0 db. However, if I powered off the ADSL modem and turn it back on, 2048/512 sync is achieved with downstream SNR margin of 13.0-13.5. *** Typical line stats with phone "on-hook" *** Mode: G.DMT / ANNEX A SNR Margin (Down/Up): 13.0 / 18.0 db Line Attentuation (Down/Up): 58.0-60.0 / 31.5 db With phone "off-hook", it takes about 20 sec to 1 minute to achieve sync. Dropouts are at a minimum; connection is very stable (or so it seems). Downstream SNR is slightly better, ranging 14.5 to 16.5 db. *** Typical line stats with phone "off-hook" *** Mode: G.DMT / ANNEX A SNR Margin (Down/Up): 15.0 / 20.0 db Line Attentuation (Down/Up): 58.0-60.0 / 31.5 db With my old ADSL modem, line attenuation (downstream) was in the 48-50 db range. Ever since I had the Billion 5210s router-modem, line attenuation reads 58-60 db... Yes, I do live pretty far from the exchange (4-5 km). Just wonder why there's a large discrepancy in attenuation readings between the two modems... I also notice a sharp increase in CRC and HEC errors while using the Billion 5210s as well. As of this posting, Billion 5210s performance stats are as follows: near-end FEC error interleaved: 7941 near-end CRC error interleaved: 456 near-end HEC error interleaved: 2900 far-end FEC error interleaved: 49 far-end CRC error interleaved: 44 far-end HEC error interleaved: 61 Error second in 15min: 5 Error second in 24hr: 107 Error second after power-up: 107 ADSL uptime: 2:18:44 --------------- Data Rate: 2048/512 Mode: G.DMT / ANNEX A SNR Margin (Down/Up): 15.0 / 20.0 db Line Attentuation (Down/Up): 59.0 / 31.5 db Phone is off-hook, btw. What really concerns me are the CRC and HEC errors. These numbers are extremely high. I've contacted the phone company and requested a line check... What are your thoughts? Suggestions welcome.
  11. I've completed another round of memory tests over the weekend. Memtest86 had been running for almost 16 hours without a single error. Therefore, it's safe to assume the RAM modules aren't faulty. These tests were carried out using the default Front Side Bus (FSB) of 166Mhz (no overclocking). Note: I did not run any tests with dual channel enabled, as I felt it was unnecessary. DRAM Frequency : By SPD << Bios default setting Memory timings : RAM 200Mhz (DDR400) / CAS : 2.5-3-3-8 / Single Channel (64-bits) With all the problems I've encountered with this machine including the minidump analysis, I'm forced to conclude either the processor, motherboard or a combination thereof, has gone "bad". Now I have to figure out how to explain this to the owner of the computer when I return it to him tomorrow. Case closed.
  12. I've been wondering about this too... Anybody?
  13. @cluberti, Thanks for your analysis, I really appreciate it The analysis seems to have confirmed my initial suspicions... I did test the memory, albeit for a couple of hours. Due to recurring system crashes, I figured if the memory was at fault, memtest86 would have detected errors in a short amount of time... I'll test the RAM again later today -- just to be sure. Only this time, I'll let it run for 12 hours. Other interesting developments... As I was using the machine today, it froze up again (no surprise there). After a forced shutdown and restart, I was greeted with: NTLDR is missing ... Press Ctrl-Alt-Del to restart WTF? So I fired up BartPE just to see what was going on... I couldn't access drive C: but was able to access the logical drive (D:). Ran chkdsk on drive C: with the following results: CHKDSK.CMD: Starting... Please enter the drive, mount point or volume name to check (for example "c:").. . Enter drive:c: Do you want to fix errors on the disk *and* locate bad sectors and recover readable information (Yes/No)... Enter "y" or "n":n Do you want to fix errors on the disk (Yes/No)... Enter "y" or "n":y ---------------------------------------------------------------- You have specified to check drive/volume c: With the following options: - Fix errors on the disk ---------------------------------------------------------------- Start check disk? (Yes/No)... Enter "y" or "n":y Running: chkdsk.exe c: /f The type of the file system is NTFS. CHKDSK is verifying files (stage 1 of 3)... File verification completed. CHKDSK is verifying indexes (stage 2 of 3)... Correcting error in index $I30 for file 5. Correcting error in index $I30 for file 5. Sorting index $I30 in file 5. Index verification completed. CHKDSK is recovering lost files. Recovering orphaned file $MFT (0) into directory file 5. Recovering orphaned file $MFTMirr (1) into directory file 5. Recovering orphaned file $LogFile (2) into directory file 5. Recovering orphaned file $Volume (3) into directory file 5. Recovering orphaned file $AttrDef (4) into directory file 5. Recovering orphaned file . (5) into directory file 5. Recovering orphaned file $Bitmap (6) into directory file 5. Recovering orphaned file $Boot (7) into directory file 5. Recovering orphaned file $BadClus (8) into directory file 5. Recovering orphaned file $Secure (9) into directory file 5. Recovering orphaned file $UpCase (10) into directory file 5. Recovering orphaned file $Extend (11) into directory file 5. Recovering orphaned file SYSTEM~1 (27) into directory file 5. Recovering orphaned file System Volume Information (27) into directory file 5. Recovering orphaned file WINDOWS (30) into directory file 5. Recovering orphaned file ntldr (3376) into directory file 5. Recovering orphaned file NTDETECT.COM (3380) into directory file 5. Recovering orphaned file boot.ini (3413) into directory file 5. Recovering orphaned file PROFILES (3419) into directory file 5. Recovering orphaned file VOLUMEID.EXE (3722) into directory file 5. Recovering orphaned file PROGRA~1 (3732) into directory file 5. Recovering orphaned file Program Files (3732) into directory file 5. Recovering orphaned file RECYCLER (9223) into directory file 5. Recovering orphaned file pagefile.sys (9245) into directory file 5. Recovering orphaned file symstore (9318) into directory file 5. CHKDSK is verifying security descriptors (stage 3 of 3)... Security descriptor verification completed. CHKDSK is verifying Usn Journal... Usn Journal verification completed. Correcting errors in the Master File Table (MFT) mirror. Correcting errors in the Volume Bitmap. Windows has made corrections to the file system. 15631213 KB total disk space. 2820732 KB in 11067 files. 3200 KB in 1470 indexes. 0 KB in bad sectors. 92901 KB in use by the system. 65536 KB occupied by the log file. 12714380 KB available on disk. 4096 bytes in each allocation unit. 3907803 total allocation units on disk. 3178595 allocation units available on disk. Unable to obtain a handle to the event log. CHKDSK.CMD: Check disk done... Press any key to continue . . . What else could go wrong?! lol. Luckily enough, chkdsk fixed the errors and I was able to get into windows...
  14. After my initial post, the computer seems to have behaved somewhat... I actually managed to shutdown the computer through the Start menu for a change. I've worked with the GA-7N400 series boards before -- both PRO and entry level boards like this one. Never ran into any problems, up until now. With this particular machine, it certainly doesn't take a lot of effort to initiate a system crash... Playing a game of spider solitaire (with no other programs running) causes a hard freeze. Something I forgot to mention earlier... While checking system temps, I noticed the CPU was running rather cool, around 42-46c. This is quite unusual for an Athlon XP 2600+ with "stock cooling". Idle temps should be in the 50-55c range. Perhaps the temp sensors have gone mad as well... Anyways, here are the dump files as requested (16 in total). Minidump.7z
  15. I've been given the wonderful task of troubleshooting an older machine. Without further ado, here goes... System Specs: Athlon XP 2600+ (Barton) Gigabyte GA-7N400S 2x256mb DDR PC3200 RAM ATI Radeon 9550 (RV360) AGP C-Media CMI8738 6CH-PCI 80GB Seagate ATA-100 400W PSU Windows XP Service Pack 3 Initial observations: Upon turning on the computer, during bios POST, I noticed the following: TRAP 00000006 ================== EXCEPTION ================================= tr=0028 cr0=00000011 cr2=00F0836B cr3=00000000 gdt limit=03FF base=00017000 idt limit=07FF cs:eip=0008:00060EC4 ss:eip=0010:00060E6C errcode=0000 flags=00010002 NoCy NoZr IntDis Down TrapDis eax=00000026 ebx=00000FFF ecx=00000413 edx=0000046B ds=0010 es=0010 edi=0046A165 esi=00000000 ebp=00060E62 cr0=00000011 fs=0030 gs=0000 This has appeared 3-4 times since I got the computer a week ago. I don't know exactly what it means, but it seems to only appear after changing the memory frequency setting in the bios with dual channel enabled. On the software side of things, I cannot install Windows if RAM is operating in dual channel mode; the system hangs during text-mode setup (specifically while copying The only solution is to disable it. I've also swapped the memory modules around, as well as use a single stick of 256mb DDR. The computer doesn't experience any startup issues in single channel mode, whether I use one or both sticks of RAM. On the other hand, Windows will not boot if dual channel is enabled AND memory frequency is configured by SPD (400mhz): Windows could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM If I change the memory frequency to 100% or Auto (333mhz) in the bios, Windows starts up just fine with dual channel enabled. Crash n' burn !! The crash scenarios mentioned below occur regardless of memory configuration and without any overclocking. (1) Music playback (soundcard; onboard AC97 disabled) Occasionally, the mouse, keyboard and screen freezes after a while. Playback however, remains uninterrupted. Computer can still be shutdown (normally) by pressing the power button. Inserting the soundcard into a different pci slot produced the same results. The soundcard isn't faulty, btw. (2) Music playback (integrated 6-channel AC97 audio) The system comes to a halt with a loud, constant screeching noise. Computer cannot be shutdown normally; must hold down the power button to power off... (3) Video playback (WMP, MPC, etc) results in a BSOD after a few minutes. STOP 0x0000007F (UNEXPECTED_KERNEL_MODE_TRAP) or, TRAP_CAUSE_UNKNOWN STOP 0x00000012 (0x00000001,0x00000000,0x00000000,0x00000000) *** Note: Using Windows default display drivers, I can *almost* watch an entire movie before any BSOD or system freeze. I also tested the Radeon card in another machine with Catalyst / Omega drivers installed. No video playback issues to speak of... Definitely nothing wrong with the graphics card. (4) Web browsing -- If I have multiple tabs open, or visit flash intensive web pages, the system either freezes or internet connectivity is lost. The system bogs down and eventually crashes... Only after "forced" shutdown or reset, do things return to normal and I'm able to browse again. Steps taken (so far): - Reset bios to default settings - Ran Memtest86... RESULT: no errors. - Checked PSU voltages... RESULT: nominal readings. - Checked harddisk for bad sectors... RESULT: none found. - Reinstalled Windows XP and updated device drivers with no positive effects... Also, there are no heat issues as far as I can tell, nor are there any leaks or bulging capacitors on the motherboard itself. The system is already running the latest bios version. After nearly a week of troubleshooting, I suspect the CPU and/or motherboard is "dying"... What are your thoughts?