BSOD caused by .NET

[Garrot]

Yesterday I decided to use windows update and had it install .NET 1.1
and 2.0. On reboot I got a BSOD before the desktop loaded. In safe
mode it was fine so had windows load last good configuration, removed
..NET. Everything was fine again. Decided to download Vista RC1 and
install that. On first boot of the OS got the BSOD again. Well, Vista
comes bundled with .NET so that explains it. The BSOD is just a stop
error and gives no info as to what is causing it, just some numbers
and letters that mean nothing to me. Anyone experience this before and
know the cause? As for now I'm back to XP sans .NET.

 

[Patrick Keenan]

Yesterday I decided to use windows update and had it install .NET 1.1
and 2.0. On reboot I got a BSOD before the desktop loaded. In safe
mode it was fine so had windows load last good configuration, removed
.NET. Everything was fine again. Decided to download Vista RC1 and
install that. On first boot of the OS got the BSOD again. Well, Vista
comes bundled with .NET so that explains it. The BSOD is just a stop
error and gives no info as to what is causing it, just some numbers
and letters that mean nothing to me. Anyone experience this before and
know the cause? As for now I'm back to XP sans .NET.

Actually, the BSOD does give information as to what's causing it. That
information *is* the numbers and letters, which are hexadecimal values.

Key is the STOP number, such as the ones listed here:
http://www.aumha.org/win5/kbestop.php

As an example, the information you need to post from the BSOD looks like
this format:
STOP 0x00000074 (0x00000003, 0x00000002, 0x80087000) BAD_SYSTEM_CONFIG_INFO

HTH
-pk