Skocz do zawartości


Zdjęcie

BSOD, nowy komp, problem


  • Zaloguj się, aby dodać odpowiedź
3 odpowiedzi w tym temacie

#1 Xemidra

Xemidra

    Nowy

  • 2 postów

Napisano 11 05 2010 - 13:50

Mam nowy komp, od jego początku mam z nim problemy tzn. często (szczególnie podczas grania) wyskakują BSOD. Zawsze przed jak i po tym zdarzeniu w dzienniku zdarzeń przewijają się te same komunikaty. Robiłem test programem memtest oraz pełne skanowanie 6 antywirusami oraz Spybodem. Skanowałem dysk na obeznośc "bad" sektorów i nic nie znalazło. Podczas BSOD najczęściej widnieje napis: MEMORY_MANAGENT. Mój system to Windows 7 x64 Ultimate.

Pierwszy BSOD:


Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


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

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c52000 PsLoadedModuleList = 0xfffff800`02e8fe50
Debug session time: Mon May 3 08:22:14.027 2010 (GMT+2)
System Uptime: 0 days 1:44:21.338
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa80018c5490, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33946 )

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

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

MEMORY_MANAGEMENT (1a)
 # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa80018c5490
Arg3: 000000000000ffff
Arg4: 0000000000000000

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


BUGCHECK_STR: 0x1a_41790

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: dwm.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80002d35ede to fffff80002cc2600

STACK_TEXT: 
fffff880`09f97968 fffff800`02d35ede : 00000000`0000001a 00000000`00041790 fffffa80`018c5490 00000000`0000ffff : nt!KeBugCheckEx
fffff880`09f97970 fffff800`02d03fca : 00000000`00000000 00000000`024dffff fffffa80`00000000 fffffa80`073efb30 : nt! ?? ::FNODOBFM::`string'+0x33946
fffff880`09f97b30 fffff800`02cc1853 : ffffffff`ffffffff 00000000`01e9e8c8 00000000`01e9e8c0 00000000`00008000 : nt!NtFreeVirtualMemory+0x5ca
fffff880`09f97c20 00000000`7785009a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`01e9e848 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7785009a


STACK_COMMAND: kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+33946
fffff800`02d35ede cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+33946

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb

FAILURE_BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33946

BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33946

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

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

MEMORY_MANAGEMENT (1a)
 # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa80018c5490
Arg3: 000000000000ffff
Arg4: 0000000000000000

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


BUGCHECK_STR: 0x1a_41790

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: dwm.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80002d35ede to fffff80002cc2600

STACK_TEXT: 
fffff880`09f97968 fffff800`02d35ede : 00000000`0000001a 00000000`00041790 fffffa80`018c5490 00000000`0000ffff : nt!KeBugCheckEx
fffff880`09f97970 fffff800`02d03fca : 00000000`00000000 00000000`024dffff fffffa80`00000000 fffffa80`073efb30 : nt! ?? ::FNODOBFM::`string'+0x33946
fffff880`09f97b30 fffff800`02cc1853 : ffffffff`ffffffff 00000000`01e9e8c8 00000000`01e9e8c0 00000000`00008000 : nt!NtFreeVirtualMemory+0x5ca
fffff880`09f97c20 00000000`7785009a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`01e9e848 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7785009a


STACK_COMMAND: kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+33946
fffff800`02d35ede cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+33946

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb

FAILURE_BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33946

BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33946

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

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

MEMORY_MANAGEMENT (1a)
 # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa80018c5490
Arg3: 000000000000ffff
Arg4: 0000000000000000

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


BUGCHECK_STR: 0x1a_41790

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: dwm.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80002d35ede to fffff80002cc2600

STACK_TEXT: 
fffff880`09f97968 fffff800`02d35ede : 00000000`0000001a 00000000`00041790 fffffa80`018c5490 00000000`0000ffff : nt!KeBugCheckEx
fffff880`09f97970 fffff800`02d03fca : 00000000`00000000 00000000`024dffff fffffa80`00000000 fffffa80`073efb30 : nt! ?? ::FNODOBFM::`string'+0x33946
fffff880`09f97b30 fffff800`02cc1853 : ffffffff`ffffffff 00000000`01e9e8c8 00000000`01e9e8c0 00000000`00008000 : nt!NtFreeVirtualMemory+0x5ca
fffff880`09f97c20 00000000`7785009a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`01e9e848 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7785009a


STACK_COMMAND: kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+33946
fffff800`02d35ede cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+33946

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb

