MSI Ti 4200 random lockups

Ive been trying to get a GeForce 4 to work in my computer for over 3 months now and I am getting very frustrated. First I had a Visiontek Ti 4200 64Mb with a Soyo Dragon+ mobo and that would lockup any time I tried to play a video game. The screen would get covered with colored blocks and i would have to do a hard reboot. Then I decided to get a new Epox 8K5A2 mobo and used that with the Visiontek card and it still did the same lockups. I sold the Visiontek card and now I have an MSI Ti 4200 64Mb card and that is doing the same thing too. Last week I bought an Epox 8K3A+ because I had seen websites using it with the exact same videocard for benchmarks so I figured it has got to work. Got the board yesterday and guess what, it does the same damn thing as the others. I have a 600W Robanton powersupply that is designed for high-end servers. It puts out 40A at +3.3v and 60A at +5v so it can't be my powersupply. I tested both cards in my parents PC which has a Duron 750 and an Epox 8KTA3 mobo(350W Codegen PSU) and they worked perfectly. Any help would be greatly appreciated.
Athlon XP 2000+
Volcano 7+ CPU cooler
Epox 8K3A+, Epox 8K5A2, Soyo Dragon+
MSI GeForce 4 Ti 4200 64Mb
512Mb Mushkin DDR 266
80Gb Seagate 7200rpm HDD
Lite-On 16xDVD and 16x CDRW
Netgear FA311 NIC
600W Robanton PSU

I upgraded my mobo to its latest BIOS version and it still didn't work so I swapped out my XP 2000+ for a Duron 750 and that still didnt work. Then I swapped my PSU for my parents 350W Codegen PSU and it works , no lockups. I just ran through 3Dmark2001 and it actually made it all the way thru. 8o Now I'm gonna swap the Duron 750 out and put my Xp 2000+ back in and I'll see if that works. If not then I'm gonna have to buy a new PSU. I'm gonna need some suggestions from people who have similar systems(Athlon XP, DDR mobo, GeForce4)

Similar Messages

[A64] RS480 random lockups, hard crashes, rebooting, freezing

Now that I've got your attention, specs:
AMD A64 3200+ rev. e (Venice)
MSI RS480, bios ver. 3.4
2x512 Corsair Value Select Dual Channel kit PC3200 CAS2.5
Leadtek PX6600GT Extreme (550/1100 stock)
SB Live! Value
WD 80GB 7200rpm 8mb cache IDE ATA100
Seasonic SS-380 (25a on 12v rails, 380w total)
Pioneer DVR-109
Inwin S500T mATX case
Nexus 92mm CPU fan on Thermalright XP-90 heatsink
I've been experiencing random lockups and restarts in 3d apps & games (Battlefield 2, Warcraft 3, Warhammer 40k: Dawn of War, GTA:SA) since I built this system back in May. I'm so sick of this computer right now that I could happily take a sledge to it and reduce it to rubble.
Symptoms:
1) Random reboots and lockups, *not* due to heat. Heat prior to lockups using Speedfan has the CPU consistently around 50 C and the video card consistently at 40-45 C. Needless to say, these are very cool temps, but an extra case fan was added to make sure that air flow in case was good.
2) Motherboard RMA'd after purchase - simply refused to post.
3) RAM RMA'd after about a month after several dozen memtest86 errors found. New RAM has been tested - each stick individually & together - and no errors after testing each configuration for 12 hours.
4) Video card RMA'd after massive heat spikes (upwards 120 C) detected. New video card arrived yesterday & have had one lockup since, which wasn't unusual with old setup. Problem still remains.
5) Sound card was removed for testing when lockup in #4 above occurred, which leads me to believe that my POS SB Live isn't the problem. Too bad, as it would have been a terrific excuse to upgrade to an Audigy 2 ZS.
6) When video card was removed, system was rock solid, not a single crash. With video card in, crashed all the time prior to RMA, and once in two days after new one received. While the old video card certainly appeared to have problems, I'm hesitant at this point to put all my problems on the video card. Is this an erroneous assumption?
7) At least eight or nine different Forceware versions were used for testing; different driver versions did not prevent crashes.
Now, it hasn't crashed again (which means nothing; it's been a couple of hours) since disabling SATA in bios and downloading & installing AMD driver for processor. Will be moving RAM from slots 1 & 2 to 3 & 4 shortly. Before my sanity is finally and truly lost, is there anything else that anybody can think of to stop these hard locks? I'm off to move the RAM around and do some further testing, but any advice whatsoever would be absolutely terrific. Thanks!
(topic title changed. apparently some people thought I was kidding.)

