Newbie install - K8T Neo2 now dead?

I installed a K8T Neo2 (MS-6702E) with these items:
Athlon64 3000
K8T Neo2 (MS-6702E)
2x512MB Corsair Value Select PC3200
MSI MX4000-T64 8X 64MB video
80 GB Hitachi SATA HDD
Rosewill RV450 PSU (3.3V 30A 5V 45A 12V 22A)
Zalman CNPS7700-ALCU Heatsink/Fan
I used both sticks (before reading the local FAQ here) to start. The d-bracket would light up and stall on "early chipset initialization" (LED1). I removed one stick and retried. Retried several times. At about the 4th or 5th reboot, I got nothing - no d-bracket, no fan, DEAD. I'm not sure what I did, if anything, just before everything died.
I installed this PSU and retried:
Antec True550 PSU (3.3v 32A 5v 40A 12v 30A)
I pretty sure the PSU is not dead because I hear a tiny whistling die away (some oscillating component) within the PSU after I shut it down. 20-pin and 4-pin power connectors have been dutifully hooked-up each time (as far as I can remember). I have swapped memory sticks but only between the two that I have (no other brands) but have not tried them in each slot. I have removed the CPU and re-seated it (no bent pins). I have removed the mainboard from the case (placing it on a non-conductive surface) and attempted to power it up by shorting pins 6/8 on JFP1 header. Nothing.
The mainboard was not insulated from the case and I would argue about the need for this. Electrically, it doesn't make sense to me. All the little sheetmetal shields on the back of the board for USB, sound, etc. all touch the case when the board is installed properly and THOSE are grounded to the board as well. So even if you insulate the board from the brass stand-offs, the board is touching the case via the back panel. If the MSI intended that the mainboard not "touch the case", then why do all the mounting holes have bare groundplane exposed? But I have an open mind - if someone can explain the reasoning for insulating the mainboard mounting points, then I'll listen.
I'm not a total newbie but the last time I assembled a PC this way was probably 6 or 7 years ago (oh yeah, it worked then Anyway, do I have a dead board or do I have more options to try? Thanks.
Paul

Quote from: blazing storm on 04-March-05, 06:45:04
Hi,
I suggest you unplug all wires and plug back in checking you've got them all in the right sockets, slots etc., take out device cards and re-install them and if all of this fails then re-seat the cpu.
Yes, did that several times. Sorry I didn't mention that. The last few times, I've only had the 20 and 4-pin connectors hooked up, no video/memory/d-bracket installed. Figured at least the CPU fan should start spinning.

Similar Messages

Boot and OS install issues with K8T Neo2 F