FAILURE_BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33946

BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33946

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

3: kd> lmvm nt
start end module name
fffff800`02c52000 fffff800`0322e000 nt (pdb symbols) c:\symbols\ntkrnlmp.pdb\7E9A3CAB626845DE8E10816E3080A3B72\ntkrnlmp.pdb
 Loaded symbol image file: ntkrnlmp.exe
 Mapped memory image file: c:\symbols\ntoskrnl.exe\4B88CFEB5dc000\ntoskrnl.exe
 Image path: ntkrnlmp.exe
 Image name: ntkrnlmp.exe
 Timestamp: Sat Feb 27 08:55:23 2010 (4B88CFEB)
 CheckSum: 00545094
 ImageSize: 005DC000
 File version: 6.1.7600.16539
 Product version: 6.1.7600.16539
 File flags: 0 (Mask 3F)
 File OS: 40004 NT Win32
 File type: 1.0 App
 File date: 00000000.00000000
 Translations: 0409.04b0
 CompanyName: Microsoft Corporation
 ProductName: Microsoft® Windows® Operating System
 InternalName: ntkrnlmp.exe
 OriginalFilename: ntkrnlmp.exe
 ProductVersion: 6.1.7600.16539
 FileVersion: 6.1.7600.16539 (win7_gdr.100226-1909)
 FileDescription: NT Kernel & System
 LegalCopyright: © Microsoft Corporation. All rights reserved.

Drugi BSOD:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


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

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c52000 PsLoadedModuleList = 0xfffff800`02e8fe50
Debug session time: Wed May 5 16:57:51.666 2010 (GMT+2)
System Uptime: 0 days 3:27:22.977
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa80031b9570, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33946 )

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

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

MEMORY_MANAGEMENT (1a)
 # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa80031b9570
Arg3: 000000000000ffff
Arg4: 0000000000000000

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


BUGCHECK_STR: 0x1a_41790

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: Metin2Mod.bin

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80002d35ede to fffff80002cc2600

STACK_TEXT: 
fffff880`0782c828 fffff800`02d35ede : 00000000`0000001a 00000000`00041790 fffffa80`031b9570 00000000`0000ffff : nt!KeBugCheckEx
fffff880`0782c830 fffff800`02cf5cc9 : 00000000`00000000 00000000`0fbb4fff ffffffff`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x33946
fffff880`0782c9f0 fffff800`02fdc170 : fffffa80`06d36180 0007ffff`00000000 fffffa80`06e8b260 fffffa80`06e8b260 : nt!MiRemoveMappedView+0xd9
fffff880`0782cb10 fffff800`02fdc57b : 00000000`00000000 00000000`0bd80000 fffffa80`00000001 00000000`00008001 : nt!MiUnmapViewOfSection+0x1b0
fffff880`0782cbd0 fffff800`02cc1853 : ffffffff`ffffffff 00000000`0008e310 fffffa80`05e3e880 00000000`00008000 : nt!NtUnmapViewOfSection+0x5f
fffff880`0782cc20 00000000`77a5015a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008e308 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77a5015a


