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

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!

Estimated random IOPS for NL-SAS drives?

Hopefully simple question. I've seen generally accepted values for random IOPS of different speed drives (~80 for 7.2k SATA, ~140 for 2.5'' 10k SAS, ~200 for 2.5'' 15k SAS, etc.).
What is the generally accepted IOPS value for 7.2k NL-SAS drives? I would have figured it would be about the same as 7.2k SATA, but I've been educated through a previous post that NL-SAS can achieve better IOPS through deeper queues? I can't seem to find an IOPS estimate specific to NL-SAS in my googling though.
What value would you use for estimating potential raw capability of an array?
This topic first appeared in the Spiceworks Community

Hopefully simple question. I've seen generally accepted values for random IOPS of different speed drives (~80 for 7.2k SATA, ~140 for 2.5'' 10k SAS, ~200 for 2.5'' 15k SAS, etc.).
What is the generally accepted IOPS value for 7.2k NL-SAS drives? I would have figured it would be about the same as 7.2k SATA, but I've been educated through a previous post that NL-SAS can achieve better IOPS through deeper queues? I can't seem to find an IOPS estimate specific to NL-SAS in my googling though.
What value would you use for estimating potential raw capability of an array?
This topic first appeared in the Spiceworks Community

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 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

Qosmio G10-133: I am having random lockups - Graphic driver issue

Hi
my machine screen goes blank at random and i get the below error message which suggests i need finally the latest graphic driver. Uninstall the Nividea driver from my machine which appeared to fix the problem but my graphics were reduced. I then reinstalled from the Toshiba site the graphic driver and i have the same problem.
Please can you help?
Error caused by NVIDIA Graphics Driver: no specific solution found.
Thank you for submitting an error report.
Problem description:
An unknown error occurred in NVIDIA Graphics Driver, created by NVIDIA Corporation.
Recommendations:
NVIDIA Corporation is currently not aware of a specific solution for the problem that you reported. Below is a list of recommendations to take that may help prevent the problem from recurring.
1. Download and install an updated NVIDIA Graphics Driver from one of the following locations:
Microsoft Update
NVIDIA Corporation
2. If an updated driver is not available, check with your computer manufacturer.
3. If you are running the latest version of NVIDIA Graphics Driver, please contact NVIDIA Corporation for your support options.
Additional information:
If this problem continues to occur with the latest product updates for NVIDIA Graphics Driver we highly recommend you obtain assistance and troubleshooting information directly from NVIDIA Corporation.
If you are not familiar with NVIDIA Graphics Driver and you are questioning how the program was installed on your computer, it is possible that the program was installed with another program. If you do not know why NVIDIA Graphics Driver is running, many programs configure themselves to start automatically every time you turn on your computer.

Hi
I agree with previous comment. We don?t know what did you done with your unit and why the display driver makes problems now. The fact is that you should use the display driver designed by notebook manufacturer and not from graphic card producer.
How to say now what you can do? Advice given by NVIDIA is correct. Try to start the unit in safe mode using F8 key at the start up. From device manager remove listed graphic device or even graphic driver software listed under software in control panel (if you can find something there). Restart the unit and when WXP is loaded try to install Toshiba designed driver again.

Solved\ Random lockups/system freezes AMD 6850 crossfire mode

Hello all,
I have come to these forums because i have a problem for 4 months now and i cant seem to figure out.
First my systemspecs:
Asrock X79 extreme 4 slot 2011 (Bios version 2.0 (latest))
Intel i7 3820
16 Gig Geil 1600 DDR 3 memory (4 dimms)
2 x MSI R6850 Cyclone Power Edition/OC (crossfire mode with bridge)
1 x OCZ agility 3 SATA III 2.5" SSD 120GB (System drive)
2 x Samsung HDD 500GB 7200rpm
TG600-BZ 600 Watt maxx 24 amps
Running Windows 7 64bit
Catalyst 12.6
12.7 CAP1
So my problem:
When i have 2 cards inserted in crossfire mode my system goes true random lock ups and freezes. Up to several times a day.
While heavy load and gaming i sometime hear the system hang for a few seconds (sounds hangs system freezez) and then it continues to run.. usually that happens about 5-6 times before the system hangs locks up and does not respond anymore.. (i can hear the sounds hanging) and have to do a reset.
I had a few BSOD's getting the well know ATIKMPAG.sys error but that happen only twice.
Funny thing is that it does not always does this while under heavy load but also while doing YouTube video's.. even had one while cooking dinner.. (computer not in use).
Seems to be completely random.
So what have i done to fix the problem:
I have done a complete clean install of windows 7 only running basic drivers and hardware.. problem persists
Check system event log on any problems but since it does sudden lockups there are no logs of these hardware events.
Did a check on my power saving options in windows.. made sure all were on performance.
I have run true Catalyst 12.1 to 12.6 and all kinds of cap's.. problem persists
Checked temp, does not come above 70 degrees Celsius. (case temp not above 30)
Made sure i run the latest BIOS version of my motherboard.
Run a 24 hours memory test with memtest86+ no errors.
Did a heavy load and MSI burn in test on the single cards separately from each other continues to run perfectly.
I have run both cards separately from each other in my system (single card mode) for 2 weeks...(both PCIE slots) system runs like a charm.. no lockups no random freezes.
So i hope anyone can help me, i have some experience troubleshooting computer problems but this one has me baffled.
TheAbeL