Quote from: Tiresmoke on 28-July-05, 02:39:59
Well yes it could be the RAM. For what it is worth everyone I have seen with Kingmax RAM seems to be happy and so far as I know it works with all the cores. It is also not very expensive stuff. Hope that helps.
Kingmax, eh? I'll see if I can find any (I'm in Canada). Do you know how good their customer service is?
I think that before I try to pick up some new ram I'll send Corsair an email; according to their site, the VS is supposed to be compatible with the RS480, which is one of the reasons I bought it. Who knows; maybe they'll upgrade the RAM that I've got for cheap. But thanks for the advice!
Quote from: dannol48
FYI...you're not the first to report problems trying an nVidia gForce video card on this motherboard (ATI surroundview enabled Xpress 200 chipset).
If you didn't notice, the Compatibility Report posted for the board ONLY has ATI Radeon cards.
Bloody hell! Why didn't I check that? Well, I gotta think about this some more. Good grief. Thanks for bringing this to my attention!

MSI G4 4200 Reviews

Where could I find MSI G4 4200 64MB Reviews?

try Here
or Here
or this one is for a 128mb here
My personal opnion is forget about the 64mb version just go and get a 128mb version. it will be more helpful in the long run
for more info just do a google search fo msi geforce 4 ti4200 reviews

Msi kt3 ultra, msi gf4 4200 tvout problem

I have a msi gf4 4200 64mb card and i have a msi kt3 ultra aru and windows xp,
my problem is tv out is garbled in pal , ntsc is grey (iam in europe), the colours seem inverted blues are red, etc and theres a ghosting effect around moving images like in videos or around the cursor
Ive tried everything from default mem setting , to high performance , tried diferent driver sets , tried windows 2000, tried via chipset drivers, latest msi, nvidia gf drivers, pal b , g , i , 60hz, diferent resolutions, clone view, single output to tv, stretch view , nothing seems to fix it, the only thing that comes close to fixing it is using the tvtool http://tvtool.info/ with color fix correction activated, but the images isnt stable its got a weird strecthing, shimmering effect on the bottom half of the tv image
Iam sure that the problem is not tv or cable related because i tried a friends p4 (board msi sis 645dx) with the exact same model gf4 4200 (not my one) with my scart cable and tv set up and it worked fine.
Could it be a voltage problem? ive even tried upping agp and core voltage a bit to see if helps, and nothing

mhuizing,
nope havent tried a diferent tv , but it should work , i tested the connection with a friends computer
exact same gfx card model and it worked fine!
My old system leadtek gf3 ti200 , epox 8kha+ worked fine with this connection.
Iam using a scart cable to a video , then from the vid to the tv via antena cable
i upgraded and voila, i got some headaches for free :P !!!

Msi g4ti 4200 64mb/128mb ddr

:O msi g4ti 4200
i am currently trying to install a msi g4ti 4200 card using win98se as os after installing the drivers 4 it it locks up and only way to exit out is to go back in safe mode and removing the card i have tried it with a gigabyte 7vtxe+ and revieved the same result and also tried it with an asus a7333 board no joy with that i have also tried different os i have also tried the detonator drivers of this site i have also tried a 128mb please can some1 help me out with this problem
thanks..
mebz (spotonuk.com)

Yes the cooler fan is working fine
Yes I did try it on another PC and the problem of lines running down the screen persisted.
Yes it must be the agp card.

