Oktober1 Skrevet 5. desember 2010 Del Skrevet 5. desember 2010 (endret) Hei! Laptopen min har begynt å tulle voldsomt i det siste, med BSOD og full frys (total lockdown uten bsod og minidump) i hytt og gevær. Den fryser - ALLTID når jeg prøver å konvertere en film med DVDFab - Stort sett en eller to ganger hver gang jeg ser en 720p film i VLC - Av og til uten videre mens jeg holder på i Word osv. - Også av og til dersom jeg må kjøre store og tunge kopieringer i bakgrunnen osv. Det er ikke alltid jeg får minidump, oftest fryser den bare, men de jeg har fått, har jeg samlet i spoilerne nedenfor. Jeg har prøvd å analysere de selv, men jeg skjønner ikke helt hva jeg skal se etter. Har prøvd å bruke diverse guider, men skjønner at det kanskje trengs noen litt klokere hoder til å forstå det, så jeg håper noen kan sette av litt tid til å hjelpe meg PCen min: Multicom Kunshan W860 - 15.6" LED, Intel Core i7 mobile, GF 260M/280M INTEL WIFI LINK 5300 HMC 533AN_HMWG tray (533AN_HMWG) Multicom Kunshan W860 15.6" Full-HD glare (W860CU-PM1) INTEL Core i7 820QM mobile (I7-820QM) 2 X TRANSCEND 2GB DDR3 SO-DIMM 204-pin 1333MHz 9-9-9 (TS256MSK64V3U-) PRODUKSJONSVARE 500GB SATA 7200RPM 2.5" (500GBSATA72002.5) Multicom GeForce GTX 280M til Kunshan W860 (W860CU-GTX280) Sony Optiarc BC-5500S Blu-Ray spiller og DVD brenner, Slim Sort SATA kun til produksjon (BC-5500S) Multicom bluetooth til M860 m.fl. (M860-BT) Windows 7 x64 Minidump fra kl 20 idag: Denne hadde stopkode 0x0000009F Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Arnstein\Desktop\120510-20077-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 (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`02e14000 PsLoadedModuleList = 0xfffff800`03051e50 Debug session time: Sun Dec 5 20:56:41.760 2010 (UTC + 1:00) System Uptime: 0 days 0:45:26.322 Loading Kernel Symbols ............................................................... ................................................................ ................................ Loading User Symbols Loading unloaded module list ........... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 9C, {0, fffff88002f6bc70, 0, 0} Probably caused by : ntkrnlmp.exe ( nt!KxMcheckAbort+6c ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MACHINE_CHECK_EXCEPTION (9c) A fatal Machine Check Exception has occurred. KeBugCheckEx parameters; x86 Processors If the processor has ONLY MCE feature available (For example Intel Pentium), the parameters are: 1 - Low 32 bits of P5_MC_TYPE MSR 2 - Address of MCA_EXCEPTION structure 3 - High 32 bits of P5_MC_ADDR MSR 4 - Low 32 bits of P5_MC_ADDR MSR If the processor also has MCA feature available (For example Intel Pentium Pro), the parameters are: 1 - Bank number 2 - Address of MCA_EXCEPTION structure 3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error 4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error IA64 Processors 1 - Bugcheck Type 1 - MCA_ASSERT 2 - MCA_GET_STATEINFO SAL returned an error for SAL_GET_STATEINFO while processing MCA. 3 - MCA_CLEAR_STATEINFO SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA. 4 - MCA_FATAL FW reported a fatal MCA. 5 - MCA_NONFATAL SAL reported a recoverable MCA and we don't support currently support recovery or SAL generated an MCA and then couldn't produce an error record. 0xB - INIT_ASSERT 0xC - INIT_GET_STATEINFO SAL returned an error for SAL_GET_STATEINFO while processing INIT event. 0xD - INIT_CLEAR_STATEINFO SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event. 0xE - INIT_FATAL Not used. 2 - Address of log 3 - Size of log 4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO AMD64 Processors 1 - Bank number 2 - Address of MCA_EXCEPTION structure 3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error 4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error Arguments: Arg1: 0000000000000000 Arg2: fffff88002f6bc70 Arg3: 0000000000000000 Arg4: 0000000000000000 Debugging Details: ------------------ BUGCHECK_STR: 0x9C_GenuineIntel CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: f LAST_CONTROL_TRANSFER: from fffff800034026e0 to fffff80002e84740 STACK_TEXT: fffff880`02f6bc38 fffff800`034026e0 : 00000000`0000009c 00000000`00000000 fffff880`02f6bc70 00000000`00000000 : nt!KeBugCheckEx fffff880`02f6bc40 fffff800`03401e1f : 00000000`00000008 00000000`00000000 00000000`00000008 00000000`00000000 : hal!HalpMcaReportError+0x164 fffff880`02f6bd90 fffff800`033f5e88 : 00000000`00000002 fffff880`02f63180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x9f fffff880`02f6bdc0 fffff800`02e82fec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40 fffff880`02f6bdf0 fffff800`02e82e53 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c fffff880`02f6bf30 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153 STACK_COMMAND: kb FOLLOWUP_IP: nt!KxMcheckAbort+6c fffff800`02e82fec 488d8c2400010000 lea rcx,[rsp+100h] SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: nt!KxMcheckAbort+6c FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9 FAILURE_BUCKET_ID: X64_0x9C_GenuineIntel_nt!KxMcheckAbort+6c BUCKET_ID: X64_0x9C_GenuineIntel_nt!KxMcheckAbort+6c Followup: MachineOwner --------- Minidump fra kl 19 idag: Stopkode 0x0000009F Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Arnstein\Desktop\120510-19640-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 (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`02e51000 PsLoadedModuleList = 0xfffff800`0308ee50 Debug session time: Sun Dec 5 19:07:33.984 2010 (UTC + 1:00) System Uptime: 0 days 5:15:12.155 Loading Kernel Symbols ............................................................... ................................................................ ................................ Loading User Symbols Loading unloaded module list ............... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 9F, {3, fffffa80079a3440, fffff80000b9c518, fffffa80098f0c60} Probably caused by : WinUSB.sys Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_POWER_STATE_FAILURE (9f) A driver is causing an inconsistent power state. Arguments: Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time Arg2: fffffa80079a3440, Physical Device Object of the stack Arg3: fffff80000b9c518, Functional Device Object of the stack Arg4: fffffa80098f0c60, The blocked IRP Debugging Details: ------------------ DRVPOWERSTATE_SUBCODE: 3 IRP_ADDRESS: fffffa80098f0c60 DEVICE_OBJECT: fffffa800938ea10 DRIVER_OBJECT: fffffa80057fce70 IMAGE_NAME: WinUSB.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcc04 MODULE_NAME: WinUSB FAULTING_MODULE: fffff88001e83000 WinUSB CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x9F PROCESS_NAME: System CURRENT_IRQL: 2 STACK_TEXT: fffff800`00b9c4c8 fffff800`02f30273 : 00000000`0000009f 00000000`00000003 fffffa80`079a3440 fffff800`00b9c518 : nt!KeBugCheckEx fffff800`00b9c4d0 fffff800`02ecd29e : fffff800`00b9c600 fffff800`00b9c600 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292b0 fffff800`00b9c570 fffff800`02eccdd6 : fffff800`03071700 00000000`00127f95 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66 fffff800`00b9c5e0 fffff800`02ecd4be : 0000002c`0885e2ce fffff800`00b9cc58 00000000`00127f95 fffff800`0303f528 : nt!KiProcessExpiredTimerList+0xc6 fffff800`00b9cc30 fffff800`02ecccb7 : 00000007`743889c1 00000007`00127f95 00000007`74388992 00000000`00000095 : nt!KiTimerExpiration+0x1be fffff800`00b9ccd0 fffff800`02ec9eea : fffff800`0303be80 fffff800`03049c40 00000000`00000002 fffffa80`00000000 : nt!KiRetireDpcList+0x277 fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner FAILURE_BUCKET_ID: X64_0x9F_3_IMAGE_WinUSB.sys BUCKET_ID: X64_0x9F_3_IMAGE_WinUSB.sys Followup: MachineOwner --------- Minidump den 3. Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Arnstein\Desktop\120310-19390-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 (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`02e0e000 PsLoadedModuleList = 0xfffff800`0304be50 Debug session time: Fri Dec 3 18:51:40.809 2010 (UTC + 1:00) System Uptime: 0 days 4:56:42.964 Loading Kernel Symbols ............................................................... ................................................................ ............................... Loading User Symbols Loading unloaded module list .............. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 101, {19, 0, fffff880009b1180, 4} Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* CLOCK_WATCHDOG_TIMEOUT (101) An expected clock interrupt was not received on a secondary processor in an MP system within the allocated interval. This indicates that the specified processor is hung and not processing interrupts. Arguments: Arg1: 0000000000000019, Clock interrupt time out interval in nominal clock ticks. Arg2: 0000000000000000, 0. Arg3: fffff880009b1180, The PRCB address of the hung processor. Arg4: 0000000000000004, 0. Debugging Details: ------------------ BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_8_PROC CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: d STACK_TEXT: fffff800`00ba1cd8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx 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: ZEROED_STACK Followup: MachineOwner --------- Tidligere Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Arnstein\Desktop\100710-19000-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 (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`02e0c000 PsLoadedModuleList = 0xfffff800`03049e50 Debug session time: Thu Oct 7 20:35:35.749 2010 (UTC + 1:00) System Uptime: 0 days 5:34:11.905 Loading Kernel Symbols ............................................................... ................................................................ ............................... Loading User Symbols Loading unloaded module list ........... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 9F, {3, fffffa8007a1a060, fffff80000b9c518, fffffa800b7c9c60} Probably caused by : WinUSB.sys Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_POWER_STATE_FAILURE (9f) A driver is causing an inconsistent power state. Arguments: Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time Arg2: fffffa8007a1a060, Physical Device Object of the stack Arg3: fffff80000b9c518, Functional Device Object of the stack Arg4: fffffa800b7c9c60, The blocked IRP Debugging Details: ------------------ DRVPOWERSTATE_SUBCODE: 3 IRP_ADDRESS: fffffa800b7c9c60 DEVICE_OBJECT: fffffa80090e9360 DRIVER_OBJECT: fffffa80090e8e70 IMAGE_NAME: WinUSB.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcc04 MODULE_NAME: WinUSB FAULTING_MODULE: fffff88003de5000 WinUSB CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x9F PROCESS_NAME: System CURRENT_IRQL: 2 STACK_TEXT: fffff800`00b9c4c8 fffff800`02eeb273 : 00000000`0000009f 00000000`00000003 fffffa80`07a1a060 fffff800`00b9c518 : nt!KeBugCheckEx fffff800`00b9c4d0 fffff800`02e8829e : fffff800`00b9c600 fffff800`00b9c600 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292b0 fffff800`00b9c570 fffff800`02e87dd6 : fffffa80`094cb168 fffffa80`094cb168 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66 fffff800`00b9c5e0 fffff800`02e884be : 0000002e`afdde4ba fffff800`00b9cc58 00000000`00139cfa fffff800`02ffb1c8 : nt!KiProcessExpiredTimerList+0xc6 fffff800`00b9cc30 fffff800`02e87cb7 : 00000007`e73477c2 00000007`00139cfa 00000007`e7347709 00000000`000000fa : nt!KiTimerExpiration+0x1be fffff800`00b9ccd0 fffff800`02e84eea : fffff800`02ff6e80 fffff800`03004c40 00000000`00000002 fffff800`00000000 : nt!KiRetireDpcList+0x277 fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner FAILURE_BUCKET_ID: X64_0x9F_3_IMAGE_WinUSB.sys BUCKET_ID: X64_0x9F_3_IMAGE_WinUSB.sys Followup: MachineOwner --------- Tidligere Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Arnstein\Desktop\091910-25958-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 (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`02e03000 PsLoadedModuleList = 0xfffff800`03040e50 Debug session time: Sun Sep 19 11:13:18.363 2010 (UTC + 1:00) System Uptime: 0 days 0:07:26.518 Loading Kernel Symbols ............................................................... ................................................................ ............................. Loading User Symbols Loading unloaded module list ........... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 9C, {0, fffff880009b9c70, 0, 0} Probably caused by : ntkrnlmp.exe ( nt!KxMcheckAbort+6c ) Followup: MachineOwner --------- 4: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* MACHINE_CHECK_EXCEPTION (9c) A fatal Machine Check Exception has occurred. KeBugCheckEx parameters; x86 Processors If the processor has ONLY MCE feature available (For example Intel Pentium), the parameters are: 1 - Low 32 bits of P5_MC_TYPE MSR 2 - Address of MCA_EXCEPTION structure 3 - High 32 bits of P5_MC_ADDR MSR 4 - Low 32 bits of P5_MC_ADDR MSR If the processor also has MCA feature available (For example Intel Pentium Pro), the parameters are: 1 - Bank number 2 - Address of MCA_EXCEPTION structure 3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error 4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error IA64 Processors 1 - Bugcheck Type 1 - MCA_ASSERT 2 - MCA_GET_STATEINFO SAL returned an error for SAL_GET_STATEINFO while processing MCA. 3 - MCA_CLEAR_STATEINFO SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA. 4 - MCA_FATAL FW reported a fatal MCA. 5 - MCA_NONFATAL SAL reported a recoverable MCA and we don't support currently support recovery or SAL generated an MCA and then couldn't produce an error record. 0xB - INIT_ASSERT 0xC - INIT_GET_STATEINFO SAL returned an error for SAL_GET_STATEINFO while processing INIT event. 0xD - INIT_CLEAR_STATEINFO SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event. 0xE - INIT_FATAL Not used. 2 - Address of log 3 - Size of log 4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO AMD64 Processors 1 - Bank number 2 - Address of MCA_EXCEPTION structure 3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error 4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error Arguments: Arg1: 0000000000000000 Arg2: fffff880009b9c70 Arg3: 0000000000000000 Arg4: 0000000000000000 Debugging Details: ------------------ BUGCHECK_STR: 0x9C_GenuineIntel CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: f LAST_CONTROL_TRANSFER: from fffff800033f16e0 to fffff80002e73740 STACK_TEXT: fffff880`009b9c38 fffff800`033f16e0 : 00000000`0000009c 00000000`00000000 fffff880`009b9c70 00000000`00000000 : nt!KeBugCheckEx fffff880`009b9c40 fffff800`033f0e1f : 00000000`00000008 00000000`00000000 00000000`00000008 00000000`00000000 : hal!HalpMcaReportError+0x164 fffff880`009b9d90 fffff800`033e4e88 : 00000000`00000002 fffff880`009b1180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x9f fffff880`009b9dc0 fffff800`02e71fec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40 fffff880`009b9df0 fffff800`02e71e53 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c fffff880`009b9f30 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153 STACK_COMMAND: kb FOLLOWUP_IP: nt!KxMcheckAbort+6c fffff800`02e71fec 488d8c2400010000 lea rcx,[rsp+100h] SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: nt!KxMcheckAbort+6c FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9 FAILURE_BUCKET_ID: X64_0x9C_GenuineIntel_nt!KxMcheckAbort+6c BUCKET_ID: X64_0x9C_GenuineIntel_nt!KxMcheckAbort+6c Followup: MachineOwner --------- Jeg ser f.eks. at WinUSB har gått igjen to ganger, men jeg skjønner ikke hva jeg skal gjøre med den. Ikke har det vært koblet noe spesielt til USB-portene utenom mus heller, så jeg skjønner ikke helt. Men uansett, så håper jeg noen tar seg tid til å kikke litt på det, så kanskje jeg klarer å fikse det og slipper å måtte sende den inn til reperasjon Endret 5. desember 2010 av Oktober1 Lenke til kommentar
fenderebest Skrevet 6. desember 2010 Del Skrevet 6. desember 2010 Av det jeg kan skjønne kan det virke som et hardwareproblem. Maskinen blir ikke overopphettet da? Lenke til kommentar
Oktober1 Skrevet 7. desember 2010 Forfatter Del Skrevet 7. desember 2010 Hmm. Tror ikke den skal ha kunne blitt overopphetet ved de to siste crashene. Da jobbet jeg bare i Word. Og jeg har målt temperatur med SpeedFan, og da får jeg ca 45-50 C under vanlig bruk, og opp mot 85 ved videokonvertering (når den kræsjer) Lenke til kommentar
Oktober1 Skrevet 7. desember 2010 Forfatter Del Skrevet 7. desember 2010 Jeg har forresten sett at det ligger ute en hotfix til WinUSB-greia. Er det lurt å oppdatere den? Selm om den ikke er tilstrekkelig testet? Lenke til kommentar
fenderebest Skrevet 7. desember 2010 Del Skrevet 7. desember 2010 Njee...selv om WinDbg gjetter at denne modulen er problemet har jeg mine tvil iforhold til andre feil på maskinen, det som er mest krtitisk er at du får en Machine Check Exception feil: http://en.wikipedia.org/wiki/Machine_Check_Exception http://support.microsoft.com/?kbid=329284 Dette skyldes som regel at noe er galt med hardware, typiske problemer er beskrevet i artiklene ovenfor. Som regel skyldes dette at datamaskinen er galt satt opp hardwaremessig, minnet funger dårlig eller at den overopphettes. Du kan jo sjekke minnet om ikke annet. Lenke til kommentar
Oktober1 Skrevet 12. desember 2010 Forfatter Del Skrevet 12. desember 2010 Ja, jeg har sjekket minnet opptil flere ganger, og det skal ikke være noe feil med de. Harddisk er også sjekket med Seagate sin sjekker, og det skal ikke være noe feil med de. Vet ikke hvordan jeg sjekker resten Jeg har også vært i kontakt med multicoms service, men vi kom ikke egentlig frem til hva det kunne være for noe. Men jeg fikk fjernet et deksel som dekket over den ene vifta (hadde visst skjedd en feil under produksjon eller noe, så det var ikke blitt fjernet.), er det mulig at noe har blitt varmet for mye opp en gang før jeg fjernet dette, og at det nå er ødelagt? Fikk en ny BSOD idag, STOP:0x00000101 Minidump: Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Arnstein\Desktop\121210-20763-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 (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`02e12000 PsLoadedModuleList = 0xfffff800`0304fe50 Debug session time: Sun Dec 12 17:58:58.208 2010 (UTC + 1:00) System Uptime: 0 days 3:28:42.363 Loading Kernel Symbols ............................................................... ................................................................ ................................ Loading User Symbols Loading unloaded module list ............ ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 101, {19, 0, fffff88002fd3180, 3} Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* CLOCK_WATCHDOG_TIMEOUT (101) An expected clock interrupt was not received on a secondary processor in an MP system within the allocated interval. This indicates that the specified processor is hung and not processing interrupts. Arguments: Arg1: 0000000000000019, Clock interrupt time out interval in nominal clock ticks. Arg2: 0000000000000000, 0. Arg3: fffff88002fd3180, The PRCB address of the hung processor. Arg4: 0000000000000003, 0. Debugging Details: ------------------ BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_8_PROC CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: WUDFHost.exe CURRENT_IRQL: d STACK_TEXT: fffff880`079aa308 fffff800`02e30453 : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`02fd3180 : nt!KeBugCheckEx fffff880`079aa310 fffff800`02e8ade7 : 00000000`00000000 fffff800`00000003 00000000`00026160 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4dfe fffff880`079aa3a0 fffff800`033f8895 : fffff800`0341d460 fffff880`079aa550 fffff800`0341d460 fffff800`00000000 : nt!KeUpdateSystemTime+0x377 fffff880`079aa4a0 fffff800`02e7ec33 : fffffa80`05633480 fffffa80`05e39001 fffffa80`05633480 fffff800`02ffce80 : hal!HalpHpetClockInterrupt+0x8d fffff880`079aa4d0 fffff800`02e9a932 : 00000000`0000003e 00000000`00caf810 fffff880`079aa750 fffffa80`0936dac0 : nt!KiInterruptDispatchNoLock+0x163 fffff880`079aa660 fffff800`02e91266 : 00000000`00000002 fffff6fc`4002ea10 00000000`00000041 00000000`00000000 : nt!MiFlushTbAsNeeded+0x282 fffff880`079aa770 fffff880`01f4e6fe : fffffa80`09a93300 00000000`00005441 fffffa80`00000001 00000000`00caf0f0 : nt!MmMapLockedPagesSpecifyCache+0x4e6 fffff880`079aa830 fffff880`01f52217 : fffffa80`09363970 fffffa80`090e0c60 00000000`00000002 fffff800`03173501 : WUDFRd!RdFdoDevice::CopyIoBuffer+0x172 fffff880`079aa8e0 fffff880`01f3e8e3 : fffffa80`0937e360 fffffa80`09365510 fffffa80`0937e360 fffff880`01f63110 : WUDFRd!RdCtrlDevice::RdFastIoDeviceIoControl+0x95b fffff880`079aa9c0 fffff800`0319d473 : fffffa80`09365510 fffff880`079aaca0 00000000`00caf060 fffff880`01f3e804 : WUDFRd!RdDriver::RdFastIoDeviceDispatch+0xdf fffff880`079aaa10 fffff800`0319df66 : 00000000`00caefc8 00000000`00000344 00000000`00000000 00000000`00caf060 : nt!IopXxxControlFile+0x373 fffff880`079aab40 fffff800`02e81993 : fffffa80`0936d060 00000000`00caefa8 fffff880`079aabc8 00000000`80018483 : nt!NtDeviceIoControlFile+0x56 fffff880`079aabb0 00000000`776afdca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`00caef58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x776afdca STACK_COMMAND: kb SYMBOL_NAME: ANALYSIS_INCONCLUSIVE FOLLOWUP_NAME: MachineOwner MODULE_NAME: Unknown_Module IMAGE_NAME: Unknown_Image DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE Followup: MachineOwner --------- Sier dette noe mer? Ser det er en relativt god stack her, vel? Lenke til kommentar
fenderebest Skrevet 12. desember 2010 Del Skrevet 12. desember 2010 Vel, er begrenset med info man får ut av en minidump. Det den sier er bare at den andre prosessoren(evt prosessorkjernen om du vil) ikke behandler avbrudd på grunn av den er hengt. Dette er konsekvent med en feil i maskinvare. Det er desverre veldig vanskelig å kunne konkretisere hvilken maskinvare som er deffekt bare ved å se på minidump filer. Det eneste virkelig "bombesikre" metoden er å bytte maskinvare og se om problemet vedvarer. Siden du har sjekket minne og harddisk ville jeg tippet på hovedkort. Det finnes programvare som tester diverse funksjonalitet i hovedkort men jeg har hatt varierende resultat med disse. Desverre er mitt eneste gode råd å bytte maskinvare å se om problemet vedvarer. Lenke til kommentar
Oktober1 Skrevet 12. desember 2010 Forfatter Del Skrevet 12. desember 2010 OK! Takk for hjelp Får sende den inn til service, og håpe de finner ut av det, og skifter det ut for meg Lenke til kommentar
fenderebest Skrevet 12. desember 2010 Del Skrevet 12. desember 2010 Yep, det som gjør meg så sikker på at det er en maskinvarefeil er som sagt at den får en Machine Check Exception. Dette er en type feil der prosessoren registrerer at det er noe galt med maskinvaren og gir beskjed til operativsystemet. Blåskjermer skyldes to ting, at en komponent i kernel mode er korrupt/buggy(Typisk en driver) eller hardware. At maskinen får en MCE utelukker så godt som 100% at en driver eller operativsystemet kan være problemet. Lenke til kommentar
Anbefalte innlegg
Opprett en konto eller logg inn for å kommentere
Du må være et medlem for å kunne skrive en kommentar
Opprett konto
Det er enkelt å melde seg inn for å starte en ny konto!
Start en kontoLogg inn
Har du allerede en konto? Logg inn her.
Logg inn nå