Hey all, first-time poster. Be gentle.

On occasion, my notebook will shut down to maintain temperature requirements. I'm currently running SpeedFan (HD0: 43C, Temp1: 66C), but I have no basis on which to judge these temperatures.

The really worrying problem to me, however, is that, I believe four times now, my machine has given be a blue screen saying that Windows must shut down, there was a Kernel error, etc. Sorry about the vague description - I keep telling myself that I'll write it down the next time it appears, but I always panic and hurry to reboot as quickly as possible. The most recent time this happened (about 45 minutes ago, to be exact), I rebooted only to be greeted my a message stating that my system couldn't detect a hard disk and would I be so kind as to "Press F1 to Retry Boot, or Press F2 to Run Setup Utility". Thrice I saw this message, pressed F1 to no avail, and rebooted my machine. Once I went into the setup utility, but it didn't seem like I could do any good there. I turned the machine off and walked away for about five minutes, turned it back on, and it booted up fine.

At which point I promptly joined this forum.

Any suggestions? My system specs are below:

Dell Inspiron 1150 (About two years old - when the Dell Overheating Crisis of '06 came around, the 1150 wasn't listed on the recall pages, so I didn't bother. Should I have?)
Running WinXP Home Edition, SP2
Celeron 2.60 GHz
512 MB RAM

Thanks!

You can start with this: How to Find BSOD (Blue Screen) Error Messages

Not entirely certain what all I'm looking for - the only two dump files I found are from January, and the Event Viewer has way too many entries to single anything out. I compiled a report, though, which follows:

Applications
---------------------------------------
Information 2/11/2007 10:15:29 AM iPod Service None 0 N/A CHRIS
Information 2/11/2007 10:15:20 AM SecurityCenter None 1800 N/A CHRIS
Information 2/11/2007 10:15:19 AM McLogEvent None 5000 SYSTEM CHRIS
Information 2/11/2007 10:15:12 AM (MSN/Windows) Messenger Service None 4 N/A CHRIS
Information 2/11/2007 10:15:08 AM btwdins None 0 N/A CHRIS

System
---------------------------------------
Information 2/11/2007 10:25:26 AM Service Control Manager None 7035 Geiger CHRIS
Information 2/11/2007 10:25:25 AM Service Control Manager None 7035 Geiger CHRIS
Information 2/11/2007 10:15:31 AM Service Control Manager None 7036 N/A CHRIS
Information 2/11/2007 10:15:30 AM W32Time None 35 N/A CHRIS
Information 2/11/2007 10:15:30 AM Service Control Manager None 7036 N/A CHRIS
Information 2/11/2007 10:15:30 AM Service Control Manager None 7036 N/A CHRIS
Information 2/11/2007 10:15:29 AM Service Control Manager None 7036 N/A CHRIS
Information 2/11/2007 10:15:29 AM Service Control Manager None 7036 N/A CHRIS
Information 2/11/2007 10:15:29 AM Service Control Manager None 7035 SYSTEM CHRIS
Information 2/11/2007 10:15:29 AM Service Control Manager None 7036 N/A CHRIS
Information 2/11/2007 10:15:28 AM Service Control Manager None 7035 SYSTEM CHRIS
Information 2/11/2007 10:15:28 AM Service Control Manager None 7035 SYSTEM CHRIS
Information 2/11/2007 10:15:28 AM Service Control Manager None 7036 N/A CHRIS
Information 2/11/2007 10:15:27 AM Service Control Manager None 7035 SYSTEM CHRIS
Information 2/11/2007 10:15:27 AM Service Control Manager None 7035 Geiger CHRIS
Information 2/11/2007 10:15:27 AM Service Control Manager None 7035 SYSTEM CHRIS
Information 2/11/2007 10:15:27 AM Service Control Manager None 7036 N/A CHRIS
Information 2/11/2007 10:15:26 AM Service Control Manager None 7035 SYSTEM CHRIS
Information 2/11/2007 10:15:26 AM Service Control Manager None 7036 N/A CHRIS
Information 2/11/2007 10:15:26 AM Service Control Manager None 7035 SYSTEM CHRIS
Information 2/11/2007 10:15:26 AM Service Control Manager None 7036 N/A CHRIS
Information 2/11/2007 10:15:24 AM Service Control Manager None 7035 SYSTEM CHRIS
Information 2/11/2007 10:14:48 AM bcm4sbxp None 6 N/A CHRIS
Information 2/11/2007 10:14:58 AM eventlog None 6005 N/A CHRIS
Information 2/11/2007 10:14:58 AM eventlog None 6009 N/A CHRIS
These are the only entries around when I figure the error must've occurred. The Security section has a ton of entries, but I noticed four Failure Audits around the time:

Failure Audit 2/11/2007 10:15:01 AM Security Logon/Logoff 529 SYSTEM CHRIS
Failure Audit 2/11/2007 10:15:01 AM Security Account Logon 680 SYSTEM CHRIS
Failure Audit 2/11/2007 10:15:00 AM Security Logon/Logoff 529 SYSTEM CHRIS
Failure Audit 2/11/2007 10:15:00 AM Security Account Logon 680 SYSTEM CHRIS

Does any of this help give an explanation? Shy of waiting for the BSOD to pop up again, I don't know how to get the exact error messages. Hope this helps somebody.

--------------------------------------------
EDIT
--------------------------------------------
I ran WinDBG and got a minidump report for one of the January dumps. I'll paste what I believe to be a bit of pertinent information:

Unable to load image naiavf5x.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for naiavf5x.sys
*** ERROR: Module load completed but symbols could not be loaded for naiavf5x.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c000001d, eeafc7d7, eef51bc4, 0}

Probably caused by : hardware ( naiavf5x+f7d7 )

Followup: MachineOwner
---------

kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c000001d, The exception code that was not handled
Arg2: eeafc7d7, The address that the exception occurred at
Arg3: eef51bc4, Trap Frame
Arg4: 00000000

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.

FAULTING_IP:
naiavf5x+f7d7
eeafc7d7 ff ???

______________________________________________________________

I don't know actually how useful this is, but I'm shootin' in the dark here.