Multiplier change in K7N2 delta2

Need a little help here.
i'm using Sempron 2600+ oc at 11x200.
question.
1: can i change (lower the multiplier) on sempron processor? coz whenever i tried to lower the multiplier, my pc won't boot at all. need to reset it to safe mode first, then it will boot again.
anybody?
thanks in advance....
cozack

The processor is locked and therfore you cannot change the multi...
11x200=2200 thats a good oc already..

Similar Messages

Problems errors ram with cpu vcore change on k7n2 delta2 platinum

hello
i'm a french new owner of k7n2 delta2 platinum and i got something strange.
I have 2*512 PC3200 cas3 of kingston value ram with voltage 1.75 instead of 1.6v running in dual CAS 2.5/3/3/8 at FSB 195 like the cpu : 2500xp barton.
With occt and memtest86+ i'm stable with a CPU vcore at 1.725.After 195 the computer starts but not really stable. So i put the cpu vcore at 1.75 to put higher fsb and then i get thousands RAM errors with memtest. i tried with cas 3/3/3/11 and it was worst. On the bios B6 i tried with different settings : agressive, optimal, 1/1, auto, manual, patch ddr or not...and always the same. My PSU is 450w and i've 4 HD 1player 1 burner.
Of course i'm happy to reach 195 but i feel disapointed to be stop with this problem of vcore/ram

Quote from: osnavi on 23-September-05, 11:36:11
"...So i put the cpu vcore at 1.75 to put higher fsb and then i get thousands RAM errors with memtest..." I would say it's not the v. core but the CPU o/c. that gives that errors, as it make not sence to increase v.core only for itself.
Oh yes it does
The CPU and memory work hand-in-hand. If one is out of sync it can cause the other to start spitting out errors.
You are overclocking and that more of a scientific art, not an exact science.
Components react differently to an entire list of variables, especially the CPU/memory.
What you are trying to do requires trail and error testing however I agree the Kingston memory is holding you back at this point with the clock you are pushing
I would go for the most stable FSB settings that allow Dynamic Overclock to be enabled to SERGEANT before I would go for ultra High FSB because you will peak the system at its highest performance curve when you need the boost, and I would bet money that peak would be higher than any strait FSB over-clock you can hit stable.
Psychologically allot of people think their systems are not running the highest performance it can unless they set the system up at the highest FSB/multiplier and that is simply not true with dynamic overclocking enabled and correctly tuned with the rest of the components.

[AMD] problems errors ram with cpu vcore change on k7n2 delta2 platinum

hello
i'm a french new owner of k7n2 delta2 platinum and i got something strange.
I have 2*512 PC3200 cas3 of kingston value ram with voltage 1.75 instead of 1.6v running in dual CAS 2.5/3/3/8 at FSB 195 like the cpu : 2500xp barton.
With occt and memtest86+ i'm stable with a CPU vcore at 1.725.After 195 the computer starts but not really stable. So i put the cpu vcore at 1.75 to put higher fsb and then i get thousands RAM errors with memtest(even if i stay fsb 195). i tried with cas 3/3/3/11 and it was worst. On the bios B5 i tried with different settings : agressive, optimal, 1/1, auto, manual, patch ddr or not...and always the same. My PSU is 450w noname and i've 4 HD 1player 1 burner & a geforce 5200 o/c 10%.
Of course i'm happy to reach 195 but i feel disapointed to be stop with this problem of vcore/ram because i have not problem of temperature with a silent boost for cpu(52°c maxi), 3 fans for the box(35°c maxi) and copper memory heat spreaders for ram.
thanks for your answer

the thing to check is the vdimm voltage for the ram ... i'm pretty sure it should be around 2.6 volts .. try upping it one step
vcore is the voltage to the cpu and doesn't affect the ram

[nForce] has somebody MSI K7N2 Delta2-FSR + barton mobile

I wanted to know if there is a possibility of changing cpu ratio because msi kt4av did't see this cpu as mobile. on epox 8rda3+,8rda3+pro, and abit everything is ok. Has there somebody such mainboard with this cpu? Does mainboard seethis cpu correctly? And does somebody know if how to change the cpu ratio in barton mobile's bios.i wanna buy MSI K7N2 Delta2-FSR

Frequency/Voltage Control in BIOS
"CPU FSB Clock"
"CPU Ratio" (multiplier)
that is from KT4AV manual
mobile CPUs aren't properly identified on most boards, but that is merely a "cosmetic touch"

@Klondike K7N2 Delta2 Platinum, new owner.