Can anybody shed light on my difficulties?
Assembled a new computer yesterday. First power-on produced nothing except 3 (2,3,4) red leds on d-bracket. After reading several postings, tried the following:
Swapped around memory modules;
Did repeated JBAT1 data clears (NB if you happen to get a board with the V1.0 user guide, note that the JBAT1 diagram appears upside down - pin one is closest to the SATA slots (page 2 - 24). The MSI downloadable user guide (V1.2) has that error corrected (page 2-25)
The only memory config that doesn’t produce three red leds is with one 512 stick installed in channel 3 (green).
Can now get to the point where Windows XP boots to the point where install is about to start, and then advises me that it can’t find a hard disk!
Have dis/reconnected the sata cable (using different cables) and checked the bios setup but can find nothing strange except that setup refers to the hard disk as BBS 0 (RAID) ST3120827AS - the reference to “RAID” worries me.

Paul, there have been people here that have had to strip their system down to the bare minimum hardware to get windows to complete the install, so try that. I had trouble completing my windows install as long as I was trying to install the RAID drivers at F6. So I ignored the prompt at F6 and windows installed fine. Then I installed my RAID drivers afterward.
These things are extremely sensitive when it comes to memory. I had the same problem you are having. Mine was cured by a BIOS upgrade to ver. 3.3. The simplest way to do it is to use "Live Watch". It will locate BIOS ver 3.3 for you, and download it to a floppy along with the flash program, and make it bootable all in one easy step. Then all you have to do is boot from the floppy you just made, and follow the instructions. Very simple.
I've read all these stickies and posts now going way back, and IMHO anyone who wants to use RAM thats not on the list should do so at their own risk. Interestingly enough, the recommended list from MSI is not the same as the list from AMD. And the memory manufacturers have their own lists of RAM that they say will work with this board. I'm using 2x 512 sticks of GEIL from the MSI recommended list.
Check out these links to see what I mean. By the way, if you haven't noticed, most of the older posts about memory problems are with respect to the K8T Neo FIS2R which is a socket 754 single channel board, so although they are similar, they're not the same. My point is just because his K8TNeo FIS2R works fine with brand "X" RAM doesn't mean your K8T NEO2 FIR will.
http://www.msi.com.tw/html/products/mainboard/testreport_pdf/6702E/memory.pdf
http://www.crucial.com/store/listparts.asp?Mfr%2BProductline=MSI+%28Micro+Star%29%2B+Motherboards&mfr=MSI+%28Micro+Star%29&cat=RAM&model=MS-6702E+%28K8T+Neo2-FIR%29&submit=Go
http://www.mushkin.com/epages/mushkin.storefront/EN/product/991140
http://www.amd.com/us-en/assets/content_type/DownloadableAssets/Athlon_64_Unbuffered_DIMM_AVL.pdf
http://www2.amd.com/us-en/Processors/TechnicalResources/1,,30_182_869_9460%5e9461,00.html?1094454813
Good luck!

Help installing XP Pro on K8T Neo2-F!!!

I'm trying to help my cousin install XP Pro on their new pc. It's got an Athlon 64 3000+, K8T Neo2-F, 512mb Samsung ram, and an 80gb ata drive. before i started to fix it, my cousin said that he stopped the xp install midway thru because he forgot to install the RAID drivers. when i try to reinstall xp, it just freezes on DOS when it says "setup is checking hardware configuration" or sumthin like that. i also noticed that their dvdrw drive stops spinning and has a clicking noise at that point. i tried installing win 98 on it and it worked, then tried to upgrade to xp, which froze when the pc rebooted. anyone have any idea what's going on???

Hi. My setup is very similar, and I had a similar problem installing XP as well. Do as simon suggested to make sure your harddrive is clean for a fresh install. Make sure the promise 579 SATA controller and the VIA SATA RAID controller are both disabled in BIOS. Especially if your not using a RAID setup or any SATA drives you wont need them anyway.
Install XP as normal. Do not install the RAID drivers from the floppies by hitting F6. Now the XP installation should be able to complete itself. If you want to use the controllers later, enable the one (or both) you want in BIOS, Then install the drivers from the CD under Device manager update driver option.

MSI K8T Neo2 FIR, need help installing drivers

Hi there,
I need help with installing drivers. Here’s my setup:
CPU: AMD Athlon 64 3500+
Mainbord: MSI K8T Neo2 FIR (VIA K8T800Pro)
OS: Windows XP Professional, SP2 installed
ATI Radeon 9600 Pro
I updated per MSI Live Monitor, but when I run ‘dxdiag’, I says I have to update the ‘VIA standard host bridge’. I don’t know what this is or where it can be found. It could be I saved the updated drivers in the wrong file (F:\ Program Files\...) where F is my primary harddisk and the drivers should be saved in F:\Windows\ System 32.
Also, my hardware setup tells me there are two videocards 'installed': a Radeon 9600 Pro and a radeon 9600 Pro (secundary). Do I need to de-install the secundary one?
Here’s a piece of my most recent dxdiag:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
System Information
Time of this report: 5/22/2005, 10:22:20
Machine name: UIWDC2ARUPUS49X
Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 2 (2600.xpsp_sp2_gdr.050301-1519)
Language: Dutch (Regional Setting: Dutch)
System Manufacturer: MSI
System Model: MS-6702E
BIOS: Version 07.00T
Processor: AMD Athlon(tm) 64 Processor 3500+, MMX, 3DNow, ~2.2GHz
Memory: 1024MB RAM
Page File: 285MB used, 2687MB available
Windows Dir: F:\WINDOWS
DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
DxDiag Version: 5.03.2600.2180 32bit Unicode
DxDiag Notes
DirectX Files Tab: No problems found.
Display Tab 1: No problems found. DirectDraw test results: All tests were successful. Direct3D 7 test results: All tests were successful. Direct3D 8 test results: All tests were successful. Direct3D 9 test results: All tests were successful.
Sound Tab 1: No problems found.
Music Tab: DirectMusic test results: All tests were successful.
Input Tab: No problems found.
Network Tab: No problems found. DirectPlay test results: The tests were cancelled before completing.
DirectX Debug Levels
Direct3D: 0/4 (n/a)
DirectDraw: 0/4 (retail)
DirectInput: 0/5 (n/a)
DirectMusic: 0/5 (n/a)
DirectPlay: 0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow: 0/6 (retail)
Display Devices
Card name: RADEON 9600 SERIES
Manufacturer: ATI Technologies Inc.
Chip type: ATI RADEON 9600 Series AGP (0x4150)
DAC type: Internal DAC(400MHz)
Device Key: Enum\PCI\VEN_1002&DEV_4150&SUBSYS_000217EE&REV_00
Display Memory: 128.0 MB
Current Mode: 1280 x 1024 (16 bit) (60Hz)
Monitor: Plug en Play-monitor
Monitor Max Res: 1600,1200
Driver Name: ati2dvag.dll
Driver Version: 6.14.0010.6546 (English)
DDI Version: 9 (or higher)
Driver Attributes: Final Retail
Driver Date/Size: 5/4/2005 04:28:54, 226816 bytes
WHQL Logo'd: Yes
WHQL Date Stamp: n/a
VDD: n.v.t.
Mini VDD: ati2mtag.sys
Mini VDD Date: 5/4/2005 04:28:34, 1133056 bytes
Device Identifier: {D7B71EE2-0210-11CF-CC6D-0820A1C2CB35}
Vendor ID: 0x1002
Device ID: 0x4150
SubSys ID: 0x000217EE
Revision ID: 0x0000
Revision ID: 0x0000
Video Accel: ModeMPEG2_C ModeMPEG2_D
Deinterlace Caps: {6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
{552C0DAD-CCBC-420B-83C8-74943CF9F1A6}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{6E8329FF-B642-418B-BCF0-BCB6591E255F}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
Registry: OK
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled
DDraw Test Result: All tests were successful.
D3D7 Test Result: All tests were successful.
D3D8 Test Result: All tests were successful.
D3D9 Test Result: All tests were successful.
Sound Devices
Description: Sound Blaster Live! 24-bit
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID: PCI\VEN_1102&DEV_0007&SUBSYS_10061102&REV_00
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: P17.sys
Driver Version: 5.12.0001.0314 (English)
Driver Attributes: Final Retail
WHQL Logo'd: Yes
Date and Size: 6/4/2004 10:27:46, 840960 bytes
Other Files:
Driver Provider: Creative Technology Ltd.
HW Accel Level: Full
Cap Flags: 0xF5F
Min/Max Sample Rate: 4000, 96000
Static/Strm HW Mix Bufs: 64, 63
Static/Strm HW 3D Bufs: 64, 63
HW Memory: 0
Voice Management: Yes
EAX(tm) 2.0 Listen/Src: Yes, Yes
I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No
Registry: OK
Sound Test Result: Not run
Sound Capture Devices
Description: Sound Blaster Live! 24-bit
Default Sound Capture: Yes
Default Voice Capture: Yes
Driver Name: P17.sys
Driver Version: 5.12.0001.0314 (English)
Driver Attributes: Final Retail
Date and Size: 6/4/2004 10:27:46, 840960 bytes
Cap Flags: 0x41
Format Flags: 0xFFF
DirectMusic
DLS Path: F:\WINDOWS\SYSTEM32\drivers\GM.DLS
DLS Version: 1.00.0016.0002
Acceleration: n/a
Ports: Microsoft Synthesizer, Software (Not Kernel Mode), Output, DLS, Internal, Default Port
Sound Blaster Live! 24-bit, Software (Kernel Mode), Output, DLS, Internal
Microsoft MIDI-mapper (emulatie), Hardware (Not Kernel Mode), Output, No DLS, Internal
Creative SoundFont Synth (emulatie), Hardware (Not Kernel Mode), Output, No DLS, Internal
Microsoft GS Wavetable SW Synth (emulatie), Hardware (Not Kernel Mode), Output, No DLS, Internal
Registry: OK
Test Result: All tests were successful.
DirectInput Devices
Device Name: Muis
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a
Device Name: Toetsenbord
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a
Poll w/ Interrupt: No
Registry: OK
USB Devices
+ USB-hoofdhub
| Vendor/Product ID: 0x1106, 0x3038
| Matching Device ID: usb\root_hub
| Lower Filters: vulfntrs
| Service: usbhub
| Driver: usbhub.sys, 8/3/2004 23:08:44, 57600 bytes
| Driver: usbd.sys, 9/7/2001 14:00:00, 4736 bytes
Gameport Devices
PS/2 Devices
+ Standaardtoetsenbord (101/102 toetsen) of Microsoft Natural PS/2-toetsenbord
| Matching Device ID: *pnp0303
| Service: i8042prt
| Driver: i8042prt.sys, 8/4/2004 00:55:30, 53760 bytes
| Driver: kbdclass.sys, 8/4/2004 00:57:18, 25216 bytes
|
+ Toestenbordstuurprogramma voor Terminal Server
| Matching Device ID: root\rdp_kbd
| Upper Filters: kbdclass
| Service: TermDD
| Driver: termdd.sys, 8/4/2004 01:03:48, 40840 bytes
| Driver: kbdclass.sys, 8/4/2004 00:57:18, 25216 bytes
|
+ HID-compliant Wheel Mouse
| Vendor/Product ID: 0x046D, 0xC03D
| Matching Device ID: hid\vid_046d&pid_c03d
| Upper Filters: LMouFlt2
| Lower Filters: LHidFlt2
| Service: mouhid
| Driver: mouhid.sys, 9/6/2001 19:04:40, 12288 bytes
| Driver: mouclass.sys, 8/4/2004 00:53:38, 23552 bytes
| Driver: LHidFlt2.Sys, 12/17/2003 09:50:00, 25505 bytes
| Driver: LMouFlt2.Sys, 12/17/2003 09:50:00, 70801 bytes
| Driver: Logi_MwX.Exe, 12/17/2003 09:50:00, 19968 bytes
|
+ Stuurprogramma voor muis van Terminal Server
| Matching Device ID: root\rdp_mou
| Upper Filters: mouclass
| Service: TermDD
| Driver: termdd.sys, 8/4/2004 01:03:48, 40840 bytes
| Driver: mouclass.sys, 8/4/2004 00:53:38, 23552 bytes
DirectPlay Service Providers
DirectPlay8 Modem Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.2180)
DirectPlay8 Serial Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.2180)
DirectPlay8 IPX Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.2180)
DirectPlay8 TCP/IP Service Provider - Registry: OK, File: dpnet.dll (5.03.2600.2180)
Internet TCP/IP Connection For DirectPlay - Registry: OK, File: dpwsockx.dll (5.03.2600.2180)
IPX Connection For DirectPlay - Registry: OK, File: dpwsockx.dll (5.03.2600.2180)
Modem Connection For DirectPlay - Registry: OK, File: dpmodemx.dll (5.03.2600.2180)
Serial Connection For DirectPlay - Registry: OK, File: dpmodemx.dll (5.03.2600.2180)
DirectPlay Voice Wizard Tests: Full Duplex: Not run, Half Duplex: Not run, Mic: Not run
DirectPlay Test Result: The tests were cancelled before completing.
Registry: OK
DirectPlay Adapters
DirectPlay8 Serial Service Provider: COM1
DirectPlay8 TCP/IP Service Provider: LAN-verbinding 2 - IPv4 -
DirectPlay Voice Codecs
Voxware VR12 1.4kbit/s
Voxware SC06 6.4kbit/s
Voxware SC03 3.2kbit/s
MS-PCM 64 kbit/s
MS-ADPCM 32.8 kbit/s
Microsoft GSM 6.10 13 kbit/s
TrueSpeech(TM) 8.6 kbit/s
DirectPlay Lobbyable Apps
Disk & DVD/CD-ROM Drives
Drive: C:
Free Space: 65.4 GB
Total Space: 76.3 GB
File System: NTFS
Model: ST380011A
Drive: F:
Free Space: 56.7 GB
Total Space: 78.2 GB
File System: NTFS
Model: Maxtor 6Y080L0
Drive: D:
Model: LITE-ON COMBO SOHC-5232K
Driver: f:\windows\system32\drivers\cdrom.sys, 5.01.2600.2180 (Dutch), 8/3/2004 22:59:54, 49536 bytes
Drive: E:
Model: LG CD-ROM CRD-8521B
Driver: f:\windows\system32\drivers\cdrom.sys, 5.01.2600.2180 (Dutch), 8/3/2004 22:59:54, 49536 bytes
System Devices
Name: VIA CPU to AGP2.0/AGP3.0 Controller
Device ID: PCI\VEN_1106&DEV_B188&SUBSYS_00000000&REV_00\3&61AAA01&0&08
Driver: F:\WINDOWS\system32\DRIVERS\VIAAGP1.SYS, 5.01.0000.3442 (English), 7/2/2003 04:42:00, 27904 bytes
Name: VIA Standard Host Bridge
Device ID: PCI\VEN_1106&DEV_7282&SUBSYS_00000000&REV_00\3&61AAA01&0&07
Driver: n/a
Name: VIA Standard Host Bridge
Device ID: PCI\VEN_1106&DEV_4282&SUBSYS_00000000&REV_00\3&61AAA01&0&04
Driver: n/a
Name: VIA Standard Host Bridge
Device ID: PCI\VEN_1106&DEV_3282&SUBSYS_00000000&REV_00\3&61AAA01&0&03
Driver: n/a
Name: VIA Standard PCI to ISA Bridge
Device ID: PCI\VEN_1106&DEV_3227&SUBSYS_00000000&REV_00\3&61AAA01&0&88
Driver: F:\WINDOWS\system32\DRIVERS\isapnp.sys, 5.01.2600.0000 (Dutch), 9/6/2001 18:20:18, 36352 bytes
Name: VIA USB 2.0 Enhanced Host Controller
Device ID: PCI\VEN_1106&DEV_3104&SUBSYS_70201462&REV_86\3&61AAA01&0&84
Driver: F:\WINDOWS\system32\drivers\usbehci.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:38, 26624 bytes
Driver: F:\WINDOWS\system32\drivers\usbport.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:44, 142976 bytes
Driver: F:\WINDOWS\system32\usbui.dll, 5.01.2600.2180 (Dutch), 8/4/2004 01:03:24, 76288 bytes
Driver: F:\WINDOWS\system32\drivers\usbhub.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:44, 57600 bytes
Driver: F:\WINDOWS\system32\hccoin.dll, 5.01.2600.2180 (English), 8/4/2004 01:03:12, 7168 bytes
Name: VIA OHCI Compliant IEEE 1394 Host Controller
Device ID: PCI\VEN_1106&DEV_3044&SUBSYS_702D1462&REV_46\3&61AAA01&0&70
Driver: F:\WINDOWS\system32\DRIVERS\ohci1394.sys, 5.01.2600.2180 (English), 8/3/2004 23:10:10, 61056 bytes
Driver: F:\WINDOWS\system32\DRIVERS\1394bus.sys, 5.01.2600.2180 (English), 8/3/2004 23:10:08, 53248 bytes
Driver: F:\WINDOWS\system32\DRIVERS\nic1394.sys, 5.01.2600.2180 (English), 8/3/2004 22:58:30, 61824 bytes
Driver: F:\WINDOWS\system32\DRIVERS\arp1394.sys, 5.01.2600.2180 (English), 8/3/2004 22:58:30, 60800 bytes
Driver: F:\WINDOWS\system32\DRIVERS\enum1394.sys, 5.01.2600.0000 (English), 8/17/2001 23:46:40, 6400 bytes
Name: VIA Rev 5 of later USB universele host-controller
Device ID: PCI\VEN_1106&DEV_3038&SUBSYS_70201462&REV_81\3&61AAA01&0&83
Driver: F:\WINDOWS\system32\drivers\usbuhci.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:38, 20480 bytes
Driver: F:\WINDOWS\system32\drivers\usbport.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:44, 142976 bytes
Driver: F:\WINDOWS\system32\usbui.dll, 5.01.2600.2180 (Dutch), 8/4/2004 01:03:24, 76288 bytes
Driver: F:\WINDOWS\system32\drivers\usbhub.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:44, 57600 bytes
Name: VIA Rev 5 of later USB universele host-controller
Device ID: PCI\VEN_1106&DEV_3038&SUBSYS_70201462&REV_81\3&61AAA01&0&82
Driver: F:\WINDOWS\system32\drivers\usbuhci.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:38, 20480 bytes
Driver: F:\WINDOWS\system32\drivers\usbport.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:44, 142976 bytes
Driver: F:\WINDOWS\system32\usbui.dll, 5.01.2600.2180 (Dutch), 8/4/2004 01:03:24, 76288 bytes
Driver: F:\WINDOWS\system32\drivers\usbhub.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:44, 57600 bytes
Name: VIA Rev 5 of later USB universele host-controller
Device ID: PCI\VEN_1106&DEV_3038&SUBSYS_70201462&REV_81\3&61AAA01&0&81
Driver: F:\WINDOWS\system32\drivers\usbuhci.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:38, 20480 bytes
Driver: F:\WINDOWS\system32\drivers\usbport.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:44, 142976 bytes
Driver: F:\WINDOWS\system32\usbui.dll, 5.01.2600.2180 (Dutch), 8/4/2004 01:03:24, 76288 bytes
Driver: F:\WINDOWS\system32\drivers\usbhub.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:44, 57600 bytes
Name: VIA Rev 5 of later USB universele host-controller
Device ID: PCI\VEN_1106&DEV_3038&SUBSYS_70201462&REV_81\3&61AAA01&0&80
Driver: F:\WINDOWS\system32\drivers\usbuhci.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:38, 20480 bytes
Driver: F:\WINDOWS\system32\drivers\usbport.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:44, 142976 bytes
Driver: F:\WINDOWS\system32\usbui.dll, 5.01.2600.2180 (Dutch), 8/4/2004 01:03:24, 76288 bytes
Driver: F:\WINDOWS\system32\drivers\usbhub.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:44, 57600 bytes
Name: VIA Standard Host Bridge
Device ID: PCI\VEN_1106&DEV_2282&SUBSYS_00000000&REV_00\3&61AAA01&0&02
Driver: n/a
Name: VIA Standard Host Bridge
Device ID: PCI\VEN_1106&DEV_1282&SUBSYS_00000000&REV_00\3&61AAA01&0&01
Driver: n/a
Name: VIA Bus Master IDE Controller
Device ID: PCI\VEN_1106&DEV_0571&SUBSYS_70201462&REV_06\3&61AAA01&0&78
Driver: F:\WINDOWS\system32\DRIVERS\viaide.sys, 1.00.0001.0001 (English), 8/3/2004 22:59:44, 5376 bytes
Driver: F:\WINDOWS\system32\DRIVERS\pciidex.sys, 5.01.2600.2180 (Dutch), 8/3/2004 22:59:42, 25088 bytes
Driver: F:\WINDOWS\system32\DRIVERS\atapi.sys, 5.01.2600.2180 (English), 8/3/2004 22:59:44, 95360 bytes
Name: VIA Standard Host Bridge
Device ID: PCI\VEN_1106&DEV_0282&SUBSYS_00000000&REV_00\3&61AAA01&0&00
Driver: n/a
Name: Sound Blaster Live! 24-bit
Device ID: PCI\VEN_1102&DEV_0007&SUBSYS_10061102&REV_00\3&61AAA01&0&30
Driver: F:\WINDOWS\system32\ksuser.dll, 5.03.2600.2180 (Dutch), 8/4/2004 01:03:14, 4096 bytes
Driver: F:\WINDOWS\system32\ksproxy.ax, 5.03.2600.2180 (Dutch), 8/4/2004 01:03:38, 130048 bytes
Driver: F:\WINDOWS\system32\drivers\ks.sys, 5.03.2600.2180 (Dutch), 8/3/2004 23:15:22, 140928 bytes
Driver: F:\WINDOWS\system32\drivers\drmk.sys, 5.01.2600.2180 (English), 8/3/2004 23:08:00, 60288 bytes
Driver: F:\WINDOWS\system32\drivers\portcls.sys, 5.01.2600.2180 (English), 8/3/2004 23:15:50, 145792 bytes
Driver: F:\WINDOWS\system32\drivers\stream.sys, 5.03.2600.2180 (Dutch), 8/3/2004 23:08:04, 48640 bytes
Driver: F:\WINDOWS\system32\wdmaud.drv, 5.01.2600.2180 (English), 8/4/2004 01:03:40, 23552 bytes
Driver: F:\WINDOWS\system32\CtDvInst.dll, 0.00.0000.0008 (English), 7/25/2003 11:35:48, 131072 bytes
Driver: F:\WINDOWS\system32\drivers\ctoss2k.sys, 5.12.0001.0172 (English), 9/22/2003 02:47:38, 178672 bytes
Driver: F:\WINDOWS\system32\drivers\ctsfm2k.sys, 5.12.0001.0172 (English), 9/22/2003 02:48:06, 130192 bytes
Driver: F:\WINDOWS\system32\sfman32.dll, 5.12.0001.0130 (English), 8/17/2001 08:35:46, 36864 bytes
Driver: F:\WINDOWS\system32\sfms32.dll, 5.12.0001.0172 (English), 9/22/2003 02:51:52, 172032 bytes
Driver: F:\WINDOWS\system32\ct2mgm.sf2, 9/22/1999 09:18:00, 2167684 bytes
Driver: F:\WINDOWS\system32\P17res.dll, 5.12.0001.0308 (English), 3/29/2004 04:02:48, 136704 bytes
Driver: F:\WINDOWS\system32\P17.dll, 1.00.0001.0029 (English), 4/8/2004 04:37:40, 60928 bytes
Driver: F:\WINDOWS\system32\drivers\P17.sys, 5.12.0001.0314 (English), 6/4/2004 10:27:46, 840960 bytes
Driver: F:\WINDOWS\system32\drivers\Pfmodnt.sys, 3.00.0000.0003 (English), 3/5/2003 12:19:28, 15840 bytes
Driver: F:\WINDOWS\system32\A3d.dll, 80.00.0000.0003 (English), 4/11/2002 03:41:06, 65536 bytes
Driver: F:\WINDOWS\system32\P17CPI.dll, 1.00.0000.0002 (English), 10/2/2003 12:48:18, 53248 bytes
Name: Ethernet-controller
Device ID: PCI\VEN_10EC&DEV_8169&SUBSYS_702C1462&REV_10\3&61AAA01&0&58
Driver: n/a
Name: PCI standard host CPU bridge
Device ID: PCI\VEN_1022&DEV_1103&SUBSYS_00000000&REV_00\3&61AAA01&0&C3
Driver: n/a
Name: PCI standard host CPU bridge
Device ID: PCI\VEN_1022&DEV_1102&SUBSYS_00000000&REV_00\3&61AAA01&0&C2
Driver: n/a
Name: PCI standard host CPU bridge
Device ID: PCI\VEN_1022&DEV_1101&SUBSYS_00000000&REV_00\3&61AAA01&0&C1
Driver: n/a
Name: PCI standard host CPU bridge
Device ID: PCI\VEN_1022&DEV_1100&SUBSYS_00000000&REV_00\3&61AAA01&0&C0
Driver: n/a
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Help would be very much appriciated, thnx!

