Prosze o pomoc w rozwiazaniu mojego problemu z komputerem który co jakis czas wyłącza sie sam
Wpisy z folderu minidump:
Wpis 1
Probably caused by : nvatabus.sys ( nvatabus+2aee )
Followup: MachineOwner
---------
Loading Dump File [C:\WINDOWS\Minidump\Mini040812-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 XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_rtm.040803-2158
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
Debug session time: Sun Apr 8 18:01:05.375 2012 (GMT+2)
System Uptime: 0 days 0:13:31.984
Loading Kernel Symbols
...............................................................
................................................................
......
Loading User Symbols
Loading unloaded module list
..........
Unable to load image nvatabus.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvatabus.sys
*** ERROR: Module load completed but symbols could not be loaded for nvatabus.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007F, {8, 80042000, 0, 0}
Probably caused by : nvatabus.sys ( nvatabus+2aee )
Followup: MachineOwner
---------
Wpis 2
Loading Dump File [C:\WINDOWS\Minidump\Mini040912-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 XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_rtm.040803-2158
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
Debug session time: Mon Apr 9 15:41:20.671 2012 (GMT+2)
System Uptime: 0 days 0:03:05.283
Loading Kernel Symbols
...............................................................
................................................................
......
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C000021A, {e12d4a58, c0000005, 7c9106c3, 108ed04}
unable to get nt!KiCurrentEtwBufferOffset
unable to get nt!KiCurrentEtwBufferBase
Probably caused by : ntoskrnl.exe ( nt!KiFastCallEntry+f8 )
Followup: MachineOwner
---------
Wpis 3
Loading Dump File [C:\WINDOWS\Minidump\Mini040912-02.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 XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_rtm.040803-2158
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
Debug session time: Mon Apr 9 15:44:04.718 2012 (GMT+2)
System Uptime: 0 days 0:02:21.329
Loading Kernel Symbols
...............................................................
................................................................
.......
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C000021A, {e10ee098, c0000005, 7c9106c3, 57ed04}
unable to get nt!KiCurrentEtwBufferOffset
unable to get nt!KiCurrentEtwBufferBase
Probably caused by : ntoskrnl.exe ( nt!KiFastCallEntry+f8 )
Followup: MachineOwner
---------
Wpis 4
Loading Dump File [C:\WINDOWS\Minidump\Mini041812-02.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 XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_rtm.040803-2158
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
Debug session time: Wed Apr 18 19:12:19.109 2012 (GMT+2)
System Uptime: 0 days 0:06:22.712
Loading Kernel Symbols
...............................................................
................................................................
...
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C000021A, {e137b9c8, c0000005, 7c9106c3, 6eed04}
unable to get nt!KiCurrentEtwBufferOffset
unable to get nt!KiCurrentEtwBufferBase
Probably caused by : ntoskrnl.exe ( nt!KiFastCallEntry+f8 )
Followup: MachineOwner
---------
Wpis 5
Loading Dump File [C:\WINDOWS\Minidump\Mini041812-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 XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_rtm.040803-2158
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
Debug session time: Wed Apr 18 19:05:29.015 2012 (GMT+2)
System Uptime: 0 days 0:05:59.618
Loading Kernel Symbols
...............................................................
................................................................
.....
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C000021A, {e10c7d78, c0000005, 7c9106c3, f8ed04}
unable to get nt!KiCurrentEtwBufferOffset
unable to get nt!KiCurrentEtwBufferBase
Probably caused by : ntoskrnl.exe ( nt!KiFastCallEntry+f8 )
Followup: MachineOwner
---------
Prosze o pomoc !!!!!!!!
//Dubel -> Kontynuuj tu:
problemy/problem-komputer-sam-sie-resetuje-t18418.html
djkamil09061991
Problem komp sie wyłancza
-
- Reklama
Kto jest online
Użytkownicy przeglądający to forum: Obecnie na forum nie ma żadnego zarejestrowanego użytkownika i 1 gość