Help w/Problem Event Blue Screen

[naturalpaths]

I am hoping someone can tell me what's wrong with my new Dell Studio w/Vista. Thank you for any help!

Here's the message I got:


Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.768.3
Locale ID: 1033



Additional information about the problem:
BCCode: a
BCP1: 0000000000000880
BCP2: 000000000000000C
BCP3: 0000000000000001
BCP4: FFFFF80001C7CA15
OS Version: 6_0_6001
Service Pack: 1_0
Product: 768_1


Files that help describe the problem:
C:\Windows\Minidump\Mini061109-01.dmp
C:\Users\Michelle\AppData\Local\Temp\WER448237-0.sysdata.xml
C:\Users\Michelle\AppData\Local\Temp\WER498D.tmp.version.txt

[naturalpaths]

All I did was turn my computer on and it threw a blue screen and then brought up a window with the error message I wrote below. I thought that the BC and BP Codes with the numerical assignments would have some meaning as to what the problem is. The BC codes and C drive listings were all the information my computer gave me.

thank you for trying to help,
Michelle-

I also ran my security software, McAffee, and the report back was that there were several problems that it could not repair due to an error. I am assuming that error has to do with the the blue screen event that occurred. My laptop is only 3 months old so needless to say this is frustrating! It's still under hardware warranty but the techs @ Dell told me I would need to pay an extra 200 bucks to talk to the software people in FL that could diagnose the problem remotely.

0x0000000A: IRQL_NOT_LESS_OR_EQUAL
Typically due to a bad driver, or faulty or incompatible hardware or software.
Technically, this error condition means that a kernel-mode process or driver tried
to access a memory location to which it did not have permission, or at a kernel
Interrupt ReQuest Level (IRQL) that was too high. (A kernel-mode process can access
only other processes that have an IRQL lower than, or equal to, its own.)

http://msdn.microsoft.com/en-gb/library/ms793589.aspx
General Troubleshooting of STOP Messages
If you can’t find a specific reference to your problem, running through the
following checklist stands a good chance of resolving the problem for you. This
checklist is also usually the best approach to troubleshooting some specific Stop
messagesExamine the “System” and “Application” logs in Event Viewer for other recent
errors that might give further clues. To do this, launch EventVwr.msc from a Run
box; or open “Administrative Tools” in the Control Panel then launch Event Viewer.

1.. If you’ve recently added new hardware, remove it and retest.
2.. Run hardware diagnostics supplied by the manufacturer.
3.. Make sure device drivers and system BIOS are up-to-date.
4.. However, if you’ve installed new drivers just before the problem appeared, try
rolling them back to the older ones.
5.. Open the box and make sure all hardware is correctly installed, well seated,
and solidly connected.
6.. Confirm that all of your hardware is on the If some of it isn’t, then pay
particular attention to the non-HCL hardware in your troubleshooting.
7.. Check for viruses.
8.. Investigate recently added software.
9.. Examine (and try disabling) BIOS memory options such as caching or shadowing.
NOTE: When a STOP message occurs, Windows can create a debug file for very detailed
analysis. To do this, it needs a workspace equal to the amount of physical RAM you
have installed. If you resize your Win XP pagefile minimum to less than the size of
your physical RAM, you will get an advisory message that your system may not be able
to create a debugging information file if a STOP error occurs. My advice is to go
ahead with this change if you want, but simply remember the limitation so that you
can change it back if you need to troubleshoot STOP messages. Some general
troubleshooting principles are suggested in the Resource Kit for approaching STOP
messages overall.


--
Peter