MSI TI-4200 Win 98SE Rebooting

I needed to create a Window 98SE disk so I can play some of my games that don't work on XP Pro. I have used the latest drivers, but after I installed the drivers for the card, the PC reboots and goes into safe mode. On my XP drive, it all works great. How can I find out what the problem is? How can I fix this so I can get to playing my games again?
Thanks, Dean.
FYI ...
nVidia 45.23 drivers
Intel 845PESV board with Pentium 4 3.06 Mhz
1 GB ram
WD 80GB hard drive

Ok, my current confuguration is as follows:
Intel DE845PESV motherboard
Intel Pentium 4 3.06 Mhz(533 FSB)
1 GB of Kingston 133mhz DDR ram
MSI TI-4200 Geforce 4 128mb graphic card
Turtle Beach Santa Cruz sound card
Compaq DVD-117 DVD drive
Liteon LTR-48246s CDR-W drive
Sony Floppy drive
Windows 98 SE
Promise Ultra ATA-133 (Tx2)
After some additional research, I believe the problem is with the nVidia drivers. I removed the drivers and had Windows configure the card as a standard VGA display card. Then everything boots OK, but only 16 colors. As soon as I install any version (I tried 40.71, 44.03 and 45.23) of the nVidia drivers, the PC re-boots with a problem loading ndis2sup.vxd. I don't know where to go from here.
The games I want to play are Mechwarrior 2 Titanium additon and Mechwarrior 3. I have tried many configurations in XP but no good. So I figure a drive with Windows 98SE will do the trick. I have everything loaded except the graphics card.
Is there any more info you need to help me?

Msi g4ti 4200

i am currently trying to install a msi g4ti 4200 card using win98 as os after installing the drivers 4 it it locks up and only way to exit out is to go back in safe mode and removing the card i have tried it with a gigabyte 7vtxe+ and revieved the same result and also tried it with an asus a7333 board no joy with that i have also tried different os i have also tried the detonator drivers of this site please can some1 help me out with this problem
thanks..
mebz (spotonuk.com) :O

mebz,
I since you have a Video Card question and you posted in the nVidia/AMD/SiS Motherboard Forum, I moved the thread to Multimedia forum for you.
Take Care,
Richard

MSI Ti-4200 TD GPU GRAPHICS "LAGGNESS"

I have bought the MSI Ti-4200 TD about 2 months ago and have installed it to my new D.I.Y computer. But it does noe seem to be running smoothly when I play games on my computer. For example, even for games like Warcraft III, C & C Generals and RalliSport Challenge. I have encounter small jams here and there during gameplay and the worst is in Rallisport Challenge where "laggness aka big jams and distortion" occurs at every 10 to 15 secs f gameplay which cause "dizziness" ...
I have even download the following driver for update on the GPU and things seems worst. After I have uninstall the old driver from my Win2K and install the fresh new driver, I have found that the system does not indicates whether my GPU is running under 2x or 4x AGP under Control Panel > MSI Information. I am unable to adjust my MSI Clock settings as an error message appearing says that "DirectDraw Init Failed. The sample will now exit". I do not have this problem with the previous driver. ?(
Below is my com specs.
Abit SA-7 SIS654D MB 533 FSB
Intel P4 2.4GHz CPU 533 FSB with SSE2
Kingston PC2700 512MB DDR SDRAM
MSI Ti-4200 TD 128MB DDR GPU
PCI 56Kbps Modem
Samsung SyncMaster 753DF Monitior
1 x Maxtor 80GB HDD
1 x Seagate 10.2GB HDD
1 x Samsung CDRW drive
1 x MSI DVD drive
1 x 420watts PSU
nVidia driver version 6.13.10.4107
VGA Bios version 4.25.00.29.00
running on 800 by 600 res. @ 72Hz 16bit colors
Full hardware acceleration
Best Mipmap detail
Performance - balanced
Antialiasing - 2x
Anisotropic filtering - off
DirectX 8.1
MSI memory clock @ 446MHz
MSI Core Clock @ 250MHz
Hope someone could find me a cure. Thanks :D

Well... Thanks for your advice, but I have already formatted my computer and re-install everything. Though now my computer and the GPU works well :] and perform rather well, but I will still take your advice to heart when the next time I come across this problem again. )
May I ask to confirm again? Is is that if I meet up with this problem, I will go to my DxDiag and de-activate my Direct Draw >> Restart my computer >> Re-activate my Direct Draw >> Restart my computer. Am I right?
Thanks again for your help :D !!!

