Bluescreen bei Shutdown

[Ralfman 10]

Hallo zusammen,

 

Ich bekomme beim Herunterfahren folgenden blue screen

 

DRIVER_IRQL_NOT_LESS_OR_EQUAL

 

Diverser Allgemeiner Text

 

Technische Information:

 

*** Stop 0x000000D1 (0x0000002b, 0x00000002, 0x00000000, 0xF8855941)

 

*** kbdclass.sys - adress F8855941 base at F885500, Datstamp 3d6ddad3

[gysinma1 13]

Hallo

 

Schau mal da

 

http://aumha.org/win5/kbestop.htm

 

Dieser Fehler gibts noch relativ häufig.

 

 

Gruss,

 

Matthias

[Ralfman 10]

Danke gysinma1,

aber gibts das auch in deutsch?

[gysinma1 13]

Puuuh. Kaum. Suche einmal im Deutschen Google ...

 

Gruss,

 

Matthias

[dennispetrasch 10]

Es passt zwar nicht ganz dazu, aber wo wir schoneinmal bei Bluescreens sind:

 

Ich bekomme bei der Installation von WinDVD 6 Ebenfalls einen Error.:

 

BAD_POOL_CALLER

 

Habe schoneinmal bei google gegoogelt, hatte da eine englische Seite gefunden, jedoch habe ich gar nicht verstanden. Link habe ich seit meiner letzen OS Installation auch nicht mehr. Villeicht kann mir ja auch jmd. weiterhelfen. Dann ist das hier sonne Art *Sammel-Blue-Screen-Thread*

 

Danke schoneinmal im vorraus:

 

Dennis

[gysinma1 13]

Hallo Freunde

 

 

Es ist sehr hilfreich bei einem Bluescreen die genauen Fehlercodes zu kennen. Der Text ist manchmal hilfreich aber oft auch zuwenig eindeutig.

 

In der Regel besteht die Message aus dem Fehler selbst (8-stellig) und nochmals drei Matrixen mit dem genauen Event mit nochmals je 8 Stellen.

 

Ich suche jetzt mal in den Referenzen nach DRIVER_IRQL_NOT_LESS_OR_EQUAL (ich tippe aber jetzt schon auf USB):

 

Also beginnen wir zuerst mit IRQL_NOT_LESS_OR_EQUAL:

Stop 0x0000000A or IRQL_NOT_LESS_OR_EQUAL

The Stop 0xA message indicates that a kernel-mode process or driver attempted 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. This Stop message is typically due to faulty or incompatible hardware or software.

 

Interpreting the Message

This Stop message has four parameters:

 

Memory address that was improperly referenced.

 

IRQL that was required to access the memory.

 

Type of access (0x00000000 = read operation, 0x00000001 = write operation).

 

Address of the instruction that attempted to reference memory specified in parameter 1.

 

If the last parameter is within the address range of a device driver used on your system, you can determine which device driver was running when the memory access occurred. You can typically determine the driver name by reading the line that begins with:

 

**Address 0xZZZZZZZZ has base at <address>- <driver name>

If the third parameter is the same as the first parameter, a special condition exists in which a system worker routine, carried out by a worker thread to handle background tasks known as work items, returned at a higher IRQL. In that case, some of the four parameters take on new meanings:

 

Address of the worker routine.

 

Kernel interrupt request level (IRQL).

 

Address of the worker routine.

 

Address of the work item.

 

Resolving the Problem

The following suggestions are specific to Stop 0xA errors. For additional troubleshooting suggestions that apply to all Stop errors, see “Stop Message Checklist” later in this appendix.

 

A Stop 0xA message might occur after installing a faulty device driver, system service, or firmware. If a Stop message lists a driver by name, disable, remove, or roll back the driver to correct the problem. If disabling or removing drivers resolves the issues, contact the manufacturer about a possible update. Using updated software is especially important for multimedia applications, antivirus scanners, and CD mastering tools.

 

A Stop 0xA message might also be due to failing or defective hardware. If a Stop message points to a category of devices (video or disk adapters, for example), try removing or replacing the hardware to determine if it is causing the problem.

 

If you encounter a Stop 0xA message while upgrading to Windows XP Professional, the problem might be due to an incompatible driver, system service, virus scanner, or backup. To avoid problems while upgrading, simplify your hardware configuration and remove all third-party device drivers and system services (including virus scanners) prior to running setup. After you have successfully installed Windows XP Professional, contact the hardware manufacturer to obtain compatible updates. For more information about simplifying your system for troubleshooting purposes, see “ Troubleshooting Concepts and Strategies” and “Troubleshooting Startup” in this book.

 

For more information about Stop 0xA messages, see the Microsoft Knowledge Base link on the Web Resources page at http://www.microsoft.com/windows/reskits/webresources. Search using keywords winnt, 0x0000000A, and 0xA.

 

 

@dennispetrasch

Ich bin weit weg davon ein Moderator zu sein, aber ich weiss nicht, ob dass der Uebersicht dienst, zwei Probleme, die nix miteinander zu tun haben, in denselben Thread zu packen.

[gysinma1 13]

