milek321 utworzono 18 sierpnia 2014 utworzono 18 sierpnia 2014 Witam, kupiłem kompa z allegro i od początku były z nim problemy. Wystepowaly czasem bsody, juz pisalem na forum itp, ale dało sie fukcjonować na tym kompie. Ostatnio zaniosłem kompa do naprawy. Typek powiedział, że zasilacz wymienił mi go, przeinstalował system zainstalowal stery. No i odbieram kompa a wlaczam fifke a tu dalej ten pieprzony problem... Tutaj zalaczam odczyt z win debugera Microsoft (R) Windows Debugger Version 6.11.0001.402 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\Users\Krzysiek\Documents\081814-53227-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: *** Invalid *** **************************************************************************** * Symbol loading may be unreliable without a symbol search path. * * Use .symfix to have the debugger choose a symbol path. * * After setting your symbol path, use .reload to refresh symbol locations. * **************************************************************************** Executable search path is: ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image Unknown_Module_00000000, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Unknown_Module_00000000 Unable to add module at 00000000 WARNING: .reload failed, module list may be incomplete Debugger can not determine kernel base address Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.18409.x86fre.win7sp1_gdr.140303-2144 Machine Name: Kernel base = 0x82e08000 PsLoadedModuleList = 0x82f515b0 Debug session time: Mon Aug 18 14:28:10.359 2014 (GMT+2) System Uptime: 0 days 0:32:29.060 ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image Unknown_Module_00000000, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Unknown_Module_00000000 Unable to add module at 00000000 WARNING: .reload failed, module list may be incomplete Debugger can not determine kernel base address Loading Kernel Symbols .Unable to load image Unknown_Module_00000000, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Unknown_Module_00000000 Unable to add module at 00000000 Loading User Symbols Loading unloaded module list ..Missing image name, possible paged-out or corrupt data. .. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {e09154, 2, 0, 82e8bac6} ***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057. Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) Followup: MachineOwner --------- Czego to może być wina ??
Youki komentarz 18 sierpnia 2014 komentarz 18 sierpnia 2014 Najpierw podaj pełną konfigurację Twojego PC wraz z marką i mocą zasilacza. Poza tym nie używasz prawidłowych symboli. http://www.forumpc.pl/tutorials/article/79-debugging-tools-for-windows-i-pliki-minidump/
milek321 komentarz 18 sierpnia 2014 Autor komentarz 18 sierpnia 2014 (edytowane) Najpierw podaj pełną konfigurację Twojego PC wraz z marką i mocą zasilacza. Poza tym nie używasz prawidłowych symboli. http://www.forumpc.pl/tutorials/article/79-debugging-tools-for-windows-i-pliki-minidump/ karta graficzna nvidia geforce gt 220 1gb procek amd athlon ii x4 630 płya główna msi nf520T-35/NF725T-C35 (MS-7615) pamiec 4gb ddr2 kart dzwiekowa nvidia gt 216 dysk samsung ata sp1654n 160gb mam tez drugi na ktorym jest system windows samsung ata 40gb sv4012h Zasilacz jest newka dzisiaj wymieniony takze mysle ze ten problem odpada, zaraz zeedytuje i napisze jak cos jaki jest zasilacz, srubokret ogarne
Youki komentarz 18 sierpnia 2014 komentarz 18 sierpnia 2014 To jeszcze sprawdz pliki Dump jak w linku wyżej.
Gość komentarz 18 sierpnia 2014 komentarz 18 sierpnia 2014 sprawdz osobno ram w róznych bankach pamieci
milek321 komentarz 18 sierpnia 2014 Autor komentarz 18 sierpnia 2014 (edytowane) Kolejne 2.. i jeden poprzedni [spoiler] Microsoft (R) Windows Debugger Version 6.11.0001.402 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\Users\Krzysiek\Documents\081814-38391-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 7601 (Service Pack 1) MP (4 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.18409.x86fre.win7sp1_gdr.140303-2144 Machine Name: Kernel base = 0x82e03000 PsLoadedModuleList = 0x82f4c5b0 Debug session time: Mon Aug 18 23:16:42.868 2014 (GMT+2) System Uptime: 0 days 4:15:13.569 Loading Kernel Symbols ............................................................... ................................................................ ........................ Loading User Symbols Loading unloaded module list ....... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000000A, {183da8b4, ff, 1, 83219446} Probably caused by : hardware ( amdppm!C1Halt+4 ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: 183da8b4, memory referenced Arg2: 000000ff, IRQL Arg3: 00000001, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: 83219446, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82f6c84c Unable to read MiSystemVaType memory at 82f4bf00 183da8b4 CURRENT_IRQL: 1c FAULTING_IP: hal!HalpClockInterruptPn+16e 83219446 0000 add byte ptr [eax],al CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System MISALIGNED_IP: hal!HalpClockInterruptPn+16e 83219446 0000 add byte ptr [eax],al LAST_CONTROL_TRANSFER: from 920733f6 to 83219446 STACK_TEXT: 8d952c28 920733f6 badb0d00 00000000 1f850c87 hal!HalpClockInterruptPn+0x16e 8d952c98 82e827ee 859e01b0 8d93b800 8d936000 amdppm!C1Halt+0x4 8d952d20 82e7a2cd 00000000 0000000e 868d9e28 nt!PoIdle+0x524 8d952d24 00000000 0000000e 868d9e28 868d9de0 nt!KiIdleLoop+0xd STACK_COMMAND: kb FOLLOWUP_IP: amdppm!C1Halt+4 920733f6 c3 ret SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: amdppm!C1Halt+4 FOLLOWUP_NAME: MachineOwner IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 MODULE_NAME: hardware FAILURE_BUCKET_ID: IP_MISALIGNED BUCKET_ID: IP_MISALIGNED Followup: MachineOwner --------- [/spoiler] [spoiler] Microsoft (R) Windows Debugger Version 6.11.0001.402 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\Users\Krzysiek\Documents\081814-28220-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 7601 (Service Pack 1) MP (4 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.18409.x86fre.win7sp1_gdr.140303-2144 Machine Name: Kernel base = 0x82e19000 PsLoadedModuleList = 0x82f625b0 Debug session time: Mon Aug 18 19:00:28.828 2014 (GMT+2) System Uptime: 0 days 1:37:18.529 Loading Kernel Symbols ............................................................... ................................................................ ......................... Loading User Symbols Loading unloaded module list ............. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000000A, {c5078544, 1c, 0, 82e9372a} Probably caused by : amdppm.sys ( amdppm!C1Halt+4 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: c5078544, memory referenced Arg2: 0000001c, IRQL Arg3: 00000000, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: 82e9372a, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from 82f8284c Unable to read MiSystemVaType memory at 82f61f00 c5078544 CURRENT_IRQL: 1c FAULTING_IP: nt!KeUpdateRunTime+10c 82e9372a 8b4c2414 mov ecx,dword ptr [esp+14h] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System LAST_CONTROL_TRANSFER: from 8322f430 to 82e9372a STACK_TEXT: 807e3c18 8322f430 00000002 000000d1 807e3d20 nt!KeUpdateRunTime+0x10c 807e3c18 9203f3f6 00000002 000000d1 807e3d20 hal!HalpClockInterruptPn+0x158 807e3c98 82e987ee 87e20398 807cc800 807c7000 amdppm!C1Halt+0x4 807e3d20 82e902cd 00000000 0000000e ece8fde5 nt!PoIdle+0x524 807e3d24 00000000 0000000e ece8fde5 df4aebcd nt!KiIdleLoop+0xd STACK_COMMAND: kb FOLLOWUP_IP: amdppm!C1Halt+4 9203f3f6 c3 ret SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: amdppm!C1Halt+4 FOLLOWUP_NAME: MachineOwner MODULE_NAME: amdppm IMAGE_NAME: amdppm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bbf07 FAILURE_BUCKET_ID: 0xA_amdppm!C1Halt+4 BUCKET_ID: 0xA_amdppm!C1Halt+4 Followup: MachineOwner[/spoiler] [spoiler] Microsoft (R) Windows Debugger Version 6.11.0001.402 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\Users\Krzysiek\Documents\081814-53227-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: Unable to load image Unknown_Module_00000000, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Unknown_Module_00000000 Unable to add module at 00000000 WARNING: .reload failed, module list may be incomplete Debugger can not determine kernel base address Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.18409.x86fre.win7sp1_gdr.140303-2144 Machine Name: Kernel base = 0x82e08000 PsLoadedModuleList = 0x82f515b0 Debug session time: Mon Aug 18 14:28:10.359 2014 (GMT+2) System Uptime: 0 days 0:32:29.060 Unable to load image Unknown_Module_00000000, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Unknown_Module_00000000 Unable to add module at 00000000 WARNING: .reload failed, module list may be incomplete Debugger can not determine kernel base address Loading Kernel Symbols .Unable to load image Unknown_Module_00000000, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Unknown_Module_00000000 Unable to add module at 00000000 Loading User Symbols Loading unloaded module list ..Missing image name, possible paged-out or corrupt data. .. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {e09154, 2, 0, 82e8bac6} ***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057. Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: 00e09154, memory referenced Arg2: 00000002, IRQL Arg3: 00000000, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: 82e8bac6, address which referenced memory Debugging Details: ------------------ ***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057. READ_ADDRESS: unable to get nt!MmSpecialPoolStart unable to get nt!MmSpecialPoolEnd unable to get nt!MmPoolCodeStart unable to get nt!MmPoolCodeEnd 00e09154 CURRENT_IRQL: 0 FAULTING_IP: +5652952f03add834 82e8bac6 ff155491e082 call dword ptr ds:[82E09154h] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA LAST_CONTROL_TRANSFER: from 82e8bac6 to 82e48b7f STACK_TEXT: WARNING: Frame IP not in any known module. Following frames may be wrong. 82f2fc14 82e8bac6 badb0d00 0000000b 000000d1 0x82e48b7f 82f2fc98 82e87877 85787818 82f3c380 82f32c00 0x82e8bac6 82f2fd20 82e7f2cd 00000000 0000000e 00000000 0x82e87877 82f2fd24 00000000 0000000e 00000000 00000000 0x82e7f2cd STACK_COMMAND: kb SYMBOL_NAME: ANALYSIS_INCONCLUSIVE FOLLOWUP_NAME: MachineOwner MODULE_NAME: Unknown_Module IMAGE_NAME: Unknown_Image DEBUG_FLR_IMAGE_TIMESTAMP: 0 BUCKET_ID: CORRUPT_MODULELIST Followup: MachineOwner ---------[/spoiler]
Gość komentarz 19 sierpnia 2014 komentarz 19 sierpnia 2014 irql wskazuje na problem ze sterownikami - jakis jest niewlasciwy - wadliwy
milek321 komentarz 19 sierpnia 2014 Autor komentarz 19 sierpnia 2014 (edytowane) Jeśli tak to zaraz ogarne z tymi sterownikami, niestety te bsody występują od kupna kompa praktycznie :cenzura: Patrze teraz na slim drivers, to wiekszość sterowników mam nieaktuialnych, sa nowsze. Po prostu zainstalowac we wszystkich nowsze wersje? Może ktoś wie jaki sterownik powoduje te błędy? nastepny po aktualizacji sterow [spoiler] Microsoft (R) Windows Debugger Version 6.11.0001.402 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\Users\Krzysiek\Documents\081914-24835-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 7601 (Service Pack 1) MP (4 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.18409.x86fre.win7sp1_gdr.140303-2144 Machine Name: Kernel base = 0x82e41000 PsLoadedModuleList = 0x82f8a5b0 Debug session time: Tue Aug 19 10:24:39.892 2014 (GMT+2) System Uptime: 0 days 0:06:13.593 Loading Kernel Symbols ............................................................... ................................................................ ......................... Loading User Symbols Loading unloaded module list ........ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007F, {d, 0, 0, 0} Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f) This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc) Consult an Intel x86 family manual to learn more about what these traps are. Here is a *portion* of those codes: If kv shows a taskGate use .tss on the part before the colon, then kv. Else if kv shows a trapframe use .trap on that value Else .trap on the appropriate frame will show where the trap was taken (on x86, this will be the ebp that goes with the procedure KiTrap) Endif kb will then show the corrected stack. Arguments: Arg1: 0000000d, EXCEPTION_GP_FAULT Arg2: 00000000 Arg3: 00000000 Arg4: 00000000 Debugging Details: ------------------ BUGCHECK_STR: 0x7f_d CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: AvastSvc.exe CURRENT_IRQL: 1c LAST_CONTROL_TRANSFER: from 6fdebe01 to 82e0d41e STACK_TEXT: 997bdd34 6fdebe01 badb0d00 00000000 00000000 hal!HalpClockInterruptPn+0x146 WARNING: Frame IP not in any known module. Following frames may be wrong. 00000010 00000000 00000000 00000000 00000000 0x6fdebe01 STACK_COMMAND: kb SYMBOL_NAME: ANALYSIS_INCONCLUSIVE FOLLOWUP_NAME: MachineOwner MODULE_NAME: Unknown_Module IMAGE_NAME: Unknown_Image DEBUG_FLR_IMAGE_TIMESTAMP: 0 BUCKET_ID: BAD_STACK Followup: MachineOwner --------- [/spoiler] pomoze ktos ? :xxx
milek321 komentarz 19 sierpnia 2014 Autor komentarz 19 sierpnia 2014 (edytowane) Zainstalowałem wszystkie aktualne stery co pokazywało w slim drivers. Odpalilem fifke na 10 minut i bum ; ) [spoiler] Microsoft (R) Windows Debugger Version 6.11.0001.402 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\Users\Krzysiek\Documents\081914-22557-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 7601 (Service Pack 1) MP (4 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.18409.x86fre.win7sp1_gdr.140303-2144 Machine Name: Kernel base = 0x82e4c000 PsLoadedModuleList = 0x82f955b0 Debug session time: Tue Aug 19 12:18:22.403 2014 (GMT+2) System Uptime: 0 days 0:37:24.119 Loading Kernel Symbols ............................................................... ................................................................ ....................... Loading User Symbols Loading unloaded module list ....... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000008E, {c000001d, 82ec501b, 807e3a6c, 0} Probably caused by : ntkrpamp.exe ( nt!KiSignalThread+25 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e) 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: c000001d, The exception code that was not handled Arg2: 82ec501b, The address that the exception occurred at Arg3: 807e3a6c, Trap Frame Arg4: 00000000 Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {WYJ FAULTING_IP: nt!KiSignalThread+25 82ec501b 740a je nt!KiSignalThread+0x31 (82ec5027) TRAP_FRAME: 807e3a6c -- (.trap 0xffffffff807e3a6c) ErrCode = 00000000 eax=00000000 ebx=807c7120 ecx=85a18001 edx=00000001 esi=85a18030 edi=85a18138 eip=82ec501b esp=807e3ae0 ebp=807e3ae8 iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 nt!KiSignalThread+0x25: 82ec501b 740a je nt!KiSignalThread+0x31 (82ec5027) [br=1] Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x8E PROCESS_NAME: System CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from 82ec4f69 to 82ec501b FAILED_INSTRUCTION_ADDRESS: nt!KiSignalThread+25 82ec501b 740a je nt!KiSignalThread+0x31 (82ec5027) STACK_TEXT: 807e3ae8 82ec4f69 807c7120 00000102 85a180c8 nt!KiSignalThread+0x25 807e3b1c 82e8360f 807c7120 00000102 00000000 nt!KiTryUnwaitThread+0x60 807e3b3c 82ec5719 807c7120 807e3ba4 85a180c0 nt!KiSignalNotificationObject+0x31 807e3b80 82ec5407 807c7120 00000001 807c8a80 nt!KiTimerWaitTest+0x1e6 807e3c68 82ec533a 807c7120 807e3ca8 00000000 nt!KiProcessExpiredTimerList+0x8b 807e3cdc 82ec34ce 000231ec 85a18030 807cc800 nt!KiTimerExpiration+0x25c 807e3d20 82ec32f8 00000000 0000000e 00000000 nt!KiRetireDpcList+0xcb 807e3d24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38 STACK_COMMAND: kb FOLLOWUP_IP: nt!KiSignalThread+25 82ec501b 740a je nt!KiSignalThread+0x31 (82ec5027) SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!KiSignalThread+25 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrpamp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 53158c8f FAILURE_BUCKET_ID: 0x8E_BAD_IP_nt!KiSignalThread+25 BUCKET_ID: 0x8E_BAD_IP_nt!KiSignalThread+25 Followup: MachineOwner ---------[/spoiler] tu jeszcze temperatury wstawiam po bsodie podczas grania http://speedy.sh/Jq5jS/temperatury.png Pomoże ktoś? Jakieś pomysły? Na noc zostawie memtesta, czy ja kiedyś uwolnie sie od tych bsodów... :cenzura: [spoiler] Microsoft (R) Windows Debugger Version 6.11.0001.402 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\Users\Krzysiek\Documents\081914-23634-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 7601 (Service Pack 1) MP (4 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.18409.x86fre.win7sp1_gdr.140303-2144 Machine Name: Kernel base = 0x82e3e000 PsLoadedModuleList = 0x82f875b0 Debug session time: Tue Aug 19 15:05:53.826 2014 (GMT+2) System Uptime: 0 days 1:44:27.138 Loading Kernel Symbols ............................................................... ................................................................ ......................... Loading User Symbols Loading unloaded module list ......... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007F, {d, 0, 0, 0} Probably caused by : amdppm.sys ( amdppm!C1Halt+4 ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f) This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc) Consult an Intel x86 family manual to learn more about what these traps are. Here is a *portion* of those codes: If kv shows a taskGate use .tss on the part before the colon, then kv. Else if kv shows a trapframe use .trap on that value Else .trap on the appropriate frame will show where the trap was taken (on x86, this will be the ebp that goes with the procedure KiTrap) Endif kb will then show the corrected stack. Arguments: Arg1: 0000000d, EXCEPTION_GP_FAULT Arg2: 00000000 Arg3: 00000000 Arg4: 00000000 Debugging Details: ------------------ BUGCHECK_STR: 0x7f_d CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 1c LAST_CONTROL_TRANSFER: from 91cb23f6 to 82e0a41e STACK_TEXT: 8d952c28 91cb23f6 badb0d00 00000000 1c413cff hal!HalpClockInterruptPn+0x146 8d952c98 82ebd7ee 87854868 8d93b800 8d936000 amdppm!C1Halt+0x4 8d952d20 82eb52cd 00000000 0000000e 00000112 nt!PoIdle+0x524 8d952d24 00000000 0000000e 00000112 00000080 nt!KiIdleLoop+0xd STACK_COMMAND: kb FOLLOWUP_IP: amdppm!C1Halt+4 91cb23f6 c3 ret SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: amdppm!C1Halt+4 FOLLOWUP_NAME: MachineOwner MODULE_NAME: amdppm IMAGE_NAME: amdppm.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bbf07 FAILURE_BUCKET_ID: 0x7f_d_amdppm!C1Halt+4 BUCKET_ID: 0x7f_d_amdppm!C1Halt+4 Followup: MachineOwner --------- [/spoiler]
Gość komentarz 20 sierpnia 2014 komentarz 20 sierpnia 2014 a czy problem występuje w jakiejs innej grze?
milek321 komentarz 20 sierpnia 2014 Autor komentarz 20 sierpnia 2014 Powiem tak, jeżeli odpalona jest jakaś gierka typu fifa, counter strike to wywala bsoda średnio po 30 min, przy zwykłym siedzeniu na necie można przetrwać z 2-3h bez bsoda
Gość komentarz 20 sierpnia 2014 komentarz 20 sierpnia 2014 okej - pomecz procek 15 minut programem occt , nastepnie przerwij i utworza ci sie na pulpicie wykresy, pokaz je
milek321 komentarz 20 sierpnia 2014 Autor komentarz 20 sierpnia 2014 (edytowane) okej - pomecz procek 15 minut programem occt , nastepnie przerwij i utworza ci sie na pulpicie wykresy, pokaz je Po 2 minutach wyskoczyl blad http://speedy.sh/ynWtZ/bladd.png Po 2 minutach wyskoczyl blad http://speedy.sh/djJSw/blad-2.png
Gość komentarz 20 sierpnia 2014 komentarz 20 sierpnia 2014 mi to moze wygladac w sumie troche na przegrzanie cpu - mialem to samo po zmianie coolera problem ustapil - te same bsody
Gość komentarz 20 sierpnia 2014 komentarz 20 sierpnia 2014 50 stopni to nie przegrzanie cpu .Athlon wytrzymuje 65
milek321 komentarz 22 sierpnia 2014 Autor komentarz 22 sierpnia 2014 Dzisiaj juz zapuszcze tego mem testa, zawsze mam zrobic na noc, ale zawsze coś wypada. Dzisiaj na bank bd w domu to zobacze tą pamieć. Ma ktoś jakieś pomysły? Czemu tak szybko po 2 minutach wyskoczyly bledy z prockiem? Coś z chłodzeniem może byc??
milek321 komentarz 24 sierpnia 2014 Autor komentarz 24 sierpnia 2014 (edytowane) Sprawdziłem ram w memteście i 0 błędów, naprawde nie wiem co robić.. chyba znowu poniose do typa. A bsody walą niemiłosiernie po 10 dziennie teraz.. i dalej te same bledy
Wciąż szukasz rozwiązania problemu? Napisz teraz na forum!
Możesz zadać pytanie bez konieczności rejestracji - wystarczy, że wypełnisz formularz.