November 20, 2006
Min dator har "drabbats av" bluescreen. Riktigt irriterande! Händer allt mer ofta nu. Vad kan vara problemet? Jag behöver alltid startar om datorn minst en gång och ibland händer det igen (dvs. två omstarter), men ibland kan den bara fortsätta funka utan problem. Idag dök dock en grönliknande färg upp på min skärm efter att datorn fått bluescreen. Jag startade om och nu funkar den fint.
Problemsignatur:
Problemhändelsens namn: BlueScreen
OS-version: 6.1.7601.2.1.0.256.48
Språkvariant-ID: 1053
Ytterligare information om problemet:
BCCode: d1
BCP1: 0000003C
BCP2: 00000002
BCP3: 00000001
BCP4: 9173FD0E
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1
Har googlat runt och hittar en väldans massa olika svar som tycks vara anpassade utefter den som ställer frågan och dennes dator.
July 30, 2010
Då måste han ladda ner Microsoft SDK för att kunna läsa den om den inte redan är installerad
Edit:
Om det nu är drivrutinsproblem så kan du testa att ladda ner Windows Driver Kit 7.1.0. Tror inte det finns till Windows 8 än dock, men upp till Windows 7 kan du använda denna ISO fil http://www.microsoft.com/en-us.....x?id=11800
November 20, 2006
Jag har Win 7 Pro 32-bit. Det jag har skrivit där är vad Windows anser vara fel och en ruta ploppar upp efter omstart och ska "hjälpa mig lösa problemet". På den "blåa" skärmen står det en massa 0x000000016 osv, men det är inget jag hinner läsa, ännu mindre skriva ner. 🙁
Det jag oftast gör är att starta upp Spotify men det kan likväl vara Firefox eller Office. Verkar som att datorn bara "måste" få bluescreen o starta om. Nu har den varit igång i några timmar utan problem med både Spotify, Firefox och Office uppe.
Hur hittar jag och analyserar dump filen? :-S
Jag har laddat ner SDK och även Driver Kit.
What's next? 🙂
July 30, 2010
Du ska använda Windows Debugging Tool programmet som följer med SDK för att kunna läsa dmp filerna som normalt ligger i Windows mappen om jag inte minns helt fel. Står lite här How to open DMP files in Windows 7?
November 20, 2006
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:WindowsMinidump50113-25880-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 (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18113.x86fre.win7sp1_gdr.130318-1533
Machine Name:
Kernel base = 0x82c45000 PsLoadedModuleList = 0x82d8e4d0
Debug session time: Wed May 1 10:04:56.779 2013 (UTC + 2:00)
System Uptime: 0 days 0:03:46.527
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {4c, ff, 1, b4b529cb}
Probably caused by : ntkrpamp.exe ( nt!KiTrap0E+2cf )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000004c, memory referenced
Arg2: 000000ff, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: b4b529cb, address which referenced memory
November 20, 2006
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82dae84c
Unable to read MiSystemVaType memory at 82d8de20
0000004c
CURRENT_IRQL: 2
FAULTING_IP:
+5dd22faf03b4dcc4
b4b529cb 0000 add byte ptr [eax],al
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: WO10.exe
TRAP_FRAME: b4b5299e -- (.trap 0xffffffffb4b5299e)
ErrCode = 00000002
eax=00000000 ebx=a74c79b0 ecx=82d72f60 edx=8001003b esi=a74c78cc edi=a74c78cc
eip=b4b529cb esp=b4b52a12 ebp=0000004c iopl=0 nv up di pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010046
b4b529cb 0000 add byte ptr [eax],al ds:0023:00000000=??
Resetting default scope
UNALIGNED_STACK_POINTER: b4b52986
LAST_CONTROL_TRANSFER: from b4b529cb to 82c85c9b
STACK_TEXT:
b4b5299e b4b529cb badb0d00 8001003b 04100000 nt!KiTrap0E+0x2cf
WARNING: Frame IP not in any known module. Following frames may be wrong.
b4b52a0e 00390045 00300036 002d0030 00330042 0xb4b529cb
b4b52a12 00300036 002d0030 00330042 00440044 0x390045
b4b52a16 002d0030 00330042 00440044 0031002d 0x300036
b4b52a1a 00330042 00440044 0031002d 00430031 0x2d0030
b4b52a1e 00440044 0031002d 00430031 002d0046 0x330042
b4b52a22 0031002d 00430031 002d0046 00370041 0x440044
b4b52a26 00430031 002d0046 00370041 00450034 0x31002d
b4b52a2a 002d0046 00370041 00450034 0030002d 0x430031
b4b52a2e 00370041 00450034 0030002d 00320030 0x2d0046
b4b52a32 00450034 0030002d 00320030 00410030 0x370041
b4b52a36 0030002d 00320030 00410030 00410046 0x450034
b4b52a3a 00320030 00410030 00410046 00390036 0x30002d
b4b52a3e 00410030 00410046 00390036 00320045 0x320030
b4b52a42 00410046 00390036 00320045 007d0031 0x410030
b4b52a46 00390036 00320045 007d0031 0049005c 0x410046
b4b52a4a 00320045 007d0031 0049005c 0070006e 0x390036
b4b52a4e 007d0031 0049005c 0070006e 006f0072 0x320045
b4b52a52 0049005c 0070006e 006f0072 00530063 0x7d0031
b4b52a56 0070006e 006f0072 00530063 00720065 0x49005c
b4b52a5a 006f0072 00530063 00720065 00650076 0x70006e
b4b52a5e 00530063 00720065 00650076 00000072 0x6f0072
b4b52a62 00720065 00650076 00000072 006f0066 0x530063
b4b52a66 00650076 00000072 006f0066 006d0072 0x720065
b4b52a6a 00000000 006f0066 006d0072 00530020 0x650076
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiTrap0E+2cf
82c85c9b 833d4497da8200 cmp dword ptr [nt!KiFreezeFlag (82da9744)],0
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!KiTrap0E+2cf
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 5147d331
FAILURE_BUCKET_ID: 0xD1_nt!KiTrap0E+2cf
BUCKET_ID: 0xD1_nt!KiTrap0E+2cf
Followup: MachineOwner
---------
November 20, 2006
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000004c, memory referenced
Arg2: 000000ff, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: b4b529cb, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82dae84c
Unable to read MiSystemVaType memory at 82d8de20
0000004c
CURRENT_IRQL: 2
FAULTING_IP:
+5dd22faf03b4dcc4
b4b529cb 0000 add byte ptr [eax],al
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: WO10.exe
TRAP_FRAME: b4b5299e -- (.trap 0xffffffffb4b5299e)
ErrCode = 00000002
eax=00000000 ebx=a74c79b0 ecx=82d72f60 edx=8001003b esi=a74c78cc edi=a74c78cc
eip=b4b529cb esp=b4b52a12 ebp=0000004c iopl=0 nv up di pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010046
b4b529cb 0000 add byte ptr [eax],al ds:0023:00000000=??
Resetting default scope
UNALIGNED_STACK_POINTER: b4b52986
LAST_CONTROL_TRANSFER: from b4b529cb to 82c85c9b
STACK_TEXT:
b4b5299e b4b529cb badb0d00 8001003b 04100000 nt!KiTrap0E+0x2cf
WARNING: Frame IP not in any known module. Following frames may be wrong.
b4b52a0e 00390045 00300036 002d0030 00330042 0xb4b529cb
b4b52a12 00300036 002d0030 00330042 00440044 0x390045
b4b52a16 002d0030 00330042 00440044 0031002d 0x300036
b4b52a1a 00330042 00440044 0031002d 00430031 0x2d0030
b4b52a1e 00440044 0031002d 00430031 002d0046 0x330042
b4b52a22 0031002d 00430031 002d0046 00370041 0x440044
b4b52a26 00430031 002d0046 00370041 00450034 0x31002d
b4b52a2a 002d0046 00370041 00450034 0030002d 0x430031
b4b52a2e 00370041 00450034 0030002d 00320030 0x2d0046
b4b52a32 00450034 0030002d 00320030 00410030 0x370041
b4b52a36 0030002d 00320030 00410030 00410046 0x450034
b4b52a3a 00320030 00410030 00410046 00390036 0x30002d
b4b52a3e 00410030 00410046 00390036 00320045 0x320030
b4b52a42 00410046 00390036 00320045 007d0031 0x410030
b4b52a46 00390036 00320045 007d0031 0049005c 0x410046
b4b52a4a 00320045 007d0031 0049005c 0070006e 0x390036
b4b52a4e 007d0031 0049005c 0070006e 006f0072 0x320045
b4b52a52 0049005c 0070006e 006f0072 00530063 0x7d0031
b4b52a56 0070006e 006f0072 00530063 00720065 0x49005c
b4b52a5a 006f0072 00530063 00720065 00650076 0x70006e
b4b52a5e 00530063 00720065 00650076 00000072 0x6f0072
b4b52a62 00720065 00650076 00000072 006f0066 0x530063
b4b52a66 00650076 00000072 006f0066 006d0072 0x720065
b4b52a6a 00000000 006f0066 006d0072 00530020 0x650076
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiTrap0E+2cf
82c85c9b 833d4497da8200 cmp dword ptr [nt!KiFreezeFlag (82da9744)],0
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!KiTrap0E+2cf
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 5147d331
FAILURE_BUCKET_ID: 0xD1_nt!KiTrap0E+2cf
BUCKET_ID: 0xD1_nt!KiTrap0E+2cf
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000004c, memory referenced
Arg2: 000000ff, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: b4b529cb, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82dae84c
Unable to read MiSystemVaType memory at 82d8de20
0000004c
CURRENT_IRQL: 2
FAULTING_IP:
+5dd22faf03b4dcc4
b4b529cb 0000 add byte ptr [eax],al
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: WO10.exe
TRAP_FRAME: b4b5299e -- (.trap 0xffffffffb4b5299e)
ErrCode = 00000002
eax=00000000 ebx=a74c79b0 ecx=82d72f60 edx=8001003b esi=a74c78cc edi=a74c78cc
eip=b4b529cb esp=b4b52a12 ebp=0000004c iopl=0 nv up di pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010046
b4b529cb 0000 add byte ptr [eax],al ds:0023:00000000=??
Resetting default scope
UNALIGNED_STACK_POINTER: b4b52986
LAST_CONTROL_TRANSFER: from b4b529cb to 82c85c9b
STACK_TEXT:
b4b5299e b4b529cb badb0d00 8001003b 04100000 nt!KiTrap0E+0x2cf
WARNING: Frame IP not in any known module. Following frames may be wrong.
b4b52a0e 00390045 00300036 002d0030 00330042 0xb4b529cb
b4b52a12 00300036 002d0030 00330042 00440044 0x390045
b4b52a16 002d0030 00330042 00440044 0031002d 0x300036
b4b52a1a 00330042 00440044 0031002d 00430031 0x2d0030
b4b52a1e 00440044 0031002d 00430031 002d0046 0x330042
b4b52a22 0031002d 00430031 002d0046 00370041 0x440044
b4b52a26 00430031 002d0046 00370041 00450034 0x31002d
b4b52a2a 002d0046 00370041 00450034 0030002d 0x430031
b4b52a2e 00370041 00450034 0030002d 00320030 0x2d0046
b4b52a32 00450034 0030002d 00320030 00410030 0x370041
b4b52a36 0030002d 00320030 00410030 00410046 0x450034
b4b52a3a 00320030 00410030 00410046 00390036 0x30002d
b4b52a3e 00410030 00410046 00390036 00320045 0x320030
b4b52a42 00410046 00390036 00320045 007d0031 0x410030
b4b52a46 00390036 00320045 007d0031 0049005c 0x410046
b4b52a4a 00320045 007d0031 0049005c 0070006e 0x390036
b4b52a4e 007d0031 0049005c 0070006e 006f0072 0x320045
b4b52a52 0049005c 0070006e 006f0072 00530063 0x7d0031
b4b52a56 0070006e 006f0072 00530063 00720065 0x49005c
b4b52a5a 006f0072 00530063 00720065 00650076 0x70006e
b4b52a5e 00530063 00720065 00650076 00000072 0x6f0072
b4b52a62 00720065 00650076 00000072 006f0066 0x530063
b4b52a66 00650076 00000072 006f0066 006d0072 0x720065
b4b52a6a 00000000 006f0066 006d0072 00530020 0x650076
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiTrap0E+2cf
82c85c9b 833d4497da8200 cmp dword ptr [nt!KiFreezeFlag (82da9744)],0
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!KiTrap0E+2cf
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 5147d331
FAILURE_BUCKET_ID: 0xD1_nt!KiTrap0E+2cf
BUCKET_ID: 0xD1_nt!KiTrap0E+2cf
Followup: MachineOwner
---------
July 30, 2010
Har du nåt program som heter Ashampoo WinOptimizer 10 eller använt det programmet? Jag sökte på wo10.exe som finns med i listan du klistrade in och enligt google så ska det vara Ashampoo WinOptimizer 10. Vad händer om du avinstallerar det programmet och sedan rensar registret med CCleaner efter avinstallationen CCleaner - Download Kanske wo10.exe som orsakar nåt problem
November 20, 2006
Jag lyckades inte få igång memtest+86. 🙁 Provade att köra det i Daemon tool för jag har inga tomma skivor här hemma, men det ville sig inte.
Idag fick jag starta om två gånger. 1:a gången så "förs" bluescreenen och jag lyckades ta kort med mobilen. Om vi skippar all "vanlig" information om vad man ska göra osv, så stod följande:
BUGGCODE_USB_DRIVER
0x000000FE (0x00000006, 0x87FBD528, 0x50456368, 0x00000000)
2:a kraschen hann jag inte läsa noga men det stod inte samma som "Buggcode osv", det stod något annat. Men efter det startade datorn om och nu funkar den fint igen.
Dumpfilerna från båda krascherna går inte att utläsa då det bara blir en massa tecken utan nån logik. 🙁
Fattar inte vad det kan vara. Men kanske bäst att börja överföra viktiga filer till extern HDD.
July 30, 2010
Du måste boota från DOS eftersom det är ett DOS program. Har du en tom USB pinne liggandes då? Kolla här hur du installerar Memtest på USB
Det ska inte se ut så här i alla fall 😀
Alla röda fält är fel i minnet och det blir soptippen nästa för dessa minnen http://www.youtube.com/watch?f.....&NR=1
1 Guest(s)