STACK_COMMAND: kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+33946
fffff800`02d35ede cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+33946

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb

FAILURE_BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33946

BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33946

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

3: kd> lmvm nt
start end module name
fffff800`02c52000 fffff800`0322e000 nt (pdb symbols) c:\symbols\ntkrnlmp.pdb\7E9A3CAB626845DE8E10816E3080A3B72\ntkrnlmp.pdb
 Loaded symbol image file: ntkrnlmp.exe
 Mapped memory image file: c:\symbols\ntoskrnl.exe\4B88CFEB5dc000\ntoskrnl.exe
 Image path: ntkrnlmp.exe
 Image name: ntkrnlmp.exe
 Timestamp: Sat Feb 27 08:55:23 2010 (4B88CFEB)
 CheckSum: 00545094
 ImageSize: 005DC000
 File version: 6.1.7600.16539
 Product version: 6.1.7600.16539
 File flags: 0 (Mask 3F)
 File OS: 40004 NT Win32
 File type: 1.0 App
 File date: 00000000.00000000
 Translations: 0409.04b0
 CompanyName: Microsoft Corporation
 ProductName: Microsoft® Windows® Operating System
 InternalName: ntkrnlmp.exe
 OriginalFilename: ntkrnlmp.exe
 ProductVersion: 6.1.7600.16539
 FileVersion: 6.1.7600.16539 (win7_gdr.100226-1909)
 FileDescription: NT Kernel & System
 LegalCopyright: © Microsoft Corporation. All rights reserved.

Trzeci BSOD:


Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


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

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c17000 PsLoadedModuleList = 0xfffff800`02e54e50
Debug session time: Fri May 7 18:47:10.332 2010 (GMT+2)
System Uptime: 0 days 4:01:20.082
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa8000042060, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33946 )

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

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

MEMORY_MANAGEMENT (1a)
 # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa8000042060
Arg3: 000000000000ffff
Arg4: 0000000000000000

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


BUGCHECK_STR: 0x1a_41790

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: explorer.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80002cfaede to fffff80002c87600

STACK_TEXT: 
fffff880`06d7b828 fffff800`02cfaede : 00000000`0000001a 00000000`00041790 fffffa80`00042060 00000000`0000ffff : nt!KeBugCheckEx
fffff880`06d7b830 fffff800`02cbacc9 : 00000000`00000000 00000000`16955fff fffffa80`00000000 fffff800`02c90000 : nt! ?? ::FNODOBFM::`string'+0x33946
fffff880`06d7b9f0 fffff800`02fa1170 : fffffa80`06e7e110 0007ffff`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9
fffff880`06d7bb10 fffff800`02fa157b : 00000000`00000000 00000000`15600000 fffffa80`00000001 fffffa80`067a6490 : nt!MiUnmapViewOfSection+0x1b0
fffff880`06d7bbd0 fffff800`02c86853 : fffffa80`03c11060 fffff880`06d7bca0 fffffa80`073f2060 00000000`0951f870 : nt!NtUnmapViewOfSection+0x5f
fffff880`06d7bc20 00000000`778a015a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`065de858 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x778a015a


STACK_COMMAND: kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+33946
fffff800`02cfaede cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+33946

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb

FAILURE_BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33946

BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+33946

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

0: kd> lmvm nt
start end module name
fffff800`02c17000 fffff800`031f3000 nt (pdb symbols) c:\symbols\ntkrnlmp.pdb\7E9A3CAB626845DE8E10816E3080A3B72\ntkrnlmp.pdb
 Loaded symbol image file: ntkrnlmp.exe
 Mapped memory image file: c:\symbols\ntoskrnl.exe\4B88CFEB5dc000\ntoskrnl.exe
 Image path: ntkrnlmp.exe
 Image name: ntkrnlmp.exe
 Timestamp: Sat Feb 27 08:55:23 2010 (4B88CFEB)
 CheckSum: 00545094
 ImageSize: 005DC000
 File version: 6.1.7600.16539
 Product version: 6.1.7600.16539
 File flags: 0 (Mask 3F)
 File OS: 40004 NT Win32
 File type: 1.0 App
 File date: 00000000.00000000
 Translations: 0409.04b0
 CompanyName: Microsoft Corporation
 ProductName: Microsoft® Windows® Operating System
 InternalName: ntkrnlmp.exe
 OriginalFilename: ntkrnlmp.exe
 ProductVersion: 6.1.7600.16539
 FileVersion: 6.1.7600.16539 (win7_gdr.100226-1909)
 FileDescription: NT Kernel & System
 LegalCopyright: © Microsoft Corporation. All rights reserved.

Czwarty BSOD:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


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

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c4a000 PsLoadedModuleList = 0xfffff800`02e87e50
Debug session time: Sat May 8 12:53:06.320 2010 (GMT+2)
System Uptime: 0 days 0:29:36.005
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41284, 7fefbddc001, 0, fffff70001080000}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4a83 )

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

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

