Na razie wywal Daemon Tools lub zastąp go czymś innym np Power iso itp.
Jedziemy z błędami.
Ze wszystkich przejrzanych zrzutów widać problem z pluginem flasha do firefoxa lub samym firefoxem.
Na chwilę obecną proszę sprawdzić jakich dodatków się używa i testowo je powyłączać. Plugin Flash'a usunąć i zainstalować najnowszy. Jeśli to nie pomoże proszę usunąć Firefox'a najlepiej czymś co wyczyści wszystko po nim - np Revo Uninstaller a potem restart. W międzyczasie po deinstalacji proszę sprawdzić jak zachowuje się doinstalowana kontrolka flash ocx dla internet explorera. Jeśli Ok no to zainstalować stabilną wersję liska i pluginu do niego a potem ostrożnie doinstalowywać resztę dodatków o ile były.
Ogólnie widać, że coś ryje niepostrzeżenie po liście PFN i z tego tytułu rodzą się błędy kiedy poszczególne sterowniki czy moduły systemu próbują odczytać to co zarezerwowały w pamięci RAM.
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\42\022313-34959-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
Machine Name:
Kernel base = 0xfffff800`03053000 PsLoadedModuleList = 0xfffff800`03297670
Debug session time: Sat Feb 23 18: 45: 49.883 2013 (UTC + 1: 00)
System Uptime: 0 days 0: 45: 33.771
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {41201, fffff6800007d368, c240000124ba5867, fffffa800664b910}
Probably caused by : ntkrnlmp.exe ( nt! ? : FNODOBFM: `string'+13702 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041201, The subtype of the bugcheck.
Arg2: fffff6800007d368
Arg3: c240000124ba5867
Arg4: fffffa800664b910
Debugging Details:
------------------
BUGCHECK_STR: 0x1a_41201
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: FlashPlayerPlu
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80003124abe to fffff800030c8c40
STACK_TEXT:
fffff880`027e2978 fffff800`03124abe : 00000000`0000001a 00000000`00041201 fffff680`0007d368 c2400001`24ba5867 : nt!KeBugCheckEx
fffff880`027e2980 fffff800`03093b91 : fffffa80`045a2d40 00000000`12e07000 fffffa80`04394b50 c2400001`24ba5867 : nt! ? : FNODOBFM: `string'+0x13702
fffff880`027e29c0 fffff800`0309382a : fffffa80`0664b910 fffffa80`0443cb30 fffffa80`0443cb30 00000000`0fa6d000 : nt!MiQueryAddressState+0x2b1
fffff880`027e2a10 fffff800`033a5c74 : 00000000`00000004 00000000`0fa6e000 fffffa80`0664b910 00000000`0010e068 : nt!MiQueryAddressSpan+0xaa
fffff880`027e2a80 fffff800`030c7ed3 : ffffffff`ffffffff fffffa80`04394b50 fffff880`027e2b88 00000000`0010e008 : nt!NtQueryVirtualMemory+0x382
fffff880`027e2b70 00000000`774a154a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0010dfe8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x774a154a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ? : FNODOBFM: `string'+13702
fffff800`03124abe cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ? : FNODOBFM: `string'+13702
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 50e79935
FAILURE_BUCKET_ID: X64_0x1a_41201_nt!_??_: FNODOBFM: _string_+13702
BUCKET_ID: X64_0x1a_41201_nt!_??_: FNODOBFM: _string_+13702
Followup: MachineOwner
---------
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\42\022213-27690-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
Machine Name:
Kernel base = 0xfffff800`03019000 PsLoadedModuleList = 0xfffff800`0325d670
Debug session time: Fri Feb 22 00: 18: 58.007 2013 (UTC + 1: 00)
System Uptime: 0 days 7: 12: 51.036
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
....................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 4E, {99, 136bad, 2, 12c02c}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
Followup: MachineOwner
---------
1: 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: 0000000000136bad, page frame number
Arg3: 0000000000000002, current page state
Arg4: 000000000012c02c, 0
Debugging Details:
------------------
BUGCHECK_STR: 0x4E_99
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: firefox.exe
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff8000311dbfc to fffff8000308ec40
STACK_TEXT:
fffff880`08e2df18 fffff800`0311dbfc : 00000000`0000004e 00000000`00000099 00000000`00136bad 00000000`00000002 : nt!KeBugCheckEx
fffff880`08e2df20 fffff800`0303aed0 : 00000000`00000000 fffff680`000cf360 00000000`00000002 00000000`00000001 : nt!MiBadShareCount+0x4c
fffff880`08e2df60 fffff800`0305e7f3 : fffffa80`074cc710 fffff700`0000c549 0000007f`fffffff8 fffff8a0`003350b0 : nt! ? : FNODOBFM: `string'+0x32418
fffff880`08e2dff0 fffff800`0305f8ce : fffffa80`074cc710 fffffa80`0000001c fffff8a0`0000927c fffff880`00000000 : nt!MiDeleteAddressesInWorkingSet+0x307
fffff880`08e2e8a0 fffff800`0336705a : fffff8a0`0a5572c0 fffff880`08e2ebe0 00000000`00000000 fffffa80`0435eb50 : nt!MmCleanProcessAddressSpace+0x96
fffff880`08e2e8f0 fffff800`0334d15d : 00000000`00000001 00000000`00000001 00000000`fff74000 fffffa80`075e5b50 : nt!PspExitThread+0x56a
fffff880`08e2e9f0 fffff800`0308175a : 00000000`00000100 fffffa80`0435ec10 00000000`00000001 fffff800`0308485d : nt!PsExitSpecialApc+0x1d
fffff880`08e2ea20 fffff800`03081aa0 : 00000000`00000246 fffff880`08e2eaa0 fffff800`0334d0d0 00000000`00000001 : nt!KiDeliverApc+0x2ca
fffff880`08e2eaa0 fffff800`0308df77 : fffffa80`0435eb50 00000000`0000043c 00000000`00000000 fffffa80`068fdee0 : nt!KiInitiateUserApc+0x70
fffff880`08e2ebe0 00000000`74b22e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`058eed68 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74b22e09
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiBadShareCount+4c
fffff800`0311dbfc cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!MiBadShareCount+4c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 50e79935
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x4E_99_nt!MiBadShareCount+4c
BUCKET_ID: X64_0x4E_99_nt!MiBadShareCount+4c
Followup: MachineOwner
---------
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\42\021813-32947-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
Machine Name:
Kernel base = 0xfffff800`0300a000 PsLoadedModuleList = 0xfffff800`0324e670
Debug session time: Mon Feb 18 18: 06: 16.770 2013 (UTC + 1: 00)
System Uptime: 0 days 0: 24: 29.796
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff8800693a58b, fffff880045e93b8, fffff880045e8c10}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_LINEAR_POOL: FindBlockRun+83 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8800693a58b, The address that the exception occurred at
Arg3: fffff880045e93b8, Exception Record Address
Arg4: fffff880045e8c10, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo
FAULTING_IP:
dxgmms1!VIDMM_LINEAR_POOL: FindBlockRun+83
fffff880`0693a58b 4c8b4e08 mov r9,qword ptr [rsi+8]
EXCEPTION_RECORD: fffff880045e93b8 -- (.exr 0xfffff880045e93b8)
ExceptionAddress: fffff8800693a58b (dxgmms1!VIDMM_LINEAR_POOL: FindBlockRun+0x0000000000000083)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff880045e8c10 -- (.cxr 0xfffff880045e8c10)
rax=303844354144317b rbx=454646304330450d rcx=fffffa8005449670
rdx=0000000000027000 rsi=454646304330450d rdi=fffffa8005449690
rip=fffff8800693a58b rsp=fffff880045e95f8 rbp=0000000000027000
r8=454646304330452d r9=0000000100000001 r10=303844364144317c
r11=0000000000000000 r12=0000000000001000 r13=0000000000000000
r14=0000000000000000 r15=000000003b360000
iopl=0 nv up ei pl nz na pe cy
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010203
dxgmms1!VIDMM_LINEAR_POOL: FindBlockRun+0x83:
fffff880`0693a58b 4c8b4e08 mov r9,qword ptr [rsi+8] ds: 002b: 45464630`43304515=?
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod 0x%08lx odwo
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032b8100
ffffffffffffffff
FOLLOWUP_IP:
dxgmms1!VIDMM_LINEAR_POOL: FindBlockRun+83
fffff880`0693a58b 4c8b4e08 mov r9,qword ptr [rsi+8]
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff8800693a287 to fffff8800693a58b
STACK_TEXT:
fffff880`045e95f8 fffff880`0693a287 : 00000000`00000000 00000000`00027000 00000000`00001000 fffffa80`05449670 : dxgmms1!VIDMM_LINEAR_POOL: FindBlockRun+0x83
fffff880`045e9610 fffff880`069346f2 : 00000000`00000001 00000000`00000000 fffff8a0`03c1e010 fffffa80`05449780 : dxgmms1!VIDMM_LINEAR_POOL: Allocate+0x8f
fffff880`045e96c0 fffff880`06925015 : 00000000`00027000 00000000`00000001 fffff880`045e9800 00000000`00000000 : dxgmms1!VIDMM_SEGMENT: ReserveResource+0x21a
fffff880`045e9770 fffff880`0692437b : fffff8a0`03c1e010 00000000`3b360000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL: AcquireGPUResourcesFromHintedBankInformation+0x215
fffff880`045e9810 fffff880`0692127c : 00000000`0000000c 00000000`00000000 00000000`00000000 fffffa80`00000000 : dxgmms1!VIDMM_GLOBAL: FindResourcesForOneAllocation+0x25f
fffff880`045e98d0 fffff880`0693b65d : 00000000`00000000 fffff8a0`0484ec10 fffffa80`00000000 fffffa80`068e41c0 : dxgmms1!VIDMM_GLOBAL: PrepareDmaBuffer+0x7e8
fffff880`045e9aa0 fffff880`0693b398 : fffff800`04461080 fffff880`0693ad00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`045e9c90 fffff880`0693ae96 : 00000000`00000000 fffffa80`053c4710 00000000`00000080 fffffa80`06203410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`045e9cc0 fffff800`0332034a : 00000000`04bbd3cd fffffa80`06208b50 fffffa80`03fd3040 fffffa80`06208b50 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`045e9d00 fffff800`03070946 : fffff800`031fbe80 fffffa80`06208b50 fffff800`03209cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`045e9d40 00000000`00000000 : fffff880`045ea000 fffff880`045e4000 fffff880`045e93c0 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: dxgmms1!VIDMM_LINEAR_POOL: FindBlockRun+83
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce799c1
STACK_COMMAND: .cxr 0xfffff880045e8c10 ; kb
FAILURE_BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_LINEAR_POOL: FindBlockRun+83
BUCKET_ID: X64_0x7E_dxgmms1!VIDMM_LINEAR_POOL: FindBlockRun+83
Followup: MachineOwner
---------
A tu jest niespodzianka o której nie wiem na razie co myśleć bo nie jest spowodowana przez plugin flash'a.
Dobrze było by puścić memtest86 na parę godzin.
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\42\021313-53274-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18044.amd64fre.win7sp1_gdr.130104-1431
Machine Name:
Kernel base = 0xfffff800`02e0f000 PsLoadedModuleList = 0xfffff800`03053670
Debug session time: Wed Feb 13 15: 45: 31.297 2013 (UTC + 1: 00)
System Uptime: 0 days 0: 24: 21.186
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 4E, {99, 3f85f, 2, 13749e}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
Followup: MachineOwner
---------
1: 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: 000000000003f85f, page frame number
Arg3: 0000000000000002, current page state
Arg4: 000000000013749e, 0
Debugging Details:
------------------
BUGCHECK_STR: 0x4E_99
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: winlogon.exe
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80002f13bfc to fffff80002e84c40
STACK_TEXT:
fffff880`0949cf18 fffff800`02f13bfc : 00000000`0000004e 00000000`00000099 00000000`0003f85f 00000000`00000002 : nt!KeBugCheckEx
fffff880`0949cf20 fffff800`02e30ed0 : 00000000`00000000 fffff680`00001670 00000000`00000002 00000000`00000001 : nt!MiBadShareCount+0x4c
fffff880`0949cf60 fffff800`02e547f3 : fffffa80`05732b30 fffff700`000007d1 0000007f`fffffff8 fffff8a0`0d8e0238 : nt! ? : FNODOBFM: `string'+0x32418
fffff880`0949cff0 fffff800`02e558ce : fffffa80`05732b30 fffffa80`00000000 fffff8a0`0000028b fffff880`00000000 : nt!MiDeleteAddressesInWorkingSet+0x307
fffff880`0949d8a0 fffff800`0315d05a : fffff8a0`052de730 fffff880`0949dbe0 00000000`00000000 fffffa80`0730e060 : nt!MmCleanProcessAddressSpace+0x96
fffff880`0949d8f0 fffff800`0314315d : 00000000`000000ff fffff880`0949db01 000007ff`fffd9000 fffffa80`05407060 : nt!PspExitThread+0x56a
fffff880`0949d9f0 fffff800`02e7775a : 00000000`00000001 fffff880`0949db68 00000000`02a6fca0 fffff880`0949dba0 : nt!PsExitSpecialApc+0x1d
fffff880`0949da20 fffff800`02e77aa0 : 00000000`77a045e8 fffff880`0949daa0 fffff800`031430d0 00000000`00000001 : nt!KiDeliverApc+0x2ca
fffff880`0949daa0 fffff800`02e83f77 : fffffa80`0730e060 00000000`77a045c0 fffff880`000000c0 00000000`00000000 : nt!KiInitiateUserApc+0x70
fffff880`0949dbe0 00000000`77952c1a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`02a6fab8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77952c1a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiBadShareCount+4c
fffff800`02f13bfc cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!MiBadShareCount+4c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 50e79935
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x4E_99_nt!MiBadShareCount+4c
BUCKET_ID: X64_0x4E_99_nt!MiBadShareCount+4c
Followup: MachineOwner
---------