BlueScreen i błąd ntkrnlmp.exe (BugCheck 1)

Wszelkie problemy komputerowe, których nie można jednoznacznie sklasyfikować do wybranego działu
dziama

Użytkownik
Posty: 1
Rejestracja: 07 gru 2010, 16:15

BlueScreen i błąd ntkrnlmp.exe (BugCheck 1)

Post07 gru 2010, 16:32

Witam
Mam problem tzn od tygodnia 3 razy pojawił mi się BluerScreen a oto ostatni wykaz z programu WinDbg.

Ja za bardzo tego nie rozumiem więc proszę o pomoc. Wydawało mi się wcześniej że to może być coś z RAM ale podczas gdy wyskakiwał mi BlueScreen zużycie pamięci na 100 % nie przekraczało więcej niż 3GB a w kompie mam 4 Gb. Proszę o jakieś sugestie.

Kod: Zaznacz cały

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\120710-22027-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c4f000 PsLoadedModuleList = 0xfffff800`02e8ce50
Debug session time: Tue Dec  7 13:13:24.098 2010 (UTC + 1:00)
System Uptime: 0 days 1:21:43.376
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1, {7feff2a13ba, 0, ffff, fffff88002314ca0}

Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )

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

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

APC_INDEX_MISMATCH (1)
This is a kernel internal error. The most common reason to see this
bugcheck is when a filesystem or a driver has a mismatched number of
calls to disable and re-enable APCs. The key data item is the
Thread->KernelApcDisable field. A negative value indicates that a driver
has disabled APC calls without re-enabling them.  A positive value indicates
that the reverse is true. This check is made on exit from a system call.
Arguments:
Arg1: 000007feff2a13ba, address of system function (system call)
Arg2: 0000000000000000, Thread->ApcStateIndex << 8 | Previous ApcStateIndex
Arg3: 000000000000ffff, Thread->KernelApcDisable
Arg4: fffff88002314ca0, Previous KernelApcDisable

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


FAULTING_IP:
+3936333833633165
000007fe`ff2a13ba ??              ???

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002cbeca9 to fffff80002cbf740

STACK_TEXT: 
fffff880`02314ad8 fffff800`02cbeca9 : 00000000`00000001 000007fe`ff2a13ba 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx
fffff880`02314ae0 fffff800`02cbebe0 : 00000000`00000008 ffffffff`ffffffff 00000000`00000001 00000000`00000020 : nt!KiBugCheckDispatch+0x69
fffff880`02314c20 000007fe`ff2a13ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x245
00000000`02a0e3d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`ff2a13ba


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt!KiSystemServiceExit+245
fffff800`02cbebe0 4883ec50        sub     rsp,50h

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiSystemServiceExit+245

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x1_SysCallNum_1187_nt!KiSystemServiceExit+245

BUCKET_ID:  X64_0x1_SysCallNum_1187_nt!KiSystemServiceExit+245

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

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

APC_INDEX_MISMATCH (1)
This is a kernel internal error. The most common reason to see this
bugcheck is when a filesystem or a driver has a mismatched number of
calls to disable and re-enable APCs. The key data item is the
Thread->KernelApcDisable field. A negative value indicates that a driver
has disabled APC calls without re-enabling them.  A positive value indicates
that the reverse is true. This check is made on exit from a system call.
Arguments:
Arg1: 000007feff2a13ba, address of system function (system call)
Arg2: 0000000000000000, Thread->ApcStateIndex << 8 | Previous ApcStateIndex
Arg3: 000000000000ffff, Thread->KernelApcDisable
Arg4: fffff88002314ca0, Previous KernelApcDisable

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


FAULTING_IP:
+3936333833633165
000007fe`ff2a13ba ??              ???

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002cbeca9 to fffff80002cbf740

STACK_TEXT: 
fffff880`02314ad8 fffff800`02cbeca9 : 00000000`00000001 000007fe`ff2a13ba 00000000`00000000 00000000`0000ffff : nt!KeBugCheckEx
fffff880`02314ae0 fffff800`02cbebe0 : 00000000`00000008 ffffffff`ffffffff 00000000`00000001 00000000`00000020 : nt!KiBugCheckDispatch+0x69
fffff880`02314c20 000007fe`ff2a13ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x245
00000000`02a0e3d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`ff2a13ba


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt!KiSystemServiceExit+245
fffff800`02cbebe0 4883ec50        sub     rsp,50h

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiSystemServiceExit+245

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x1_SysCallNum_1187_nt!KiSystemServiceExit+245

BUCKET_ID:  X64_0x1_SysCallNum_1187_nt!KiSystemServiceExit+245

Followup: MachineOwner

Awatar użytkownika
Andziorka

VIP+
Posty: 594
Rejestracja: 06 kwie 2009, 17:50
Kontaktowanie:

BlueScreen i błąd ntkrnlmp.exe

Post07 gru 2010, 16:56

- wykonaj test pamięci tym programem: http://www.hotfix.pl/instrukcja-obslugi ... m-a204.htm
- podaj konfigurację komputera, nie zapomnij o marce i mocy zasilacza
- komputer był podkręcany? przywróć pierwotne ustawienia
'Oto dzień zwycięstwa nad rozumem, głupiej wrażliwości Twej..'



  • Reklama

Wróć do „Problemy”



Kto jest online

Użytkownicy przeglądający to forum: Obecnie na forum nie ma żadnego zarejestrowanego użytkownika i 192 gości