The two vis.cards issue is normal, it sees the primary output (VGA) as a device and the TV-out a separate device.
Go to device manager to see if there's any device on ur rig that doesn't have drivers.
Did u install the 4-in1 drivers, get the latest version from the MSI support site.
good luck.

I had installed Adobe CS5 Master Collection on my PC about a year ago, the PC is now dead and i purchased a mac. i just wanted to know if i can download the Mac version and use that cereal number to activate the it? and if yes how and where do i go? wo

i had installed Adobe CS5 Master Collection on my PC about a year ago, the PC is now dead and i purchased a mac.
i just wanted to know if i can download the Mac version and use that cereal number to activate it? and if yes how and where do i go? would appreciate anyones help. Cheers Ron

i just wanted to know if i can download the Mac version and use that cereal number to activate it?
No.
Serial numbers are Mac only or Windows only. There is a platform swap process (from Mac to PC etc) but only for CS6.
As a CS5 owner, your choices are to either pay to upgrade to CS6 for Mac or join the Cloud.

[Athlon64] Fedora Core 4 install on K8T neo2 with 9.1 BIOS?

I'm seeing a strange error when trying to install Fedora Core 4 on my new Athlon 64 box. I had numerous problems with the BIOS that was installed when I got it (3.3) - mostly related to dual channel memory configuration, but I was able to get Fedora Core 4 installed. After upgrading the BIOS to 9.1 I can boot into my installed FC4 and it appears to work well, but the installation crashes when it's trying to mount the initrd RAM disk (I think). I would like to start with a fresh installation because I don't know what state the current instalation is in since it was installed in the middle of experimentation. Does anybody have this working?
My setup is:
K8T neo2
Athlon 64 3000+
2x512 MB RAM
250GB WD ATA Disk
Like I said, it seems rock stable with current install, so I don't think there's any hardware issues. I think it's an incompatibility between the FC4 install kernel and the 9.1 BIOS.
Thanks