MEMORY_MANAGEMENT (1a)
 # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041284, A PTE or the working set list is corrupt.
Arg2: 000007fefbddc001
Arg3: 0000000000000000
Arg4: fffff70001080000

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


BUGCHECK_STR: 0x1a_41284

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: SearchProtocol

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80002d10df3 to fffff80002cba600

STACK_TEXT: 
fffff880`077645f8 fffff800`02d10df3 : 00000000`0000001a 00000000`00041284 000007fe`fbddc001 00000000`00000000 : nt!KeBugCheckEx
fffff880`07764600 fffff800`02d2dc03 : fffffa80`00000000 00000000`000000e3 00000000`00000000 000007fe`ff590000 : nt! ?? ::FNODOBFM::`string'+0x4a83
fffff880`07764640 fffff800`02cedcc9 : fffffa80`00000000 000007fe`fbebbfff 00000000`00000000 fffffa80`04d5c0c8 : nt! ?? ::FNODOBFM::`string'+0x3364b
fffff880`07764800 fffff800`02c8d734 : ffffffff`ffffffff fffff880`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9
fffff880`07764920 fffff800`02fa0c4f : fffff8a0`0991ea70 fffff880`07764c20 00000000`00000000 fffffa80`041a8820 : nt!MmCleanProcessAddressSpace+0x228
fffff880`07764970 fffff800`02f794d1 : 00000000`00000000 fffff8a0`09a97601 000007ff`fffac000 00000000`00000000 : nt!PspExitThread+0x92f
fffff880`07764a30 fffff800`02c970e3 : 00000000`00000000 fffffa80`05eb59d0 00000000`00000000 00000000`00000000 : nt!PsExitSpecialApc+0x1d
fffff880`07764a60 fffff800`02c97520 : 00000000`77724298 fffff880`07764ae0 fffff800`02f795dc 00000000`00000001 : nt!KiDeliverApc+0x2eb
fffff880`07764ae0 fffff800`02cb98f7 : fffffa80`041a8820 00000000`77724270 00000000`000000c0 fffff8a0`09a5a030 : nt!KiInitiateUserApc+0x70
fffff880`07764c20 00000000`776717ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`0134f528 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x776717ba


STACK_COMMAND: kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+4a83
fffff800`02d10df3 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+4a83

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb

FAILURE_BUCKET_ID: X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4a83

BUCKET_ID: X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4a83

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

2: kd> lmvm nt
start end module name
fffff800`02c4a000 fffff800`03226000 nt (pdb symbols) c:\symbols\ntkrnlmp.pdb\7E9A3CAB626845DE8E10816E3080A3B72\ntkrnlmp.pdb
 Loaded symbol image file: ntkrnlmp.exe
 Mapped memory image file: c:\symbols\ntoskrnl.exe\4B88CFEB5dc000\ntoskrnl.exe
 Image path: ntkrnlmp.exe
 Image name: ntkrnlmp.exe
 Timestamp: Sat Feb 27 08:55:23 2010 (4B88CFEB)
 CheckSum: 00545094
 ImageSize: 005DC000
 File version: 6.1.7600.16539
 Product version: 6.1.7600.16539
 File flags: 0 (Mask 3F)
 File OS: 40004 NT Win32
 File type: 1.0 App
 File date: 00000000.00000000
 Translations: 0409.04b0
 CompanyName: Microsoft Corporation
 ProductName: Microsoft® Windows® Operating System
 InternalName: ntkrnlmp.exe
 OriginalFilename: ntkrnlmp.exe
 ProductVersion: 6.1.7600.16539
 FileVersion: 6.1.7600.16539 (win7_gdr.100226-1909)
 FileDescription: NT Kernel & System
 LegalCopyright: © Microsoft Corporation. All rights reserved.


