Results 1 to 21 of 21

Thread: 35

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1
    Registered User PROXIMO's Avatar
    Join Date: Mar:2005
    Location: BG
    Posts: 411

    35

    , ga-965p-ds4 6 , 64, 32 . WoW . 4 , 5-5-5-15 .




    965 . , , . 1 5 , 3 1 . .

  2. #2
    Registered User ishek's Avatar
    Join Date: Jul:2003
    Posts: 148
    . C:\WINDOWS\Minidump , . .
    Gigabyte P35-DS3R, E6320 435x7, 2x1gb SuperT T800UX1GC4, SAPPHIRE X1950GT, Seagate 320GB ST3320620AS, Asus 1814BLT, Fortron Bluestorm II 500W, Dell 228WFP

  3. #3
    Registered User PROXIMO's Avatar
    Join Date: Mar:2005
    Location: BG
    Posts: 411

  4. #4
    Registered User petst's Avatar
    Join Date: Nov:2003
    Location:
    Posts: 576
    , power setting - change plan settings - change advanced power settings - Hard disk - Turn off hrd disk after - Never (0).
    ...

  5. #5
    Registered User PROXIMO's Avatar
    Join Date: Mar:2005
    Location: BG
    Posts: 411
    0 , 1 , 1 4 ,

  6. #6
    Registered User petst's Avatar
    Join Date: Nov:2003
    Location:
    Posts: 576
    . - .
    ...

  7. #7
    nikonian Uve_Smotanson's Avatar
    Join Date: Feb:2005
    Location:
    Posts: 3,800
    , Vista, , . , . , .
    Nikon D60, Nikkor AF-S DX 18-55mm, f/3.5-5.6G ED II

  8. #8
    Registered User PROXIMO's Avatar
    Join Date: Mar:2005
    Location: BG
    Posts: 411
    , 1 warning events
    TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts.

    ?

  9. #9
    Registered User ishek's Avatar
    Join Date: Jul:2003
    Posts: 148
    , , . +sp2 10, . , . + - tcpip.sys.

    ,
    Gigabyte P35-DS3R, E6320 435x7, 2x1gb SuperT T800UX1GC4, SAPPHIRE X1950GT, Seagate 320GB ST3320620AS, Asus 1814BLT, Fortron Bluestorm II 500W, Dell 228WFP

  10. #10
    Registered User PROXIMO's Avatar
    Join Date: Mar:2005
    Location: BG
    Posts: 411
    4 , 2-3 100 ,


  11. #11
    Registered User ishek's Avatar
    Join Date: Jul:2003
    Posts: 148
    windbg.exe debugging windows:
    http://support.microsoft.com/kb/824344

    dxgkrnl.sys, "DirectX Graphics Kernel". , -.
    directx:
    http://support.microsoft.com/kb/940105/

    . :
    http://oca.microsoft.com/en/windiag.asp

    , .
    Gigabyte P35-DS3R, E6320 435x7, 2x1gb SuperT T800UX1GC4, SAPPHIRE X1950GT, Seagate 320GB ST3320620AS, Asus 1814BLT, Fortron Bluestorm II 500W, Dell 228WFP

  12. #12
    Registered User PROXIMO's Avatar
    Join Date: Mar:2005
    Location: BG
    Posts: 411
    , WoW

  13. #13
    Registered User PROXIMO's Avatar
    Join Date: Mar:2005
    Location: BG
    Posts: 411
    a dxgkrnl.sys BSOD 2 4,
    Code:
    Microsoft (R) Windows Debugger  Version 6.6.0007.5
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\V. Stanchev\Desktop\Mini090507-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 2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Kernel base = 0x82000000 PsLoadedModuleList = 0x82108ab0
    Debug session time: Wed Sep  5 00:09:48.915 2007 (GMT+3)
    System Uptime: 0 days 0:36:58.559
    *********************************************************************
    * 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 2
    *** 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 A, {88c036f4, ff, 0, 821d3e34}
    
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
    
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
    
    *** WARNING: Unable to verify timestamp for laPP.sys
    *** ERROR: Module load completed but symbols could not be loaded for laPP.sys
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    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                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    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                                     ***
    ***                                                                   ***
    *************************************************************************
    Probably caused by : laPP.sys ( laPP+339 )
    
    Followup: MachineOwner
    ---------
    2 . 4

    lapp.sys; dxgkrnl.sys win32k.sys
    Wow
    Last edited by PROXIMO; 7th September 2007 at 01:32.

  14. #14
    Registered User PROXIMO's Avatar
    Join Date: Mar:2005
    Location: BG
    Posts: 411
    To . 163.11
    Code:
    *** WARNING: Unable to verify timestamp for ndis.sys
    *** ERROR: Module load completed but symbols could not be loaded for ndis.sys
    Probably caused by : tcpip.sys ( tcpip+6b405 )
    
    Followup: MachineOwner
    k

  15. #15
    Bombera's Avatar
    Join Date: Jul:2001
    Location: 4EVA
    Posts: 13,833
    , , . . , , , . , . . 100 % .
    EVGA X299 FTW K|i9-7960X@4.7|4x8 Patriot Viper Steel 4000|GTX 1660 Ti|970 EVO 1 TB|Seasonic Focus GX-1000|Xigmatek Elysium|
    Rampage IV Extreme BE|E5-1680v2@4.7|4x4 HyperX 1866|Cougar Aqua 240|GTX 1050 Ti|970 EVO 1/4 TB|CM 850 SilentPro|HAF-X|

  16. #16
    Registered User PROXIMO's Avatar
    Join Date: Mar:2005
    Location: BG
    Posts: 411
    , , 100%+ , 4 6 , . 4 .

  17. #17
    Bombera's Avatar
    Join Date: Jul:2001
    Location: 4EVA
    Posts: 13,833
    . .
    , . , 24 , . 10 , . , .
    EVGA X299 FTW K|i9-7960X@4.7|4x8 Patriot Viper Steel 4000|GTX 1660 Ti|970 EVO 1 TB|Seasonic Focus GX-1000|Xigmatek Elysium|
    Rampage IV Extreme BE|E5-1680v2@4.7|4x4 HyperX 1866|Cougar Aqua 240|GTX 1050 Ti|970 EVO 1/4 TB|CM 850 SilentPro|HAF-X|

  18. #18
    Registered User PROXIMO's Avatar
    Join Date: Mar:2005
    Location: BG
    Posts: 411
    . BSOD .

    2 1 , , .



    ______


    24

    Probably caused by : dxgkrnl.sys ( dxgkrnl+238cb )
    Last edited by PROXIMO; 9th September 2007 at 17:41.

  19. #19
    Bombera's Avatar
    Join Date: Jul:2001
    Location: 4EVA
    Posts: 13,833
    , , - . .
    EVGA X299 FTW K|i9-7960X@4.7|4x8 Patriot Viper Steel 4000|GTX 1660 Ti|970 EVO 1 TB|Seasonic Focus GX-1000|Xigmatek Elysium|
    Rampage IV Extreme BE|E5-1680v2@4.7|4x4 HyperX 1866|Cougar Aqua 240|GTX 1050 Ti|970 EVO 1/4 TB|CM 850 SilentPro|HAF-X|

  20. #20
    Registered User PROXIMO's Avatar
    Join Date: Mar:2005
    Location: BG
    Posts: 411
    , / 4 1 1 2 5 , . . Video Card Stability .


    ( , )
    A timeout (30000 milliseconds) was reached while waiting for a transaction response from the ShellHWDetection service.

    edit
    Probably caused by : nvlddmkm.sys ( nvlddmkm+517ac )
    Last edited by PROXIMO; 9th September 2007 at 19:21.

  21. #21

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

Copyright © 1999-2011 . .
iskamPC.com | mobility.BG | Bloody's Techblog | | 3D Vision Blog |