Sorry to mention Windows. Most of the folks that I know who run Linux run a Partition with windows as well.
Anyways... The 9.1 Bios is the correct one for you but so far you are the first I have heard from that has tried Linux with that Bios and there well could be a problem. You may want to drop MSI a line as they likely are also unaware of this and it may be a simple fix. However none of the MSI staff read this forum so if you can mail them you will likely get a better responce. Let them know all the pertanent details of course and let us know what you find out as it may help the next person with this problem.

Kingston HyperX 2x 512MB + MSI K8T Neo2 + 3200 Winchester = SERIOUS ISSUE

OK, so thats the spec:
Microstar K8T Neo2
Kingston HyperX DDR 2x 512MB PC-400 (KHX3200ULK2/1G) CL2 (producer's timings : 2-2-2-5-1)
AMD 64 3200 Winchester core CPU
And here's the problem, watch out - its gonna get real wierd from now on :D
First setup: Green Slot 1 + Purpule Slot 1 = system dead
Second: Green 2 + Purp 2 = system dead
Third: Green 2, only one dice installed and heres what happend: It booted (wow!) but.. the system recognizes it as a 256 dice !! I've triple chcecked, its a double sided 512 module! When I insert both modules into green1 and green2 the system sees only 512 megs while it obvioulsly should see 1 GB !
I have totally NO IDEA whats going one. The memory modules had been chcecked on a dual channel Nforce2 with a Barton CPU and it works perfectly at peak timings with the proper memory ammount.
I ask You, what the hell is going on ?

Interestingly enough I have exactly the opposit issue.
With BIOS 3.0 my system detected all the memory.
I updated to 3.2 and now it only detects 1/2 my memory. I tried all the slot swaping same issue.
I've downgraded to BIOS 3.0 and my system randomly shuts off.
K8T Neo2
AMD 64 3000+ Winchster
SimpleTech Dual Channel PC3200 2x512mb DDR400 DoubleSided

K8T Neo2 V2.0 SATA-Problem

Hi Folks,
I got a "problem" with my K8T Neo2 V2.0. At first I had 3 IDE-drives, but I needed a new DVD-burner to read double-layer discs. So I bought a SATA-Drive, plugged it in and it worked good. (VIA 5.13A hyperions). After that I decided to go for a new, bigger, faster harddisk .. also SATA. I wanted to profit from the speed so I made a clean install of Windows XP on that new SATA-drive. BIOS was set to IDE and the Windows-setup recognized the drive correctly without an driver from floppy. Then I used the newly released 5.14A Hyperions and the strangeness began. Suddenly the safe-removal-icon for the SATA drives in the taskbar was gone, no more hot-plug capabillity I thout. I wanted to install a game from DVD and I realized darn slow read-speed from the new DVD-drive. I read only with 3x-speed and double-layer DVDs with 2x. I made a repair-install of Windows XP an rolled back to the 5.13A Hyperions and now my safe-removal-icon and the normal read-speed is back - but now sometimes I get an "program-lag". When I close a programm and want to open an other, or just a menu or something, sometimes the PC don't react for 1-2 seconds.
Any suggestions? Any knowledge about SATA-behavior on the K8T Neo2 V2.0? (or the VIA Hyperions?)

Well here are some specs:
Athlon 64 X2 4200+
2x 512 MB DDR400 RAM, Infineon
1x IDE HDD, Maxtor 6Y120P0
1x SATA HDD, Seagate ST3250410AS16
1x IDE DVD-Drive Pioneer A06S
1x SATA DVD-Recorder Plextor PX-810SA
Creatice SB Live! 5.1
PSU Enermax 350 Watt (EG365AX-VE / 3,3V=32A; 5V=32A, 12V=26A)
Windows XP Pro with SP2 installed on SATA-HDD
The Hyperions from the MSI-Driver CD also don't work (same no-hot-plug-problem).
In the BIOS the SATA-channels are configured as IDE, I never needed a driver floppy for XP-install.
The system event-log only shows one failure "loading of boot- or systemdriver viamraid failed". When I had my old XP install on the IDE drive (with installed 5.14A hyperions) the VIA V-Raid utility was installed and could be started, the hot-plug-ability was working as I plugged in the DVD-Recorder. Then I installed XP on the new SATA-HDD (with plugged in dvd-recorder) and the problems came up. Also now no via vraid-utility is installed.

MSI K8T Neo2 F 939 pin, any known video or other driver issues?

Using a MSI K8T Neo2 F, AMD 64 3500+ winchestor, 1gb DDR400 3200 memory, New WD 740GD SATA HDD, ATI 9800 GT Pro 256 videocard. Fresh XP Pro SP2 install with all the update, latest Via 4 in 1s.
Seems like my problems began when I upgraded video drivers to either Cat 4.9s or 5.1s (ATI Radeon 9800 GT Pro 256) in order to get Doom3 running as it wouldn't run on the v 3.4 drivers that came on the cd-rom with the videocard.
HL2 would play fine with those old drivers. After upgrading to newer drivers, HL2 and Doom 3 (which now at least plays) won't play for more than 5 minutes yet other games will. The same videocard (perhaps 3 months old now) with cat 4.9 drivers ran perfectly in my old system so I know the videocard's still OK.
I can use a restore point prior to installing the newer drivers BUT that doesn't solve the problem as to why I can't use the newer drivers.
I've heard where some have problems with XP SP2 vs SP1. Anyone here have opinions on that?
I have spare HDDs so I can use one with another fresh XP install, even try just SP1 if that'd matter? Doing that would eliminate hardware as being an issue.
It's now not just games either, it'll crash doing Turbotax and other (not demanding) times when not gaming. Games put alot of demand on any system.
Have also tryed another PSU, now an Antec Truepower 430W vs a cheaper brand 550W. Not heat related as I've tryed this with a house fan blowing on high directly at the mobo, cpu side (cover's off).
I've been trying to solve this for about a month now and it's very annoying.
I ran Memtest for 8 hours last night, no errors so the memory's OK. I'm now running another test program called Prime95 via advice from someone at Anandtech.com. http://forums.anandtech.com/messageview.aspx?catid=32&threadid=1513208
If ANYONE here has seen anything like this relating to this motherboard (which I suspect might be a problem?), please share your thoughts.
Thanks