Quote from: TheAbel on 19-July-12, 14:19:47
This is indeed the Tagan piperock 600 watt. Problem is that i have no idea how much amp my cards are pulling from 1 rail.. are they trying to pull it all from 1 rail? or are they getting power from 2 different rails. If my crossfire setup is pulling al his power from 1 rail i still have a problem..
Also i read in the review (my german is rusty but ok, tnx xmad) that when turbo mode is enabled that all rails work as one rail.. so 80 amp is available? Is this even possibly?
My new PSU will arrive today so i will report tomorrow if it has solved the issue or not.
No, as noted in my last reply for your PSU: "48A combined total for +12V rails". Max for any individual 12V rail is 20A. If three of the rails are loaded to total of 48A then the 4th is useless. You can't just add up 20+20+20+20 & come up with 80, it doesn't work that way on PSU although Antec seems to think so.

Fresh Install Random Lockups

I've been using a Mac since 1997 and I have never seen anything like what my machine started doing yesterday. Yesterday the machine started to randomly freeze up. All windows become unresponsive as do menus and all keyboard commands. The mouse cursor still responds.
The first step I took was to boot from my Snow Leopard disc, rand disc repair and then permissions repair. This did not fix the problem. For some reason the apple menu seems to trigger some of the lockups, but other times it is another app. Finally I backed up my entire user directory. Then I booted from the install disc, erased the hard drive, and installed a clean copy of Snow Leopard.
It was most frustrating when after the clean install the computer froze in the same manner as before. I've tried resetting the PRAM also.
I'm open to any suggestions at this point. I'm an independent web developer, and having my machine down, is giving me an ulcer. Thank you in advance for anyone who can help.

It is possible your hard drive is failing. I had a similar experience a while back. The machine hangs like it does as it is trying to read the hard drive.
I didn't get any other warnings. SMART status was verified and Disk Utility reported no problems.
If you don't already, you might want to make sure you have a backup.

Random Lockups K9N2 SLI Platinum

Hey guys, Ive been dealing with a very annoying issue with a random Windows lockup, when I mean lockup its a press the reset button lockup. At first I thought it was a faulty Hard Drive, I replaced that with a Fresh reload of Windows 7 64 Bit. This issue has been going on for a few months, even before the Hard Drive going bad.. Some days/weeks I can play games without a problem, the lockups only occur within the first 5 to 10 minutes of playing, If I make it past that I am good to go.. In the last week I ran Memtest86 v4.0 and 3dMark Vantage, I got no errors or lockup's on either test.
Right after I ran the 3dMark Test I checked the temp in the bios here is what I found CPU Temp 111 F and System Temp 84 F, Im sure this is higher when Im gaming
I have been also getting this error in the event viewer on a lockup:
Component: AMD Northbridge
Error Source: Machine Check Exception
Error Type: HyperTransport Watchdog Timeout Error
Processor ID: 0
Here is my PC build, Ive been thinking about getting a new case that vents the heat from the top, I think this case I have is storing a lot of heat, the case itself gets very hot while playing games, I have 4 120mm fans running to. I was orginally running SLI with the 9800GT, I rebooted one day and one of the cards went, I sent both back to PNY and got 2 new ones but only put one back in since the heat was just to bad, I have a spare card now.
COOLER MASTER Elite 330 RC-330-KKN1-GP Black SECC ATX Mid Tower Computer Case
MSI K9N2 SLI Platinum AM2+/AM2 NVIDIA nForce 750a SLI ATX AMD Motherboard
AMD Phenom 9950 Agena 2.6GHz Socket AM2+ 125W Quad-Core Black Edition Processor Model HD995ZXAGHBOX
CORSAIR XMS2 4GB (2 x 2GB) 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) Dual Channel Kit Desktop Memory Model TWIN2X4096-6400C5DHX
CORSAIR CMPSU-750TX 750W ATX12V / EPS12V SLI Ready CrossFire Ready 80 PLUS Certified Active PFC Compatible with Core i7 Power
PNY VCG981024GXEB-FLB GeForce 9800 GT Hybrid Power 1GB 256-bit GDDR3 PCI Express 2.0 x16 HDCP Ready SLI Supported Video Card
Western Digital Caviar Black WD5001AALS 500GB 7200 RPM SATA 3.0Gb/s 3.5" Internal Hard Drive
Any help would be appreciated
Thanks

