|
windows 7 ongelma
|
|
|
su1kk0
Newbie
|
28. heinäkuuta 2009 @ 11:58 |
Linkki tähän viestiin
|
|
uusi kone ja windows 7 tilttaa jatkuvasti. tulee se bluescreen vai mikä se on. Apua kaivataan!
|
Senior Member
|
28. heinäkuuta 2009 @ 16:54 |
Linkki tähän viestiin
|
|
Bluescreenin tiedoista voisi olla apua!
|
|
su1kk0
Newbie
|
28. heinäkuuta 2009 @ 17:25 |
Linkki tähän viestiin
|
|
Onko ne tiedot siinä blue screenissä joka on näkyvissä vain muutaman sekunnin vai saako ne muuten selvile?
|
AfterDawn Addict
3 tuotearviota
|
28. heinäkuuta 2009 @ 17:40 |
Linkki tähän viestiin
|
|
Katso onko kaatumisen hetkellä tullut c:\windows\minidump kansioon .dmp tiedostoa.
Give a man a fish and you feed him for a day.
Teach a man to fish and you feed him for a lifetime.
|
|
su1kk0
Newbie
|
28. heinäkuuta 2009 @ 17:44 |
Linkki tähän viestiin
|
|
olihan sielä vaikka kuinka monta mutta millä ohjelmala ne saa auki
|
|
su1kk0
Newbie
|
28. heinäkuuta 2009 @ 18:31 |
Linkki tähän viestiin
|
|
koitan avata tuolla windowsin debuggerilla mutta tullee lukeen että sinulla ei ole oikeuksia tiedoston avaamiseen. Miten saan nuo oikeudet muutettua?
|
|
su1kk0
Newbie
|
28. heinäkuuta 2009 @ 18:45 |
Linkki tähän viestiin
|
|
tälläistä lukkee
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\072809-14554-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 \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7100 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700
Machine Name:
Kernel base = 0xfffff800`02a4b000 PsLoadedModuleList = 0xfffff800`02c84e90
Debug session time: Tue Jul 28 11:47:52.612 2009 (GMT+3)
System Uptime: 0 days 0:07:02.079
*********************************************************************
* 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 \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {80000003, fffff9600011339d, fffff88007225010, 0}
Unable to load image \SystemRoot\System32\win32k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* 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+ *
*********************************************************************
*********************************************************************
* 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+ *
*********************************************************************
Probably caused by : win32k.sys ( win32k+c339d )
Followup: MachineOwner
|
|
su1kk0
Newbie
|
28. heinäkuuta 2009 @ 19:08 |
Linkki tähän viestiin
|
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [c:\windows\minidump\072809-14554-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Inaccessible path: 'c:\windows\i386'
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: c:\windows\i386
Windows 7 Kernel Version 7100 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700
Machine Name:
Kernel base = 0xfffff800`02a4b000 PsLoadedModuleList = 0xfffff800`02c84e90
Debug session time: Tue Jul 28 11:47:52.612 2009 (GMT+3)
System Uptime: 0 days 0:07:02.079
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {80000003, fffff9600011339d, fffff88007225010, 0}
Unable to load image \SystemRoot\System32\win32k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+c339d )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 0000000080000003, Exception code that caused the bugcheck
Arg2: fffff9600011339d, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88007225010, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - Argumentti ei kelpaa.
FAULTING_IP:
win32k+c339d
fffff960`0011339d cc int 3
CONTEXT: fffff88007225010 -- (.cxr 0xfffff88007225010)
rax=000000000000005b rbx=fffff900c1a32540 rcx=fffff900c1a32540
rdx=000000000000da40 rsi=0000000000000210 rdi=0000000000000000
rip=fffff9600011339d rsp=fffff880072259f0 rbp=fffff88007225ca0
r8=fffff900c1a6fac0 r9=00000000ffffffff r10=0000000000002407
r11=fffff900c1ec66a0 r12=0000000000000001 r13=fffff88007225b68
r14=00000000000025ff r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00200286
win32k+0xc339d:
fffff960`0011339d cc int 3
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: iexplore.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff900c1a32540 to fffff9600011339d
STACK_TEXT:
fffff880`072259f0 fffff900`c1a32540 : fffff960`00119671 fffff900`c1a32540 fffff880`07225ca0 00000000`00000000 : win32k+0xc339d
fffff880`072259f8 fffff960`00119671 : fffff900`c1a32540 fffff880`07225ca0 00000000`00000000 00000000`00000000 : 0xfffff900`c1a32540
fffff880`07225a00 fffff900`c1a32540 : fffff880`07225ca0 00000000`00000000 00000000`00000000 00000000`ffffffff : win32k+0xc9671
fffff880`07225a08 fffff880`07225ca0 : 00000000`00000000 00000000`00000000 00000000`ffffffff 00000000`00000001 : 0xfffff900`c1a32540
fffff880`07225a10 00000000`00000000 : 00000000`00000000 00000000`ffffffff 00000000`00000001 00000000`00000001 : 0xfffff880`07225ca0
FOLLOWUP_IP:
win32k+c339d
fffff960`0011339d cc int 3
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: win32k+c339d
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a0a3ad0
STACK_COMMAND: .cxr 0xfffff88007225010 ; kb
FAILURE_BUCKET_ID: X64_0x3B_win32k+c339d
BUCKET_ID: X64_0x3B_win32k+c339d
Followup: MachineOwner
---------
|
AfterDawn Addict
3 tuotearviota
|
28. heinäkuuta 2009 @ 21:23 |
Linkki tähän viestiin
|
win32k.sys on todella geneerinen virheilmoitus. Olen aika paljon minidumppeja analysoimalla korjannut ongelmia duunissa, mutta tuohon en osaa sanoa mitään.
Lainaus:
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: iexplore.exe
Tuo saattaisi viitata IE ongelmaan. Kokeile käyttää jotain toista selainta.
Give a man a fish and you feed him for a day.
Teach a man to fish and you feed him for a lifetime.
|
|
Mainos
|
|
|
|
su1kk0
Newbie
|
30. heinäkuuta 2009 @ 10:44 |
Linkki tähän viestiin
|
tänään kaatui taas ja tuli tälläinen minidump:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [c:\windows\minidump\073009-17737-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Inaccessible path: 'c:\windows\i386'
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: c:\windows\i386
Windows 7 Kernel Version 7100 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7100.0.amd64fre.winmain_win7rc.090421-1700
Machine Name:
Kernel base = 0xfffff800`02a0d000 PsLoadedModuleList = 0xfffff800`02c46e90
Debug session time: Thu Jul 30 10:31:09.750 2009 (GMT+3)
System Uptime: 0 days 0:01:01.093
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff80002b0a3d5, fffff880035e6c80, 0}
Probably caused by : memory_corruption ( nt!MiGetTopLevelPfn+65 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002b0a3d5, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff880035e6c80, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - K sky osoitteessa 0x%08lx viittasi muistiin osoitteessa 0x%08lx. Muisti ei voi olla %s.
FAULTING_IP:
nt!MiGetTopLevelPfn+65
fffff800`02b0a3d5 4c8b4928 mov r9,qword ptr [rcx+28h]
CONTEXT: fffff880035e6c80 -- (.cxr 0xfffff880035e6c80)
rax=000ffafffffffffd rbx=000fffffffffffff rcx=02ff0a7fffffff70
rdx=fffffff555674d24 rsi=fffffa8003908000 rdi=0000058000000000
rip=fffff80002b0a3d5 rsp=fffff880035e7668 rbp=0000000000000000
r8=fffffe00035e76a0 r9=000ffafffffffffd r10=fffff880035e7718
r11=0000000000000001 r12=000000003ffffff8 r13=0000000000000000
r14=fffff6fb40000000 r15=0000000fffffffff
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
nt!MiGetTopLevelPfn+0x65:
fffff800`02b0a3d5 4c8b4928 mov r9,qword ptr [rcx+28h] ds:002b:02ff0a7f`ffffff98=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80002b0a3d5
STACK_TEXT:
fffff880`035e7668 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiGetTopLevelPfn+0x65
FOLLOWUP_IP:
nt!MiGetTopLevelPfn+65
fffff800`02b0a3d5 4c8b4928 mov r9,qword ptr [rcx+28h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!MiGetTopLevelPfn+65
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 49ee9439
STACK_COMMAND: .cxr 0xfffff880035e6c80 ; kb
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x3B_nt!MiGetTopLevelPfn+65
BUCKET_ID: X64_0x3B_nt!MiGetTopLevelPfn+65
Followup: MachineOwner
---------
Viestiä on muokattu lähettämisen jälkeen. Viimeisin muokkaus 30. heinäkuuta 2009 @ 10:45
|