Can you explain where I'll find "VPU recover (adapter settings)"? In display settings or ATIs cat. control center, guessing? I'm at work now but will check that soon.
AGP fast-write has been off.
As for going back to older video drivers, it did seem OK with the old Cat. v3.4 drivers that came on the videocards driver cd-rom and played HL2 fine with those drivers HOWEVER, Doom3 doesn't run with those older drivers and needs the newer drivers to function.
When it crashes, the screen usually goes to black (not BSOD). Sometimes it'll just freeze with skipping sound for a few seconds before going black, sometimes it'll reboot but usually I just reboot it. Can't 3 finger solute to task manager or Esc out of it either.

K8T Neo2 .. Posts, but won't boot the operating system

Hi Folks,
New here. I've got a good one which I may have caused by experimenting with Dynamic overclocking at various levels.
After a normal Post, and noting that all 4 diagnostic leds are lit ( operating system booting ), the screen just goes blank.
- Reset CMOS and Dos Flashed the BIOS to 3.3 ( K8T Neo - F ) to no avail.
The other kicker is that if I try booting from the DVD (IDE Master) drive with an XP OS disk, After "press any key to boot from CD" followed by " Inspecting system configuration" .. or something like that ... again ... the screen goes blank. Dat's it. Any Ideas ?? Ugh.
Here's my machine:
[Athlon64 3500 90nm (Winchester)
K8T Neo2 - F ('64 Socket 939)
1Gb OCZ 500mhz DDR ( this is overkill for this board ... live and learn )
Evga 6800GT
One SATA Seagate 120GB Hard Drive
ASUS DVD Writer
LiteOn Combo DVD/CDRW
LiteOn DVD
Generic 6 in 1 Floppy Drive
Rosewill 500W PSU
Generic? Winmodem

Fafner,
Ok. Here's the scoop. Before reading your last reply ( also I already tried another SATA cable ), I left the SATA enabled in the BIOS, but disconnected the SATA cable from the SATA Drive. Sure enough, the XP Setup flies through all the way untill the ' Install or ' R ' recover ' option screen is displayed. The only other time I got this far was when I disabled the SATA controller in the BIOS. So now, again, with this controller enabled, but the Drive cable disconnected from the Drive, Setup goes as far as it can. Sounds like I somehow fried the SATA Drive .. eh ?
mdak

K8T Neo2 + 4GB RAM + W2K= Freeeze...

Have installed brand new machine to run FEM analyzes. Needs LOTS of RAM to do that.
This is my hardware:
K8T Neo2
2x Twinmos PC3200 2048MB dual pack (4 x 1GB RAM) (CL3)
2x SATA disks running in RAID 0
Geforce 6800GT
CD ROM etc
Hiper HPU-4R480: 480W +5V-32A,+12V - 18A+16A, -12V-0.8A,+5VSB-2.5A,+3.3V-28A
With any RAM chip installed alone (RAM = 1GB) and any combination of pairs - (RAM=2GB) dual channel or single channel everything works great!
But 4GB installed gives me problems with network, video etc.
My question is:
Will 4GB work using Win 2000 or Win XP Pro - Ever?!? Or should this work? Is my problems a windows problem or a hardware problem?
Does anyone know?
Thanks!

It should, U might need a bios flash, what version are you on.
Is it possible to run the 4 sticks without the vid card, or another card ?
Can u run it in single channel ?
If all af the sticks work in together in dimm 1 and 3 in dual channel, u can rule out the memory as cause.
Twinmos has caused problems in the past. Imho they should be over now..

K8T Neo2-F + Liveupdate

Hi. I just got a 3200 venice for my k8t neo2-f, and I need to update the bios.
I was just wondering why liveupdate does not show any of the 9 series bioses...
If there is no way to winflash the bios (prefered, noting the risks) how would I flash from a CD (I have no floppy)

Quote from: Tiresmoke on 26-January-06, 08:32:37
OK now let Live Update create a flash disk with 3.x...
Remember, he doesn't have any FDD.
@ranciddy,
Do you have some CD burning software handy, that is capable of creating a bootable CD? Maybe you need an image of a bootable floppy, these you can get on www.bootdisk.com Some CD burning apps like Nero also have images of bootable disks incorporated.
Next: is there any FAT32 formatted partition on your HDD? That would make anything easier.
At first, download the required BIOS update from MSI website, unpack it to a convenient folder (like D:\BIOS or so) using your favourite unzip-tool.
Then create a bootable CD project with your burning app. Put the BIOS-folder into the project window and select some bootable floppy image as source for the boot files. Please refer to the documentation of your burning software.
Then boot from that CD, change to the drive you stored your BIOS update and run it from there.
If you don't have a FAT32 formatted drive, you need a boot floppy image, that contains CD-ROM drivers.
Apparently it's easier to install a FDD;) but "Geiz ist Geil"
Michael

Small problems : K8T Neo2-F v2.0

Hi there !
I just got and build yesterday my K8T Neo2-F v2.0 with Athlon processor, and had some problems mounting the board.
First problem : I have a Lian Li PC V1000 case, and this case is coming with frontal connectors :
- Power LED, which is a 3 pins connector (with only pins 1 and 3 wired) ... so where do I connect this, since on the mainboard, this is a 2 PIN connector as far as I see ?!?
- Power SW : I have connected this ... but what is it used for ?!?
- USB2.0 : 2 USB front connectors that I connected to the JUSB1
- IEEE 1395 : This is also a front connector for Firewire (I think) with SHIELD, VP, VP, TPB-, TPB+, VG, VG, TPA- and TPA+ ... where do I connect this ??
Also, I have frontal audio out and in, but it is said that If I connect it to the mainboard (where there are default jumpers), the output will not be redirected anymore to the back panel ? So it means we can't have both front and rear connecors enabled for audio ?
Otherwise, The PC started fine. I went to the BIOS and saw the CPU Temp to 20 degrees (If I remember well ...) ... just need to re-install windows on the main drive.
Also, I have 1 boot drive and 1 data drive in IDE (That are recognized by windows), but also a data drive with SATA, that is not recognized yet by windows ... I guess I just need to press the magic key during boot process to enable RAID, right ?
Many Thanks for your help,
cdelecole

Its kinda sorted now, basically moving all dvdroms onto an addon ide card, and the system now boots everytime.
Its been a weird problem, and I suspect a bios issue, but as the system is now working my friend is happy.

K8T-Neo2 system POSTs but no BIOS

Hello all,
Assembled a new system (specs below). When I attempt to boot it, I get a single short beep (=POST ok, right?) and the MSI / Core cell logo screen, but can't get to BIOS, let alone open the DVD-ROM tray to load O/S CD. D-Bracket shows
RG, where R=red and G=green
GG
which the manual translates as: "Boot Attempt: This will set low stack and boot via INT 19h."
On the front panel the HDD activity light is on.
System details:
Motherboard: MSI K8T Neo2-F MS-6702E Ver 1
BIOS Type/Revision: Unknown, whatever came loaded on a new board. Cleared via the jumper.
CPU: AMD Athlon 64 3000+, Venice Core, AMD stock heatsink and fan
RAM: Corsair Value Select; currently one 512MB stick in slot 2 (also tried in slot 1)
Video card: Jaton 3DForce FX5700LE
Power Supply: Antec Smart Power 350W
+3.3V @ 22A; +5V @ 21A; +12V_sub_1 @ 10A; +12V_sub_2 @ 15A. +5v/+3.3V max 130W
HD: Western Digital WD1200JB, 120GB, 8Mb Cache on IDE1 (master). New drive, nothing on it.
DVD-ROM: Lite-On SOHW-1633S on IDE2 (master)
O/S: Not loaded yet! Will be Ubuntu linux.
Things that I have tried:
-Started with both sticks of RAM in slots 1 and 3 and system wouldn't even post. Removed one stick and I'm at the situation described above.
-Cleared CMOS
-Disconnected combined floppy / flash card reader drive from cable and power supply
-Swapped keyboards. Note, no mouse connected.
-Set jumper on HD to master (previously no jumper installed per Western Digital manual for single drive on IDE channel)
Any ideas what the problem is, and how to fix it? My own best guess is that the Venice core CPU isn't compatible with the BIOS. I saw that the new BIOS came out recently. Should I try flashing the latest BIOS in, and if so, how do I do it on a non-functioning system?
Thanks!

Situation update:
I tried unplugging the HDD IDE cable, and am now able to get into BIOS (thanks Ui30!). Unfortunately, there are still some problems. BIOS fails to auto-detect the HDD as Primary Master and DVD-RW as Secondary Master. I set them to type 9 per the Western Digital install guide, and CD/DVD-ROM, respectively. (If someone knows what number to enter for "write precompensation" I have the rest of the info to manually configure the HDD). I cannot edit the boot sequence in BIOS to include these devices.
On the next boot attempt with HDD reconnected, BIOS reports "Primary Master HDD Error" and "Secondary Mater is ATAPI incompatible". However, it is trying to read the floppy drive, and I have included it as the 1st item in the boot sequence. On subsequent boot attempts without the HDD connected, BIOS looses my settings and reverts to "no device" for the Primary Master.
The BIOS is A6702VMS V3.4B2, dated 2/25/05. Is flashing the most recent BIOS likely to help any of these problems? I plan to do this eventually anyway for dual channel memory support. Is bootstrapping it now off the floppy likely to cause problems worse than what I'm facing already?
D-Bracket still reports
RG
GG
I tried limiting the RAM to DDR200, but that didn't seem to do anything over the auto mode.
System gives one short beep during POST, then 2 short beeps, a pause, and 1 more beep when it tries to read the DVD-ROM. I still can't eject the DVD tray, but since BIOS isn't recognizing the DVD drive, that's not too surprising.
So, what else should I try? The goal is of course for the system to recognize the DVD-ROM and HDD so I can proceed with loading Ubuntu.
Thanks again!

MSI K8T Neo2 constant hangup

OK, so I changed my motherboard a few days ago, and got myself a MSI K8T Neo2 card, with the AMI bios ver.3.31a
I put in my old 2 x Apacher 256mb pc 2700 ram (single side) in there, and tried to add in some other ram, but it failed.
I also got my 350powersupply running on it. (It says 5v, 3.3v and 12v on the side, saw someone asking about that in another tread, if that helps)
So now I get to boot all the way into windows (XP SP2 btw), and I even get it running for a long while (sometimes)
Like last night, it was up all night doing recovery from a old HD, that took 7-8hours, and no brakedown.
However, when I try to do normal things... like open a folder, there is a 1 in 20 chance (about) that it will hang.. Same with watching a movie, while watching it will just hang.
So when starting a program/task, running a program/task, ending a program/task. There is always a chance of frezzing up.
Anyone got any idea of what the problem is?

35A, 28A, 17A, 0.3A, 0.8A, 2A
I'w been thinking about a ram problem, seeing how the ram is old, and most people complain over the fact that Ram prevents booting (not a problem) and makes the system unstable (just my problem).
Video driver/card problem never crossed my mind.. it's nvidia.. the most streamline drivers out there.
There is no cpu drain, and no apps that are not responding. I have been having this problem all the way since I did a clean install of windows, so I don't think it's a program problem.
However.. I found the first sign of "always" crash last night.
If I wanted to play Evil Genius, and I had a file application started, (emule or Ares) It would hang before it could load up, always. If I had them turned of, then it would have a far bigger chance of starting and running normaly.

Newbie install - K8T Neo2 now dead?

Similar Messages

Maybe you are looking for