Piąty BSOD:


Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


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

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c68000 PsLoadedModuleList = 0xfffff800`02ea5e50
Debug session time: Sat May 8 15:09:56.506 2010 (GMT+2)
System Uptime: 0 days 1:19:01.192
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FE, {8, 6, 6, fffffa80058cfb20}

Probably caused by : usbhub.sys ( usbhub!UsbhHubProcessChangeWorker+ec )

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

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

BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 0000000000000008, USBBUGCODE_RESERVED_USBHUB
Arg2: 0000000000000006, USBHUB_TRAP_FATAL_TIMEOUT
Arg3: 0000000000000006, TimeoutCode: Timeout_PCE_Disable_Action - PortData->PortChangeListDone - Timeout trying to set Disable bit
Arg4: fffffa80058cfb20, TimeoutContext - PortData

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


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xFE

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff8800584a9ec to fffff80002cd8600

STACK_TEXT: 
fffff880`031cbc18 fffff880`0584a9ec : 00000000`000000fe 00000000`00000008 00000000`00000006 00000000`00000006 : nt!KeBugCheckEx
fffff880`031cbc20 fffff800`02fd5827 : fffffa80`057de050 fffffa80`057b0230 ffffffff`dc3a58a0 fffff800`02e7d5f8 : usbhub!UsbhHubProcessChangeWorker+0xec
fffff880`031cbc80 fffff800`02ce5861 : fffff800`02e7d500 fffff800`02fd5804 fffffa80`039e9b60 00000000`00000000 : nt!IopProcessWorkItem+0x23
fffff880`031cbcb0 fffff800`02f7da86 : 0000056e`00000000 fffffa80`039e9b60 00000000`00000080 fffffa80`039d6040 : nt!ExpWorkerThread+0x111
fffff880`031cbd40 fffff800`02cb6b06 : fffff880`02f63180 fffffa80`039e9b60 fffff880`02f6dfc0 0000056e`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031cbd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP: 
usbhub!UsbhHubProcessChangeWorker+ec
fffff880`0584a9ec cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: usbhub!UsbhHubProcessChangeWorker+ec

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: usbhub

IMAGE_NAME: usbhub.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcc2d

FAILURE_BUCKET_ID: X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec

BUCKET_ID: X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec

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

2: kd> lmvm usbhub
start end module name
fffff880`05838000 fffff880`05892000 usbhub (pdb symbols) c:\symbols\usbhub.pdb\295DCA65F67B44BF8DD26C3B6D89A6F71\usbhub.pdb
 Loaded symbol image file: usbhub.sys
 Mapped memory image file: c:\symbols\usbhub.sys\4A5BCC2D5a000\usbhub.sys
 Image path: \SystemRoot\system32\DRIVERS\usbhub.sys
 Image name: usbhub.sys
 Timestamp: Tue Jul 14 02:07:09 2009 (4A5BCC2D)
 CheckSum: 0005BB10
 ImageSize: 0005A000
 File version: 6.1.7600.16385
 Product version: 6.1.7600.16385
 File flags: 0 (Mask 3F)
 File OS: 40004 NT Win32
 File type: 2.0 Dll
 File date: 00000000.00000000
 Translations: 0409.04b0
 CompanyName: Microsoft Corporation
 ProductName: Microsoft® Windows® Operating System
 InternalName: usbhub.sys
 OriginalFilename: usbhub.sys
 ProductVersion: 6.1.7600.16385
 FileVersion: 6.1.7600.16385 (win7_rtm.090713-1255)
 FileDescription: Default Hub Driver for USB
 LegalCopyright: © Microsoft Corporation. All rights reserved.

