BSOD on nforce 6080i bo
It doesn't even let me install drivers just bsod... until I physically remove the card.. onboard sound works just fine...how pathetic huh!
I assume you mean nForce 680i. What sound card are you talking about, though? Is it an X-Fi or an Audigy? Or is it a Li've!? And which model?
What kind of a BSOD is it's Did you get to catch the error message or any of the codes? MACHINE_CHECK_EXCEPTION, PAGE_FAULT_IN_NONPAGED_AREA, etc.
And just for others' info, what exact motherboard manufacturer/model is it's
I haven't experienced your problem myself, but I don't think it's too uncommon around here. Have you tried the card in another slot, maybe?Message Edited by sireebob on 03-9-2007:30 PM
Similar Messages
-
New Drivers ,When ???
[ALIGN=center][size=15]
New Drivers ,When ??? [/SIZE] [/ALIGN]From the Audio Driver Problem thread:
Quote
Posted: Sat Oct 19, 2002 3:13 pm Post subject:
I talked to NVIDIA about the BSOD on nForce 1 and they have a driver that fixes that. We should be seeing that driver soon.
by guy at http://www.bjorn3d.com/ -
Noticed problem accessing E drive = error message
tried defrag, chkdsk /f and couldn't complete
nothing before today stored in system restore
started getting BSOD IRQ_EQUAL_TO_NOT_LESS_THAN Stop 0x000000000xA
tried to start copying files from E with bsod after a 1-2 min of copy process
ran Hitachi drive diag and drive failed in basic and advanced mode
ran ontrack drive diag and drive would stop after a few min on the read test
so...thought drive was bad...copied what I could from drive and returned for warranty replacement
installed and formatted new SATA drive...copied files to E
now getting BSOD on copying all files
cannot complete virus check on any drive... bsod on all drive access after a few minutes
updated BIOS and mobo drivers
no change... did Win Repair
now computer really runs like crap...getting fail on spoolsv.exe
booted into safe mode and did virus check ccleaner and spybot check
??? should I fix ccleaner registry problems?
didn't BSOD during safe mode
went back to normal mode, same spoolsv.exe error
kept saying I need to update to sp2, but hangs during 'finishing install'
tried running sp3 candidate...hangs
what would you do?
should I give up and try to upgrade to Vista and hope it fixes everything?Seems like your OS files have gotten corrupted - from Command Prompt try SFC /SCANNOW with the OS CD-ROM in a drive. You also need to calm down and run some basic diagnostics, e.g. memtest86+ like someone else said and then run WDC diags on your remaining drives and a full Windows scan of at least the boot drive with CHKDSK /R or "Scan for and attempt recovery of bad sectors" with the Windows scanner.
Which nForce3 driver pack are you using - the last from nVidia was 5.10 (5.11 is bad so do not use). Where did you DL the SATA/RAID drivers? If from MSI and it's the version with V5.34 NVATABUS.SYS I wouldn't use that - the 5.10 pack SATA is OK but the best SATA/IDE driver, if you must, is the V4.79 SATA-IDE which is only available as part of an aborted attempt at a unified driver pack, 6.37Beta, by nVidia... available here http://downloads.guru3d.com/nForce-6.37-Beta-Drivers-download-971.html BUT use only the drivers in the IDE folder, which you'd have to install manually. You could also do a custom remix, like I have, by replacing the IDE folders in the 5.10 pack with the ones from the 6.37Beta pack.
BTW forget about Vista with a nForce3 mbrd - nVidia has removed all "compatibility" notices and their official stance is that it(Vista+nForce3) does not work with a dual-core CPU and they will not be doing drivers. -
Win XP BSOD while capture video on MSI GF FX 5900XT-VTD128
Hello.
I have such a problem. While capture video (overlay mode, 720x576) very
often (but not always) Windows XP crashes on BSOD with the following error:
DRIVER_IRQL_NOT_LESS_OR_EQUAL
STOP: 0x000000d1 (0xF0504000, 0x00000002, 0x00000001, 0xF7A2CE57)
nv4_mini.sys - address F7A2CE57 base at F7A1A000, datestamp 4061d74b.
My system configuration is:
Hardware: MB Epox EP-8RDA3I (latest BIOS version), CPU AMD Athlon XP 2400+,
RAM DDR PC3200 512 MB dual channel (Kingston), Video MSI GeForce FX 5900
XT-VTD 128 (VIVO, Philips SAA 7114). NO overclocking!
Software: Windows XP Prof SP1, DirectX v.9.0.b, Nvidia Nforce driver v.4.24
WHQL, Nvidia ForceWare driver v.56.72 WHQL (default settings), MSI WDM capture driver v.3.08 (late). Capture software: VirtualDUB, iuVCR and any other.
What anyone will advise me?
Thank You.
Best regards, Dmitry.61.21 driver is a beta driver. its not 100%. wait until they release a full working driver. it will be released on http://www.nvidia.com.
-
MSI K7N2 Delta-ILSR (MS-6570) BSOD problems grrr
I recently purchased this board and although it is an awesome product, I'm having a problem with BSOD's when I play a game for a certain period of time
Specs:
MSI K7N2 Delta-ILSR (7.6 BIOS)
AMD Athlon XP 2800+ Barton
512MB (2x256MB) Samsung PC-2700 DDR memory (2.5-3-3-6 1T)
MSI 128MB GeForce4 Ti 4200 (4X AGP)
NVIDIA nForce on-board sound
Western Digital 80GB drive w/ 8MB cache
MSI X48 CD/CD-RW/DVD combo drive
Windows XP Professional SP1
PSU:
Turbolink 420watt (came with case)
+3.3V is 28A
+5V is 40A
+12V is 18A
So what happens is I get a STOP error during the game that shows the kmixer.sys driver as the culprit. Sometimes it's accompanied by PAGE_FAULT_IN_NON_PAGED_AREA too. I read somewhere that kmixer.sys has to do with windows audio and that it's a 3rd party driver issue or a memory issue. I'm using the latest NVIDIA 3.13 nForce platform drivers. I ran Memtest lastnight for 12 hours straight and 0 errors. I'm thinking the memory may not be compatible with the board nor dual channel, is this possible? I have also tried several different drivers for both video and chipset including MSI's own and I still get the kmixer.sys BSOD when playing games. My previous motherboard was an MSI KT3 Ultra2-R (MS-6380E) which I had no issues with. Any help would be greatly appreciated. Thank you in advance.
--Update--
I just tried to play a game with audio disabled and it crashed this time with DRIVER_IRQL_NOT_LESS_OR_EQUAL with nv4_mini.sys as the problem. My IRQ table shows some sharing, but device manager shows no conflicts.Ok I tried running the DTM-CB3 module which is nForce2 approved at 3-4-4-11 2T timings and experienced the same result even at 2.6 and 2.7v. I tried both in dual-channel and same thing happened. However, I downloaded a program called Prime95 and ran the CPU torture test and the system returned a fatal error within the first few minutes. CPU Temp was at 57 C and the warning beep (set to 60C though) sounded intermittentley which is strange. I let it cool down then ran the torture test again and about 5min. later the system either seized completely or the program crashed. IE has also crashed randomly on me. I did this several times, before trying a different FSB/DRAM ratio. So I left the system at 200 FSB and used a 6:5 ratio so my memory was running at DDR333 and processor was a 3200+. I ran Prime95 again and the system locked up just as it did the other times. So after I did this a few times with consistent results. I went back and set the FSB to 166 and tried a 5:6 ratio so the memory was DDR400 and processor was the normal 2800+. I ran it again and to my suprise it passed all the tests and after an hour of this, I tried a game and that was perfectly fine as well. I checked the temps and CPU was only 45 C this time. So I'm thinking the processor can't handle anything above 50C or it's just plain overheating. I ordered a Thermaltake Silent Boost HSF today which is tested up to 3400+ so this should fix my problem. If not, then I'm going to replace the memory with a 512MB Geil PC3200 golden dragon dual-channel kit.
-
Hi
MSI Nforce K7N2 Delta-ILSR
Bios V1016
Antec True380SPGB True Power 380w
AMD Athlon XP2800+
2x512mb Crucial DDR
1xSATA HDD
Abit Siluro GF4 Ti4200
I've installed 1 SATA onto the onboard Raid controller, but I keep getting BSOD when either playing a game or watching avi's. The 0x00000000 message is disappearing too quickly to right down but is saying windows was shut down to prevent damage to the hardware.
Will the K7N2 Delta-ILSR Promise controller work with just one SATA hdd connected, I know that the silicon image controller on my Asus A7N8X-E will support just one SATA connected but will the promise chipset.
I've updated all the drivers but the dreaded BSOD keeps happening.
If it won't it not's a major problem as I do have a PCI sata controller card I can install.
Or are there any issues with the above graphics card and the MSI mobo?
Thanks for any help.Yep I've created a array with the single SATA and got Windows installed.
I've also changed the memory settings so they are now 1:1 with the FSB.
I've also altered the advance settings so I'll be able to write down the full 0X00000000 string.
Just set net access up via my PC and got this error report from M$
Error Message: STOP 0x000000EA THREAD_STUCK_IN_DEVICE_DRIVER (Q293078)
Error Caused by Graphics Device Driver
Thank you for submitting an error report. Microsoft is unable to determine what specifically caused the problem you reported. To troubleshoot the problem, please see the information listed below.
Analysis
A device driver installed on your computer caused the problem, but we cannot determine the precise cause. Depending on which situation is applicable to you, please do one of the following:
* If you are running Windows Server 2003 you may experience crashes if you have adjusted the Hardware Acceleration setting. Microsoft recommends that you set the Hardware Acceleration setting to None for server systems. To check your Hardware Acceleration setting, go to the Advanced section of the display properties dialog box.
* If you know the manufacturer of the device, contact the manufacturer's product support service for assistance.
* If you don't know the driver's manufacturer and need help diagnosing and resolving this problem, contact your computer manufacturer's product support service.
* Updated drivers might be available on the Microsoft Windows Update website. At Windows Update, you can have your computer scanned and, if there are updated drivers available, Windows Update will offer a selection of drivers that you might be able to use. To learn more about updated drivers that might be available, visit Microsoft Windows Update.
* For information about Microsoft support options, visit Microsoft Product Support Services.
I've downloaded the current graphics card drivers from Abit and I'll install them and see what happens.
I've also adjusted the AGP in the bios from 64mb to 128mb. -
[nForce]: Trouble Shooting Guide V1.6a
Hello.
Here is a guide to help solve some problems with K7N2 motherboards.
Problems arise in systems because some components do not work as they should.
Typical issues found with these boards consist of Non-nForce2 Approved RAM & a weak power supply. Other issues could be a cpu won't run at its rated fsb speed or an incorrectly mounted cpu cooler.
Sound problems - too many or incorrectly placed metal standoffs, bad drivers.
Windows won't install or you get a file read error - Incorrectly mounted CPU heat sink, RAM or power supply (PSU).
I've listed some instructions below to help those users that need a basic comprehensive guide to troubleshoot their systems with. Please read through the entire guide prior to posting for help on the forum.
Before you start doing anything, remove the power cord and make sure that you have touched the metal case of your system. This is called "Grounding yourself" and if you don't you could damage your system due to static discharge!
Thanks to Arioch and Dragon60 for comments on this.
1) BIOS/Startup POST reports wrong cpu or frequency
Check if jumper j10 and j11 are set to safemode and also check fsb settings in bios. If the jumpers are set to safe mode set them to normal, this is found in your motherboard manual. The jumpers vary with motherboards and manufacturers.
SafeMode sets cpu and memory to 100mhz.
Both memory and cpu are double pumped.
Data is clocked on the rise and fall of each clock cycle.
That means that 100mhz real frequency is 200mhz virtual frequency.
This is NOT without error and so your results may vary a little.
Non-Delta supports all cpu up to fsb 333
Delta supports all Socket A cpu
Duron upto 1300MHz = 100MHz (=200DDR)
Duron from 1400MHz = 133MHz (=266DDR)
Athlon B type = 100MHz (=200DDR)
Athlon C type = 133MHz (=266DDR)
Athlon XP - C type = 133MHz (=266DDR)
Athlon XP - D type = 166MHz (=333DDR)
Athlon XP - E type = 200MHz (=400DDR)
Support for new Duron 1400, 1600, 1800 with 266Mhz FSB (applebred)
The following boards support them:
(If a board is not on the list then it's not supported!)
-K7N2 6570 V1.0
-K7N2G-L 6570 V1.0
-K7N2G-ILSR 6570 V1.0
-K7N2 Delta 6570 V1.0
-K7N2GM-L 6777 V1.0
Thanks to DeathStalker
The best way to identify a processor is by using the OPN (Ordering Part Number) which can be found on the processor (E.g. AXDA 2700 D K V 3 D).
How to check which cpu you have:
http://www.amd.com/us-en/assets/content_type/DownloadableAssets/Electrical_Specification_Rev04_ENG.pdf
2) Over temp CPU
Is the Heat Sink and Fan rated for the CPU?
The CPU Heat Sink could be mounted wrong! Carefully remove it and check it. It can and will fit 2 ways but ther is only 1 right way. Examine the installation very carefully!
The Heat Sink has a recessed edge that has to be installed over the ridge (higher part or bump) of the socket. If installed backwards then it won't cool the entire area of the processor 'die' and could cause it to burn, thus killing it, or give you trouble as outlined in this guide.
Make sure that you use a QUALITY Thermal Compound/Paste and DO NOT reuse old compound! Note that some Heat Sinks are shipped with Thermal Pads, these are ok for some but will not give you the best heat transfer that a quality paste will.
Below are three images, the first two are incorrect, the last is correct.
Again..It is important to match the notch or step in the heatsink to the socket or it will not seat properly, causing immediate shutdowns, and ultimately damage your CPU.
If you use too much Silver based Thermal Compund you risk shorting the bridges on the CPU. This could cause damage to the CPU itself so use sparingly! If you feel that you've used too much then clean the die and substrate (the brown or green fiberglass material that the die is mounted on) and re-apply. Orange Clean TM is excellent for cleaning any type of thermal compound from a processor. Isopropyl Alchohol is ok but may leave traces of silver on the substrate. Using a 10X eye loupe will ensure that no traces of silver are shorting any bridges together after cleaning. DO NOT clean your processor while it rests in its socket on the motherboard. You run the risk of cleaner mixed with compound and dirt settling into your socket and that will cause further problems.
Last but not least. DO NOT use acetone to clean anything inside your PC. (or outside for that matter) It MAY not do any damage BUT it may dissolve some parts. Especially the coating on capacitors and resistors.
Silverbased compounds are not recommended by most manufacturers and if any traces are detected by them from an RMA'd processor they will usually void the warranty!
The latest AMD XP CPU's (XP-2000 and above) require a copperbased heatsink because their die are smaller and generate far more heat per square centimeter than the "old" CPU's did.
a)How to check the Heat Sink before taking it off:
There is a simple way to check the Heat Sink without taking it off. You do this by first checking your idle temp with SpeedFan or MBM, it should be below 50-55C.
Download Prime95 and run torture test for about 10 minutes while monitoring the temps, after about 1 minute or so it should stabilize and your temp should have gone up about 10-15C (max).
If it still goes up or the system crashes, there is a chance that you've mounted the heat sink incorrectly.
If your system can't run this check, (i.e. freezes or crashes) try setting your FSB to 100. Try to run the test again. If it still fails to run it could well be that the heat sink is mounted wrong or your power supply doesn't have enough power.
You cant check if the heatsink only has partial contact with the CPU die by looking on temperature monitor programs. The heatsink needs to be removed to see that.
If, after reading the guide regarding CPU Heat Sinks, you don't understand what we are talking about, then refer this link: AMD CPU & Cooling guide
http://www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/23986.pdf
3) Power Supplies
Most common cheap 300-350W power supply units (PSU for short) can't handle an XP-1700 or above, try a better one to be sure.
Make sure your PSU has 200W combined on the +3.3v & +5V rails and that the +3.3V rail is rated for 20A (A = Amps or Amperage) or above. This should be enough for most systems.
On the latest boards the +12V rail has become very important too, expecially with AMD ThunderBird & above CPU's. Make sure your PSU can supply 16A or more.
Alway's make sure you have a decent PSU, it never fails to spend a bit more on that part!
Borrow a bigger one from a friend if you are not sure.
Here's a good post on choosing the right power supply:
Choosing The Right Power Supply
This is the bare minimum that you should see on a PSU running an AMD processor. Intel is a bit more forgiving in some cases but with the amount of devices we use these days this minimum is a good guidline:
+3.3V - 28A or better
+5V - 35A or better
+12V - 16A or better
Watch out!! Cheap PSU's like Q-Tec come nowhere near these figures!! Do NOT trust the 300W or 400W rating on them!!! Q-Tec is about the worst of them all!!
4) Metal Stand-offs
Sometimes we are all a bit careless when it comes to changing a motherboard and forget to look at the layout of the stand-offs (those little silver or brass pieces that the screws screw into to hold the motherboard in the case) that are left from the old motherboard. Some motherboards use more than others thus some overlook the 'extra' one and mount that new board and never know the difference. Until they try to start their new baby up!
Remove the board and check for to see if you have too many of them by counting the holes or screws that you took out and then count the number of stand-offs you have in the case. Remove any uneeded stand-offs then remount your motherboard. Having 'extra's' can short out circuitry and cause all sorts of problems most of which are audio related.
Here are what typical stand-offs look like:
5) Sound
Two types of audio chipsets are used in these boards:
a) The -ILSR version uses Soundstorm and has drivers supplied from MSI or nVidia.
b) The -L version uses RealTek sound and has drivers supplied by MSI and Realtek.
There have been a lot of issues regarding the -L board and its drivers supplied by MSI. Realtek drivers seem to repair these issues and can be found here:
www.realtek.com.tw
Follow the ALC650 link.
6) RAM
Most of the issues involving these boards have been memory related. For various reasons cheaper generic memory doesn't run with nForce2 chipsets well and you should get nForce2 Approved RAM. Here is a link to nVidia's compatibility list as well as a list of what has worked for some:
Good Memory Choices for ALL K7N2 nF2 released boards
It's not a good idea to try to run DDR266 RAM when you have a 333FSB CPU, get DDR333 ram of decent quality.
If you think that you're having RAM issues then replace the ram with another brand to see if it fixes it or borrow some from a friend to check. Make sure it isn't cheap quality RAM or what you borrow isn't cheap quality. You can run to the local CompUSA (if you live in the USA that is) and buy some better quality RAM and return it later if you find that it isn't the problem.
DDR ram speeds:
Duron up to 1300/Athlon-B = 100FSB = PC-1600 = DDR200
Duron from 1400 = 133FSB = PC-2100 = DDR266
Athlon-C/XP up to 2600 = 133FSB = PC-2100 = DDR266
Athlon XP D-type and above = 166FSB = PC-2700 = DDR333
Athlon XP E-type and above = 200FSB = PC-3200 = DDR400
Set Fsb / Dram Ratio to 1:1 that means that the memory is working at the same speed as the fsb does.
Higher DDR speeds are only a must if you try to overclock. You can use faster RAM on a slower system and the motherboard bus will switch down in speed accordingly. The speeds given above are what should be used as a minimum, otherwise you're creating a serious bottleneck of data from the RAM.
Use a decent RAM testing utility such as Memtest86 if you suspect RAM is faulty. Typical failures of RAM include but are not limited to:
a) BSOD (Blue Screen of Death!)
b) Data Corruption
c) Machine won't cold boot
Try your system always with 1 RAM module at a time to see if you have a bad module. Swap modules if you have more than 1 to see if one or the other is bad. When upgrading remeber that adding more modules can give you trouble too. Especially if you mix manufacturers. Some sticks just won't work in pairs and some fail when you put 3 or more in the system. When you want to use 3 sticks, make very sure you use the nVidia tested and approved modules, they are your best chance that they will work without problems.
If still nothing try to seat the ram in another slot, sometimes they work better in another slot.
Thanks boost
Or raise the RAM voltage a little but be careful doing this! Sometimes this works when you have a lot of ram in the system.
7) BIOS
Sometimes when we play with our BIOS settings and set something wrong in it or set something incompatible with our hardware this causes the motherboard to not boot up. Sometimes they come from the factory that way as well. If so then clear the CMOS and start with the default settings. If it works try setting ONLY A FEW SETTINGS at a time and nothing more! If it works then go further from there a couple of settings at a time.
There are issues when changing VCORE and it gets stuck.
There are 3 ways to work around this issue.
1. Updating to the latest bios seems to fix it most of the time.
2. Clear CMOS, change VCORE in the BIOS, save changes then reboot and it should be changed.
3. Change VCORE in BIOS, save changes, turn off pc then disconnect PSU from wall outlet by either disconnecting the power cord or use the switch on the backside of the psu if there is one. Reconnect the power cord or turn the switch on again. Boot up the system, go into the BIOS and check under pc health to see if it has changed.
For RAID boards only!!
If you recieve a message at boot saying:
No Hard disk/drive present...BIOS will not be installed...
or something comparable, it means that there are no drives connected to the raid controllers and it's not installing the drivers needed to support the function of that particular device FROM BIOS ONLY! This is nothing to worry about and all of the other functions of your machine should work properly.
Modded bios to fix problems when using multiplier 10 and 10.5 and also to be able to use a higher FSB than with the MSI bios.
http://www.nforcershq.com/forum/viewtopic.php?t=46052
8) Clearing the CMOS chip
Disconnect the system power cord and push the case power button to drain all remaining power in the psu for approximately 15 seconds
Then move jumper jbat1 and wait 10 seconds and move it back to the original position. You should ensure that the jumper has metal inside of it when removed, sometimes (rarely) they don't. This process resets or clears the CMOS chip and is shown in most motherboard manuals.Now connect the power cord and restart your system.
Some motherboards require that the battery must be removed for 20 minutes before putting the battery and jbat1 back for the CMOS chip to be cleared.
***Starting your K7N2 Delta2 at default settings***
By "labtech1"
As some of you will be aware there is no safe mode jumper J10 on the K7N2 Delta2 series of boards. This has been replaced by the "insert" key method as used by Abit and Epox. To start your board at its default settings following an unsuccessful overclocking attempt you need to do the following using a ps2 keyboard. Turn off your machine and disconnect from the mains or turn off the switch on the back of the power supply. Press the front panel power switch several times to discharge any charge remaining in the power supply capacitors. Reconnect the power by plugging into wall socket or turning on psu power switch. Press and hold down "insert" on the keyboard and press the case front panel power switch. If you are successful it should start the cpu and memory at 100Mhz FSB. If it does press "delete" to reenter the bios to change your settings to known safe settings. Good luck.
9) Harddisks
If your hard drive is giving you problems:
Western Digital (WD) drive's are jumpered somewhat strange compared to others:
No jumper = Stand-Alone drive with no other drive attached to the cable.
Jumper master = Use this setting on your main drive if you have a slave drive installed in your system.
Jumper slave = Use this setting if you have a second hard drive installed in your system.
Cable Select - the preferred jumper setting
If your Hard Drive is doing weird things:
Make sure you have connected the color-coded connectors to the color-coded connectors on the motherboard and connect the other END of the cable to the hard drive. The middle connector can be left unattached without problems if not needed.
Not all motherboards have color-coded connectors.
IBM harddisks seem to fail a lot, try Drive-Fitness-Test on it, see if it has problems.
Run drive fitness test (DFT)
Maxtor also has its own version of hard drive check for their drives and is available from their website.
Any brand of hard drive can have problems so check the manufacturer website to see if there is a testing utility to use to make sure they are ok. Hard drive failures can cause some of the strangest problems with computers and should be checked via the Event Viewer of your Operating System or using the mfg's utility. Sometimes the Event Viewer will give you clues that you have bad sectors leading you to a potential hard drive failure. You could also find IDE/SCSI controllers that are suspect by looking there as well. Win9x and ME DO NOT have Event Viewers.
Alway's be sure your harddisk is in tip-top shape! If you suspect that it's not, replace it to verify.
IDE devices and hard drive guide (Written by Assaf & Bas)
IDE devices and hard drive guide(Written by Assaf & Bas)
To enable a hard drive over 137GB in Win2000 edit this registry key:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Atapi\Parameters]
"EnableBigLba"=dword:00000001
The K7N2G & Delta -ILSR boards support 2 IDE Devices on IDE 1 & 2, 1 IDE hard drive on IDE3 and 2 SATA drive's on the SATA Ports.
There is a modded bios that allows 2 drives on IDE3. USE THIS AT YOUR OWN RISK!!! Here is a link to it:
http://www.nforcershq.com/forum/viewtopic.php?t=27626&highlight=
Harddisk/power LED not functioning:
If your Hard Drive or Power LED doesn't work try turning the plug around on the motherboard connector. Some manufacturers don't mark or wire the LED cables properly and the LEDs will only work when + and - is correct.
Hard drive LEDs do not work with SATA drives but O&O Drive LED opens a little window and there you can see when a harddrive or cd is accessed. Works on both ide and sata drives.
10) Floppy Drives
If your floppy drive doesn't work or the LED stays on all of the time make sure the floppy is set correctly in the BIOS because the BIOS doesn't autodetect a floppy drive.
Check the cable making sure that the twist in the cable is at the floppy-drive side and flip the connector at the around. If it stays on after that or you still can't read a floppy disk try another drive or a different manufaturer type drive.
11) USB Ports
USB 2.0 ports are supported ONLY in Win2000 w/SP3 and XP w/SP1. Update your OS from Windows Update and let the OS install the ports after reboot and they should work.
If your USB ports aren't working:
Check in the BIOS if the ports are enabled. If you're using the front USB ports of your case check to see if all of the wires are connected properly.
There are 4 wires for each USB channel.
In some manufaturer's cases they are supplied with a wire called USBOC. Don't connect this as it can cause problems.
Also different mfg's mark the wires with different names so the basic nomenclature would be something like this:
+5v = +VCC
-D = -USB
+D = +USB
Note: Normally the cables are marked as +USB1 or -USB1, +USB2 or -USB2 and so on...please ensure that all of the 1's are together and all of the 2's are together.
12) Replacing parts and the system won't boot after
It's never a good idea to replace stuff like CPU and ram without taking the board out of the case. But if you do so please support the board because if you don't you might bend the board a little and cause trace breakage or component connections to the board to crack or break causing a bad contact. Always support the board when you replace components no matter what!
Also make sure your system is compatible with any replacement component. For example your PSU may not be able to handle a video card upgrade from a GeForce2 440MX to a GeForce4 Ti-4600 because the +12v rail is too low or the motherboard isn't rated to output the proper voltage to the AGP port.
If you have parts that work in another computer with a different chipset this DOES NOT mean they will work with the nforce2 chipset.
13) Graphics Card
If there is stability problem and/or can't use agp 8x then update to the latest bios and it should work. Also try to disable the 8x feature of the motherboard in the BIOS. If neither of these work then you may have a PSU that is under-powered and needs to be replaced. You could also have a faulty video card, AGP port on the motherboard among other things. If you have to disable the 8x feature in the BIOS then there is still a problem even if the card starts working. That may mean the motherboard is bad. Also use the latest drivers available from the respective manufacturer and don't forget to uninstall the old drivers first!! There is a sticky post in the VGA forum that details this process.
14) Checking the power supply
Don't do this if you don't know what you are doing!
a) Disconnect the power supply.
b) Orient the 20-pin power connector with the clip up.
c) Locate pin 4 and pin 8 top row, mostly green and black wire. (Usually the PSU manufacturer will have a drawing labeling the pins on their website)
d) Use a wire to short them (or better a 12V test lamp).
e) Now connect the power cord and the fan inside the power supply should start spinning. If it doesn't your power supply might be dead.
15) Windows
a) If you find that Windows2000/XP won't run stable:
Try to disable APIC and install again. Not all drivers/devices like the APIC.
b) Windows2000/XP won't install USB 2.0:
Install the latest service pack using Windows Update (SP3 Win2000 or SP1 WinXP). Windows should detect the USB ports on reboot and install the drivers for them. They should work now but if not you could have a faulty motherboard.
If you use a current or slipstreamed copy of Win2K or XP with the latest service pack they include these new drivers. This download will no longer be available on Windows Update.
USE THESE AT YOUR OWN RISK!!!
Slipstreaming Win2K with Service Packs and Creating a Bootable CD:
http://old.bink.nu/bootcd/
Slipstreaming Windows XP Service Packs and Creating a Bootable CD
http://www.windows-help.net/WindowsXP/winxp-sp1-bootcd.html
16) Raid
Configure a raid array:
After you have connected 1 or 2 hard drives to your Raid IDE port(s) press CTRL + F during boot and create a raid array.
It is possible to have 2 raid arrays working at the same time.
To boot from a raid array set SCSI as the first boot device.
To install windows on a raid array you have to press F6 to load raid drivers during the initial install of windows. This will be repeated during Windows desktop installation of drivers because the initial drivers are only loaded to memory during this initial install allowing the Windows installation program to access the raid drives. A default driver is loaded at bootup so that the drives can be accessed until the real drivers are loaded from the MB disk.
Raid 0 sets up striping which gives more performance for applications. Raid 1 sets up mirroring which gives drive security by duplicating the primary drive to the secondary drive.
When using two different sized drives in a raid array, the larger drive is forced to only use the amount of disk space that the smaller drive provides.
nForce 2 raid FAQ
(Mostly by Wonkanoby)
The third IDE only works with harddrives not optical drives such as CD,DVD. It only supports one drive.
You must create an array first, weather you are using 2 drives or just one
or nothing will happen .
You must also have a 3.5 floppy with the appropriate drivers handy.
INSTALLATION
To install raid as a boot drive.
Control + F and make the array.
Set SCSI second to cdrom in boot order.
Boot to xp cd and hit F6 as it prompts you to do right at the beginning and then insert the floppy.
This will be repeated during Windows desktop installation of drivers because the initial drivers are only loaded to memory during this initial install allowing the Windows installation program to access the raid drives.
The rest of the format/install is all as normal.
Drivers for the raid can be found here.
http://us-download.msi.com.tw/support/dvr_exe/sata48N.exe
Promise PDC20376 Serial-ATA RAID Utility
http://us-download.msi.com.tw/support/dvr_exe/37653.exe
If you make a new floppy, unrar them.
Then copy every thing including the text files to the floppy.
(no text files, nothing happens)
MODDED BIOS
such as
http://www.nforcershq.com/forum/viewtopic.php?t=27626
There are several offering full RAID.
They add ability to have 2x drives on ide 3.
I'm skeptical running raid 0 with both on the same ide myself.
Now these you must get the bios and the drivers.
The drivers are not the same as those for the RAID MSI includes.
The drivers are linked on that BIOS page I have provided.
RAID 0, sets up striping, which gives more performance for applications.
RAID 1, sets up mirroring which gives drive security by duplicating the primary drive to the secondary drive.
When using two different sized drives in a RAID array, the larger drive is forced to only use the amount of disk space that the smaller drive provides.
17) Good Links
J*A*G'S *Updated* nForce Cooling Guide (written by JAG)
Suggestions on posting and getting better answers (written by GlennVidia)
Good Memory Choices for K7N2G- IL and ILSR Board (written by Bonz)
ati problem ,post vga card model and bios (written by Wonkanoby)
Powersupplies(Written by Bas)
Moan Guide (Written by Wonkanoby)
A few good websites to have around!!
The Freeware Thread
NFORCE 2 OVERCLOCKING AND MODDING GUIDES
Use these guides, including the content of this entire guide, at your own risk!
This forum and it's members, including MSI, assume no liability whatsoever!
Part One
Part Two
I am not an expert on computers so I have most likely forgotten a lot of things. Please send me a private message or email me and I will add it if it's applicable. If you feel that something here is in error then please contact me via the above as well.
I also want to thank everyone that helped put this guide together.
All Star Lineup!
Arioch
DeathStalker
maesus
ClarkKent57
boost
Assaf
Bas
Tweetyoost
Stygge
HansH
GlennVidia
RoganJosh
Bonz
Wonkanoby
Dragon60
[T-A]_Super_10
labtech1Hello.
Here is a guide to help solve some problems with K7N2 motherboards.
Problems arise in systems because some components do not work as they should.
Typical issues found with these boards consist of Non-nForce2 Approved RAM & a weak power supply. Other issues could be a cpu won't run at its rated fsb speed or an incorrectly mounted cpu cooler.
Sound problems - too many or incorrectly placed metal standoffs, bad drivers.
Windows won't install or you get a file read error - Incorrectly mounted CPU heat sink, RAM or power supply (PSU).
I've listed some instructions below to help those users that need a basic comprehensive guide to troubleshoot their systems with. Please read through the entire guide prior to posting for help on the forum.
Before you start doing anything, remove the power cord and make sure that you have touched the metal case of your system. This is called "Grounding yourself" and if you don't you could damage your system due to static discharge!
Thanks to Arioch and Dragon60 for comments on this.
1) BIOS/Startup POST reports wrong cpu or frequency
Check if jumper j10 and j11 are set to safemode and also check fsb settings in bios. If the jumpers are set to safe mode set them to normal, this is found in your motherboard manual. The jumpers vary with motherboards and manufacturers.
SafeMode sets cpu and memory to 100mhz.
Both memory and cpu are double pumped.
Data is clocked on the rise and fall of each clock cycle.
That means that 100mhz real frequency is 200mhz virtual frequency.
This is NOT without error and so your results may vary a little.
Non-Delta supports all cpu up to fsb 333
Delta supports all Socket A cpu
Duron upto 1300MHz = 100MHz (=200DDR)
Duron from 1400MHz = 133MHz (=266DDR)
Athlon B type = 100MHz (=200DDR)
Athlon C type = 133MHz (=266DDR)
Athlon XP - C type = 133MHz (=266DDR)
Athlon XP - D type = 166MHz (=333DDR)
Athlon XP - E type = 200MHz (=400DDR)
Support for new Duron 1400, 1600, 1800 with 266Mhz FSB (applebred)
The following boards support them:
(If a board is not on the list then it's not supported!)
-K7N2 6570 V1.0
-K7N2G-L 6570 V1.0
-K7N2G-ILSR 6570 V1.0
-K7N2 Delta 6570 V1.0
-K7N2GM-L 6777 V1.0
Thanks to DeathStalker
The best way to identify a processor is by using the OPN (Ordering Part Number) which can be found on the processor (E.g. AXDA 2700 D K V 3 D).
How to check which cpu you have:
http://www.amd.com/us-en/assets/content_type/DownloadableAssets/Electrical_Specification_Rev04_ENG.pdf
2) Over temp CPU
Is the Heat Sink and Fan rated for the CPU?
The CPU Heat Sink could be mounted wrong! Carefully remove it and check it. It can and will fit 2 ways but ther is only 1 right way. Examine the installation very carefully!
The Heat Sink has a recessed edge that has to be installed over the ridge (higher part or bump) of the socket. If installed backwards then it won't cool the entire area of the processor 'die' and could cause it to burn, thus killing it, or give you trouble as outlined in this guide.
Make sure that you use a QUALITY Thermal Compound/Paste and DO NOT reuse old compound! Note that some Heat Sinks are shipped with Thermal Pads, these are ok for some but will not give you the best heat transfer that a quality paste will.
Below are three images, the first two are incorrect, the last is correct.
Again..It is important to match the notch or step in the heatsink to the socket or it will not seat properly, causing immediate shutdowns, and ultimately damage your CPU.
If you use too much Silver based Thermal Compund you risk shorting the bridges on the CPU. This could cause damage to the CPU itself so use sparingly! If you feel that you've used too much then clean the die and substrate (the brown or green fiberglass material that the die is mounted on) and re-apply. Orange Clean TM is excellent for cleaning any type of thermal compound from a processor. Isopropyl Alchohol is ok but may leave traces of silver on the substrate. Using a 10X eye loupe will ensure that no traces of silver are shorting any bridges together after cleaning. DO NOT clean your processor while it rests in its socket on the motherboard. You run the risk of cleaner mixed with compound and dirt settling into your socket and that will cause further problems.
Last but not least. DO NOT use acetone to clean anything inside your PC. (or outside for that matter) It MAY not do any damage BUT it may dissolve some parts. Especially the coating on capacitors and resistors.
Silverbased compounds are not recommended by most manufacturers and if any traces are detected by them from an RMA'd processor they will usually void the warranty!
The latest AMD XP CPU's (XP-2000 and above) require a copperbased heatsink because their die are smaller and generate far more heat per square centimeter than the "old" CPU's did.
a)How to check the Heat Sink before taking it off:
There is a simple way to check the Heat Sink without taking it off. You do this by first checking your idle temp with SpeedFan or MBM, it should be below 50-55C.
Download Prime95 and run torture test for about 10 minutes while monitoring the temps, after about 1 minute or so it should stabilize and your temp should have gone up about 10-15C (max).
If it still goes up or the system crashes, there is a chance that you've mounted the heat sink incorrectly.
If your system can't run this check, (i.e. freezes or crashes) try setting your FSB to 100. Try to run the test again. If it still fails to run it could well be that the heat sink is mounted wrong or your power supply doesn't have enough power.
You cant check if the heatsink only has partial contact with the CPU die by looking on temperature monitor programs. The heatsink needs to be removed to see that.
If, after reading the guide regarding CPU Heat Sinks, you don't understand what we are talking about, then refer this link: AMD CPU & Cooling guide
http://www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/23986.pdf
3) Power Supplies
Most common cheap 300-350W power supply units (PSU for short) can't handle an XP-1700 or above, try a better one to be sure.
Make sure your PSU has 200W combined on the +3.3v & +5V rails and that the +3.3V rail is rated for 20A (A = Amps or Amperage) or above. This should be enough for most systems.
On the latest boards the +12V rail has become very important too, expecially with AMD ThunderBird & above CPU's. Make sure your PSU can supply 16A or more.
Alway's make sure you have a decent PSU, it never fails to spend a bit more on that part!
Borrow a bigger one from a friend if you are not sure.
Here's a good post on choosing the right power supply:
Choosing The Right Power Supply
This is the bare minimum that you should see on a PSU running an AMD processor. Intel is a bit more forgiving in some cases but with the amount of devices we use these days this minimum is a good guidline:
+3.3V - 28A or better
+5V - 35A or better
+12V - 16A or better
Watch out!! Cheap PSU's like Q-Tec come nowhere near these figures!! Do NOT trust the 300W or 400W rating on them!!! Q-Tec is about the worst of them all!!
4) Metal Stand-offs
Sometimes we are all a bit careless when it comes to changing a motherboard and forget to look at the layout of the stand-offs (those little silver or brass pieces that the screws screw into to hold the motherboard in the case) that are left from the old motherboard. Some motherboards use more than others thus some overlook the 'extra' one and mount that new board and never know the difference. Until they try to start their new baby up!
Remove the board and check for to see if you have too many of them by counting the holes or screws that you took out and then count the number of stand-offs you have in the case. Remove any uneeded stand-offs then remount your motherboard. Having 'extra's' can short out circuitry and cause all sorts of problems most of which are audio related.
Here are what typical stand-offs look like:
5) Sound
Two types of audio chipsets are used in these boards:
a) The -ILSR version uses Soundstorm and has drivers supplied from MSI or nVidia.
b) The -L version uses RealTek sound and has drivers supplied by MSI and Realtek.
There have been a lot of issues regarding the -L board and its drivers supplied by MSI. Realtek drivers seem to repair these issues and can be found here:
www.realtek.com.tw
Follow the ALC650 link.
6) RAM
Most of the issues involving these boards have been memory related. For various reasons cheaper generic memory doesn't run with nForce2 chipsets well and you should get nForce2 Approved RAM. Here is a link to nVidia's compatibility list as well as a list of what has worked for some:
Good Memory Choices for ALL K7N2 nF2 released boards
It's not a good idea to try to run DDR266 RAM when you have a 333FSB CPU, get DDR333 ram of decent quality.
If you think that you're having RAM issues then replace the ram with another brand to see if it fixes it or borrow some from a friend to check. Make sure it isn't cheap quality RAM or what you borrow isn't cheap quality. You can run to the local CompUSA (if you live in the USA that is) and buy some better quality RAM and return it later if you find that it isn't the problem.
DDR ram speeds:
Duron up to 1300/Athlon-B = 100FSB = PC-1600 = DDR200
Duron from 1400 = 133FSB = PC-2100 = DDR266
Athlon-C/XP up to 2600 = 133FSB = PC-2100 = DDR266
Athlon XP D-type and above = 166FSB = PC-2700 = DDR333
Athlon XP E-type and above = 200FSB = PC-3200 = DDR400
Set Fsb / Dram Ratio to 1:1 that means that the memory is working at the same speed as the fsb does.
Higher DDR speeds are only a must if you try to overclock. You can use faster RAM on a slower system and the motherboard bus will switch down in speed accordingly. The speeds given above are what should be used as a minimum, otherwise you're creating a serious bottleneck of data from the RAM.
Use a decent RAM testing utility such as Memtest86 if you suspect RAM is faulty. Typical failures of RAM include but are not limited to:
a) BSOD (Blue Screen of Death!)
b) Data Corruption
c) Machine won't cold boot
Try your system always with 1 RAM module at a time to see if you have a bad module. Swap modules if you have more than 1 to see if one or the other is bad. When upgrading remeber that adding more modules can give you trouble too. Especially if you mix manufacturers. Some sticks just won't work in pairs and some fail when you put 3 or more in the system. When you want to use 3 sticks, make very sure you use the nVidia tested and approved modules, they are your best chance that they will work without problems.
If still nothing try to seat the ram in another slot, sometimes they work better in another slot.
Thanks boost
Or raise the RAM voltage a little but be careful doing this! Sometimes this works when you have a lot of ram in the system.
7) BIOS
Sometimes when we play with our BIOS settings and set something wrong in it or set something incompatible with our hardware this causes the motherboard to not boot up. Sometimes they come from the factory that way as well. If so then clear the CMOS and start with the default settings. If it works try setting ONLY A FEW SETTINGS at a time and nothing more! If it works then go further from there a couple of settings at a time.
There are issues when changing VCORE and it gets stuck.
There are 3 ways to work around this issue.
1. Updating to the latest bios seems to fix it most of the time.
2. Clear CMOS, change VCORE in the BIOS, save changes then reboot and it should be changed.
3. Change VCORE in BIOS, save changes, turn off pc then disconnect PSU from wall outlet by either disconnecting the power cord or use the switch on the backside of the psu if there is one. Reconnect the power cord or turn the switch on again. Boot up the system, go into the BIOS and check under pc health to see if it has changed.
For RAID boards only!!
If you recieve a message at boot saying:
No Hard disk/drive present...BIOS will not be installed...
or something comparable, it means that there are no drives connected to the raid controllers and it's not installing the drivers needed to support the function of that particular device FROM BIOS ONLY! This is nothing to worry about and all of the other functions of your machine should work properly.
Modded bios to fix problems when using multiplier 10 and 10.5 and also to be able to use a higher FSB than with the MSI bios.
http://www.nforcershq.com/forum/viewtopic.php?t=46052
8) Clearing the CMOS chip
Disconnect the system power cord and push the case power button to drain all remaining power in the psu for approximately 15 seconds
Then move jumper jbat1 and wait 10 seconds and move it back to the original position. You should ensure that the jumper has metal inside of it when removed, sometimes (rarely) they don't. This process resets or clears the CMOS chip and is shown in most motherboard manuals.Now connect the power cord and restart your system.
Some motherboards require that the battery must be removed for 20 minutes before putting the battery and jbat1 back for the CMOS chip to be cleared.
***Starting your K7N2 Delta2 at default settings***
By "labtech1"
As some of you will be aware there is no safe mode jumper J10 on the K7N2 Delta2 series of boards. This has been replaced by the "insert" key method as used by Abit and Epox. To start your board at its default settings following an unsuccessful overclocking attempt you need to do the following using a ps2 keyboard. Turn off your machine and disconnect from the mains or turn off the switch on the back of the power supply. Press the front panel power switch several times to discharge any charge remaining in the power supply capacitors. Reconnect the power by plugging into wall socket or turning on psu power switch. Press and hold down "insert" on the keyboard and press the case front panel power switch. If you are successful it should start the cpu and memory at 100Mhz FSB. If it does press "delete" to reenter the bios to change your settings to known safe settings. Good luck.
9) Harddisks
If your hard drive is giving you problems:
Western Digital (WD) drive's are jumpered somewhat strange compared to others:
No jumper = Stand-Alone drive with no other drive attached to the cable.
Jumper master = Use this setting on your main drive if you have a slave drive installed in your system.
Jumper slave = Use this setting if you have a second hard drive installed in your system.
Cable Select - the preferred jumper setting
If your Hard Drive is doing weird things:
Make sure you have connected the color-coded connectors to the color-coded connectors on the motherboard and connect the other END of the cable to the hard drive. The middle connector can be left unattached without problems if not needed.
Not all motherboards have color-coded connectors.
IBM harddisks seem to fail a lot, try Drive-Fitness-Test on it, see if it has problems.
Run drive fitness test (DFT)
Maxtor also has its own version of hard drive check for their drives and is available from their website.
Any brand of hard drive can have problems so check the manufacturer website to see if there is a testing utility to use to make sure they are ok. Hard drive failures can cause some of the strangest problems with computers and should be checked via the Event Viewer of your Operating System or using the mfg's utility. Sometimes the Event Viewer will give you clues that you have bad sectors leading you to a potential hard drive failure. You could also find IDE/SCSI controllers that are suspect by looking there as well. Win9x and ME DO NOT have Event Viewers.
Alway's be sure your harddisk is in tip-top shape! If you suspect that it's not, replace it to verify.
IDE devices and hard drive guide (Written by Assaf & Bas)
IDE devices and hard drive guide(Written by Assaf & Bas)
To enable a hard drive over 137GB in Win2000 edit this registry key:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Atapi\Parameters]
"EnableBigLba"=dword:00000001
The K7N2G & Delta -ILSR boards support 2 IDE Devices on IDE 1 & 2, 1 IDE hard drive on IDE3 and 2 SATA drive's on the SATA Ports.
There is a modded bios that allows 2 drives on IDE3. USE THIS AT YOUR OWN RISK!!! Here is a link to it:
http://www.nforcershq.com/forum/viewtopic.php?t=27626&highlight=
Harddisk/power LED not functioning:
If your Hard Drive or Power LED doesn't work try turning the plug around on the motherboard connector. Some manufacturers don't mark or wire the LED cables properly and the LEDs will only work when + and - is correct.
Hard drive LEDs do not work with SATA drives but O&O Drive LED opens a little window and there you can see when a harddrive or cd is accessed. Works on both ide and sata drives.
10) Floppy Drives
If your floppy drive doesn't work or the LED stays on all of the time make sure the floppy is set correctly in the BIOS because the BIOS doesn't autodetect a floppy drive.
Check the cable making sure that the twist in the cable is at the floppy-drive side and flip the connector at the around. If it stays on after that or you still can't read a floppy disk try another drive or a different manufaturer type drive.
11) USB Ports
USB 2.0 ports are supported ONLY in Win2000 w/SP3 and XP w/SP1. Update your OS from Windows Update and let the OS install the ports after reboot and they should work.
If your USB ports aren't working:
Check in the BIOS if the ports are enabled. If you're using the front USB ports of your case check to see if all of the wires are connected properly.
There are 4 wires for each USB channel.
In some manufaturer's cases they are supplied with a wire called USBOC. Don't connect this as it can cause problems.
Also different mfg's mark the wires with different names so the basic nomenclature would be something like this:
+5v = +VCC
-D = -USB
+D = +USB
Note: Normally the cables are marked as +USB1 or -USB1, +USB2 or -USB2 and so on...please ensure that all of the 1's are together and all of the 2's are together.
12) Replacing parts and the system won't boot after
It's never a good idea to replace stuff like CPU and ram without taking the board out of the case. But if you do so please support the board because if you don't you might bend the board a little and cause trace breakage or component connections to the board to crack or break causing a bad contact. Always support the board when you replace components no matter what!
Also make sure your system is compatible with any replacement component. For example your PSU may not be able to handle a video card upgrade from a GeForce2 440MX to a GeForce4 Ti-4600 because the +12v rail is too low or the motherboard isn't rated to output the proper voltage to the AGP port.
If you have parts that work in another computer with a different chipset this DOES NOT mean they will work with the nforce2 chipset.
13) Graphics Card
If there is stability problem and/or can't use agp 8x then update to the latest bios and it should work. Also try to disable the 8x feature of the motherboard in the BIOS. If neither of these work then you may have a PSU that is under-powered and needs to be replaced. You could also have a faulty video card, AGP port on the motherboard among other things. If you have to disable the 8x feature in the BIOS then there is still a problem even if the card starts working. That may mean the motherboard is bad. Also use the latest drivers available from the respective manufacturer and don't forget to uninstall the old drivers first!! There is a sticky post in the VGA forum that details this process.
14) Checking the power supply
Don't do this if you don't know what you are doing!
a) Disconnect the power supply.
b) Orient the 20-pin power connector with the clip up.
c) Locate pin 4 and pin 8 top row, mostly green and black wire. (Usually the PSU manufacturer will have a drawing labeling the pins on their website)
d) Use a wire to short them (or better a 12V test lamp).
e) Now connect the power cord and the fan inside the power supply should start spinning. If it doesn't your power supply might be dead.
15) Windows
a) If you find that Windows2000/XP won't run stable:
Try to disable APIC and install again. Not all drivers/devices like the APIC.
b) Windows2000/XP won't install USB 2.0:
Install the latest service pack using Windows Update (SP3 Win2000 or SP1 WinXP). Windows should detect the USB ports on reboot and install the drivers for them. They should work now but if not you could have a faulty motherboard.
If you use a current or slipstreamed copy of Win2K or XP with the latest service pack they include these new drivers. This download will no longer be available on Windows Update.
USE THESE AT YOUR OWN RISK!!!
Slipstreaming Win2K with Service Packs and Creating a Bootable CD:
http://old.bink.nu/bootcd/
Slipstreaming Windows XP Service Packs and Creating a Bootable CD
http://www.windows-help.net/WindowsXP/winxp-sp1-bootcd.html
16) Raid
Configure a raid array:
After you have connected 1 or 2 hard drives to your Raid IDE port(s) press CTRL + F during boot and create a raid array.
It is possible to have 2 raid arrays working at the same time.
To boot from a raid array set SCSI as the first boot device.
To install windows on a raid array you have to press F6 to load raid drivers during the initial install of windows. This will be repeated during Windows desktop installation of drivers because the initial drivers are only loaded to memory during this initial install allowing the Windows installation program to access the raid drives. A default driver is loaded at bootup so that the drives can be accessed until the real drivers are loaded from the MB disk.
Raid 0 sets up striping which gives more performance for applications. Raid 1 sets up mirroring which gives drive security by duplicating the primary drive to the secondary drive.
When using two different sized drives in a raid array, the larger drive is forced to only use the amount of disk space that the smaller drive provides.
nForce 2 raid FAQ
(Mostly by Wonkanoby)
The third IDE only works with harddrives not optical drives such as CD,DVD. It only supports one drive.
You must create an array first, weather you are using 2 drives or just one
or nothing will happen .
You must also have a 3.5 floppy with the appropriate drivers handy.
INSTALLATION
To install raid as a boot drive.
Control + F and make the array.
Set SCSI second to cdrom in boot order.
Boot to xp cd and hit F6 as it prompts you to do right at the beginning and then insert the floppy.
This will be repeated during Windows desktop installation of drivers because the initial drivers are only loaded to memory during this initial install allowing the Windows installation program to access the raid drives.
The rest of the format/install is all as normal.
Drivers for the raid can be found here.
http://us-download.msi.com.tw/support/dvr_exe/sata48N.exe
Promise PDC20376 Serial-ATA RAID Utility
http://us-download.msi.com.tw/support/dvr_exe/37653.exe
If you make a new floppy, unrar them.
Then copy every thing including the text files to the floppy.
(no text files, nothing happens)
MODDED BIOS
such as
http://www.nforcershq.com/forum/viewtopic.php?t=27626
There are several offering full RAID.
They add ability to have 2x drives on ide 3.
I'm skeptical running raid 0 with both on the same ide myself.
Now these you must get the bios and the drivers.
The drivers are not the same as those for the RAID MSI includes.
The drivers are linked on that BIOS page I have provided.
RAID 0, sets up striping, which gives more performance for applications.
RAID 1, sets up mirroring which gives drive security by duplicating the primary drive to the secondary drive.
When using two different sized drives in a RAID array, the larger drive is forced to only use the amount of disk space that the smaller drive provides.
17) Good Links
J*A*G'S *Updated* nForce Cooling Guide (written by JAG)
Suggestions on posting and getting better answers (written by GlennVidia)
Good Memory Choices for K7N2G- IL and ILSR Board (written by Bonz)
ati problem ,post vga card model and bios (written by Wonkanoby)
Powersupplies(Written by Bas)
Moan Guide (Written by Wonkanoby)
A few good websites to have around!!
The Freeware Thread
NFORCE 2 OVERCLOCKING AND MODDING GUIDES
Use these guides, including the content of this entire guide, at your own risk!
This forum and it's members, including MSI, assume no liability whatsoever!
Part One
Part Two
I am not an expert on computers so I have most likely forgotten a lot of things. Please send me a private message or email me and I will add it if it's applicable. If you feel that something here is in error then please contact me via the above as well.
I also want to thank everyone that helped put this guide together.
All Star Lineup!
Arioch
DeathStalker
maesus
ClarkKent57
boost
Assaf
Bas
Tweetyoost
Stygge
HansH
GlennVidia
RoganJosh
Bonz
Wonkanoby
Dragon60
[T-A]_Super_10
labtech1 -
BSOD and Memory (perhaps)
Over the last six weeks I have run into a number of BSOD issues which have left me both perplexed and yet and at the same time livid.
The messages onscreen are inconsistent although the crash invariable occurs when playing a game, every game in fact except Medieval Total war (for some reason).
I have attempted to analyse the memory - memtest ran overnight and found no errors. The finger of blame then shifted to point to Norton which has now been blown away, PSU has been checked, thermal paste reapplied etc etc
I was having issues with Nvidia 57.62 drivers but rolled back to 53.03 and that situation seemed to resolve itself in as much as no specific dll was mentioned on the BSOD. Every message seems to point to memory (when followed up on Google) but I would like to resolve any problem if I can rather than replace the memory sticks.
Memory timings were set by SPD at 7-3-3-2 and Crucial are a company related to Microm if that helps
IRQ settings are as follows - if that helps
IRQ 0 System timer OK
IRQ 1 Standard 101/102-Key or Microsoft Natural PS/2 Keyboard OK
IRQ 3 Communications Port (COM2) OK
IRQ 4 Communications Port (COM1) OK
IRQ 6 Standard floppy disk controller OK
IRQ 8 System CMOS/real time clock OK
IRQ 9 Microsoft ACPI-Compliant System OK
IRQ 11 NVIDIA nForce PCI System Management OK
IRQ 13 Numeric data processor OK
IRQ 14 Primary IDE Channel OK
IRQ 15 Secondary IDE Channel OK
IRQ 19 NVIDIA GeForce FX 5700 Ultra OK
IRQ 20 Standard OpenHCD USB Host Controller OK
IRQ 20 NVIDIA(R) nForce(TM) Audio Codec Interface OK
IRQ 21 Standard Enhanced PCI to USB Host Controller OK
IRQ 21 OHCI Compliant IEEE 1394 Host Controller OK
IRQ 22 Standard OpenHCD USB Host Controller OK
IRQ 22 NVIDIA(R) nForce(TM) MCP Audio Processing Unit (Dolby(R) Digital) OK
Sorry to be vague with the BSOD message info but if I see one more tonight Mr Fist will meet Mr Screen at extreme velocity
Thanks in AdvanceIRQ's are fine
So drivers and Norton are the only thing you've introduced to this system prior to this problem?
How long has this OS been up and running?
Have you installed a lot of programs and/or uninstalled them?
At first, I would consider several things.
I need to look back and try to remember when it started happening and then try to tie in what how and when (changes) I've made to the OS, such as new programs, drivers, introuduced new hardware etc. After some investigation, if I can't attribute this problem to possibly any changes I may have made, then I have to consider a hardware or power problem. I don't have either of the latter as I have a good supply like you and I use a UPS with a line conditioner.
You've tested the RAM but that doesn't rule out a problem completely but good enough to look elsewhere for the time being. If it worked great before, no sense in changing memory settings, logic tells me that's like swatting the dog for crapping on your new carpet, when it was really your one year old's diaper that's leaking.
By now I may have come to the conclusion it's probably me that's introduced or had a hand in cocking up my system and I consider a full reformat and re-install to verify my suspicion. It's certainly takes me less time to load the OS then to nitpick around, especially with how I beat up my OS on a regular basis. I can't even go 9 months before I decide it's time.
Just some things to think about, no point in getting angry at a computer, you own it so you have a right to abuse it -
Machine Specs:
- AMD Athlon XP 2600+ With L2 512 KB (Model 10)
- MSI K7N2 Delta -L nFORCE 2 Ultra 400 (601-670-020) (My AwardBios is updated to v5.7, Using nVIDIA`s O/B Audio and Ethernet Controllers)
- TwinMOS PC3200(CL2.5) 512 MB DDR400 RAM (Desktop Series)
- Samsung SpinPoint (SP0411N) 40 GB 7200 Rpm HDD
- GeForce2 MX400 64MB AGP 4x (Oem Manufacturer)
- Samsung SyncMaster 753s 17" Monitor
- Sony 52x Cd-Rom
- Philips Stereo Headphones
- Windows XP Home Edition Turkish (Service Pack 1 Turkish) , I did all of critical and other updates ,Totally up to date.Device drivers are too...(nForce 3.13 whql International,Forceware 56.72 whql International)
Problem :
- ERROR EVENT : 1003 ERROR NAME : IRQL_NOT_LESS_OR_EQUAL
Original Error Texts:
A problem has been detected & Windows has been shut down to prevent damage to your computer.
IRQL_NOT_LESS_OR_EQUAL
If this is the first time you've seen this Stop error screen, restart the computer. If this screen appears again follow these steps.
Check to make sure any new hardware or software is properly installed. If this is a new installation, ask your hardware or software manufacturer for any Windows updates you might need. If the problem continues, disable or remove any newly installed hardware or software.
Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components restart your computer, Press F8 to select Advanced Start-up options & select Safe Mode.
Technical Information :
*** STOP: 0x0000000A (0x00000004, 0x00000002, 0x00000001, 0x804F1473)
Beginning dump of physical memory
Physical memory dump complete. Contact your system Administrator or technical support group for further assistance.
After restarting manually from the PC. I get the following message
The system has recovered from a serious error.
BCCode : a BCP1 : 00000004 BCP2 : 00000002 BCP3 : 00000000
BCP4 : 804F1ADA OSVer : 5_1_2600 SP : 0_0 Product : 256_1
C:\WINDOWS\Minidump\Mini042202-01.dmp
C:\DOCUME~1\DANIEL~1\LOCALS~1\Temp\WER3.tmp.dir00\sysdata.xml
And when I check EVENT VIEWER
Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 22/04/2002
Time: 5:55:03 PM
User: N/A
Computer: XXX-BOX
Description:
Error code 0000000a, parameter1 00000004, parameter2 00000002, parameter3 00000000, parameter4 804f1ada.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 30 30 30 30 30 30 30 0000000
0020: 61 20 20 50 61 72 61 6d a Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 30 34 2c 20 000004,
0038: 30 30 30 30 30 30 30 32 00000002
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 30 2c 20 38 30 34 66 00, 804f
0050: 31 61 64 61 1ada
I installed 6 operating systems on my pc (WinXp Home Edition Turkish/English,WinXP Pro Turkish/English,Win98 Turkish/English) and tested it, but every time i meet the same thing (MS Blue Screen Of Death Sux...).I checked the WinXP`s logs and searched for error code`s meaning from microsoft knowledge database. They are saying nothing about this problem but the problem`s root is coming from a bad device driver. It seems to be a generic problem for all operating systems cuz all of them were restarting themselves randomly, before i close "auto-restart on critical errors" option.After i saw some messages on forums , i searched for my RAM maker`s home page then i learned that my RAM is assembled with VIA KT Series and SIS chips & optimized for them. I think nForce is too picky about rams.But i aint sure about where the hell is this problem coming from. If you guys are sure about that is an unsupported ram problem and knew the list of ram marks&models that supported by MSI K7N2 Delta -L ,please help me about this damn problem. Thanks for your help.
Note : I tried Asus Ati Radeon 9200SE 64mb g.adapter (some peoples told me thats about g.adapter), but problem continued.If I read correctly in your specs I see only 11 Amps on the +12v Rail. Is this correct?
If so, I'd advise a PSU that has at least 18 amps on the +12v Rail, perhaps as low as 16 with the other rails to match as shown currently in your spec.
11 Amps is just way too underpowered for that rig. I am surprised it even boots.
At what point does the BSOD occur? -
BSOD's and boot errors on HP Blackbird 002
Hello,
I have a HP BLACKBIRD 002 LC with Quad Core - Intel(R) Core2(TM) Quad-Core 2.4GHz Q6600, 2 GB 1066MHz CORSAIR PC2-8500 DDR2 SDRAM, ASUS Striker Extreme, NVIDIA GeForce 8800 GTX, with 768MB of GDDR3 SDRAM running Microsoft Windows Vista Ultimate.
I’ve had it since December 2007 and have had no problems whatsoever until this past December (2011). Around the 30th or 31st of December, I started getting Blue Screens of Death (BSOD’s) at random points all with multiple and variable errors. I’ve tried going into SAFE mode and SAFE mode with networking to resolve the issue, but would eventually get a BSOD. Sometimes now, it won’t even power on the monitor or it shuts down completely when I try to enter the BIOS setup. Other times, it boots into the NVIDIA boot agent and then exits due to some error.
Prior to December 2011 and the errors, I did not install any new hardware nor any major software, besides routine software upgrades that would pop up. I conducted weekly scans with AVG virus software. Last major thing I did was uninstall a game.
Since then I have tried changing the power source cabling, checking the seating of components and cabling inside, recovering Windows to earlier images (20 and then 15 December), re-installing Windows, replacing the CMOS battery, and running whatever memory or hardware diagnostic tools that I can find in the internal menus and the Vista CD. My brother-in-law, who works as an IT help desk guy, took a look at it remotely and couldn’t figure it out. I sent him some of the Minidump files(which I still have and can send) and the best he could isolate was consistent errors in the Minidump files with this “ntkrnlpa.exe ntkrnlpa.exe+1026e0 0x82411000 0x827cb000 0x003ba000 0x4ea6b87e .”
I did not make a recovery disc since the shadow copy backed everything up. I do have a full system image from earlier in December that I can use to recover my files, so at this point I’m fine with restoring the factory settings if that’s even possible.
I have no idea what to do next, so would appreciate any advice. Thanks.I'd pull the "backplane" (the PCB out) and run power and data cables to the drives which I would keep in there caddys.
...and as you said if you need the LED lighting, you can always find a power source for those somewhere.
Blackbird 002 – Core i7-920 ~ eVGA X58 SLI ~ 6GB Corsair Dominator DDR3 1600 ~ OCZ Vertex 60 GB SSD ~ WD Black 1TB ~ 3 x SLI BFG gtx260s max core 55 ~ Custon LC (cpu)
Blackbird 002 – Core i7-920 ~ eVGA X58 SLI ~ 12GB Corsair Dominator DDR3 1600 ~ 2 x WD Velociraptor 300GB (Raid 0) ~ WD Velociraptor 300GB ~ WD Velociraptor 150GB ~ eVGA e-GeForce 9800 GT AKIMBO ~ Asetek LCLC (cpu)
Omen – Intel Core 2 Extreme X6800 ~ eVGA nForce 750i SLI FTW ~ 4GB Corsair Dominator DDR2 1066 ~ WD Raptor 150GB ~ WD Black 1TB ~ eVGA GeForce 8800 GTX ~ LG Multi read write -
New Nforce driver 2.0 Released !!
@@@@@@Release Highlights@@@@@@
11am PST update: kit updated to correctly recognized graphics driver WHQL logo
First full unified package for nForce and nForce2
Full localizations for all languages
Fixes audio DirectX BSOD issue on Windows XP systems
Adds ASIO driver support
Adds OpenAL driver support
Updated nForce Audio control panel
Incorporates performance improvements and other bug fixes
@@@@@Notes@@@@@
Windows XP users must install Service Pack 1 prior to attempting to install this package. Failure to do so will result in the inability to support USB 2.0 and NVIDIA IDE drivers.
Audio drivers will not install on the following nForce2 products: ASUS A7N8X and Chaintech 7NJS. Please use the drivers that come with these products to enable audio functionality.
USB keyboards and/or mice will be disabled during the installation of this package. Please connect PS2 devices before starting the installation process.
@@@@@Driver Versions@@@@@
Audio driver 3.06 WHQL
Audio control panel 3.07
Network driver 2.81 WHQL
GART driver 2.78 WHQL
SMBus driver 2.75 WHQL
Memory controller driver 2.75 WHQL
IDE driver 2.70 In The Box WHQL
IDE driver 3.07 Full Driver
Display Drivers 40.72 WHQL
Bye ...I had to manually install the drivers on my existing xp installation. aside from that I have not gotton the black screen playing aaops with surround turned on which is when it was occuring. The installer did however extract the drivers to the c drive nicely. On a seperate partition and a clean install of xp the drivers did successfully install the agp driver but I had to manually install the soundstorm, memory, sound, and network. For anyone wondering how to install the soundstorm drivers manually I did mine by goijng to the directory where the files for the audio utilities were extracted finding the inf file right clicking and selecting install. I noticed one thing that might be a problem and that was the part where the microsoft sound files get installed didn't come up. however the soundstorm control panel and tray icon both function normally. On the existing XP installation I first removed all of items for nforce which were in the add remove programs control panel and then updating the drivers listed in the device manager again when I installed the sound drivers and utility the microsoft installer did not come up either, but the tray icon and control panel seem to work finem
-
Nforce drivers which one ? nvidia or msi ?
i need to know which ones gives you max performance ? either nvidia ones or msi's ! .. i had msi nforce3 drivers so i uninstalled them and installed nvidia's ones , i also have a nvidia gfx card , so after installing nvidia nforce drivers i was getting BSOD , so i had to format windows and installed msi's ..
BSOD = may be msi drivers were in the reg and never got uninstalled properly so i m gettin BSOD so you get BSOD if u put nvidia nforce3 having a nvidia gfx card?
so how many of you are using nvidia's ? and which ones better?
my os windows xp sp2I've always used nvidias drivers , realtek's sound drivers . Now latest 5.10 .
Xp sp2 no problem here.
MSI drivers are made by nvidia of course .
The MSI 5.03 driver package was something in the middle of nvidias 4.27 and 5.10
when it comes to some of the individual driver versions .
After all : For graphics cards most people always use ATI's site for ATI cards and nvidia's site for Nvidia cards.
Same should apply with chipset drivers . -
Hello everyone. For the past .. over a year now, I've been having BSoD issues. It happens during several things.
#1: Recording gameplay using capture card
#2: Unplugging said capture card from USB while forgetting to use the "safely remove" option
#3: After stopping some process that uses up a lot of CPU usage or RAM, like games, rendering software, etc
#4: Going to audio recording devices in control panel, selecting "listen to this device" for my mic and then unselecting it later
#4: Randomly, or just some pattern that I haven't picked up on
First off, I'm bad at technical stuff with PC's so I apologize if I say something dumb or don't completely understand something.
For a while, because of the "listen to this device" thing, I assumed it was dealing with my audio. It seemed to fit everything besides RAM/usage problems. My motherboard fried a good amount of time after, and was replaced, but the problem still
occurred, so I assumed it wasn't the mobo. Not long ago, I figured it might actually have to do with my RAM. I can't remember what led me to this idea, but it was something I read up on. It seemed to make more sense than some audio issue.
So I'll add these BSV dmp's in it, and ask you to assist me in figuring out what the problem is.
There's normally 1-2 things highlighted in BSV, but one that ALWAYS is highlighted is ntoskrnl.exe at "Size" 0x005dd000, although at different "Address In Stack"s. I've read that ntoskrnl is essential for the pc to work, so maybe that's
why it always shows up, but anyways..
==================================================
Dump File : 050713-66125-01.dmp
Crash Time : 5/7/2013 3:16:33 PM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : fffff880`0224c47c
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff880`07f4ffc0
Caused By Driver : nvmcp64.sys
Caused By Address : nvmcp64.sys+80fc0
File Description : NVIDIA® nForce(TM) MCP APU Audio Library
Product Name : NVIDIA nForce(TM) Audio Driver
Company : NVIDIA Corporation
File Version : 6.14.0465.0 built by: NVIDIA
Processor : x64
Crash Address : ntoskrnl.exe+71f00
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\050713-66125-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 291,448
Dump File Time : 5/7/2013 3:18:37 PM
==================================================
==================================================
Dump File : 041713-30609-01.dmp
Crash Time : 4/17/2013 3:27:44 PM
Bug Check String : PROCESS_HAS_LOCKED_PAGES
Bug Check Code : 0x00000076
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`052e2060
Parameter 3 : 00000000`00000001
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+71f00
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : x64
Crash Address : ntoskrnl.exe+71f00
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\041713-30609-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 262,144
Dump File Time : 4/17/2013 3:29:36 PM
==================================================
==================================================
Dump File : 041713-39671-01.dmp
Crash Time : 4/17/2013 1:04:14 PM
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff880`03e7b9a5
Parameter 3 : fffff880`02f9d648
Parameter 4 : fffff880`02f9cea0
Caused By Driver : nvlddmkm.sys
Caused By Address : nvlddmkm.sys+11557f
File Description : NVIDIA Windows Kernel Mode Driver, Version 331.65
Product Name : NVIDIA Windows Kernel Mode Driver, Version 331.65
Company : NVIDIA Corporation
File Version : 9.18.13.3165
Processor : x64
Crash Address : stdriver64.sys+19a5
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\041713-39671-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 294,792
Dump File Time : 4/17/2013 1:06:06 PM
==================================================
==================================================
Dump File : 032313-28609-01.dmp
Crash Time : 3/23/2013 9:25:07 PM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 00000000`55d78327
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff880`03f2a9a5
Caused By Driver : stdriver64.sys
Caused By Address : stdriver64.sys+19a5
File Description : stdriver.sys
Product Name : stdriver.sys
Company : NCH Software
File Version : 1.13:14:30:54
Processor : x64
Crash Address : ntoskrnl.exe+71f00
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\032313-28609-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 294,784
Dump File Time : 3/23/2013 9:26:05 PM
==================================================
==================================================
Dump File : 031313-25765-01.dmp
Crash Time : 3/13/2013 2:13:16 PM
Bug Check String : PROCESS_HAS_LOCKED_PAGES
Bug Check Code : 0x00000076
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`021186e0
Parameter 3 : 00000000`00000002
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+71f00
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7600.16385 (win7_rtm.090713-1255)
Processor : x64
Crash Address : ntoskrnl.exe+71f00
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\031313-25765-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 7600
Dump File Size : 290,656
Dump File Time : 3/13/2013 2:14:42 PM
==================================================
Hopefully this is enough information. BSV shows up to 50 of them, and those are the most recent 5. Thanks for any info.KOOL4ID
The most recent date on those DMP files is from May 2013 so not useful. Please check the wiki to make sure they are enabled in your control panel.
One thing of note is that you hae drivers from as far back as 2004 that would be updated when you update to service pack 1. That may fix this problem in itself so I would do that.
Service pack 1 Update.
http://windows.microsoft.com/installwindows7sp1
Learn how to install Windows 7 Service Pack 1 (SP1)
http://windows.microsoft.com/en-US/windows7/learn-how-to-install-windows-7-service-pack-1-sp1
Additional Resources:
http://windows.microsoft.com/en-US/windows7/uninstall-sp1
http://windows.microsoft.com/troubleshootwindows7sp1
Wanikiya and Dyami--Team Zigzag -
Asus A8n-vm chipset problem (nforce 410)
Hello there, i'm new here!
i have installed my Sun Solaris 10 on a motherboard Asus A8N-VM with the Nvidia Nforce 410 chipset. I also have a PCI-Express Graphic Card from XFX (geforce 6800 XT).
where can i download the drivers and how do i install the Graphic Card, onboard LAN and onboard audio?
friendly greetings, Erik de ZeeuwYeah, I remember this error, I couldn't even install the X-Fi drivers. I solved it disabling the onboard IEE394 Firewire controller. Now the drivers install ok, but after some time gaming (half an hour usually), a bsod caused by ha20x2k and a reboot. I've just installed beta 002 bios, time for some testing now, but I'm afraid I will return this motherboard
-
Very Weird Bsod Error!!
Hi all,
I have had my setup for about 6 months and have been satisfied with its performance and have had almost no problems.
Today a big problem came, I turned on my computer from a cold boot and after the windows xp splash screen was halfway done I hear a click from inside my case and then a blue screen of death on my monitor with MACHINE CHECK EXCEPTION. I could do nothing but power it off and turn it back on. When windows loaded successfully this time, I get the infamous "Your system has recovered from a serious error." message, and I could few the details but it looks scrambled and foreign to me, I don't know what the error is pointing at.
I am pretty sure this is a hardware error and I am leaning towards my harddrive because it is the oldest component I have and I have tested my ram with memtest and friends computers and no problems whatsoever.
I am stumped except for two possible solutions I could try:
1. I read on this forum something about upping CPU voltage? I have it at default 1.50V. What should it be and will it do any harm?
2. I currently have official bios 1.4. I could flash to 1.5 to see if my problems are solved but I don't exactly know what has been fixed in the newest bios.
So being somebody who never got BSOD, and now I get them about once every 2 weeks and cannot get it to repeat because it is random at windows xp startup I am out of ideas.
Any help or insight appreciated. Thanks in advance!!I had a similar issue with a 32bit system that popped like that with a BSOD but I know something fried because of the burning smell. It worked fine after that and had the same issue...random BSOD's. I thought I inspected the board closely the first time and even when I decided to swap boards, the problem continued.
I kept the original board as I figured it was probably ok and would eventally use it. Well, it came time where I had the opportunity to use it and lo and behold, I found a burn mark hidden under a PCI slot. Needless to say, I had it replaced under warranty.
Now I tested my RAM several times with Memtest86 and recieved no errors, so I continued on until I recieved the board in my sig. I got new RAM for this rig and took my Abit AN7 and PC2700 RAM and assembled another PC for my son. Once I got up and running, I decided to do further in depth testing. I discovered I was able to get errors with certain timings during one spcific test pass. All others passed with various timings except 2 2 2 11 which I knw would pass on all similar systems. I had the RAM replaced under warranty and when I recieved the new modules 2 days later, it passed all my tests with flying colors. BSODS are now a thing of the past and that PC is a model of stability, I almost wish I kept it as I miss the nvidia onboard sound.
The moral here is that one simple test doesn't always reveal a problem, it's a great tool, but it's not a definitive catch all.
Just something to consider...
There may also be a driver or IRQ issue as well.
Post your IRQ's from System Information like this:
Heres mine
IRQ 0 System timer OK
IRQ 1 Standard 101/102-Key or Microsoft Natural PS/2 Keyboard OK
IRQ 4 Communications Port (COM1) OK
IRQ 5 WinFast TV2000 XP WDM Audio Capture OK
IRQ 6 Standard floppy disk controller OK
IRQ 8 System CMOS/real time clock OK
IRQ 9 Microsoft ACPI-Compliant System OK
IRQ 11 NVIDIA nForce PCI System Management OK
IRQ 12 PS/2 Compatible Mouse OK
IRQ 13 Numeric data processor OK
IRQ 14 NVIDIA nForce3 250 Parallel ATA Controller (v2.6) OK
IRQ 15 NVIDIA nForce3 250 Parallel ATA Controller (v2.6) OK
IRQ 16 RADEON X800 XT Platinum Edition OK
IRQ 17 WinFast TV2000 XP WDM Video Capture OK
IRQ 20 Standard OpenHCD USB Host Controller OK
IRQ 21 Standard Enhanced PCI to USB Host Controller OK
IRQ 22 NVIDIA Network Bus Enumerator OK
IRQ 23 Standard OpenHCD USB Host Controller OK
IRQ 23 NVIDIA(R) nForce(TM) MCP Audio Processing Unit OK
The last two are normal as I've forced nVidia's sound drivers and Sound Control Panel so your's probably wont look the same. I don't recommend doing this, it was only an experiment and a crappy one at best.
Maybe you are looking for
-
IPad no longer recognized by any computer after 4.2.1 update
Hi, my iPad is no longer recognized by any computer after the 4.2.1 update. It does not show up in iTunes and this even in recovery mode. When connected to charger it does not show that it would charge (but it does). The iPad is still usable except i
-
Can I use WinXP Home serial number using WinXP Pro install disc
Hello everyone, I am going to downgrade from Vista to XP (my DELL machine was originally XP Home) but I don't have my old XP install files anymore. I did do have a Windows XP Professional SP3 install disc. My question is: Would I be able to use my
-
MATERIAL_MAINTAIN_DARK
Hi folks, I am using this Funtion module MATERIAL_MAINTAIN_DARK. But i am getting a error of No description transferred. Can any body give me sample code that uses this Function module.
-
Need Help Adding Network Printer
I am trying to add a network printer on a Solaris (Sun OS 5.6) system. I am doing this using lpadmin as outlined in volume 2 of the system admin guide. The printer appears on the system, but when I try sending a print job, I get the message 'Segmenta
-
I tried to created radio button dynamically through loop. But for the values and labels- i am not able to assign values dynamically. Is there any other way by which i can dynamically create radio buttons inside a loop and assign them values & labels?