K7T266 PRO2 - RU Blue screen

I have a MSI K7R Pro2 - RU (MS-6380) and i'm experimenting blue screens with windows xp. I get always the same error : STOP 0x00008E
Does someone of you know what's causing this ?
I always have this error while playing never in a office use.
My other hardware :
(Asus) Geforce 2 32mb
(creative) Sound Blaster Audigy Frenmch eX (with the front panel)
(3com) Ethernet card 10/100
(unknown) 2 sticks of ram
dvd
At first i though it was the sound card, because i bought this config when both were disp. i mean the mb, and the sound card. The drivers for the sound card didn't were very stable, so i waited till some drivers came out for win xp.
But now i have more stable drivers, but the problems are still here. I also took the sound card out. But the problem was still there.
Now i have some questions ...
it is mb related ?
graphic card related ? (at first i also had probs with, cf infinite loop, but changed drivers and changed PSU and no more inifte loops)
OS related ? (tried with win98, but got blue screens too)
Well i have win xp, maybe i could try to update to sp1, but it's something i would want to avoid....
So any ideas ??
Oh i almost forgot :
This problem is very strange, because it never happens at the same time. Sometimes i can play hours and hours without a problem, but some other times, got the same prob again and again.

Well it seems to be the ram ...
I took out the 2nd stick of ram, and in 2 days of quasi non - top gaming i didn't had a single blue screen ..
Thank to you i'm finaly can play without the fear of a BSOD ...
I'll try to put the 2nd stick in the 3rd place and see if it was the stick of ram or the emplacement...
I also should swap the "working" stick with the "non working", and see if it's really the stick.
Thank you, and i'll post again with my results.

Similar Messages

KT266 Pro2 Blue Screen.. via chips??

everytime i try to run a program, more specifically, games; IE: WarCraft 3, Command & Conquer: Generals, or n/ething that requires Direct X (my speculation) when i quit the game (and only when i quit the game) i get this gay blue screen in windows 2000 (and it was in XP also) that says "IRQ NOT... " something something, i'm not sure, all iget is the IRQ part about my AGP controller? or VIA chipset?
can someone please tell me how 2 fix it, and i have the via drivers installed, and videocard drivers updated
Rig:
AMD Athlon T-Bird 1.333 Ghz @ 266 FSB
MSI K7T-266 Pro2 w/ Via
ATi All In Wonder Radeon 32 Meg DDR Ram
256 DDR PC2100 Ram
NEC 16X DVD
MSI 40x12x48 CD-RW (defective BTW!! grrr)
Quantum 40 Gig 7200 RPM HD

http://www.msi.com.tw/program/service/forum/index.php?threadid=1131&boardid=13&styleid=1

HELP! k7t266 pro2-u winxp install

Hi,
I have a problem with installation of winXP SP1 on my computer. First i got a blue screen in the first step of installation (windows loads drivers, then freezes). It said that acpi.sys is the problem. I disabled it and then the problem was irq not less... . Then i disabled
internal cache, system bios cacheable and shadowing options and installation started but the computer was too slow ( it took about an hour to copy the files on hard disk). After the installation was finished i put back the fields internal cache to writeback and c00 32k shadow to cached and left system bios cacheable on disabled ( i read in the manual that it might be a reason for system hangups) to speed it up. For a while it seemed like it was working ok, i installed the drivers, software... but tomorrow everything up. windows started to freeze when i tried to encode mp3's from audio cd's, when i tried to install new sofware...
I dont know what to do and don't want to disable internal cache because of the huge system slowdown...
Can anyone help !!!
my config is
amd athlon xp 1800+
microstar k7t266 pro2-u with lan
256mb kingston 266 ddr
maxtor 40gb ata133
teac w540e writer
nvidia g-force 2 mx400 64mb

Quote
Hi!
What can your PSU provide in terms of ampères?
Load BIOS setup defaults. Open case.
Have the HDD and the CDRW on different IDE channels and cables, with both as Master respectively at the end of the cable.
Install VIA 4in1 drivers.
When everything works, make proper BIOS adjustments.
Best wishes, and good night!
Can't provide the data about my PSU because i'm not at home right now.
I will do it tomorow.
Cables are already set up like that.
Thank you

T400 windows 7, blue screen memory_management and IRQL_NOT_LESS_OR_EQUAL

