Blue Screen Stop Errors

  • Thread starter Thread starter FRAZZLED
  • Start date Start date
F

FRAZZLED

Having big problems with windows shutdowns after user log in. Various blue
screen errors have come up at each attempt to rectify the issue. Examples are
* IRQL_NOT_LESS_OR_EQUAL with the following code
STOP: 0x0000000A (0x0000082A, 0x00000002, 0x00000000, 0x80535027)
* PAGE_FAULT_IN_NONPAGED_AREA
STOP: 0x00000050 (0xC0E1317c, 0x00000000, 0x8050525F, 0x00000000)

Several attempts to get in via SAFE MODE have met similar fate.
eg. STOP:000000BE (0xC0000005, 0x8055059A, 0xF77E096C, 0x00000000)
eg. STOP:000000F4 (0x00000003, 0x82AEBAF8, 0x82AEBC6C, 0x80604418)

Booting from the CD and attempting a recovery got me to a desktop and then
the IRQL error came again.

Any solutions would be very much appreciated. There were no new hardware or
software installations leading to this. My kids are online frequently and
have not covered any new territory that is obvious to me
 
Background information on Stop Error message
http://msdn2.microsoft.com/en-us/library/ms793589.aspx

0x0000000A: IRQL_NOT_LESS_OR_EQUAL
Typically due to a bad driver, or faulty or incompatible hardware or
software. Use the General Troubleshooting of STOP Messages checklist
above. 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.)
Source: http://aumha.org/a/stop.htm

Background information on Stop Error message
http://msdn2.microsoft.com/en-us/library/ms793437.aspx

0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
(Click to consult the online MSDN article.)
Requested data was not in memory. An invalid system memory address was
referenced. Defective memory (including main memory, L2 RAM cache, video
RAM) or incompatible software (including remote control and antivirus
software) might cause this Stop message, as may other hardware problems
(e.g., incorrect SCSI termination or a flawed PCI card).
Source: http://aumha.org/a/stop.htm

Remove the dust bunnies and test the RAM memory
http://www.elephantboycomputers.com/page2.html#Hardware_Tshoot

Check the hard drive for bad sectors by running chkdsk /f /r

Check the System log of Event Viewer for Error Reports.

Please post copies of all Error and Warning Reports appearing in the
System log in Event Viewer for the last boot. No Information Reports or
Duplicates please. Indicate which also appear in a previous boot.

You can access Event Viewer by selecting Start, Control Panel,
Administrative Tools, and Event Viewer.

A tip for posting copies of Error Reports! Run Event Viewer and double
click on the error you want to copy. In the window, which appears is a
button resembling two pages. Click the button and close Event
Viewer.Now start your message (email) and do a paste into the body of
the message. Make sure this is the first paste after exiting from
Event Viewer.

Are there any yellow question marks in Device Manager? Right click on
the My Computer icon on your Desktop and select Properties,
Hardware,Device Manager. If yes what is the Device Error code?

Try Start, Run, type "sigverif.exe" without quotes and hit OK. What
drivers are listed as unsigned? Disregard those which are not checked.

--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
 
Back
Top