so und nun der zweite im Bund:

Stop 0xC2 or BAD_POOL_CALLER

The Stop 0xC2 message indicates that a kernel-mode process or driver incorrectly attempted to perform memory operations in the following ways:

 

By allocating a memory pool size of zero bytes.

 

By allocating a memory pool that does not exist.

 

By attempting to free a memory pool that is already free.

 

By allocating or freeing a memory pool at an IRQL that was too high.

 

This Stop message is typically due to a faulty driver or software.

 

Interpreting the Message

Table C-5 describes the information provided by Stop 0xC2 messages. The value of the first parameter indicates the type of violation (see the Description column) and determines the meaning of the next three parameters.

 

Table C-5. Parameter Listing for Stop Message 0xC2 Parameter 1

Parameter 2

Parameter 3

Parameter 4

Description

 

0x00000000

This value is always 0

The pool type being allocated

The pool tag being used

The caller is requesting a zero byte pool allocation

 

0x00000001, 0x00000002, or 0x00000004

Pointer to pool header

First part of pool header contents

This value is always zero

Pool header has been corrupted

 

0x00000006

Reserved

Pointer to pool header

Pool header contents

Attempt to free a memory pool that was already freed

 

0x00000007

Reserved

Pointer to pool header

This value is always zero

Attempt to free a memory pool that was already freed

 

0x00000008

Current IRQL

Pool type

Size of allocation

Attempt to allocate pool at invalid IRQL

 

0x00000009

Current IRQL

Pool type

Address of pool

Attempt to free pool at invalid IRQL

 

0x00000040

Starting address

Start of system address space

This value is always zero

Attempt to free usermode address to kernel pool

 

0x00000041

Starting address

Physical page frame

Highest physical page frame

Attempt to free a non-allocated nonpaged pool address

 

0x00000042 or 0x00000043

Address being freed

This value is always zero

This value is always zero

Attempt to free a virtual address that was never in any pool

 

0x00000050

Starting address

Start offset in pages from beginning of paged pool

Size in bytes of paged pool

Attempt to free a non-allocated paged pool address

 

0x00000099

Address being freed

This value is always zero

This value is always zero

Attempt to free pool with invalid address or corruption in pool header

 

0x0000009A

Pool type

Size of allocation in bytes

Allocation’s pool tag

Attempt to allocate must-succeed

 

 

Resolving the Problem

The following suggestions are specific to Stop 0xC2 errors. For additional troubleshooting suggestions that apply to all Stop errors, see “Stop Message Checklist” later in this appendix.

 

A Stop 0xC2 message might occur after installing a faulty device driver, system service, or firmware. If a Stop message lists a driver by name, disable, remove, or roll back the driver to correct the problem. If disabling or removing drivers resolves the issues, contact the manufacturer about a possible update. Using updated software is especially important for multimedia applications, antivirus scanners, DVD playback, and CD mastering tools.

 

A Stop 0xC2 message might also be due to failing or defective hardware. If a Stop message points to a category of devices (such as disk controllers, for example), try removing or replacing the hardware to determine if it is causing the problem.

 

If you encounter a Stop 0xC2 message while upgrading to Windows XP Professional, the problem might be due to an incompatible driver, system service, virus scanner, or backup. To avoid problems while upgrading, simplify your hardware configuration and remove all third-party device drivers and system services (including virus scanners) prior to running setup. After you have successfully installed Windows XP Professional, contact the hardware manufacturer to obtain compatible updates. For more information about simplifying your system for troubleshooting purposes, see “ Troubleshooting Concepts and Strategies” and “Troubleshooting Startup” in this book.

 

For more information about Stop 0xC2 messages, see the Microsoft Knowledge Base link on the Web Resources page at http://www.microsoft.com/windows/reskits/webresources. Search using keywords winnt, 0x000000C2, and 0xC2.

[Konfus 10]

Hi,

 

@ralfman: Hier die deutsche Lösung:

http://support.microsoft.com/?kbid=313050

 

@dennispetrasch:Beim bad_pool_caller greift der Gerätetreiber auf einen nicjht für ihn adressierten Speicherbereich zu.

Ich denk das Du einen 0xC2 bekommst.

Aktualisiere mal den Grafikkartentreiber oder fahre die Auflösung ein wenig nach unten.

 

Wenns hart auf hart kommt nehme WinDBG als Debugger und gehe gem. folgenden Artikel vor:

http://support.microsoft.com/default.aspx?scid=kb;en-us;265879

 

Link zum Debugger, Symbols und Infos:

http://www.microsoft.com/whdc/devtools/debugging/default.mspx

 

gruß

 

Konfus

[dennispetrasch 10]

es liegt zu 90 % an meiner GK. Ich habe die Radeon 9800 XT mit dem neusten Catalyst. Ein bis zwei Beiträge danach beschreibe ich mein Installationproblem mit der GK.

 

Wäre nett wenn ihr darauf ne Antwort wüsstet, stehe hier voll auf dem Schlauch

 

@Ralfman

 

Hast du dein Problem nun lösen können ?

[Ralfman 10]

@Konfus.

 

DANKE

 

Ralfman