Szósty BSOD:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


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

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c03000 PsLoadedModuleList = 0xfffff800`02e40e50
Debug session time: Mon May 10 19:45:34.460 2010 (GMT+2)
System Uptime: 0 days 1:03:41.145
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {5100, fffff6fc80650f20, 2b4, 1}

Probably caused by : win32k.sys ( win32k!AllocateObject+dd )

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

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

MEMORY_MANAGEMENT (1a)
 # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000005100, The subtype of the bugcheck.
Arg2: fffff6fc80650f20
Arg3: 00000000000002b4
Arg4: 0000000000000001

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


BUGCHECK_STR: 0x1a_5100

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: explorer.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80002ccd267 to fffff80002c73600

STACK_TEXT: 
fffff880`07a3f718 fffff800`02ccd267 : 00000000`0000001a 00000000`00005100 fffff6fc`80650f20 00000000`000002b4 : nt!KeBugCheckEx
fffff880`07a3f720 fffff800`02c9e7fb : 00000000`00000698 fffff880`07a3f880 fffff900`c9e00000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0xae27
fffff880`07a3f830 fffff800`02da4ceb : 00000000`00698000 00000000`00698000 00000000`00000021 fffff880`07a3fab0 : nt!MiAllocatePagedPoolPages+0x4bb
fffff880`07a3f950 fffff800`02c85f60 : 00000000`00698000 fffff880`021c9cc0 00000000`00000021 00000000`00000000 : nt!MiAllocatePoolPages+0x8e2
fffff880`07a3faa0 fffff800`02da7bfe : 00000000`00000000 00000000`00095f21 fffff800`00000020 fffff880`021c9cc0 : nt!ExpAllocateBigPool+0xb0
fffff880`07a3fb90 fffff960`001828ed : 00000000`00003392 00000000`00000000 00000000`00000000 fffff960`001940d1 : nt!ExAllocatePoolWithTag+0x82e
fffff880`07a3fc80 fffff960`00183e0f : 00000000`00000001 fffff880`07a3fe18 00000000`00000001 fffff960`00194302 : win32k!AllocateObject+0xdd
fffff880`07a3fcc0 fffff960`00159f2f : fffff880`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!SURFMEM::bCreateDIB+0x1fb
fffff880`07a3fdb0 fffff960`00158fa5 : 00000000`2a010160 fffffa80`069cf4f0 00000000`00000000 00000000`00000001 : win32k!GreCreateDIBitmapReal+0x533
fffff880`07a3fee0 fffff800`02c72853 : 00000000`2a010160 fffffa80`00000780 00000000`000004b0 00000000`00000002 : win32k!NtGdiCreateDIBitmapInternal+0x231
fffff880`07a3ffb0 000007fe`fdb05e2a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`001ed988 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fdb05e2a


STACK_COMMAND: kb