Hi can anybody help me solving this problem? I have T400 with windows vista 32. I upgraded it into windows 7. And now my laptop is having problem with the blue screen when the windows started it says about memory management or IRQL that asked me to disable the BIOS memory such as caching or shadowing.... What do you guys reckon?? Cheers.

I used to get that BLUE SCREEN ALL THE TIME
I stoped getting it one after I slipstreamed windows xp pro to sp1 and did a clean install
I use latest nvidia http://www.nvidia.com
I use the latest via drivers http://www.via.com.tw
also you should check to make sure your video card is seated properly take it out and put it back in
clear cmos/bios
check your memory make sure it's seated properly also try moving it around I found that the middle slot was bad on my board but I have a K7T266 pro2 v2 thank god I have a three year warenty still time to rma when every I get around to upgrade

Raid 0 Failure! XP Pro won't read array on MSI k7T266 pro2 *URGE

Before anything else, thanks for reading and I hope you can help:
I have an MSI k7T266 Pro2A-RU motherboard with 512MB of Mushkin RAM, AMD XP 1600+, a Geforce2 MX400, Audigy Soundcard and a cheap PCI NIC card. I consider myself an above average technician and I've come up on a problem I can't figure out. There is about 80GB of data at stake here:
I have 2 IBM Deskstar 40GB 7200 RPM drives that were configured in a RAID 0 (stripe) configuration over a year and a half ago. This gave me a total of 80GB online. Windows XP Professional was installed and the drives have been running fine every since...
The system was practically bulletproof and it was very rare it ever locked up for any reason. A few days ago, however, the system locked up about 4 or five times. There was no software or hardware that had been added or installed and system use hadn't really changed up or down. I run up to date antivirus software (Command Anti-Virus), run behind a secure firewall and watch what I open. The lock ups were random, but happened when I was away from the computer. ( I leave my system on all the time).
Being a bit paranoid, on 1/28/03, I acquired an 80GB Maxtor drive to install to back up my datafiles. Before the install, I notice the system had locked up at least once that day, so I figured I would hurry up and get the drive in to back up. I installed the 80, booted, configured it in XP and made it active and transfered a few test files over. No problem. I made the decision to back up my data files before bed and continued to work for the next two hours. The system ended up locking up with a windows blue screen STOP error message: KERNEL_FAULT_INPAGE_ERROR when I tried to run a program. Thinking little of it, I rebooted the computer to find I could no longer access the data on the RAID.
I've tried nearly EVERYTHING I can think of. (You can already assume I've done the basics (check/replace the cables, etc). Here's a list and the results:
---- Reboot in all available modes (Safe, Safe with NW, Normal, Last known, etc). They all FAIL. In safe modes, you can see where the system actually tries to boot off the array (runs through driver files and stops on MUP.SYS) and hangs. Same result with all other drives removed except the RAID.
---- Installed another drive, loaded XP with the raid controller files (By the way, it's a Promise ATA 100 "lite" controller), plugged the RAID back in and it hangs on boot up. Safe mode gives the same results. Tried the same thing with Windows 2000 (so I could access the NTFS partition) and Windows 2000 won't load when the array is plugged in, but loads ok when it isn't (used the 2000 driver for the RAID controller for this attempt). Safe mode gives the same results.
---- Removed all drives except the Array and tried to reload XP (with the array drivers downloaded again from the site.) No effect. System hangs.
---- In a last ditch effort, I have access to Winternals Administration Pack 2002 of all of their tools. ERC Commander, designed for this type of problem, Disk Commander, and the other tools all do the same thing: Any time the system attempts to read from or access the arry, the OS will hang. It won't even check for NTFS compatibility in the ERC commander program booting from a boot CD, and for those that are familiar with it, the Disk Commander program blue screens with a STOP: 0x000007B (0xF896963C, 0xC0000034, 0x0, 0x0) error. Research has told me this is an INACCESSABLE BOOT DEVICE message.
These are the main highlight major attempt things and there's a few things in between I've tried (like using Norton Ghost to try and mirror the array to the 80GB. Norton ghost said there is an error reading the partition and can't go any further (Returns an Internal error))
I'm at the point where I have run out of available options and don't know what else to try. I have since purchased the exact same motherboard off e-bay to see if it just so happens to be the controller and to see if my RAID will come back so I can at least read the data off of it. It should be here in a few days. If that doesn't work, I'm toasted. Could I be fighting a hardware (drive or board or controller) problem. Is the array THAT corrupt the OS can't read it???
If anyone has any other bright ideas, I'm willing to try about anything short of damaging the array. Any help is greatly appreciated. Please post here, or e-mail to [email protected].
BTW, the Promise BIOS is Fasttrak 100 "Lite" v 1.31.1(Build 30)
Thanks.
- Chuck! ?( ;( ;( ;( ;( ?(

got one but its lightley used for storage but amd forum storage is full of tales of woe with them
type deskstar and problems in goggle for a laugh

K7T266 Pro2 - BSOD - missed bag of tricks

Hi all, I have a problem with my computer and I am not sure what's the problem. The System has been running fine for about a year.
Lately when I shut my computer off for a length of time and start it up a few hours later I get a blue screen, generic of course and have to restart, when I do reboot the computer starts up in safe mode, I then recieve a display error and have to reset my display properties. Which of course causes another Blue screen and recieve the following error - SoundBalster Live! "Math Co-proessor is not detected. Eum10k1.vxd cannot be loaded"
Config
k7t266 pro2
AMD AThlon 1800+
pc2100 DDR 256 mb
Geforce 2 32 mb
60 md HDD ATA 133
Sound Blaster Live - Value
Dlink 528 networkcard.
and of course Windows 98 se
anyone have any idea what this might be.
TIA
Dave

Hi,
There are some known issues with SB live cards and MSI motherboards. Is it possible to try the onboard sound. Its not too bad a I use it:)
Rob

K7T266 Pro2 RU repaired but...

Hello.
Long time no see, I'm back now ^^
Since the glorious times of my first Socket A system, much water have flowed on rivers so to say that many things happened, to me and in the world.
Well, ok, to make long story short here's the thing.
Some time ago (iirc some years) I were trying some spare hardware I have and when I was trying my old K7T266 Pro2 RU motherboard, after some tests, I did a mistake: I didn't installed properly a stick of ram, being partially inserted on one side and not fixed properly in its slot, so, forgetting and/or not noticing it, I switched on the motherboard and the poor board "poofed" out dead. The component that burned was nearby the ram slots, named D7 on the board and it was an SS12, a schottky diode: I thought so that replacing it would have sufficed to bring the board back to life, so I went to a tech assistance shop and they gave me an SS14 diode, claiming that it have the same characteristics of the SS12 being it just stronger than the earlier and that it can stand some more voltage, so I bought it for a few euro.
After that I left all the mess apart since I lost interest to it, until now that I decided to try to fix the motherboard with the new component and see it I were right about it, but here came the first problem: when I were trying to unsolder the old burnt diode, it was really difficult, first off because it was too near the ram slots (so I were fearing to melt the plastics of the retention system), second off because the pin on the opposite side of the ram slots wasn't wanting to let go the track it was soldered! I struggled much to make it let go and after I succeeded, luckily, the track under was lifted from the board and I found it even cut!
After swearing all of my calendar (don't mind about this, it's something we do much in italy, not always tho :P), I then tried to solder the new diode: it wasn't so difficult, and luckily i managed to sold back the cut track rejoining it and, because the whole thing wasn't so fix, I put even a drop of Superattak glue (cyanoacrylate): the result was very good, even tho couldn't be as if it nothing happened, but acceptable in general.
I tried then to reinstall it on one of my old case desktop ATX lying around, throwed my old Athlon XP 1800+ Palomino and a stick of 256 MB DDR266 from an old Intel celeron 1.7GHz Willamette rig I got recently, and powered it up again: first attempt didn't do anything, after some cable checking (I don't remember now but maybe I reversed the reset and power on switches plugs ^^) it finally run... and *drum roll* it even did the POST! I was happy, then, and was thinking that everything were going the good way. But Murphy is always hiding somewhere, so my happiness wasn't lasting long.
Ok, then, I decided to try to test it again to see if the hardware is still going, so I tried to install windows XP on a spare maxtor 80gib I had lying around, but with no much luck: firsts attempts hanged many times always on the same step (still on the early blue text-only screens), so I decided to try to run a memtest first, to check it before everything, and here comes the new main issue.
I've installed memtest86+ v4.20 on an old 256 mb usb pendrive, successfully, because I needed to test the ram on some other computers, so I had the thing already ready for the task: I inserted it on one of the onboard usb plug (the v1.1 ones: naturally on the usb 2.0 it's not even detected) and tried to boot the board from it. Failing.
I then tried it again on other computers: first my notebook, then some other rigs and all of them run the test correctly. To be sure I reinstalled the memtest on the pendrive, to no avail.
I've tried to change the ram stick, I've plugged a 512 MB DDR400 one (not the one of the incident, but surely a working one, since I tried it successfully on other rigs), and change the slot too, still to no avail.
The pendrive "boots", but it hangs prompting me:
Quote
SYSLINUX 3.86 2010-04-01 CBIOS Copyright (C) 1994-2010 H. Peter Anvin et al
No DEFAULT or UI configuration directive found!
Boot:
What should I do?
Is it because of the USB 1.1?
Or maybe a BIOS issue?
Or is it really my motherboard that's still TFU? I really hope not, I want to make it work again :(
Anyway, of anybody of you that still have this glorious motherboard, can you please tell me if you can run memtest86+ from one of the ONBOARD USB (1.1) plugs?
I take it from here, btw: http://www.memtest.org/ (http://www.memtest.org/download/4.20/memtest86+-4.20.usb.installer.zip to be correct).
Please answer me, thank you in advance!!
Edit: I forgot to say that I did the c37 removal mod for making the board compatible with 0.13 µ cpus, successfully, natuarlly :P

Quote from: Bas on 06-February-12, 19:38:58
Looks like the harddisk is broken.
As it complains about the partitions just like XP does.
No, I tried to boot the memtest from usb disconnecting everything else, so no hdd and no cd/dvd. I also tried to disable every integrated periferal and device: fdc, serials and parallel, midi, game, ide, raid, audio, modem and usb (1.1 naturally).
Btw when I said that it complains about the partitions? :o
Quote from: eagle3 on 06-February-12, 20:58:32
Try memtest on a cd and boot from that; or use a linux live cd. Or the marvellous Ultimate Boot cd. http://www.ultimatebootcd.com/
Also that board was built around the time of the bad cap debacle..
I think I would have binned it..
I followed your suggestion (but I thought it by myself too) and tried with the cd version of memtest86+, burning the iso onto a brand new cd (sigh, so much space wasted :p), and tried it: it finally worked, and I found that the 256 Mib ddr266 stick isn't compatible with the board, since the test didn't even started, another stick of 512 Mib ddr333 got errors (even 1 is too much to me, but it didn't have only 1 error), and finally the 512 Mib ddr400 tested fine for about 2 hours! That's a relieve ^^
Unluckily even using the good working ram, it still don't want to boot memtest86+ from the usb pendrive.
I still ask to anyone with my same board if they can do the same test, just to be sure that's just the board that can't boot properly from usb, or maybe a little incompatibility with my old pendrive.
Thanks for now.

Memory module not recognized on K7T266 Pro2

Hello.
I have a computer with only 256 Mb of RAM and I wanted to add 256 Mb but my second memory module of 256 Mo is not recognized whereas it functions very wel.
Here are details :
- Mother board : MSI K7T266 Pro2 (ms-6380 v2.0) with 3 memory slots
- BIOS : Award Modular W6380F1 V3.0 071902
- Memory module of origin : Samsung 256 Mo PC2100 (2 Sides)
- New memory module : Corsair Value 256 Mo PC3200 (1 Side)
Configs Tested :
- Samsung only : OK
- Corsair only : OK
- Samsung in Slot 1 and Corsair in Slot 2 or 3 : the computer starts but with only 256 Mb of RAM (in this config, Everest Ultimate Edition finds both memory modules but also only 256 Mb of RAM)
- Corsair in Slot 1 and Samsung in Slot 2 or 3 : the computer starts with a blank screen and several beeps.
Can somebody help me so that my second memory module is recognized correctly ? I specify that I did not modify the BIOS.
I thank you by advance.

I'm no memory expert, but from being around here I've learned that there is more to a stick of RAM than the MHz speed. If timings etc were perfectly the same for the 3200 and the 2100, the system (the Northbridge) could simply set down memory speed to the slowest of the sticks.
However, I also know that many have been helped by entering BIOS, Advanced Chipset..., and go to the subtitle Memory timings controlled by..., and change from By SPD to By User. Then manually set down to 133 (266 effectively). This is if you absolutely want these two sticks.

K7T266 Pro2 RU, Raid-0 & Linux

When I try to install either Red Hat 8.0 or Mandrake 9.0 on my K7T266 Pro2 RU, which has 2 x 40GB drives configured as RAID-0 (ie 1 x 80GB), both versions of Linux see the two physical drives and not the one logical stripe array. Why? It almost seems that the Linux drivers for the Promise 20265R are treating the raid channels and normal IDE channels. I want to install Linux onto the RAID-0 stripe!
I have searched for guides/tutorials on installing Linux on RAID, but all the ones I found only talked about RAID-1 (Mirroring).
Windows 2000/XP only sees the one logical drive.
Any help would be appreciated!
Chris.

The installer is wrecking the /etc/raidtab file when trying to detect existing raid arrays.
Solution: Format a floppy disk with a DOS filesystem (in Linux, you can use the command "mkdosfs /dev/fd0"). Copy
use detect_devices;
package detect_devices;
log::l("PATCHING");
*raidAutoStartRaidtab = sub {
my (@parts) = @_;
log::l("patched raidAutoStartRaidtab");
$::isInstall or return;
require raid;
#- faking a raidtab, it seems to be working )
#- (choosing any inactive md)
raid::inactivate_all();
foreach (@parts) {
   my ($nb) = grep { !raid::is_active("md$_") } 0..7;
   output("/tmp/raidtab", "raiddev /dev/md$nb\n device " . devices::make($_->{device}) . "\n");
   run_program::run('raidstart', '-c', "/tmp/raidtab", devices::make("md$nb"));
unlink "/tmp/raidtab";
use raid;
package raid;
*prepare_prefixed = sub {
my ($raids, $prefix) = @_;
log::l("patched prepare_prefixed");
$raids or return;
&write($raids, "/etc/raidtab") if ! -e "/etc/raidtab";
eval { cp_af("/etc/raidtab", "$prefix/etc/raidtab") };
foreach (grep { $_ } @$raids) {
   devices::make("$prefix/dev/$_->{device}") foreach @{$_->{disks}};
to the floppy disk. Remove the floppy and reboot using the Mandrake Linux 9.0 CD1 to do a CD-ROM installation. During boot, press F1 at the splash screen, then place your floppy disk that contains patch.pl in the floppy drive. At the prompt, type "patch", then follow the installation as usual.
Hope that helps

K7T266 Pro2 RU: Boot problem, wrong CMOS setting

Hi All,
I have had the Pro2 RU MB for a year now with very few problems. Over Christmas I was cleaning up my computer and was going to do a format :C and reload windows. When I went to start the computer after cleaning it up (remove all cards, clean up dust) I got 4 red leds on d-led. Tried everything (different memory, reset bios, unplug everything except video, ect) always 4 reds. Bought a duron 1.3 GHz put it in started the computer it start to post, went through fastrack raid screen and then I got "CMOS settings wrong" "press F1 to setup", "F2 load defaults" ...... screen I go F1 into setup make ajustments and everytime I save and I get 4 red leds on reboot. If I go F2 load defaults and continue it will try and boot, my hard drives are in a raid 0 array and it will check floppy, ide 0, cdrom by default so it can't boot. If I reboot at this point it will go 4 red leds. I can't flash the bios which is ver 3.2 because the bios protection is enabled and I can't change any settings. I could use some help this one has my stumped.
I have tried 3 different power supplies, and that is not the problem.
K7T266 Pro2 RU
Duron 1.3GHZ, retail box HSF
256MB Cruical pc2100 ram
300w AMD approved PSU
Geforce2 GTS 32MB
2 60GB Quantum HD in raid 0 array
Win 2k pro
Cheers Rugger

I have reset the cmos with pc unplugged...yes.
I have read the FAQ at this site, I have used the search feature at this forum I have googled my problem searched a few other sites and I am stuck. I have been building computers and troubleshooting problems for 3 years now. If it was a new board I would RMA it at my wholesaler.
It seems like there is a problem with the cmos chip because it will not accept any changes to the settings. As soon as you save the changes in the cmos the computer reboots and I get 4 red leds in d-led.
Cheers Rugger

Window XP Blue Screen

Hi,
I have k7t turbo2 motherboard and Atlon 1600+xp MP, which always give me blue screen. I have format my HD for many many times. I had no idea of how to keep my computer stable.
Can any one help me?

Motherboard CPU Type : AMD Athlon XP, 1400 MHz
(5.25x267)1600+
Motherboard Name : MSI K7T
Power/Pro/Pro2/Pro2-A/Turbo/Turbo2/
Turbo Limited Edition
Motherboard Chipset : VIA VT8363A Apollo KT133A
System Memory    : Apacer Tech. (256 MB PC133 SDRAM)
: Apacer Tech. (64 MB PC133 SDRAM)
: Apacer Tech. (64 MB PC133 SDRAM)
: Total 384 MB (SDRAM)
BIOS Type    : Award Modular (10/07/02)
Communication Port   Communications Port (COM1)
Communication Port   Communications Port (COM2)
Communication Port   Printer Port (LPT1)
Display
Video Adapter    : NVIDIA GeForce 256 (Microsoft
Corporation) (32 MB)
3D Accelerator    : nVIDIA GeForce 256
Monitor   Samtron : 76DF/77DF (HMAT215241)
Multimedia
Audio Adapter    : VIA AC'97 Audio Controller
Storage
Floppy Drive   : Floppy disk drive
Disk Drive   : MAXTOR 6L040J2 (40 GB, 7200 RPM,
Ultra-ATA/133)
Optical Drive   : CREATIVE CD5221E JJ990720 (52x CD-ROM)
Optical Drive   : CREATIVE CD-RW RW1210E
Partitions
C: (FAT32)   38160 MB (33118 MB free)
Input
Keyboard   : Standard 101/102-Key or Microsoft Natural
PS/2 Keyboard
Mouse    : PS/2 Compatible Mouse
Modem    : SmartUSB56 Voice Modem
Peripherals   : Printer EPSON Stylus Photo 830 Series
Power Supply : Macron Power Output 300W Max, Model
MPT-301

Newbie Freaking Out-K7T266 Pro2-A Shutdown, then startup

I had built a computer for myself, and it runs like a dream. It has the AMD Athlon XP 1800+ with the KT3 Ultra 2 Mainboard. I had no problems with it. Then, I decided to build one for my husband, but chose the K7T266 Pro2-A Mainboard with the same processor. (I am clearly waaay over my head right now). When I try and shut down the computer, I get a small click coming from the inside of the tower speaker, barely audible(similar to the small sound you get when you are installing a new driver, and it pops up to tell you that the disk is not in the drive????), then it attempts to shut down, only to reboot a split second later. Either it reboots fine, or it hangs onto a black screen, and emits 3 long beeps.
I desparately need some help here. I am going by the book (PC Building for Dummies" (please, don't run and hide....I am trying to learn!), and it helped me out a great deal on the first computer. This one has got me stumped. I also downloaded the new version of the boards bios last night, but it did not help. I also opened it up, re-seated the wires to the front switched, as well as the d-bracket, memory, video card, and modem. I went into the Advanced power management and disabled everything.
System Info:
K7T266 Pro2-A Mainboard
Bios 5.6
CPU: AMD Athlon XP 1800+
GenForce 4 MX 440 64MB D
Memory DDR PC2100 256MB
Modem: HSP56 Micromodem
O/S: Win98SE (Updated, as well as downloaded the shutdown patch)
Please...I really jumped the gun when I started this thing. I should have studied up more on all the technical info, but I have been known to just jump in and do it. I have learned my lesson. I am bowing to all the computer technicians right now. ;(

I had that problem with a computer I recently built. Try swapping the power supply out of your other computer. I bought a cheapo case and the motherboard couldnt shut the power supply off.
Good luck! :D

K7T266 Pro2 incompatibilty problem with Nvidia GeForce4 Ti4200

I just bought the GeForce4 Ti 4200 from Siluro and installed it on my MSI K7T266 Pro2 MB and have since then experienced some problems when booting XP pro.
Everything seems to work fine untill the very last application loads in XP after boot. Then the screen turn white, the mouse cursor becomes a black and white stripped square and the system reboots automatically. Generally after second boot, evreything seems to work fine but I get an XP error message stating that "the Nvidia Geforce4 TI 4200 drivers may be the origin of the critical problem encountered".
I have all lastest drivers for both the MB (Bios 3.7 + lastest VIA drivers) and the Nvidia GeForce (Detonator 41.09) and yet experience the problem... Help!!
MB K7T266 Pro2 MS-6380 Ver. 2 (Bios 3.7)
Siluro Geforce4 Ti 4200 (Detonator 41.09
XP Pro

I have an AMD Athlon 1700+
768 MRam DDR 266
Sound card is Sound Blaster Audigy Platinum EX
I have an ADSL connection with Alcatel Modem
I hope this is what you required... If not, let me know exactly what it is as I do not really know what PSU and the rest stands for (or when I can get that information on my PC!)
Thanks again for your help!

K7T266 Pro2-RU raid crash

I have had this system up for about 8 months. One day when converting mp3 to wav the system crashed. When rebooting I would get a black screen or it would hang during the boot process. I was using XP and W2K server - never had an issue until this crash, and now problems when booting with either.
I attempted to do update the raid drive (got the grand message re: stop what the heck your doing or face certian death or Continue and prepair to die - when updating the driver in xp). Nothing worked. So I fdisked the drive (20gb ibm) drive that was my c: and reinstalled W2k Server...still seeing the same issue.
Raid array says it is functional, but that is about it. System hangs durning boot, and if ide 3 and or 4 is unplugged, I can then boot up and work off of the 20gb drive.
Anyone, anyone?
System:
2000 server on a 20gb ibm
1.5gb of Ram
2- 40gb ibm darkstar hard drives in array
Promise raid lite 1.13
K7T266 Pro2-RU
tried new cables,
changing around the jumper,
latest raid drivers from our friends at msi,
but today I am thinking hammer may do the trick...

Still no luck, today I went out and downloaded
File Scavenger 2.0.
It could see the array, and for 40 dollars I can buy a license to repair the drives...or so they say.
Does MSI have any raid repair utilities, or does anyone know of any good raid repair programs

MSI K7T266 Pro2 troubleshooting

Hello,
I just recently recieved a MSI K7T266 Pro2 motherboard (A6390MS) and I'm getting some weird troubles with it. I connected everything to the motherboard and when i start up the computer the screen comes up fine... but for some reason when i go to hit delete to go into setup it doesn't work. It continues to boot until it tries to detect any hard drives connected to raid. Since i don't have anything hooked up to it, it says "No Array is Defined.........." Then it says to hit to continue booting. For some reason it must not be detecting my keyboard because any button i hit does nothing at all. So after i let it sit there and do nothing, it goes back to the first screen that tells you the BIOS version and CPU and all that, and it displays the message "CMOS/GPNV Checksum Bad"
I'm not exactlly sure what that means or why it is saying this. I've been sitting here for a week trying new things. My Keyboard is PS/2 so i figured that might be it. I tried using a PS/2 to USB adaptor and it still won't do anything when i hit DEL to go into Setup. I tried different keyboards and I only get the same thing. I checked MSI's website and they have no information at all and i couldn't find anything on the internet to help. Hopefully someone here may know what my problem is. I think that the PS/2 ports are bad, and if so, how is that fixable?
I didn't buy the motherboard, my friend's dad gave it to me to try out because my previous ASUS motherboard died out on me. So as far as sending it back to MSI, I dunno if that is possible. I'd have to find out how long their warrenty is and how long ago he bought it.

It won't even read the floppy disk drive to use a boot disk because it seaches for the HDD first i guess.
Now after taking the battery out and all that it just keeps saying CMOS settings wrong instead of the other message about "CMOS/GPNV Checksum Bad" and i can't make it go away.
I'm really lost now and not sure what to do with the board because it's obvious that it works... but if it is something as small as the ps/2 ports being damaged, it would be such a waste.
Also the PC Speaker is making a rapid clicking noise and im not sure what it means. It also beeps 3 times after it tries to detect the raid and goes back to the start up screen that shows the information about the processor and ram and stuff

K7T266 PRO2 - RU Blue screen

Similar Messages

Maybe you are looking for