OS: Windows XP Pro, SP2 + Latest updates from windowsupdate.com
CPU: Intel Centrino 1.7
RAM: 1GB
CONNECTION: 512/128 ADSL Broadband
LIMEWIRE VERSION: 4.9.11
JAVA VERSION: 1.5.0.40
ROUTER: NO
FIREWALL: Trend Micro PC-cillin Internet Security 2005
ANTIVIRUS: Trend Micro PC-cillin Internet Security 2005
LIMEWIRE EXPERIENCE: 4 Weeks

ISSUE: Within 10 seconds of Limewire loading after the initial splash screen the computer immediately reboots.

Limewire loads to the point of which the dialogue box asking to upgrade to Limewire Pro appears. My screen then turns black and the computer reboots.

I do not press any key on my keyboard or button on my mouse prior to the reboot, I only launch the Limewire application.

I have tried a complete reformat and reinstall of Windows but the issue persists.

I cant determine the cause of the problem, if there is any possible help it would be much appreciated.

Are you getting the blue screen of death before it reboots. What Graphics card are you using. And thank you for posting all the information you must have done some reading in the forum before you posted. Thats RARE

__________________










A little common sense goes a long way

Later Grandpa

I do not receive any BSOD as far as I know. The screen just completely blanks out to black and reboots.

I am using a mobile AIT Radeon 9700 128MB Dedicated video card.

have you checked out this post. http://www.gnutellaforums.com/showth...threadid=39600

Looks as though it may be a display adapter problem.

if its "ATI" do a search in the forum for it, and see if any of those posts help.

Fabion, that post does not help sadly. Ultracross, sadly no luck.

Hasnt anyone had the same issue as me?

I have a strange feeling it may be conflicting with one of the Windows updates, but I would have no idea how to figure that out.

http://downloadfinder.intel.com/scri...ProductID=1847

The above is a link from Intel I was provided.

I decided to try Limewire once again, and once again it rebooted my computer, but instead this time when my computer loaded it provided me with one of those error reporting dialogues from Microsoft. So I went ahead and let it report the error.

Before I knew it, it loaded a page and said it had found a solution for my error. It provided me with the link I have given above.

I dont understand why it works for me, but the thing I downloaded from the link works for me and allows me to run Limewire without restarting.

Does anyone know why?

Greetings. I have the same issue as you do. But first here are my stats:

P4 1.8
512 RDRAM
NVIDIA 6800 GT 77.77 Drivers
Latest Limewire
Java 1.4.2 08

Now, I've narrowed the issue down to my NVIDIA drivers and here's why: I had NVIDIA drivers 71.89 installed and was using the above versions of everything else. I had problems with a gray screen but the Java rollback to 1.4.2 solved my problem with the 71.89 drivers. After I installed the 77.77 NVIDIA drivers and launched Limewire I got the white screen, then the language screen...then a lovely reboot. The only difference with you is my error reporting pointed to my device driver instead of a downloadable solution.

So I'm facing the following options: Rollback my NVIDIA drivers to keep using Limewire, or keep my current drivers and wait for Gnutella to fix the compatability issues. I choose my drivers as they effect everything else on my system.

I hope this helps resolve some issues and I sincerely hope Gnutella fixes this soon. I really enjoy the simplicity and speed of Limewire so good luck to all involved.

There are post in this forum about Nvidia,Radion, and other graphic card issues. Read them change your settings an LimeWire will work fine my self I run Nvidia 6200 with no problems just had to find the right settings. I would not expect that LimeWire is going to change there platform when there is such a simple fix. So as you said before the choice is yours, you can either fix it or not use LimeWire.

It wasn't a problem with LimeWire at all. There was a bug in the piece of software that Windows uses to talk to your network card. LimeWire just happened to move data fast enough through your card to trigger the bug.

The way Windows is designed, the software that talks to your network card (called a "driver") runs in a special mode called "kernel mode" or "ring 0" ("privledged mode" in old IBM mainframe terminology). When software that runs in "kernel mode" dies, it almost always takes the entire system down with it.

If you ever have a bug that restarts your whole system, it's almost always a bug in "kernel mode" software or the hardware itself.

You installed a newer version of the software that Windows uses to talk to your network card, thereby getting rid of that particular bug.

LimeWire, and pretty much every piece of software that you think of as a program, runs in "user mode" or "ring 3" ("problem mode" in old IBM mainframe terminology, since problems in "problem mode" can be handled without restarting the system). If software running in "user mode" has a major problem, the hardware automatically switches to some "kernel mode" software that handles the problem, usually by forcing the problematic "user mode" software to quit. When there's a problem with "kernel mode" software, there's usually no piece of software that can fix the problem, so the whole system has stop and be restarted.

There's a design philosophy called "micro kernels" that tries to minimize the amount of software that runs in "kernel mode". In microkernel systems, the operating system talks to the hardware through software running in "user mode". For a brief time, I used a microkernel operating system. It had a very buggy network driver that had major problems about once a day. However, it was a microkernel system, so the driver was running in "user mode", which meant that the "kernel mode" software was able to deal with the problem. The operating system just politely informed me that it had restarted the driver. The only thing I really noticed was that any webpages I was loading at the time had to be refreshed. The operating system was able to keep going because the problem was in "user mode" (or "problem mode") software.

Microkernel systems are generally more reliable than traditional "monolithic kernel" sytems. Unfortunately, it takes a lot of work to make microkernel systems run as fast as monolithic kernel systems.

Windows NT (an ancestor of Windows XP) was intended to be a microkernel system, and Mac OS X is decended from a microkernel system called NeXT Step. In both cases, the system designers later decided to speed up the systems by moving some parts of software from "user mode" to "kernel mode".