Thread: Multiple BSODs
View Single Post
  #35  
Old June 24th 09, 11:00 PM posted to microsoft.public.windowsxp.help_and_support
Gerry
external usenet poster
 
Posts: 9,437
Default Multiple BSODs

Oscar

The Event ID: 7023 errors can be ignored.

You may find the degree of diffulty for my next suggestion too much You
can use a Kernel Debugger to examine the 0x0000000A: IRQL Dump Report.
If you succeed in running the debugger post a copy of the Report and
obtain a stack trace.

Install Debugging Tools for Windows 32-bit Version
http://www.microsoft.com/whdc/devtoo...nstallx86.Mspx

There follows the standard information I have on the two errors.

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

You receive a "Stop 0x0000000A" error message in Windows XP
http://support.microsoft.com/kb/314063/

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

--


Hope this helps.

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



o.smallenbroek wrote:
I dont really want to uninstall messenger, although i do agree that it
creates a lot of problems. I uninstalled messenger and then upgraded
it.

I got another BSOD while just running messenger and utorrent. The
error codes still point to my harddrive. Maybe if i put a differnt
one in it will solve the problem.

Here are the other error reports.

Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 6/24/2009
Time: 3:28:02 PM
User: N/A
Computer: OSCAR
Description:
The computer has rebooted from a bugcheck. The bugcheck was:
0x10000050 (0xf7421c5e, 0x00000001, 0xbf976eb0, 0x00000000). A dump
was saved in: C:\WINDOWS\Minidump\Mini062409-02.dmp.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

IT also said FAULT_IN_NONPAGED_AREA win32k.sys and these errors came
up in the event log:
__________
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7023
Date: 6/24/2009
Time: 12:10:09 PM
User: N/A
Computer: OSCAR
Description:
The Application Management service terminated with the following
error:

The specified module could not be found.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
________
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7023
Date: 6/24/2009
Time: 12:10:09 PM
User: N/A
Computer: OSCAR
Description:
The Application Management service terminated with the following
error:

The specified module could not be found.

Anoter BSOD
Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 6/23/2009
Time: 2:09:11 PM
User: N/A
Computer: OSCAR
Description:
The computer has rebooted from a bugcheck. The bugcheck was:
0x1000000a (0x00000000, 0x0000001c, 0x00000000, 0x804dc85d). A dump
was saved in: C:\WINDOWS\Minidump\Mini062309-01.dmp.


Ads