FOLLOWUP_IP: 
win32k!AllocateObject+dd
fffff960`001828ed 488bd8 mov rbx,rax

SYMBOL_STACK_INDEX: 6

SYMBOL_NAME: win32k!AllocateObject+dd

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc5e0

FAILURE_BUCKET_ID: X64_0x1a_5100_win32k!AllocateObject+dd

BUCKET_ID: X64_0x1a_5100_win32k!AllocateObject+dd

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

3: kd> lmvm win32k
start end module name
fffff960`000d0000 fffff960`003df000 win32k (pdb symbols) c:\symbols\win32k.pdb\A9F6403F14074E9D8A07D0AA6F0C1CFF2\win32k.pdb
 Loaded symbol image file: win32k.sys
 Mapped memory image file: c:\symbols\win32k.sys\4A5BC5E030f000\win32k.sys
 Image path: \SystemRoot\System32\win32k.sys
 Image name: win32k.sys
 Timestamp: Tue Jul 14 01:40:16 2009 (4A5BC5E0)
 CheckSum: 002FE623
 ImageSize: 0030F000
 File version: 6.1.7600.16385
 Product version: 6.1.7600.16385
 File flags: 0 (Mask 3F)
 File OS: 40004 NT Win32
 File type: 3.7 Driver
 File date: 00000000.00000000
 Translations: 0409.04b0
 CompanyName: Microsoft Corporation
 ProductName: Microsoft® Windows® Operating System
 InternalName: win32k.sys
 OriginalFilename: win32k.sys
 ProductVersion: 6.1.7600.16385
 FileVersion: 6.1.7600.16385 (win7_rtm.090713-1255)
 FileDescription: Multi-User Win32 Driver
 LegalCopyright: © Microsoft Corporation. All rights reserved.

Załączam również:

Dziennik zdarzeń oraz all mini-dump:

http://www.przeklej....tx-0014cq2er6jo
http://www.przeklej....mp-0014cq2ns5a5
http://www.przeklej....mp-0014cq2tk40i
http://www.przeklej....mp-0014cq32hbq4
http://www.przeklej....mp-0014cq3e1agh
http://www.przeklej....mp-0014cq42q7tb
http://www.przeklej....mp-0014cq48q2mv


HASŁO DO PLIKÓW: pomocy

PROSZĘ NIECH MI KTOŚ POMOŻE Dołączona grafika
Ja już nie wiem co z tym zrobić !


  • 0

#2 geronimoo

geronimoo

    Uzależniony od forum

  • 1 457 postów

Napisano 11 05 2010 - 14:21

Testowałeś pamięć memtestem z botowalnej płyty? I jak długo? Spakuj katalog "minidump" rarem wyślij na speedyshare a tu daj link do pliku. Podaj dokładną konfigurację sprzętową, dokładną nazwę zasilacza spisz z naklejki na nim (widoczna po zdjęciu boku obudowy).

Użytkownik geronimoo edytował ten post 11 05 2010 - 14:22

  • 0

#3 Xemidra

Xemidra

    Nowy

  • 2 postów

Napisano 11 05 2010 - 17:43

AMD Phenom II X4 955 Black Edit /3.2GHz, 125W, BOX, AM3/
Asus M4A77TD PRO
A-Data 4GB (2x2GB) 1600MHz CL9 Gaming
Asus Radeon HD5770 1GB ddr5
Western Digital Blue 500GB 7200rpm 16MB cache SATAII
bequiet! PurePower L7 530W
Cooler Master Elite 332 (Black)
i czytnik kart pamięci Mode Com ze złączem USB, właśnie to w nim gdy był podłączony pendrive pokazał się jeden z BSOD
  • 0

#4 emson263

emson263

    Obserwator

  • 5 postów

Napisano 13 09 2010 - 00:33

Miałem identyczną sytuację gdy byłem u klienta na serwisie okazało się że jeden z kabelków się rozlutował przy stacji dysku twardego, dostal szumów i wibracji pracował nieco za głośno jestem na 95% przekonany ze i w Twoim przypadku będzie to dysk twardy




[warn=Kantoro] 
Za wprowadzanie w bład dodaję ostrzeżenie. Jak kabelek mógł się rozlutować "przy stacji dysku twardego".
[/warn] 

Użytkownik Kantoro edytował ten post 31 10 2010 - 12:54

  • 0

Zobacz więcej tematów z tagiem: kompilacja 7601 Memtest86+ testowanie pamięci BSOD blue screen niebieski ekran



Użytkownicy przeglądający ten temat: 0

0 użytkowników, 0 gości, 0 anonimowych