Hi.
I am kinda old but maybe not as old as you . Experience before...
Much regard to your efforts for writing some exhaustive information on the MSI K7N2 Delta2 Platinum. I think I would be more than completely lost without your help http://www.nforcershq.com/forum/here-vp624299.html#624299. Now at least my system is running.
I have some specific points, and please forgive me if I'm asking something you may have answered. Got kids running around, that kind of thing. Have to run out and pick up milk in a minute, life is busy, you get it... sure? Any links are helpful too.
The existing server had an XP software raid (hack some dm* files a bit, there is a toms hardware article on it here http://www.tomshardware.com/reviews/windowsxp-make-raid-5-happen,925-2.html on a Shuttle AN35 Ultra 400 and a Barton Athlon XP 2600+ 0343.
But it's a barebones board so I thought I would 'Upgrade' the file server with an 'everything' board. Enter the K7N2 Delta2 Platinum. Enter also a 0310 2500+ which I patched the mobile jumper for fun and cut all of L6. The NFORCE2 seems to ignore these settings, and swapping in the 2600+ completely stock doesn't seem to change anything below:
Questions I have which I have not got answered yet (and running 1/20/2005 bios the board came with): I can't adjust the vCore! I can only set it in the bios but not in Windows, where I have 8rdavcore - this dynamically lowered my FSB and vcore when the system was idle. 8rdavcore lists the board but there is no driver in the drop-down: this is not the giveio.sys driver mentioned on the home page, it is a driver to interface with the vcore and other settings on the board.
With your recommendations klondike the system at least boots reliably. Already I am disappointed in the MSI versus the Shuttle for this reason alone, no vcore and the settings seem really picky in the MSI Bios. The shuttle though had a periodic problem with crashes which I never figured out. LC 6420GP 80plus PS, ATI 9250 AGP, Team Value memory (identical in timing to the Value memory in your post Klondike), 3ware 9500S-8 hardware raid, NEC USB 5 port USB card and a 3com 10/100, all moved to the new system, with the 3ware newly introduced replacing the software raid. Removes the annoying rebuild when the system crashes out, prevents major disk data glitches.
I want this system to dynamically underclock, but as yet, I cannot adjust the vcore down. For example, Corecenter, or nTune, has the field for vcore and other values, but except for FSB, they are locked, and 8rdavcore log shows it cannot load the driver. The Shuttle went to under 100 fsb with a low voltage dynamically, I think vcore 1.25 with the Athlon XP Barton 2600+, and run super-cool and use about 75 watts of power vs 110w.
Any ideas?

Came back to the machine, swapped back in the Athlon XP Barton 2600+, took a look in the BIOS (don't know if I changed anything, probably), and now the vCore is greyed out again in 8rdavcore. "No ATXP1 found."
Edit: I used the CMOS jumper to reset settings several times to no effect.
Sorry I did not get the log when it was working. I will next time! I assume where it says "not responding" has something to do with the problem.
Here is the log from 8rdavcore:
Code: [Select]
00/24 16:36:50 | ===============================================
00/24 16:36:50 | 8RDAVCORE: Version 8rdavcore 0.8.8-dev8
00/24 16:36:50 | 8RDAVCORE: Windows NT/2000/XP detected
00/24 16:36:50 | giveio: Opened Service-manager successfully
00/24 16:36:50 | giveio: Service giveio exists
00/24 16:36:50 | giveio: Service giveio is running
00/24 16:36:50 | board: Found section General
00/24 16:36:50 | board: Found section Abit KT7A
00/24 16:36:50 | board: Found section Abit NF7
00/24 16:36:50 | board: Found section Acorp NFU400N
00/24 16:36:50 | board: Found section Aopen AK79D-400VN
00/24 16:36:50 | board: Found section Asus A7N8X-E
00/24 16:36:50 | board: Found section Asus A7N8X v2.0 Deluxe
00/24 16:36:50 | board: Found section Chaintech CT-7NJL1/CT-7NJS
00/24 16:36:50 | board: Found section DFI Infinity NFII Ultra
00/24 16:36:50 | board: Found section DFI Lanparty NFII Ultra
00/24 16:36:50 | board: Found section Epox EP-8RDA+ Rev. 1.x
00/24 16:36:50 | board: Found section Epox EP-8RDA+ Rev. 2.x
00/24 16:36:50 | board: Found section Epox EP-8RDA(3,6,+,I,E)
00/24 16:36:50 | board: Found section Gigabyte GA-7N400 Pro
00/24 16:36:50 | board: Found section Gigabyte GA-7NNXP
00/24 16:36:50 | board: Found section Jetway N2PA
00/24 16:36:50 | board: Found section Leadtek K7NCR-18D
00/24 16:36:50 | board: Found section MSI K7N2 Delta L
00/24 16:36:50 | board: Found section Shuttle AN35N Ultra V1.1
00/24 16:36:50 | board: Found section Shuttle SN45G
00/24 16:36:50 | board: Found section Soltek 75FRN(2)-L
00/24 16:36:50 | board: Found section Soltek NV400-L64
00/24 16:36:50 | SMI: Got IO base 0x4400
00/24 16:36:50 | SMI: Back-to-back writes disabled.
00/24 16:36:50 | smi: Function code not set, forcing to 0x88
00/24 16:36:50 | SMI: Not responding.
00/24 16:36:50 | 8RDAVCORE: Using board MSI K7N2 Delta L
00/24 16:36:50 | nforce2_smbus: 1.1: 0x8410de
00/24 16:36:50 | nforce2_smbus: Address of bus 0 is 0x5000
00/24 16:36:50 | nforce2_smbus: Address of bus 1 is 0x5100
00/24 16:36:50 | 8rdavcore: Init SMBUS drivers done
00/24 16:36:50 | atxp1: Searching on NFORCE2_SMBUS:NFORCE2_SMBUS0
00/24 16:36:50 | atxp1: Searching on NFORCE2_SMBUS:NFORCE2_SMBUS1
00/24 16:36:51 | atxp1: No ATXP1 found
00/24 16:36:51 | SMI: Not responding.
00/24 16:36:51 | SMI: Not responding.
00/24 16:36:51 | SMI: Not responding.
00/24 16:36:51 | SMI: Not responding.
00/24 16:36:51 | SMI: Not responding.
00/24 16:36:51 | 8rdavcore: Init voltage drivers done
00/24 16:36:51 | nforce2-pci: Revision c1
00/24 16:36:51 | 8rdavcore: Init chipset drivers done
00/24 16:36:51 | WINBOND: Found a W83627THF
00/24 16:36:51 | ite: ITE8712F found
00/24 16:36:51 | ITE: 16-bit fan counter 0x3c
00/24 16:36:51 | SMI: Not responding.
00/24 16:36:51 | SMI: Not responding.
00/24 16:36:51 | SMI: Not responding.
00/24 16:36:51 | SMI: Not responding.
00/24 16:36:51 | SMI: Not responding.
00/24 16:36:51 | SMI: Not responding.
00/24 16:36:51 | SMI: Not responding.
00/24 16:36:51 | lm90: Searching on NFORCE2_SMBUS:NFORCE2_SMBUS0
00/24 16:36:51 | lm90: Searching on NFORCE2_SMBUS:NFORCE2_SMBUS1
00/24 16:36:51 | lm90: No LM90 found
00/24 16:36:51 | 8rdavcore: Init sensor drivers done
00/24 16:36:51 | smart: Physical drive 0 opened
00/24 16:36:51 | smart: SMART enabled on drive 0
00/24 16:36:51 | smart: Physical drive 1 opened
00/24 16:36:51 | smart: SMART_GET_VERSION failed
00/24 16:36:51 | smart: Physical drive 2 opened
00/24 16:36:51 | smart: SMART_GET_VERSION failed
00/24 16:36:51 | smart: Physical drive 3 opened
00/24 16:36:51 | smart: SMART_GET_VERSION failed
00/24 16:36:51 | smart: IDE drive 0
00/24 16:36:51 | smart: Model: ST3750640AS
00/24 16:36:51 | smart: Firmware: 3.AAE
00/24 16:36:51 | smart: Serial: 3QD14TMH
00/24 16:36:51 | smart: Buffer: 16777216 Byte
00/24 16:36:51 | smart: Available attributes (F=Pre-Failure, O=On-Line, P=Performance, E=Error-rate, C=Event-Count, S=Self-Preserving):
00/24 16:36:51 | smart: ID Name Value Worst Threshold Raw Flags
00/24 16:36:51 | smart: 1 Raw Read Error Rate 117 91 6 158 FOPE
00/24 16:36:51 | smart: 3 Spin Up Time 94 93 0 0 FO
00/24 16:36:51 | smart: 4 Start Stop Count 100 100 20 102 O CS
00/24 16:36:51 | smart: 5 Reallocated Sector Count 100 100 36 0 FO CS
00/24 16:36:51 | smart: 7 Seek Error Rate 72 60 30 153 FOPE
00/24 16:36:51 | smart: 9 Power on time 100 100 0 195 O CS
00/24 16:36:51 | smart: 10 Spin Retry Count 100 100 97 0 FO C
00/24 16:36:51 | smart: 12 Power Cycle Count 100 100 20 106 O CS
00/24 16:36:51 | smart: 187 Unknown 100 100 0 0 O CS
00/24 16:36:51 | smart: 189 Unknown 100 100 0 0 O ECS
00/24 16:36:51 | smart: 190 Unknown 63 54 45 37 O S
00/24 16:36:51 | smart: 194 Temperature 37 46 0 37 O S
00/24 16:36:51 | smart: 195 Hardware ECC Recovered 81 61 0 207 O EC
00/24 16:36:51 | smart: 197 Current Pending Sector 100 100 0 0 O C
00/24 16:36:51 | smart: 198 Offline Uncorrectable 100 100 0 0 C
00/24 16:36:51 | smart: 199 UDMA CRC Error Count 200 200 0 3 OPECS
00/24 16:36:51 | smart: 200 Write Error Count 100 253 0 0
00/24 16:36:51 | smart: 202 Unknown 100 253 0 0 O CS
00/24 16:36:51 | 8rdavcore: Init SMART drivers done
00/24 16:36:51 | pnp: Detected W83627THF
00/24 16:36:51 | pnp: Registers are unlocked
00/24 16:36:51 | pnp: GPIO config: 0x40, 0x40, 0x00, 0x00, 0x00
00/24 16:36:51 | pnp: LD7: CR30=0x0f, 0xf0, 0xff, 0x0b, 0xff, 0xff, 0x00
00/24 16:36:51 | pnp: LD8: CR30=0x01, 0xff, 0x5e, 0x00
00/24 16:36:51 | pnp: LD9: CR30=0x00, 0xff, 0xff, 0xff
00/24 16:36:51 | cpuload: thread created, id: 208, update: 5000
00/24 16:36:51 | autofsb: autofsb_load(): Added AutoFSB1
00/24 16:36:51 | autofsb: autofsb_load(): Added AutoFSB1.2
00/24 16:36:51 | 8rdavcore: Chipset reported multiplier: 115
00/24 16:36:52 | 8rdavcore: Calculated multiplier: 114
00/24 16:36:52 | 8rdavcore: init_values done
00/24 16:36:54 | 8rdavcore: Using driver
00/24 16:36:54 | control: control_set_val(): POSSIBLE BUG: Got a NULL pointer
00/24 16:36:54 | 8rdavcore: Init control startup values done
00/24 16:36:54 | 8rdavcore: Create sensor list done
00/24 16:36:54 | 8rdavcore: Create preset list done
00/24 16:36:54 | 8rdavcore: Create AutoFSB list done
00/24 16:36:54 | 8rdavcore: Create trigger list done
00/24 16:36:54 | 8rdavcore: Create sensor field done
00/24 16:36:54 | 8rdavcore: No primary VCore control!
00/24 16:36:54 | 8rdavcore: Create voltage list done
00/24 16:36:55 | 8rdavcore: Create SMART list done
00/24 16:36:55 | 8rdavcore: AutoFSB disabled
00/24 16:36:59 | control: control_get_val(): POSSIBLE BUG: Got a NULL pointer
00/24 16:36:59 | 8rdavcore: Saved Main vars
00/24 16:36:59 | 8rdavcore: Saved sensor settings
00/24 16:37:00 | 8rdavcore: Saved presets
00/24 16:37:00 | 8rdavcore: Saved autofsb settings
00/24 16:37:01 | 8rdavcore: Saved log settings
00/24 16:37:01 | 8rdavcore: Freeing lists...
00/24 16:37:01 | Done.

K7N2 Delta2-FSR Won't Boot

Hi everyone,
I was in my bios cell settings and I believe I accidently changed my FSB setting from 166 to 200 with my multiplier set at 12.
My motherboard is a K7N2 Delta2-FSR (601-6570e-020) with a AMD Sempron 2800 and 2x512mb RAM. The system was totally fine before hand and now it won't boot at all. I can switch on the system and all the drives power up but my screen stays black with the amber light on and no post beeping. I have tried removing all my memory modules and when i boot with no memory, i get the long continuous beeps which signal "No Memory Present". When i install 1 module it doesn't post and doesn't beep at all.
I have tried unplugging my power cable from the PSU and tried resetting the clear CMOS Jumper to pins 2-3 for 15-30 seconds and then returning the jumper to pins 1-2. I have then plugged the power cable back into my PSU and then powered on the system but still i get the black screen. I have read on these forums about a "Safe Mode" jumper known as "J10" but my motherboard doesn't have this jumper. It only has the JBAT1 jumper.
Are their any other methods to reset my FSB to default or to reset the bios safely?
Will be grateful & appreciative for any help given,
Many thanks

Quote from: couttsey21 on 20-September-06, 07:43:58
All my fans are spinning, unfortauntely my motherboard didn't come with a D-Bracket so I can't test it out using that.
Any other suggestions?
well you can try without D-bracket also, just wait 5-6 seconds to ensure no boot or boot. ------> https://forum-en.msi.com/index.php?topic=96529.msg697033#msg697033

K7N2 delta2 soun

hi. i tried to search for some help but i couldnt find anything what should help me. i bought K7N2 delta2 board with integrated audio card (just 3 connectors-in, out, mic). Problem is, that winamp says "no sound device found" and then some infos (i have czech winows and i cant translate it to english; but its something that was used device, which is "out of range"-dunno if its correctly translated).
first i installed sound drivers from cd. when it wasnt working, i installed msi live and i updated chipset and sound driver. nothing changed. then i decided to browse this forums an somebody said to user with same problem that he should install original sound drivers from realtek. in installed them, but i still get error msg. dunno what to do. i dont want to buy another sound card.
i have in my bios settings listed realtek [auto]. there are only options auto or disabled.
.thanks

wow, this will be hard...
(ISA) 0 System timing (my own translation to english :(
(ISA) 1 Keyboard
(ISA) 3 COM2
(ISA) 4 COM1
(ISA) 6 disc driver (controller)?
(ISA) 8 system clocks + cmos
(ISA) 12 mouse
(ISA) 13 numeric processor (koprocessor?)
(PCI) 5 Radeon 9600
(PCI) 5 Standard openhcb usb host controller
(PCI) 9 mutimedial sound adapter
(PCI) 9 nvidia nforce pci system management
(PCI) 10 nvidia network bus enumerator
(PCI) 10 hots controller from pci to usb ??
(PCI) 11 pci standard 2way controller for ide
(PCI) 11 stanard openhcb usb host controller
sorry for the translation, but i have czech version of win xp

How to boot from SATA on a K7N2 Delta2 Platinum

Hi guys,
here is my problem, I've just bought a brand new HD Samsung SATA II 2504C, once connected to the MB I can' t boot from it, even if I change the boot sequence.
I have already two HDs connected to IDE ports, under XP I can format it, I can even install a Linus distro such as Elive, but it refuses to boot.
Is there a trick?
K7N2 Delta2 Platinum
BIOS: B5 1/20/2005
AMD 3000+
2 HDs UMDA 133
2 DVD writer LG and SAMSUNG
1 HD on SATA, which causes me troubles.

disable IDE RAID and ensure SATA is enabled in BIOS
disconnect any other IDE HDDs before you install Windows to your SATA drive; they can be reconnected again afterwards.
make sure that the SATA drive is listed first in 'Hard Disk Priority' under 'Boot Order' in BIOS

[nForce] K7N2 Delta2 Platinum w/Version B.5 BIOS, trouble with post and XP install.

I have
K7N2 Delta2 Platinum
MS-6570E Version 1.0 motherboard
AMD Sempron 2600+
Elixir 500MB PC-3200 DDR (3 sticks, total 1.5GB)
eVga Nvidia MX4000 64MB AGP card
Maxtor ATA-100 PCI controller
I pulled everything else out of the box. I've tried the B.3, B.4, and B.5 BIOS and set everything to Optimized Defaults. I created a striped RAID Array of 4 WD 80GB drives on the primary and secondary onboard controller. The CD is on the Maxtor controller.
There are some problems I can't figure out.
1) The mobo identifies the CPU as Athlon XP 1100
2) The POST hangs just before seeking the IDE drives. I have to hit a key for it to continue.
3) The LED's on the D bracket have the top right light dark until the key is hit. Something to do with initializing the floppy controller.
4) The XP install fails to a blue screen just after hitting the F8 key to accept the license. The code is 0x0000007B.
Can someone tell me what these issues have to do with each other and how I can correct them?