Bad keyboard causing random lockups and not allowing booting up?

Will a bad keyboard, or keyboard port, make a computer lockup and keep it from rebooting?
I have a slimline s3200n that has been having random lockups. When I try to reboot it, it gets stuck at the startup screen (the one where you get the F9, F10, etc options). I can hit F9 for hours and the computer does nothing. I have to do another hard shutdown and if I wait for a little bit the computer will start back up again. Will work fine, then randomly lockup and go through the cycle again.
I tried to run the Hardware diagnostic utility but it gave me an error, didnt write down the exact error, but it was a timeout error while gathering hardware information.
I am using the keyboard that came with the computer and I do not have another keyboard to use for a test.

I have this exact same issue, and am wondering what to do. I have a 2.2 GHz Intel Core 2 Duo and am using 10.4.11 as software. I have a Dell monitor. Anyone have any thoughts?

865P NEO random lockups.

Hi Folks,
It's been two days now that I have tried every possible system component stress test, voltage and configuration adjustment and even clean Windows 98SE installation tests in order to eliminate or at least locate the cause of random lockups sometimes in games, sometimes even just at system idle.
My system configuration is:
Enermax 300 Watts PSU
865P NEO (not NEO 2) Bios v1.1
Pentium 2.4B 533Mhz bus (no overclocking done)
ThermalTake Spark 7 Cooler
Two Kingston DDR 333Mhz sticks in Dual Channel mode
ATI Radeon 9700 Pro
Seagate Barracuda 40Gb
Sound Blaster Audigy sound card
Liteon 48x24x48 CDRW
I know these kind of problems are the most difficult to detect, so any idea at this moment is very welcome. All I can say is that all these components were tested also on an ASUS P4S800 without any single issue, what leads me to think of a possible falty motherboard.
Thanks in advance for sharing you experiences.
Gig

Hi NovJoe,
Thanks for you kind response. I discarded in the first place the PSU, as I mention in my message, due to the fact that the same components worked using the same PSU on an ASUS P4S800 flawleslly. Besides, if you calculate the total power consumption of the components I have, taking in account that in some stress tests like (3DMark) not all are involved, I think you'll agree that the PSU it's not an issue.
As a matter a fact, yesterday i finally managed to eradicate those mind buggling random lockups selecting the Performance Mode in the BIOS and setting the CPU voltage to 1.575. As opposite of the Fail Safe Mode, the other one brought much more stability to the system, but watching closely the voltages, I have note an incredible CPU voltage drop to almost 1.44V. I know, you'll say: "I told was the PSU", but I did the same test with the ASUS motheboard and the CPU voltage was steady as a rock. So, I said to myself: "We'll let's pump it up a bit to prevent that low voltage drops. Voila, now the variations go between 1.52 and 1.57. Reslult: NO more lockups.
The only thing that remains unanswered to me is if all 865P NEO have that CPU voltage drop issue. So, I kindly invite anyone who is willing to and have a couple of minutes to take peek into the System Health option in the BIOS and post the CPU minimum and maximum voltage ranges.
Thanks once again for your postings.
Gig

6710 Navigator random lockups during navigation