Quote from: GavinMS1 on 25-February-10, 08:17:04
Sounds exactly like the problem I was having when I upgraded to an AM3 965 Phenom-II from an AM2 6000+ and 800MHz DDR2 6GB to 1100MHz DDR2 @1066 8GB all at the same time. All I can suggest is to make sure your motherboard chipset drivers are current. Right now for 750a SLI Nforce the current driver from NVidia is SMBUS Driver (v4.74) WHQL, SMU Driver (v1.71) WHQL. That is in the v15.49 download from the NVidia website. Also make sure your video card drivers are also current. v196.21 WHQL is the latest from the NVidia website for windows 7 64 bit for 9 series cards. another thing you could try is updating you BIOS to the latets version for K9N2 Sli Platinum, it is v3.6. In this website at the top you should see a link to down load the FORUM FLASHER tool made by Svet (Hopefully he posts a reply to this as well, he would most likely be able to help you out more with this). There is also an info page containing instructions on how to use it somewhere on this website as well.
Im pretty good for keeping drivers updated, to double check I downloaded the Nvidia tool to check for updated drivers, says everything is up to date.. I havent updated the bios, Ive done it in the past on other machines and Im always a little scared to do it
I downloaded SpeedFan, here are some temps sitting idle, Im not sure what the temps should be, what do you guys think?
CPU: 163F
Remote Temp: 234F
Temp: 166F
Temp1: 97F
Temp2: 84F
Temp3: 205F
HD0: 100F
Core: 105F

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?

13" Macbook pro random freezing after upgrading hard drive.

i have a 2010 mbp 13" 2.4
I upgraded the hhd from the 250 to a 320 5400 RPM drive i cleared the cache did a clean install of osx 10.6 grabbed all the updates and then rolled my time machine to restore all my files.
But now it randomly freezes for about 4-7 seconds. It's extremely annoying and i can't figure out why. Short of a clean install any ideas on what might fix this?
Thanks

The AHT does test the graphics chips. Run the extended version and see if anything shows up in the form of an error code. Also, there may be a crash log in Console. Try to run something processor intensive so the Mac freezes, and then run the AHT. Heat could be a factor.
Do you have access to an Apple Store? If so, make an appointment at the Genius Bar and bring in your Mac for evaluation. They would probably have a more comprehensive hardware test they could run. If you get any error codes, bring those along.
It sounds like you could have some sort of hardware problem here. Since you are under warranty, it might be time to let Apple diagnose and fix it. It sounds like you may have had video issues during the first week of ownership with the original hard drive, and these may actually be independent of the hard drive.
Good luck!
Good luck!

Multimedia, random lockups and Shutdown problems

I have a MSI K7T266 Pro2 motherboard. Even after loading the most current driver update (4 in 1 4.43) the machine works fine, but by the next day it will either freeze while playing any type of multimedia (mediaplayer, cable tv viewer, etc), randomly freeze or will just restart itself. I have had these problems ever since I purchased this motherboard. I have been building computers for years and have never encountered such a tempermental motherboard.
I am currently running Windows 2000 Professional and Windows XP Professional on different partitions. Both operating systems were installed cold onto a new formated hard drive. The problems exist in both operating systems.
Is there a way to permanently fix these problems?

Hi,
Can you give us more details, ie system specs. Also please go through the troubleshooting guide on top.

Random lockups on X-Fi Driver L

Similar Messages

Maybe you are looking for