Windows 7 Forum: konfiguracja, optymalizacja, porady, gadżety •
BSOD-y po formacie systemu, zwykle podczas grania - Wersja do druku

+- Windows 7 Forum: konfiguracja, optymalizacja, porady, gadżety • (https://windows7forum.pl)
+-- Dział: Pomoc i wsparcie, Windows 7 (/pomoc-i-wsparcie-windows-7-26-f)
+--- Dział: Hardware (/hardware-28-f)
+--- Wątek: BSOD-y po formacie systemu, zwykle podczas grania (/bsod-y-po-formacie-systemu-zwykle-podczas-grania-20439-t)



BSOD-y po formacie systemu, zwykle podczas grania - wildmor - 11.12.2011 23:14

Witam,
mam pewien problem, po formacie systemu zaczęły mi wyskakiwać blue screeny, co sie wcześniej nigdy nie działo, zazwyczaj podczas grania.
Co może być tego powodem?


RE: Blue screeny - thermalfake - 12.12.2011 01:02

Fajnie tylko, że ja tych bluescreenów nie widzę, nie mam daru wróżki.
Wrzuć spakowane pliki *.dmp z katalogu c:\windows\minidump na dowolny serwer hostingowy i tu podlinkuj.


RE: Blue screeny - wildmor - 12.12.2011 08:26

Sory,
klik


RE: Problem z blue screenami - wildmor - 24.12.2011 12:09

odpisze ktos?!


RE: Problem z blue screenami - thermalfake - 24.12.2011 22:49

Ciągle jeden i ten sam typ błędu się przewija
PFN_LIST_CORRUPT (4e)

-> długoczasowy memtest dla pamięci RAM http://windows7forum.pl/testowanie-pamieci-ram-programem-memtest86-t-12774.html
pozamieniać też pamięci slotami, testować także pojedyńczo zamieniajac tylko slotami bo może się okazać, że jeden z nich na płycie głównej jest uszkodzony.
-> skanowanie antywirusowe, anti-malware


Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C: \Users\user\Desktop\bsody\dmp10\120611-31543-01.dmp]
Mini Kernel Dump File:  Only registers and stack trace are available