While extensively using the GPS functionality of my new 6710 for the first time this week, I've come across a problem of random lockups during navigation.
There seems to be no obvious pattern to the phenomenon, sometimes it occurs just a few seconds after the route has been calculated and navigation has startet, at other times it occurs after already having navigated a large part of the route.
My subjective impression is, lockups are more likely to occur whenever the device tries to calculate an alternate route (when the user instructed it to do so by selecting the respective option) due to traffic information it received.
After a lockup, the navigation program cannot be closed the usual way (by selecting 'Exit'), but only by pressing the red 'hang up' key; and even then, it stays in memory (it's still in the 'open programs' list). Sometimes, the phone altogether is locked up, only way to "re-animate" it then is to switch it off and on again.
Anyone experienced a similar issue, and/or has an idea what might be the problem here, and how to solve it?

Hello,
When i asked nokia about this problem their reply was: "we don't offer support for third party apps, try using ovi". It didn't matter for them that a NAVIGATOR phone does not support a navigation software, considering that Ovi Maps does not know the street i'm living on, neither 90% of my country.So i can't use Ovi, because it will not take me anywhere.
It is a surprise for me that they even want money for Ovi considering the above.
F'more i tried the new Garmin software version (5.00.60) , but i obtained the same result, even though hanging lessens a little bit.
I even had Garmin on my E50, E51 and N73 but did not had this problem.
I think a new firmware will fix this issue.
Regards,
Cristi.

[SOLVED] Random lockups 3.10.10-1 kernel 64bit

I have for a while random lockups on my system. The whole system halts all i can do is hardreset the system. No keyboard respons at all.
This is Journalctl -r output just before i reset the system. There are over 1000 lines of "kernel: mei_me 0000:00:16.0: reset: wrong host start response"
-- Reboot --
sep 10 12:39:52 asusarch systemd[1]: Started Trigger Flushing of Journal to Persistent Storage.
sep 10 12:39:52 asusarch systemd[1]: systemd-journald.service: main process exited, code=exited, status=1/FAILURE
sep 10 12:39:52 asusarch systemd-journal[1858]: Journal started
sep 10 12:39:52 asusarch systemd-journal[1858]: Allowing system journal files to grow to 8.0M.
sep 10 12:39:52 asusarch systemd[1]: Started Trigger Flushing of Journal to Persistent Storage.
sep 10 12:39:52 asusarch systemd[1]: systemd-journald.service: main process exited, code=exited, status=1/FAILURE
sep 10 12:39:52 asusarch systemd-journal[1854]: Journal started
sep 10 12:39:52 asusarch systemd-journal[1854]: Allowing system journal files to grow to 8.0M.
sep 10 12:39:52 asusarch systemd[1]: Started Trigger Flushing of Journal to Persistent Storage.
sep 10 12:39:52 asusarch systemd[1]: systemd-journald.service: main process exited, code=exited, status=1/FAILURE
sep 10 12:39:52 asusarch systemd-journal[1850]: Journal started
sep 10 12:39:52 asusarch systemd-journal[1850]: Allowing system journal files to grow to 8.0M.
sep 10 12:39:52 asusarch systemd[1]: Started Trigger Flushing of Journal to Persistent Storage.
sep 10 12:39:52 asusarch systemd[1]: systemd-journald.service: main process exited, code=killed, status=10/USR1
sep 10 12:39:52 asusarch systemd[1]: systemd-journald.service: main process exited, code=exited, status=1/FAILURE
sep 10 12:39:52 asusarch systemd-journal[1847]: Journal started
sep 10 12:39:52 asusarch systemd-journal[1847]: Allowing system journal files to grow to 8.0M.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: wrong host start response
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: reset: unexpected enumeration response hbm.
sep 10 12:39:52 asusarch kernel: mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING
Anyone that has an idea what i can do to track down the problem.
Last edited by cecar (2013-09-11 09:22:11)

Blacklist/unload the mei_me module. This may have negative consequences on suspending (though I have noticed no difference on my Core2Duo machine).
When you system locks up, does it really lock up? That is, can you try enabling the Magic SysRq key and then try to use that the next time this happens? I suspect that your userspace might have frozen, but the kernel should still be alive and functioning (otherwise you would typically end up with a kernel panic).
In any case, I don't think that the mei_me thing would cause a total lockup of your machine. Besides the journal being spammed like crazy with those messages, I didn't notice any difference in the functionality of the machine.
Edit: I think that in cases such as this, the simplest thing you can do is change kernels and see if the problem persists. As it is, you have provided no real indication that the issue is even related to the kernel upgrade/version. So downgrade just the kernel and see if the problem persists (or install the [testing] kernel).
Last edited by WonderWoofy (2013-09-10 17:40:13)

Random lockups on X-Fi Driver L

I'm writing this to ask help for a problem that has appeared since my recent upgrade. I had an X-Fi Fatalty on a Socket A Athlon XP 3000+ system which worked perfectly. However since i upgraded to core 2 duo e6600 with motherboard Gigabyte DS4 i have random lockup issues when starting windows. To be more specific, windows would lockup at random times when loading creative volume control at startup. i can still move the mouse but thats it. I have checked for irq conflict and it seems there is none, X-Fi is assigned irq 20 and its the only thing on that irq. i have flashed my motherboard to the latest bios from gigabyte which seems to fix the x-fi redetection problems for this motherboard, but i still have this lockup issue. windows just freezes randomly at startups when loading the x-fi volume control panel. if it doesnt freeze (i am lucky) and it does load it then there is no problem, the xfi works perfectly. I would appreciate it if somebody could help me. thank you.
PS I have changed pci slots, this doesnt fix the problem
PS2: I am not Ocing, i am using latest drivers for everything i have spend 3 days to find a solution so iam saying i have checked a lot of things Message Edited by iceblade on 0-26-2006 04:2 PM

Any help? Would be much appreciated! sry for double posting

Random lockups w/ iPhone 3GS following iOS4 update?

Has anybody else experienced random lockups i.e. icons go gray like program is executing but nothing occurs only solution is to reset. I've also experienced display going black but still slightly illuminated? Reset only solution. Other than that seems all my apps work correctly and complete functionality 99.9% of the time!

Some people havent had one problem when updating to iOS4, others have been over run with problems. I myself have lost virtually all sound from my loud speaker so calls, txt messages and ipod are virtually unheard now..
Went to my local Genius bar in Liverpool today, complete waste of time, the guy restored it like I hadnt already done that a 100 times, then said oh yeah it is qeit not heard of that one before, to get a new one will cost you £139!!
Yeah right mate, not payin that as its not my fault! did ask him if he ever looks on the Apple forum about faults people are having, and I got a blank look. Told him a thread with tens of thousands people all having the same problem with low sound from the speakers and calls being ended in mid conversation since updating to OS4 seems a bit strange then... another blank look!
Ive lost all faith with apple as a company now and will not be upgrading to a iPhone 4 anytime soon or any apple product, no one seems interested in helping but quick enough to take your money, thats my opinion anyway..
Gaz

MSI GeForce 4 TI 4200 and random lockups

Hey guys, i just got a new Geforce card, installed it, and i cant do ANYTHING even remotely related to graphics (even small animated movies on the internet) without a hard lockup or my screen going blank.
GA-7DXR+ (newest bios. (F8, i believe)
350W Power Supply (dunno what brand)
Generic CD-ROM
Plextor 12/10/32 CD-RW
Netgear 10/100 NIC
Soundpbaster 16
Maxtor 80gig HDD
MSI Geforce 4 Ti4200 (128mb DDR RAM)
2 port Firewire adapter (dunno what brand)
edit: 512mb of PC2100 DDR RAM
tia

Orm,
To start with your power supply could be too weak to run the Athlon XP(Guessing you have an Athlon XP) and the GF4 under load. 150W combined and 14A on the 3.3v RAIL is not enough.
You could try removing your your firewire, sound and nic cards, and unplugging your two CD Drives.
See if you can get any farther then. Also get the latest Detonator Drivers from the nVidia Website. They should be on 41.09 now.
Good Luck,
Richard
P.S. Which OS are you running?

MSI Ti 4200 random lockups

Similar Messages

Maybe you are looking for