X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 	tests=BAYES_00,SARE_MSGID_LONG40,SPF_PASS
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <4B1A6DEC.7010509@cwilson.fastmail.fm>
References: <4B1A229C DOT 7090404 AT cwilson DOT fastmail DOT fm> 	 <4B1A4EEC DOT 4030108 AT sbcglobal DOT net> 	 <4B1A6DEC DOT 7010509 AT cwilson DOT fastmail DOT fm>
Date: Sat, 5 Dec 2009 14:13:50 -0500
Message-ID: <a13b5a590912051113r7057fd96rc066f023d7b16f32@mail.gmail.com>
Subject: Re: Hippo icon for cygwin...
From: Robert Pendell <shinji AT elite-systems DOT org>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Sat, Dec 5, 2009 at 9:27 AM, Charles Wilson wrote:
> Greg Chicares wrote:
>> Might this file:
>> =C2=A0 1a652c4c8c31b80c85d6cbc2b4093060 *hippo.ico
>> be somehow malformed? My computer BSODs every time I try to view
>> it in 'irfanview'. This has happened three times in a row.
>
> BSOD? Well, *any* BSOD is by definition a bug inside ring 0 (e.g. the
> core Windows kernel, or a graphics driver. =C2=A0So, it isn't *.ico's fau=
lt.
>
> Still, it'd be good to avoid...
>

Not necessarily.  A BSOD can be caused by any faulty driver,
application, or service in the system.  It can also be caused by
faulty hardware.  Bad ram will cause memory corruption and make
programs or drivers fail to run properly.  I have diagnosed BSOD
errors before and tracked them down to both faulty ram and faulty hard
drives.  Using windbg to identify the culprit helps.

Robert Pendell
shinji AT elite-systems DOT org
CAcert Assurer
"A perfect world is one of chaos."

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple