K8t neo2-FSR random restart problem

Hi.
Yesterday I bought k8t neo2-FSR and AMD64 3000+. System restarting randomly. I found that agp and lan controller sharing same IRQ. I disabled the LAN and onboard audio from bios. Update bios to 3.3. Now there is no IRQ conflict. But it is still restarting randomly. I've checked the voltages wth MSI CORE CENTER. there is no problem.
Any ideas?
Thanks for replies.
MSI K8T NEO2-FSR (BIOS 3.3)
AMD64 3000+
AOPEN 300 W POWER
2X512 KINGSTON DDR3200
LEADTEK FX5600 VGA (A310 VIVO)
80 GB ATA133 HDD
AUDIGY ES SOUND CARD
LG CDROM
PHILIPS DVD-RW
XP PRO (SP2)

I've checked the memories with memtest and got too many errors. . I've moved DDR's to slots 2-4 froom 1-3. And checked again with memtest. Still errors. I've removed one module and test again still errors. I think my DDR's and Neo2 are not happy together. RAM timings for Kingston KVR400X64c3a/512 is 3.3.3.8. Help need.
Connected USB devices; ADSL router, MS Joystick, MS Mouse
Thanks for replies.

Similar Messages

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.

K8T-Neo2 (939) mobo + RAM problem