Quote from: dmichael34 on 17-September-05, 22:42:56
The Maxtor controller was removed when you originally suggested to do so. The add on controller is an SIL 680 RAID.
I will try reseating the processor next.
I can also attempt a boot through POST without the array, as this shouldn't affect the boot process.
I did notice that the ctrl-alt-del on the LEFT side of the keyboard doesn't work.
However, the ctrl-alt-del on the RIGHT side of the keyboard does work.
Maybe I've been looking for a serious problem and overlooking the obvious.
I do not see how the CPU temp would cause a pause at boot until "any key" is hit... it sounds more to me like the system has paused to either look for a device or boot a BIOS on a device card.
If I am not mistaken, you are using a RAID card to boot windows? Is this correct?
If that is true it is possible the boot sequence is not set correctly in the BIOS such as "BOOT OTHER DEVICE" ( I cannot remember the exact term in the BIOS)
I am not sure about that but you could try changing the boot sequence so your RAID card is above "HARD DISK" on the list

RAID1 issues on K7N2 Delta2-LSR

I originally started down the road of trying to setup a RAID0 with two new WD Raptors and discovered one was bad - WinXP Pro install fails on SATA RAID K7N2 Delta2-LSR
So I continued on with installing WinXP on the remaining Raptor and figured I could setup a RAID1 array when the replacement Raptor arrived. Today, I popped in the replacement Raptor on the SATA2 controller, booted into WinXP, and confirmed the new drive was recognized. I could see the new drive in Disk Management and all looked good.
I rebooted into bios, enabled the RAID Config on SATA Primary and SATA Secondary, saved and exited. Upon reboot, I was able to go into the nVidia RAID setup (F10).
The NVIDIA RAID UTILITY - Array List showed one Mirror 74G array with a Status of Degraded. I hit [Enter] Detail and [A] Add to add the new hard drive to the array. Then I selected [R] Rebuild which didn't seem to do anything (no HD activity), but the Array List reported the array Status as Healthy. I never went through the process of defining a new array where drives are added from the left to the right side of the Define New Array screen since the Array List initially showed one Mirror 74G array, which is what I wanted.
I exited [Ctrl-X] Exit and the array failed to boot. The NVIDIA BIOS section "Detecting array..." failed to detect the array. Rebooting confirmed the same.
To make matters worse, I couldn't get into Bios (Delete) or the NVIDIA Setup (F10). I had to unplug the second Raptor to get into the Bios, upon which I disabled the RAID Config. My original Raptor remains intact with WinXP.
I would have figured that a mirrored array could be created on the fly from a master hard drive - is this not the case?
How do I go about fixing this problem since now I cannot connect the second Raptor and get into Bios/NVIDIA Setup? Does the BIOS need to be reset?
Again, any help would be greatly appreciated!

