Jeg får konstante bluescreens.
Eller, jeg var heldig og få det en gang. De andre gangene har pcen bare hengt seg, og den gjør det som oftest en stund etter at skjermbeskytteren har startet (ingen anelse om det er snakk om 5 min eller 5 timer). trodde først at det var pga ventemodus, men deaktiverte denne slik at det bare var skjermbeskytter.
Fortsatt henger den seg..
Flere ganger henger den seg mens jeg bruker den også, noe som er mega irriterende.
Microsoft Debugging Tools:
121910-18018-01.dmp - 285 Kb
Håper noen her kan hjelpe meg å finne ut hva dette er.
Pcen ble reformatert sist helg i håp om at det skulle løse problemet, og følgende er byttet i maskinen av hardware:
Eller, jeg var heldig og få det en gang. De andre gangene har pcen bare hengt seg, og den gjør det som oftest en stund etter at skjermbeskytteren har startet (ingen anelse om det er snakk om 5 min eller 5 timer). trodde først at det var pga ventemodus, men deaktiverte denne slik at det bare var skjermbeskytter.
Fortsatt henger den seg..
Flere ganger henger den seg mens jeg bruker den også, noe som er mega irriterende.
Microsoft Debugging Tools:
Kode
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\121910-18018-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16617.amd64fre.win7_gdr.100618-1621 Machine Name: Kernel base = 0xfffff800`02a18000 PsLoadedModuleList = 0xfffff800`02c55e50 Debug session time: Sun Dec 19 02:10:18.917 2010 (UTC + 1:00) System Uptime: 0 days 13:22:33.524 Loading Kernel Symbols ............................................................... ................................................................ ............................ Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 7F, {8, 80050031, 406f8, fffff80002b0782d} Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* UNEXPECTED_KERNEL_MODE_TRAP (7f) 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: 0000000000000008, EXCEPTION_DOUBLE_FAULT Arg2: 0000000080050031 Arg3: 00000000000406f8 Arg4: fffff80002b0782d Debugging Details: ------------------ BUGCHECK_STR: 0x7f_8 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: msnmsgr.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002a87ca9 to fffff80002a88740 STACK_TEXT: fffff800`00ba4d28 fffff800`02a87ca9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000406f8 : nt!KeBugCheckEx fffff800`00ba4d30 fffff800`02a86172 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69 fffff800`00ba4e70 fffff800`02b0782d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2 fffff880`0843cf90 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40def STACK_COMMAND: kb FOLLOWUP_IP: nt!KiDoubleFaultAbort+b2 fffff800`02a86172 90 nop SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: nt!KiDoubleFaultAbort+b2 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9 FAILURE_BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2 BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2 Followup: MachineOwner ---------
Håper noen her kan hjelpe meg å finne ut hva dette er.
Pcen ble reformatert sist helg i håp om at det skulle løse problemet, og følgende er byttet i maskinen av hardware:
- Harddisk
- Hovedkort
- Minnebrikker