Installed FRC LabView, now get blue screen of death (BSOD)

[meakerb]

I installed LabView (but not the WindRiver C++ or Java) from the disk provided to the FRC team. Now, whenever I boot the machine, I get a blue screen of death (BSOD) about 25 seconds after the login screen shows up (I don't have to log in, it just happens).

The BSOD shows the following message:

A problem has been detected and 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 your computer. If this screen appears again, follow these steps:

   :

{bla, bla, bla}

Technical information:

*** STOP: 0x0000000A (0x00000005,0x00000002,0x00000001,0x804F0F55)

Beginning dump of physical memory

Physical memory dump complete.

Contact your system administrator or technical support group for further assistance.

Background info:

My PC is running Windows XP with SP3 on it.

I had a previous evaluation copy of LabView on my PC. Since the evaluation license had expired, I did an uninstall (using Windows' add/remove programs, which called the LabView uninstaller) before installing the FRC LabView, including removing the Program Files/National Instruments folder. I did not touch the registry.

When I did the FRC LabView Install, I didn't enter a activation code (since I couldn't find the sheet that told me what it was), so I left it blank (the prompt stated that this would provide an evaluation license).

As stated above, I get the BSOD whenever I boot my machine now, even without logging in. I can, however, boot into safe mode. I tried doing an uninstall from there but the uninstaller just give an error 1601 for all the files.

From another computer that is on my home network, I ran a program called BlueScreenView. This program provides info from the minidump file associated with each crash. I was able to access over the network the necessary files to produce this analysis (hopefully you'll be able to enlarge this to read it):

This shows the three running pieces of code: tcpip.sys, ntoskrnl.exe, and HTTP.sys. According to the address reported by the BSOD, the routine ntoskrnl.exe was executing when the crash occured (if I'm reading this right).

So how do I go about fixing my PC to not get the BSOD?

Thanks.

[nathand]

Can you successfully boot into Safe Mode?  If you can, you might be able to uninstall LabVIEW and see if the problem goes away.

[DAQjr]

Can you try disabling your network interfaces in safe mode and see if that will allow you to boot normally.  I realize that's not a solution, but it may help narrow down the problem.

[meakerb]

Tonight I booted up my PC and it booted properly! I've been on it for a couple of hours now with no BSOD.

I originally thought it was a software issue since the BSOD started happening immediately after installing LabView, but now I'm wondering if it is a hardware problem (cooling?) since nothing has changed from yesterday software wise when I couldn't get the PC to boot. This doesn't explain why I could boot into safe mode though.

Flat out wierd. Any suggestions?

[Smootastic]

Hi meakerb,

It's good to hear that the computer is running again.  As far as the cause goes, the best we can do is try to narrow down the problem, especially if you think it's hardware-related.  Much like the earlier suggestion, disabling certain hardware devices, such as network cards, in safe mode will help to narrow down the issue.  As long as the process may be, uninstalling software in safe mode will help to narrow a software-related issue.

Good Luck!

Kyle

FIRST Applications Engineer

[meakerb]

Yes, I'm VERY pleased that the computer is running again. If the problem occurs again, how do I get around the issue of not being able to uninstall the software while in safe mode (I was getting an error 1601 for each file the uninstaller was trying to remove).?

[Smootastic]

Hi meakerb,

I found this article on the error:

http://support.microsoft.com/kb/315346

Good Luck!

Kyle

FIRST Applications Engineer