Symbol search path is:  symsrv*symsrv.dll*c: \symb*http: //msdl.microsoft.com/download/symbols
Executable search path is:  
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product:  WinNt, suite:  TerminalServer SingleUserTS Personal
Built by:  7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02a18000 PsLoadedModuleList = 0xfffff800`02c5d670
Debug session time:  Tue Dec  6 15: 42: 05.526 2011 (UTC + 1: 00)
System Uptime:  0 days 1: 09: 07.993
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 8ae05, 2, 31304}

Probably caused by :  memory_corruption ( nt!MiBadShareCount+4c )

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

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

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie:  calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1:  0000000000000099, A PTE or PFN is corrupt
Arg2:  000000000008ae05, page frame number
Arg3:  0000000000000002, current page state
Arg4:  0000000000031304, 0

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


BUGCHECK_STR:   0x4E_99

CUSTOMER_CRASH_COUNT:   1

DEFAULT_BUCKET_ID:   VISTA_DRIVER_FAULT

PROCESS_NAME:   iw4mp.exe

CURRENT_IRQL:   2

LAST_CONTROL_TRANSFER:   from fffff80002b1dd7c to fffff80002a94c40

STACK_TEXT:  
fffff880`0a536268 fffff800`02b1dd7c :  00000000`0000004e 00000000`00000099 00000000`0008ae05 00000000`00000002 :  nt!KeBugCheckEx
fffff880`0a536270 fffff800`02a29a53 :  fffffa80`01acad50 00000000`00000001 00000000`00000000 00000000`00000080 :  nt!MiBadShareCount+0x4c
fffff880`0a5362b0 fffff800`02ae27ad :  00000000`00000002 00000000`00000001 fffffa80`01acad50 00000000`00000000 :  nt! ? : FNODOBFM: `string'+0x11d18
fffff880`0a536340 fffff800`02a5929f :  fa80042a`cc5004c0 fa80042a`cc5004c0 fffff880`0a536400 00000000`00000060 :  nt!MiRemoveLowestPriorityStandbyPage+0x1d5
fffff880`0a5363c0 fffff800`02d314ea :  fffffa80`05a22ed0 fffffa80`00000001 fffffa80`05a22ed0 00000000`00000005 :  nt!MiPfPutPagesInTransition+0x826
fffff880`0a536530 fffff800`02a83c8d :  fffffa80`05a22ed0 00000000`012d8000 00000000`00004000 00000000`000012d8 :  nt!MmPrefetchForCacheManager+0x8e
fffff880`0a536580 fffff800`02d7ee10 :  00000000`00000000 00000000`012d8000 fffffa80`069f4210 00000000`06568000 :  nt!CcFetchDataForRead+0x17d
fffff880`0a5365e0 fffff880`012ccf08 :  fffff880`00000000 00000000`00000005 fffffa80`00028000 fffffa80`00004001 :  nt!CcCopyRead+0x180
fffff880`0a5366a0 fffff880`011b1098 :  fffffa80`069f4210 fffffa80`060cc0d8 00000000`00000000 fffffa80`069f4201 :  Ntfs!NtfsCopyReadA+0x1a8
fffff880`0a536880 fffff880`011b48ba :  fffff880`0a536950 00000000`06568003 00000000`06568000 fffffa80`069f4200 :  fltmgr!FltpPerformFastIoCall+0x88
fffff880`0a5368e0 fffff880`011d2630 :  fffffa80`069f4210 00000000`00000000 fffff880`0a536b40 00000000`00004000 :  fltmgr!FltpPassThroughFastIo+0xda
fffff880`0a536920 fffff880`011b1098 :  00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`069f4210 :  fltmgr!FltpFastIoRead+0x1d0
fffff880`0a5369c0 fffff880`011d252f :  00000000`00000000 00000000`00000801 fffffa80`03b6bd90 6b6c6d4d`75452401 :  fltmgr!FltpPerformFastIoCall+0x88
fffff880`0a536a20 fffff800`02d7e949 :  fffffa80`069f4210 fffffa80`00000001 fffffa80`03b7d9f0 fffffa80`069f4210 :  fltmgr!FltpFastIoRead+0xcf
fffff880`0a536ac0 fffff800`02a93ed3 :  00000000`000004e0 00000000`00000000 00000000`00000000 00000000`00000000 :  nt!NtReadFile+0x417
fffff880`0a536bb0 00000000`75452e09 :  00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 :  nt!KiSystemServiceCopyEnd+0x13
00000000`07f6ef78 00000000`00000000 :  00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 :  0x75452e09


STACK_COMMAND:   kb

FOLLOWUP_IP:  
nt!MiBadShareCount+4c
fffff800`02b1dd7c cc              int     3

SYMBOL_STACK_INDEX:   1

SYMBOL_NAME:   nt!MiBadShareCount+4c

FOLLOWUP_NAME:   MachineOwner

MODULE_NAME:  nt

DEBUG_FLR_IMAGE_TIMESTAMP:   4e02aaa3

IMAGE_NAME:   memory_corruption

FAILURE_BUCKET_ID:   X64_0x4E_99_nt!MiBadShareCount+4c

BUCKET_ID:   X64_0x4E_99_nt!MiBadShareCount+4c

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



RE: Problem z blue screenami - pikolo000 - 04.01.2012 16:57

poczytaj sobie tu http://www.slow7.pl/index.php?option=com_content&view=article&id=94%3Auruchamianie-systemu-windows-czyli-co-zrobi-gdy-mamy-problem-z-uruchomieniem&catid=39%3Ainstalacja-i-konfiguracja-W7&Itemid=30&limitstart=6