Hi there..sorry if this is covering old ground with this mobo but here goes :(
I've had my MSI board for about a year and a half now running with 1gig(2x512mB) of Hynix PC3200 DDR400 SDRAM. I've recently decided to upgrade to 2gigs of ram and after fiddling with a 1gig stick that didn't want to work I grabbed another pair of Hynix 512mB sticks. I've tried all manner of configurations to get all four DIMMs working but to no avail. When the ram is placed old_old_new_new i get a fail to POST and a top left Green light on the diode with three reds (does that make sense) which means early chipset initialisation according to the manual.
When I place old_new_old_new the machine POSTS, gets to the windows loading screen, then goes black, flicks and stalls.
I've followed the instructions in the manual but it pretty much says I should be able to place the *identical* sticks in all 4 DIMMs without a problem. Any help would be greatly appreciated :( :(
System:
MSI K8T-Neo2 939 (BIOS 3.30)
AMD Athlon64 3000+
Antec 350W PSU
Hynix PC3200 DDR400 SDRAM (currently works with 2x512mB)
Hope thats enough information..

Several things.
You may have the wrong Bios for your CPU core but to determine that we need to know which Bios and CPU core you have.
Your PSU is way to lite to handle the load. You need 24 or more amps on the 12v rail and no 300w will have that.
You can not use three sticks of ram ever on this dual channel board. Actually it is the CPU that forces that limit as the memory controller is inside of the CPU. You can use 1, 2, or 4 sticks but never 3.
Memory should be matched and 4 sticks can force you to run at DDR333 so best to go with 2 - 1gb sticks in any case.
Mixing Memory make and model rarely works as each model will have somewhat different chips and timings. Stay with memory that is match for dual channel to work right.

MSI K7N2 DELTA -L (601-6570-020) nFORCE 2 DUAL 400 , RANDOM RESTART PROBLEM (WinXP,Win98)

Machine Specs:
- AMD Athlon XP 2600+ With L2 512 KB (Model 10)
- MSI K7N2 Delta -L nFORCE 2 Ultra 400 (601-670-020) (My AwardBios is updated to v5.7, Using nVIDIA`s O/B Audio and Ethernet Controllers)
- TwinMOS PC3200(CL2.5) 512 MB DDR400 RAM (Desktop Series)
- Samsung SpinPoint (SP0411N) 40 GB 7200 Rpm HDD
- GeForce2 MX400 64MB AGP 4x (Oem Manufacturer)
- Samsung SyncMaster 753s 17" Monitor
- Sony 52x Cd-Rom
- Philips Stereo Headphones
- Windows XP Home Edition Turkish (Service Pack 1 Turkish) , I did all of critical and other updates ,Totally up to date.Device drivers are too...(nForce 3.13 whql International,Forceware 56.72 whql International)
Problem :
- ERROR EVENT : 1003 ERROR NAME : IRQL_NOT_LESS_OR_EQUAL
Original Error Texts:
A problem has been detected & Windows has been shut down to prevent damage to your computer.
IRQL_NOT_LESS_OR_EQUAL
If this is the first time you've seen this Stop error screen, restart the computer. If this screen appears again follow these steps.
Check to make sure any new hardware or software is properly installed. If this is a new installation, ask your hardware or software manufacturer for any Windows updates you might need. If the problem continues, disable or remove any newly installed hardware or software.
Disable BIOS memory options such as caching or shadowing.
If you need to use safe mode to remove or disable components restart your computer, Press F8 to select Advanced Start-up options & select Safe Mode.
Technical Information :
*** STOP: 0x0000000A (0x00000004, 0x00000002, 0x00000001, 0x804F1473)
Beginning dump of physical memory
Physical memory dump complete. Contact your system Administrator or technical support group for further assistance.
After restarting manually from the PC. I get the following message
The system has recovered from a serious error.
BCCode : a BCP1 : 00000004 BCP2 : 00000002 BCP3 : 00000000
BCP4 : 804F1ADA OSVer : 5_1_2600 SP : 0_0 Product : 256_1
C:\WINDOWS\Minidump\Mini042202-01.dmp
C:\DOCUME~1\DANIEL~1\LOCALS~1\Temp\WER3.tmp.dir00\sysdata.xml
And when I check EVENT VIEWER
Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 22/04/2002
Time: 5:55:03 PM
User: N/A
Computer: XXX-BOX
Description:
Error code 0000000a, parameter1 00000004, parameter2 00000002, parameter3 00000000, parameter4 804f1ada.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 30 30 30 30 30 30 30 0000000
0020: 61 20 20 50 61 72 61 6d a Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 30 34 2c 20 000004,
0038: 30 30 30 30 30 30 30 32 00000002
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 30 2c 20 38 30 34 66 00, 804f
0050: 31 61 64 61 1ada
I installed 6 operating systems on my pc (WinXp Home Edition Turkish/English,WinXP Pro Turkish/English,Win98 Turkish/English) and tested it, but every time i meet the same thing (MS Blue Screen Of Death Sux...).I checked the WinXP`s logs and searched for error code`s meaning from microsoft knowledge database. They are saying nothing about this problem but the problem`s root is coming from a bad device driver. It seems to be a generic problem for all operating systems cuz all of them were restarting themselves randomly, before i close "auto-restart on critical errors" option.After i saw some messages on forums , i searched for my RAM maker`s home page then i learned that my RAM is assembled with VIA KT Series and SIS chips & optimized for them. I think nForce is too picky about rams.But i aint sure about where the hell is this problem coming from. If you guys are sure about that is an unsupported ram problem and knew the list of ram marks&models that supported by MSI K7N2 Delta -L ,please help me about this damn problem. Thanks for your help.
Note : I tried Asus Ati Radeon 9200SE 64mb g.adapter (some peoples told me thats about g.adapter), but problem continued.

If I read correctly in your specs I see only 11 Amps on the +12v Rail. Is this correct?
If so, I'd advise a PSU that has at least 18 amps on the +12v Rail, perhaps as low as 16 with the other rails to match as shown currently in your spec.
11 Amps is just way too underpowered for that rig. I am surprised it even boots.
At what point does the BSOD occur?

K8T NEO2 dual core upgrade problems

Hi Everyone hope someone can help here I have just purchased a dual core 4200 socket 939 for my 6702e it has been running fine on my 3200 the 4200 is the one with the 2 512k cache if that helps.
I have the latest bios through msi update think 9.40 so here is my issue. As I have stated this runs no problems at all with my single core 64xp but once I put the new processor in no boot or anything not even an error beep, all the indicator lights on the back panel go amber. I have cleared the cmos and installed 1 stick in the second purple slot 1 gig still nothing.
Any help would be appreciated and thanks in advance.

Quote from: HenryW on 28-March-08, 09:46:59
Is the X2 4200+ new or did you buy it used from eBay or some such? What does it show for BIOS version at the upper left when you boot the PC? I ask this just to confirm you do indeed have 9.4 BIOS.
Make a signature with PC information. Also include specs for PSU from label on it, see my sig. example of what info to provide. By making signature your specs will show in every post you make.
To create signature:
Click on PROFILE above (near top of this page) and then in your "Profile" what I show in red below, scroll down to "Signature" and enter your specs in the box and then click on "Change profile" button on the bottom.
Rebooted to make sure hehe yepper 9.4 bios
Also fixed signature to the best of my knowledge.
Thanks again for the reply and yes this is a used processor off of ebay reputable seller with no negatives so he has a DOA clause but just trying to trouble shoot this so I don't have egg on my face before I ship it back
Profile Info
Summary
Show Stats
Show Posts
Modify Profile
Account Related Settings
Forum Profile Information
Look and Layout Preferences
Notifications and Email
Personal Message Options

[Athlon64] K8T Neo2 -FSR Promise 20579 x64 Driver Here

I HAVE THE PROMISE RAID DRIVE FOR WINDOWS X64. I HAVE NOT TRIED IT YET BUT I HAVE LOOKED AT THE FILE CODE AND IT IS THE X64 BIT DRIVER FOR THE 20579 CONTROLLER.
I HAVE POSTED DRIVER AT DRIVER GUIDE http://members.driverguide.com/driver/detail.php?driverid=454385
COPY LINK TO BROWSER TO GET IT.

Why would you post it in a members only area?

MacBook Pro 15 inch Mid-2010 keeps randomly restarting

So, I got this Macbook back in August of 2010, and this random restart problem just started occuring after I updated to Mountain Lion. It usually occurs when I open up heavy usage applications, such as Photoshop, iMovie, iPhoto, FaceTime,etc. When I just solely decide to turn on my MacBook to just use Safari and iTunes, it never restarts, or it will once in a blue moon. Also read a page Apple posted about MacBook Pro 15 inch Mid-2010's having problems and that they would fix it free of charge, but I'm not sure if that relates to my problem? --link here --> http://support.apple.com/kb/ts4088
I tried resetting the SMC, and NVRAM/PRAM. Even verfied disk permissions and repaired on Disk Utility, nothing changed.
Could anyone help?

If you have more than one user account, you must be logged in as an administrator to carry out these instructions.
Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
Select the most recent panic log under the heading System Diagnostic Reports on the left. If you don't see that heading, select
View ▹ Show Log List from the menu bar. Post the entire contents of the panic report — the text, please, not a screenshot. In the interest of privacy, I suggest you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header and body of the report, if it’s present (it may not be.) Please don't post shutdownStall, spin, or hang reports.

K8T NEO FSR problems and questions.

I read this in an article on http://www.hardware.no:
"MSI is one of the companies that offer free upgrade to a new motherboard with better
specifications, if you have bought 915P Neo2 Platinum, 915P Combo-FR or 915G Combo FR
in the period of time between 21st and 27th june."
Late in june, I bought myself MSI K8T Neo-FSR motherboard, and an Athlon 64 3200+2.2GHz.
When I run "Core Center", the program shows that my CPU idle temp is 60 Celsius and my
sys temp is 36 degrees, which is COMPLETELY wrong?!?!.
This is very weird, because I have a nice computer case with 5 fans that blow out all
the warm air inside. When I play games, the CPU goes up to 65 degrees and my computer
restarts. This is VERY annoying. How do you turn this off in BIOS settings?
I'm quite frustrated with the thought that my CPU temp. shows 60-70 Celsius.
I have read tons of other forums and I have found out that it's not only me that experience
this problem. I seriously hope that you will fix this bug ASAP.
Does this offer also apply to K8T NEO-FSR? Can I get a free upgrade?
If I don't get my problems fixed, I will take further actions.
My System specifications:
MSI K8T NEO-FSR, Athlon 64 3200+2.2GHz, Asus Geforce 4 Ti 4400, TwinMOS 1024 DDR3200 RAM, Western digital 80+120+80 GB 7200 RPM, Chieftec BX Tower BX-03SL-SL-SL P4 / AMD, 2x papst 120mm fans, 2x 80mm papst fans, 1 fan in the door of the computer case.

I never heard MSI was doing such an offer...
Anyway, you need the latest BIOS, that solves the temps reading thing, this happens because AMD changed the CPU a bit.
It's not getting that hot, it's just a reading failure.
A BIOS flash should solve it.

K8T800 K8T NEO-FSR Memory Problems

Just a warning before I start in, this is a pretty long post. I'm going to try to include all the information I can.
Here's my system right now. It's running Windows XP Professional with all the latest updates.
Processor: AMD Athlon 64 3000, 512KB L2 Cache 64-bit Processor. Not overclocked at all.
Motherboard: MSI K8T800 K8T NEO-FSR, latest BIOS updates from MSI
Video Card: ATI RADEON 9800PRO Video Card, 128MB DDR, latest Catalyst drivers from ATI installed. Not overclocked at all.
Memory: Mushkin 184 Pin 2x512MB DDR400 PC-3200, running at DDR400 with Auto selected for all the memory timings in the BIOS. Memory placed in DIMM#1 and DIMM#2. Not overclocked at all.
Hard Drive: Western Digital 80 Gig
I started experiencing random reboots and critical errors in game applications on Sunday. The computer would randomly reboot at random intervals from Windows. In addition, while running games like Warcraft 3, Asheron's Call, or World of Warcraft I would receive frequent critical errors that certain sections of the memory could not either be read or written to.
I figured that there was some kind of problem with the memory, so I downloaded Memtest86 and ran it. The first stick of RAM was in DIMM#1 and the second stick in DIMM#2. This was the memory configuration during all the random reboots and critical errors.
Memtest86 came up with several failures during the 5th phase of the test. The same failures came up upon repeated testing in the same phase of the test. I decided to try to isolate the failure and see if one stick or the other was defective. I yanked out the second stick from DIMM#2 and left the first stick in DIMM#1. The first stick (which I'll refer to as the "good RAM stick") passed the memtest repeatedly. I then stuck the second RAM stick into DIMM#1 alone and the computer would not even POST.
I then moved the second RAM stick (which I'll refer to as the "bad RAM stick") over to DIMM#2 alone and managed to get it to POST. The bad stick failed the memtest with the exact same errors during the same phase of testing as the combined sticks had failed during the initial test. For the sake of completeness, I moved the bad stick over to DIMM#1 alone and finally managed to get it to POST. However, the bad stick passed the memtest repeatedly. Puzzled, I moved the bad stick over to DIMM#3 alone and tested it there, which it also passed repeatedly. I moved it back into DIMM#2 alone and it failed the test repeatedly again and again.
Intrigued, I then moved the good RAM stick into DIMM#2 alone, to try to see if perhaps there was some kind of motherboard error occurring. The good stick passed the memtest repeatedly in DIMM#2. I then moved the good stick into DIMM#3 alone and it passed the test repeatedly in that slot.
After checking the motherboard manual to make sure I could do it, I put the bad stick in DIMM#1 and the good stick in DIMM#3 and ran the memtest. The combined sticks passed the test where previously, while configured in DIMM#1 and DIMM#2, they had failed it. I moved the sticks back into DIMM#1 and DIMM#2 to test again. The combined sticks failed as they had during the initial test.
I then reconfigured the sticks to DIMM#1 and DIMM#3 again and booted up the system. Although I only had limited testing time last night, I seemed to be totally stable. The system did not reboot at all and I actually managed to play WoW for an hour without a single crash.
Any suggestions on what's occuring? I figured that maybe the mobo's memory seating in DIMM#2 was messed up, but I wanted to get some more guidance from others.

Well if it's an Antec Sl-350, that one only has 16A @ 12V, way too little to handle your system.....
I would get another PSU in any case, as even the TP-380 is bare minimum.....
Go for the Enermax 465 it has 33A @ 12V and then you are sure it's not a power problem...
Also, a good PSU is never a waiste of money

BIOS problems with K8T Neo2

K8T Neo2, AMD64 3400, 2x 512 3200 DDR (slots 1 & 3), PNY nVidia Quadro FX500, WD Caviar 60GB.
The system will not boot (cold or warm) without first clearing the BIOS via the JBAT. If I try to restart the system, the LED panel shows four red (processor error). If I clear the CMOS, it will post then say that there was an error in the BIOS. It will then ask if I want to enter the setup (F1) or load defaults and continue (F2). If I go into the setup, make any changes (even just the date and time) and restart the system, it won't post until I clear the CMOS again.
The owner is getting fed up and is threatening to go buy a Dell, so any help would be very much appreciated!!!
- Justin

Pete,
Quote from: Pete67890 on 16-March-05, 07:53:07
Not sure how good the beta version is, after flashing I am unable to get the system to post.
Have you tried bootblock-programming, as described somewhere on MSI website? FDD is needed for that.
Quote
Talked with MSI and they are sending me another board and instructed me to re-flash with the same file (3.34). Apparently it resolves an issue with endusers using an AMD 64 3400+ chip
This is a CPU that is intended to be sold to OEMs like HP/Medion only. It runs only with 600MHz HTT. Maybe you should ask your dealer to replace that with a retail CPU, e.g. 3200+ with Winchester Core.
Quote
and more importantly (see my thread) will fix my problem of not being able to save CMOS settings.
That might be a problem related to the "wrong" CPU, IMHO.
Quote
*One other note, MSI said that I need to change the front side bus to 800 for these processors not 1000 as the default would have it.... If its not changed the system wont post.
Indeed - had you been able to enter BIOS setup previously? If yes, then try flashing BIOS 3.30 using the Boot Block method and set your HTT to 800. Maybe then you will be able to save your BIOS settings.
Quote
If you still want the file, I could send it to you, but use it at your own risk..just post your email.
I am still interested, just use the "PM"-or Mail-button on the left. Thanks in advance.
Greets,
Michael

My mbp randomly restart (attached the problem report)

can someone help me to find out what cause my mbp randomly restart?tks!!
Interval Since Last Panic Report: 679540 sec
Panics Since Last Report:          8
Anonymous UUID:                    1360F7D0-6AEC-B609-DEB0-3D16BE57A1BF
Tue Sep 10 19:15:49 2013
panic(cpu 2 caller 0xffffff7fa1612f1a): "GPU Panic: [<None>] 5 3 7f 0 0 0 0 3 : NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0xd2000000 0xffffff81101bd000 0x0a5480a2, D0, P3/4\n"@/SourceCache/AppleGraphicsControl/AppleGraphicsControl-3.4.5/src/AppleM uxControl/kext/GPUPanic.cpp:127
Backtrace (CPU 2), Frame : Return Address
0xffffff8107a2b710 : 0xffffff801f41d626
0xffffff8107a2b780 : 0xffffff7fa1612f1a
0xffffff8107a2b850 : 0xffffff7f9fbc9f1e
0xffffff8107a2b910 : 0xffffff7f9fc9e12d
0xffffff8107a2b950 : 0xffffff7f9fc9e18e
0xffffff8107a2b9c0 : 0xffffff7f9ff64ed0
0xffffff8107a2baf0 : 0xffffff7f9fcc6a75
0xffffff8107a2bb10 : 0xffffff7f9fbd0d50
0xffffff8107a2bbc0 : 0xffffff7f9fbce7d0
0xffffff8107a2bdc0 : 0xffffff7f9fbcf845
0xffffff8107a2bea0 : 0xffffff7f9fb6b0a4
0xffffff8107a2bef0 : 0xffffff7fa15d60df
0xffffff8107a2bf40 : 0xffffff7fa15d51e7
0xffffff8107a2bf60 : 0xffffff801f43e25e
0xffffff8107a2bfb0 : 0xffffff801f4b3137
      Kernel Extensions in backtrace:
         com.apple.NVDAResman(8.1.2)[96AE69DE-8A37-39D0-B2D3-D8446A6AA670]@0xffffff7f9fb 68000->0xffffff7f9fe0dfff
            dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7f9f972000
            dependency: com.apple.iokit.IONDRVSupport(2.3.7)[6C8CFC18-75F0-3DEF-86C7-CEB2C1FD6BB1]@0xff ffff7f9fb54000
            dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[990D1A42-DF16-3AB9-ABC1-6A88AC142244]@0 xffffff7f9f99b000
         com.apple.driver.AppleMuxControl(3.4.5)[49FEF732-D7A3-327B-A7AA-6AC5A6E3DCFF]@0 xffffff7fa1605000->0xffffff7fa1617fff
            dependency: com.apple.driver.AppleBacklightExpert(1.0.4)[1D0BB11E-7D71-34CF-ACC3-57DF01CADA 08]@0xffffff7fa1600000
            dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7f9f972000
            dependency: com.apple.driver.AppleGraphicsControl(3.4.5)[4A2C8548-7EF1-38A9-8817-E8CB34B8DC A6]@0xffffff7fa15ec000
            dependency: com.apple.iokit.IOACPIFamily(1.4)[A35915E8-C1B0-3C0F-81DF-5515BC9002FC]@0xfffff f7f9fabe000
            dependency: com.apple.iokit.IONDRVSupport(2.3.7)[6C8CFC18-75F0-3DEF-86C7-CEB2C1FD6BB1]@0xff ffff7f9fb54000
            dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[990D1A42-DF16-3AB9-ABC1-6A88AC142244]@0 xffffff7f9f99b000
         com.apple.nvidia.nv50hal(8.1.2)[988EAF3A-3318-3787-8A5A-844830FA1522]@0xffffff7 f9fe19000->0xffffff7fa00edfff
            dependency: com.apple.NVDAResman(8.1.2)[96AE69DE-8A37-39D0-B2D3-D8446A6AA670]@0xffffff7f9fb 68000
            dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7f9f972000
         com.apple.driver.AGPM(100.12.87)[A7004F02-7D39-3398-8BD3-729DCC404E5F]@0xffffff 7fa15d4000->0xffffff7fa15e3fff
            dependency: com.apple.iokit.IOPCIFamily(2.7.3)[1D668879-BEF8-3C58-ABFE-FAC6B3E9A292]@0xffff ff7f9f972000
            dependency: com.apple.driver.IOPlatformPluginFamily(5.3.0d51)[2C131EAF-F74C-39D1-A702-A499B 39C293C]@0xffffff7fa0573000
            dependency: com.apple.iokit.IONDRVSupport(2.3.7)[6C8CFC18-75F0-3DEF-86C7-CEB2C1FD6BB1]@0xff ffff7f9fb54000
            dependency: com.apple.iokit.IOGraphicsFamily(2.3.7)[990D1A42-DF16-3AB9-ABC1-6A88AC142244]@0 xffffff7f9f99b000
BSD process name corresponding to current thread: kernel_task
Mac OS version:
12E55
Kernel version:
Darwin Kernel Version 12.4.0: Wed May 1 17:57:12 PDT 2013; root:xnu-2050.24.15~1/RELEASE_X86_64
Kernel UUID: 896CB1E3-AB79-3DF1-B595-549DFFDF3D36
Kernel slide:     0x000000001f200000
Kernel text base: 0xffffff801f400000
System model name: MacBookPro6,2 (Mac-F22586C8)
System uptime in nanoseconds: 3138898049871
last loaded kext at 1509372005675: com.apple.driver.AppleUSBEthernetHost          2.3.6 (addr 0xffffff7fa1717000, size 28672)
last unloaded kext at 1634035335921: com.apple.driver.AppleUSBCDC          4.1.23 (addr 0xffffff7fa1714000, size 12288)
loaded kexts:
com.splashtop.driver.SRXFrameBufferConnector          1.6
com.splashtop.driver.SRXDisplayCard          1.6
com.Cycling74.driver.Soundflower          1.5.2
com.apple.driver.AppleUSBEthernetHost          2.3.6
com.apple.driver.AppleHWSensor          1.9.5d0
com.apple.filesystems.autofs          3.0
com.apple.iokit.IOBluetoothSerialManager          4.1.4f2
com.apple.driver.AGPM          100.12.87
com.apple.driver.AppleMikeyHIDDriver          122
com.apple.driver.AppleHDA          2.3.7fc4
com.apple.iokit.BroadcomBluetoothHCIControllerUSBTransport          4.1.4f2
com.apple.driver.AppleMikeyDriver          2.3.7fc4
com.apple.driver.AppleLPC          1.6.0
com.apple.driver.AppleSMCLMU          2.0.3d0
com.apple.driver.AppleMuxControl          3.4.5
com.apple.driver.AppleIntelHDGraphics          8.1.2
com.apple.GeForce          8.1.2
com.apple.driver.AppleSMCPDRC          1.0.0
com.apple.driver.AppleUpstreamUserClient          3.5.10
com.apple.driver.AppleMCCSControl          1.1.11
com.apple.driver.AudioAUUC          1.60
com.apple.iokit.IOUserEthernet          1.0.0d1
com.apple.Dont_Steal_Mac_OS_X          7.0.0
com.apple.driver.ApplePolicyControl          3.4.5
com.apple.driver.ACPI_SMC_PlatformPlugin          1.0.0
com.apple.driver.AppleIntelHDGraphicsFB          8.1.2
com.apple.driver.SMCMotionSensor          3.0.3d1
com.apple.driver.AppleUSBTCButtons          237.1
com.apple.driver.AppleUSBCardReader          3.1.7
com.apple.driver.AppleUSBTCKeyboard          237.1
com.apple.driver.AppleIRController          320.15
com.apple.iokit.SCSITaskUserClient          3.5.5
com.apple.driver.XsanFilter          404
com.apple.iokit.IOAHCIBlockStorage          2.3.1
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless          1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib          1.0.0d1
com.apple.BootCache          34
com.apple.driver.AppleUSBHub          5.5.5
com.apple.driver.AppleFWOHCI          4.9.6
com.apple.driver.AirPort.Brcm4331          615.20.17
com.apple.driver.AppleAHCIPort          2.5.2
com.apple.driver.AppleUSBEHCI          5.5.0
com.apple.iokit.AppleBCM5701Ethernet          3.6.1b4
com.apple.driver.AppleSmartBatteryManager          161.0.0
com.apple.driver.AppleEFINVRAM          1.7
com.apple.driver.AppleRTC          1.5
com.apple.driver.AppleACPIButtons          1.7
com.apple.driver.AppleHPET          1.8
com.apple.driver.AppleSMBIOS          1.9
com.apple.driver.AppleACPIEC          1.7
com.apple.driver.AppleAPIC          1.6
com.apple.driver.AppleIntelCPUPowerManagementClient          196.0.0
com.apple.nke.applicationfirewall          4.0.39
com.apple.security.quarantine          2.1
com.apple.driver.AppleIntelCPUPowerManagement          196.0.0
com.apple.kext.triggers          1.0
com.apple.iokit.IOSerialFamily          10.0.6
com.apple.driver.DspFuncLib          2.3.7fc4
com.apple.iokit.AppleBluetoothHCIControllerUSBTransport          4.1.4f2
com.apple.nvidia.nv50hal          8.1.2
com.apple.iokit.IOFireWireIP          2.2.5
com.apple.driver.AppleHDAController          2.3.7fc4
com.apple.iokit.IOHDAFamily          2.3.7fc4
com.apple.driver.AppleSMBusPCI          1.0.11d0
com.apple.driver.AppleBacklightExpert          1.0.4
com.apple.driver.AppleSMBusController          1.0.11d0
com.apple.iokit.IOAudioFamily          1.8.9fc11
com.apple.kext.OSvKernDSPLib          1.6
com.apple.iokit.IOSurface          86.0.4
com.apple.iokit.IOBluetoothFamily          4.1.4f2
com.apple.driver.AppleGraphicsControl          3.4.5
com.apple.driver.IOPlatformPluginLegacy          1.0.0
com.apple.driver.IOPlatformPluginFamily          5.3.0d51
com.apple.NVDAResman          8.1.2
com.apple.iokit.IONDRVSupport          2.3.7
com.apple.iokit.IOGraphicsFamily          2.3.7
com.apple.driver.AppleSMC          3.1.4d2
com.apple.iokit.IOSCSIBlockCommandsDevice          3.5.5
com.apple.iokit.IOUSBMassStorageClass          3.5.1
com.apple.driver.AppleUSBMultitouch          237.3
com.apple.iokit.IOUSBHIDDriver          5.2.5
com.apple.iokit.IOSCSIMultimediaCommandsDevice          3.5.5
com.apple.iokit.IOBDStorageFamily          1.7
com.apple.iokit.IODVDStorageFamily          1.7.1
com.apple.iokit.IOCDStorageFamily          1.7.1
com.apple.driver.AppleUSBMergeNub          5.5.5
com.apple.driver.AppleUSBComposite          5.2.5
com.apple.iokit.IOAHCISerialATAPI          2.5.1
com.apple.iokit.IOSCSIArchitectureModelFamily          3.5.5
com.apple.iokit.IOFireWireFamily          4.5.5
com.apple.iokit.IOUSBUserClient          5.5.5
com.apple.iokit.IO80211Family          530.4
com.apple.iokit.IOAHCIFamily          2.3.1
com.apple.iokit.IOEthernetAVBController          1.0.2b1
com.apple.iokit.IONetworkingFamily          3.0
com.apple.iokit.IOUSBFamily          5.6.0
com.apple.driver.AppleEFIRuntime          1.7
com.apple.iokit.IOHIDFamily          1.8.1
com.apple.iokit.IOSMBusFamily          1.1
com.apple.security.sandbox          220.3
com.apple.kext.AppleMatch          1.0.0d1
com.apple.security.TMSafetyNet          7
com.apple.driver.DiskImages          345
com.apple.iokit.IOStorageFamily          1.8
com.apple.driver.AppleKeyStore          28.21
com.apple.driver.AppleACPIPlatform          1.7
com.apple.iokit.IOPCIFamily          2.7.3
com.apple.iokit.IOACPIFamily          1.4
com.apple.kec.corecrypto          1.0
Model: MacBookPro6,2, BootROM MBP61.0057.B0F, 2 processors, Intel Core i7, 2.66 GHz, 8 GB, SMC 1.58f17
Graphics: Intel HD Graphics, Intel HD Graphics, Built-In, 288 MB
Graphics: NVIDIA GeForce GT 330M, NVIDIA GeForce GT 330M, PCIe, 512 MB
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1067 MHz, 0x80CE, 0x4D34373142353237334348302D4346382020
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1067 MHz, 0x80CE, 0x4D34373142353237334348302D4346382020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x93), Broadcom BCM43xx 1.0 (5.106.98.100.17)
Bluetooth: Version 4.1.4f2 12041, 2 service, 11 devices, 1 incoming serial ports
Network Service: iPhone 2, Ethernet, en3
Serial ATA Device: M4-CT512M4SSD2, 512.11 GB
Serial ATA Device: MATSHITADVD-R   UJ-898
USB Device: hub_device, 0x0424 (SMSC), 0x2514, 0xfa100000 / 2
USB Device: iPhone, apple_vendor_id, 0x12a0, 0xfa140000 / 6
USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0236, 0xfa120000 / 5
USB Device: BRCM2070 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0xfa110000 / 4
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8218, 0xfa113000 / 7
USB Device: Internal Memory Card Reader, apple_vendor_id, 0x8403, 0xfa130000 / 3
USB Device: hub_device, 0x0424 (SMSC), 0x2514, 0xfd100000 / 2
USB Device: Built-in iSight, apple_vendor_id, 0x8507, 0xfd110000 / 4
USB Device: IR Receiver, apple_vendor_id, 0x8242, 0xfd120000 / 3

You're having the 'bad' NVIDIA card kernel panics...
Mid-2010 15" MacBook Pros - the bad NVIDIA GPU
If you're having frequent kernel panics with your 15" mid-2010, or intermittent screen problems, the problem is, more than likely, the faulty NVIDIA GPU found in a number of those machines.
Here's just a sample of a kernel panic log that points to the faulty NVIDIA card:
Kernel Extensions in backtrace (with dependencies):
         com.apple.GeForce(6.4.0)@0x82ac4000->0x82b7afff
            dependency: com.apple.NVDAResman(6.4.0)@0x834a0000
            dependency: com.apple.iokit.IONDRVSupport(2.2.1)@0x82fd3000
            dependency: com.apple.iokit.IOPCIFamily(2.6.5)@0x7a802000
            dependency: com.apple.iokit.IOGraphicsFamily(2.2.1)@0x8301b000
         com.apple.nvidia.nv50hal(6.4.0)@0x83c05000->0x84019fff
            dependency: com.apple.NVDAResman(6.4.0)@0x834a0000
         com.apple.NVDAResman(6.4.0)@0x834a0000->0x8378dfff
            dependency: com.apple.iokit.IOPCIFamily(2.6.5)@0x7a802000
            dependency: com.apple.iokit.IONDRVSupport(2.2.1)@0x82fd3000
            dependency: com.apple.iokit.IOGraphicsFamily(2.2.1)@0x8301b000
Here's the "official" Apple take on the issue - but the very real kernel panics need not be preceded by 'Intermittent black screen or loss of video'... in fact, you might not experience any video problems at all. Although video problems can certainly be a portent of things to come…
So what can you do? Print out a copy of your kernel panic and a copy of the Knowledge Base article and take them, along with your machine, to your local Apple Store or an Apple Authorized Service Provider. They should be more than willing to install a new logic board at no cost. I have no idea why this faulty GPU is making the headline here on the MacBook Pro forum so often now - could it be because Mountain Lion is just bringing the issue to a head more readily? I don't know - I only know that we're seeing more and more of these kernel panics of late.
Good luck,
Clinton

K8T Neo FSR with Audigy 1 Problem

I just received a major upgrade, for me anyway, last night. ALL I was getting on boot was 4-RED LED lights on the D-Bracket2 connector. I was ready to RMA the WHOLE thing to Tiger Direct, when I decided in one last ditch effort to try again.....I pulled my Audigy, and wham, it booted normally. Now let me describe.
1. I KNOW it's not a power issue, as I had EVERYTHING but Sound and Video removed, and unplugged, including hard drives. The D-Bracket2 LED's were still all-red on boot.....system would not POST.
2. Pulled ALL hrdware from system, except Video and Audigy, same results.
3. Last try, pulled EVERYTHING, including Audigy, and it booted normally.
4. Re-connected everything, except Audigy, re-installed Windows XP SP2, no problems, system runs.
I tried EVERY PCI slot with the Audigy, ALL with the same results; system would not run with it in there. The card was good 15 minutes prior on the OLD Abit Board. (meaning it works.)
ANy ideas???
System Specs:
K8T Neo FSR MB
Athlon64 2800+ CPU
GeForce Ti 4200 128MB Video
512MB Mushkin Green Memory (1 DIMM)
Maxtor 160GB HD
WD 20GB HD
45X CD-ROM
24X CD/RW (Sony)
onboard NIC, Sound (Audigy problem made me resort to the onboard sound)

Suggestions:
http://www.tigerdirect.com/applications/SearchTools/item-details.asp?EdpNo=1104458&CatId=1078
The above might be only 420W but it has 18 amps under 12+, which is fine for your setup.
http://www.newegg.com/app/ViewProductDesc.asp?description=17-148-002&depa=1
http://www.tigerdirect.com/applications/SearchTools/item-details.asp?EdpNo=719596&CatId=1079
http://www.tigerdirect.com/applications/SearchTools/item-details.asp?EdpNo=719582&CatId=1078
http://www.tigerdirect.com/applications/SearchTools/item-details.asp?EdpNo=1120272&CatId=1078

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.

MSI K8T Neo2 slow SATA problem

Hello members,
I do have a MSI K8T Neo2 mainboard with Via chipset. The board supports SATA 150. AFAIK this means it should support transfer rates up to 150 MB/s.
Now Ive bought a SATA3 SSD with over 500 MB/s. Because SATA 3 is downcompatible to SATA 1 its working so far.
The only problem is I expected 150MB/s but I do only get about 115 MB/s with benchmark programs like HD Tune and AS SSD Benchmark in sequential read.
I do have the latest drivers and bios updates but it seems MSI SATA controllers is very slow.
Can anyone help me getting it faster?

Thank you.
Does this mean in praxis I dont get 150 MB/s ?
Is this general or only MSI specific?

Problem with my older K8T Neo2-Fir or my bios?

Hi there Friends
Can someone help me with a problem i got. I have installed this video card:
Sapphire Radeon X1950 Pro 512MB DDR3 / AGP / 2xDVI / TV-OUT
On this older motherboard: K8T Neo2-Fir [Gbe Lan;IEEE1394, SATA RAID] Socket 939.
Do I need a Bios upgrade because this board seams only supporting max 256mb of video memory. Doesn`t this motherboard and bios version supporting 512 mb?
What should I doing to be able to change my settings in bios to the correct size for the memory. From 256 to 512 mb
This is my bios: Amibios Bios 9.10
Someone help me with this problem

Quote from: Mr Freddy on 03-November-07, 04:39:19
Thats correct, and i want to setting the right memory size in bios, but i cant doing that in my bios. The maximum value i can choice is 256mb. Do you understand wath i mean? Why cant i change this settings to more than 256mb? Is this because this bios are not supporting more than 256mb? (sorry for my bad english)
"Thats correct, and i want to setting the right memory size in bios, but i cant doing that in my bios."
That do NOT setup VGA memory size...
"The maximum value i can choice is 256mb. Do you understand wath i mean? Why cant i change this settings to more than 256mb?"
because there no need to be more than 256...
"Is this because this bios are not supporting more than 256mb?"
that setting doesn't affect VGA memory size...(you can't change VGA memory size, its fixed...) for your VGA with 512MB memory you should apply 64MB for AGP aperture size.

K8t neo2-FSR random restart problem

Similar Messages

Maybe you are looking for