I initially thought a change in direction of the topic belonged in a new thread, but I see the value in keeping it all together. I'll keep everything from this point out in the 3rd thread.
1st thread - WinXP Pro install fails on SATA RAID K7N2 Delta2-LSR - due to bad HD
2nd thread - RAID1 issues on K7N2 Delta2-LSR - this thread
3rd thread - Bad K7N2 Delta2-LSR?

K7N2 Delta2-LSR doesn't POST

Hi there, sorry before if anyone had asked this question before,
I have a system
K7N2 Delta2-LSR
Sempron 2600+
Adata Vitesta 2x256Mb
Winfast A250LE TD Ti4200
PATA hard drive...
i just tried to oc this system,
before : Sempron 2600+ @1833MHz, fsb 166, ram timing auto, vcore default 1.5V
1st trial : FSB 185, ram timing auto, vcore 1.55V, POST success, but i didn't boot to OS, entering setup again, wanna try higher FSB
2nd trial : at FSB 188, ram timing auto (i only changed FSB and vcore), vcore still 1.55V, my system didn't POST...
I tried to clear cmos, by moved the jumper, but it still didn't POST. Anybody help me pliz, what problem did i face?
Thank's

Quote from: HenryW on 11-August-07, 00:27:10
Do you have the manual that came with the motherboard? What kind of RAM do you have ( PC2700-333Mhz or PC3200-400Mhz)? If you are going to be increasing FSB you should have PC3200.
You will need to set the jumper on J10 to pins 2-3 (safe mode) restart PC and reset BIOS to default settings. Next turn off PC & set J10 jumper back to pins 1-2.
Before attempting to overclock again come back here for advice.
Yup, i have ram, DDR 500, but i run it at fsb 166.
what i tried is FSB at 190 Vcore 1.7V (default 1.6V) ram timing 2-3-3-7 T1
but the cpu temp is 52C (on bios)... is this normal? i only use the stock cooling HSF...
at FSB 166, temp is 47C. But i touch the HSF, not so hot like that temp, is the sensor wrong?
Anyway, on the socket A, there is an electric ribbon (sorry, i don't know the name...i name it my self ), is that the sensor for the cpu temp?
"J10" is nothing on my MoBo, i use "insert" while pressing power button, it worked just the same like "J10" works...

K7N2 Delta2-LSR LAN not detecting

I just purchased a K7N2 Delta2-LSR with a AMD 2600 Processor. I am building my own system from the ground up basically and I have put Win XP Pro on to it. I went to do a windows update and can not connect to the internet through the ethernet card on the Motherboard. I tried to use my installation disk that was provided by my ISP but it can not detect a network adaptor. I am trying NOT to install too much on the system as I still need to do a windows update and put SP2 on the system as well. Any help on what I need to put on from the MSI disk or what to change to get this to work would be much appreciated. Thank you.

first like Wonkanoby said make sure you have the drivers installed.
then from your start menu choose run and type in cmd. when it opens type in ipconfig and see what it says. if it doesnt match your isp's info and what your ip address should be you need to reset your modem to refresh your isp's info.
turn off your pc, unplug your modem(from the electrical out let so it can reset its self, not from the PC). leave it for 60 seconds, plug it back in and wait for it to become fully active. then restart your pc. once in windows run cmd again and ipconfig and the info should be correct and you should be connected to the net.

MSI K7N2 Delta2 Platinum + Corsair mem = hell

Alright, Last christmas I got an MSI K7N2 Delta2 Platinum Mobo. I had an AMD Athlon XP 3000+
w/333mhz FSB. I was using cheapo generic ram which worked, but had horrible performance.
So I bought the TWINX1024-3200XL, Corsair 1GB(2x512) PC3200 400mhz DDR-Ram.
So........when I set that up, I got HUGE instability problems. While playing Half-Life 2, the game
would randomly go BSOD, which I didn't get with the cheapo ram. So I went into the options and
I changed the bios settings from By SPD (which set it to 200mhz fsb) to Auto (which changed it
to 166mhz after detecting my 166mhz fsb cpu), at which point the instability ended. But every
time I tried to run it at 400mhz, tons of crashing and BSODs in HL2 as well as windows. So I've
been using it at 333mhz for the past 6 or so months without any problems, aside from the fact
that I can't run my $300 ram at stock speed.
After reading some threads here and at other forums, I learned that apparently my
motherboard doesn't allow the cpu/ram to run async. Which would make some degree of
sense, since when they ran sync, both at 333mhz, I encountered no crashing. However, I just
bought an AMD Athlon XP 3200+ w/400mhz fsb and I was hoping that the problems would be
over. Alas, no. With the bios set to By SPD at 400mhz, Half-Life 2 (which is what I use to test
system stability, since Memtest 86, Prime 95, etc. All ran through all the tests and for over 24
hours without a single error, then the second I play HL2, it crashes) crashes within 1 minute. So
I angrily restart and change the bios settings, this time I set it to Auto, which is also 400mhz now due to the 400mhz fsb CPU. I was actually able to play Half-Life 2 flawlessly for about 45 minutes, I made it past the driving phase on the buggy, shot down the chopper, then I eliminated all resistance near the crane. Unfortunately, once everything was dead silent and I pressed R to reload, BSOD. >=|
Is my motherboard a piece of crap that doesn't support the ram, or is the ram bad? Has anybody else been able to run these two (MSI K7N2 Delta2 Platinum + Corsair PC3200 Performance Ram) together with perfect stability? Please help! I'm going nuts. =*|
Many Thanks!
~Takeda
--System Specs--
Windows XP Professional SP1
Antec SX1040B2 File Server Case
550watt Antec TrueControl PSU
MSI K7N2 Delta2 Platinum
AMD Athlon XP 3200+/400mhz FSB (2.2GHz)
Thermaltake Volcano 12
1GB(2x512) Corsair Twinx1024XL Dual Channel
ATI All-In-Wonder 9800 Pro
Sound Blaster Audigy 2ZS Platinum
Pioneer 10x DVD Drive
Sony DRU-700A
Western Digital 120.0GB 7200RPM HD ATA/100
Western Digital 120.0GB 7200RPM HD ATA/100
nForce Ethernet Adapter w/Cable line
Logitech MX500 Optical Mouse
Logitech Elite Keyboard
19" Envision Monitor EN985e
Logitech Z-680 5.1 Speakers

well, for the errors. In half-life 2, after however much playtime, the screen will just randomly go blue, without any official windows message or error code, forcing me to manually restart with the reset button. It's done this for the most part. Other times, when I change the settings, the game will just boot me back to the desktop, giving me a visual basic runtime error. Oddly enough, when I set the ram to 166mhz fsb, the game is totally stable. I've also just updated to the newest bios 11.50 and tried all of the previous settings as well as the "optimized defaults" and "fail-safe defaults" all still result in the crashing.
Yeah, I've tested other games. The results were mixed though. certain games like Need For Speed Hot Pursuit 2 would lockup, other games like command and conquer generals seemed to mostly be stable, with a few random crashes. The problem is that I haven't really gotten any true BSODs in games, I just get lockups. However, windows would give BSODs, but they seemed like they were driven by faulty hardware, since it would be random and would go away entirely once I underclocked the ram.
Other times in the past when I've run the ram at 200mhz fsb, windows would randomly crash when I was browsing the web. In those cases it would give me a stop message and an error number. But I haven't gotten then so far today. I can't remember what all the errors were, but there were about 2-3 random crashes related to ntfs.sys and other system files. So at first, I thought maybe it was just a windows problem, but I had just freshly formatted and reinstalled windows, so it seemed unlikely. And of course, the second I changed it back to 166mhz fsb, I was able to keep my computer on for a week, playing half-life 2, doom 3, command and conquer generals, as well as tons of other games and general web browsing without a single incident. So the problem, although highly vague, seems to be related directly to the ram, if just by the fsb change.
I dunno, these are really really odd problems, never encountered these before in like 6 years of tweaking my comps, so I'm guessing that it's either just an incompatibility with my motherboard/ram (in which case I'm screwed), my mobo is broken, or my ram is broken. I think my only real option left, now that I've bought a new $130 cpu to match the ram is to RMA the ram and hope that it somehow works. But the fact that it's been able to pass prime95 and memtest86 flawlessly makes me concerned as to whether or not corsair will be able to diagnose a problem, if there is one, with the ram if I do RMA it. sigh.
I'm not sure if my video card is underpowered, since I have a 550watt psu and the radeon 9800 isn't too much of a hog. But I think I may RMA that as well. damn, I dunno.
*update*
Correction, it seems that now I have a 200mhz fsb cpu, setting the ram to 6:5 for 166mhz causes windows to almost immediately lock up. I'm guessing that's part of the whole unable to run the cpu/ram async thing.
Also, when I tried changing the latency to 2.5 and 3.0, I got the following error:
Many thanks!
~Takeda

K7N2 Delta2-LSR Fsb issues

Hello everyone, I have a 2700+ xp 333fsb @ 2.158ghz (fsb 166 x 13)
Running on a K7N2 Delta2-LSR. Preparing for a lanparty I decided to try and do a small OC, so i decided to Oc it to 200fsb x 11 (2.200 ghz) I saved and rebooted and now it will not post. I have tried all known methods of clearing the CMos, including removing the battery and clearing the cmos, waiting in times between that, unplugging and doing all that, but nothing worked. After reading other posts it seems this problem can be fixed by shorting the j10 or j11 jumper, neither of those jumpers is on my Mobo, if there is another way to reset the fsb, please help me!!
ps. All other hardware that is non essential has been removed, and all the hardware was working before, i made no hardware changes before the OC attempt. Please help before i leave for lan party! (Friday aug 6, at 6:00)
(Edit), yeah setting the fsb past 166 went over the 333 limit for my 2700+ xp. So how can i reset this?

Quote
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.
Copied from one of the stickies.

New K7N2 Delta2 Platinum crashes with new memory

I recently bought a new K7N2 Delta2 Platinum motherboard and 2 x 512MB DDR400 OCZ memory, and now my machine continually crashes.
I've tested the memory sticks individually using memtest, and there are no problems with the memory. However, when I was in touch with OCZ support, they mentioned that there is apparently a problem with the nForce2 chipset being able to handle new 2 x 512MB memory. I had my motherboard working successfully with old DDR400 memory (BH5-based), which I sold when I bought the new memory. I was pointed to this site by OCZ support:
http://www.bleedinedge.com/forum/showpost.php?p=30004&postcount=7
Is this the case?
If so, I'm surprised to see that MSI (or any manufacturer with nForce2 chipsets) can claim up to 3GB support. Comments?
Apparently, one thing to try is 2T command rate, but I can't find where to set it in my BIOS. I heard that it's probably set to 1T by default on my board.
Can anyone suggest any other options?
I'm somewhat frustrated that I've bought a new board and pretty expensive memory, and now have an unstable system. It's also too late to return to the reseller.
Any help would be appreciated!
Thanks.
Stuart.

Quote
I've tested the memory sticks individually using memtest, and there are no problems with the memory
Did you also test them together? If not, do so. Then up voltage as suggested.
Do you have them in dual channel, i.e one green slot and one purple slot?
Quote
Apparently, one thing to try is 2T command rate, but I can't find where to set it in my BIOS. I heard that it's probably set to 1T by default on my board.
That is correct; it is set up for 1T and can not be changed.
Not true that nforce2 chipset has problems running 2x512MB but it is notoriously picky. Your board tends to under-volt the memory too so you may be OK after increasing the voltage.
You don't say what bios you are using but bosskiller's modded bios b.72c has produced good results and addresses memory issues.
Read < here >

Multiplier change in K7N2 delta2

Similar Messages

Maybe you are looking for