Im going nuts... ;(

Page 2 of 2 FirstFirst 12

  1. Posts : 43
    Windows 7 x64 (build 7600)
    Thread Starter
       #11

    I uninstalled avast...and played a bit DiRT2,and it seems like the problems are solved...

    but why was avast making problems? i had avast while using RC...
      My Computer


  2. Posts : 5,747
    7600.20510 x86
       #12

    nexexcalibur said:
    I uninstalled avast...and played a bit DiRT2,and it seems like the problems are solved...

    but why was avast making problems? i had avast while using RC...
    You'd have to ask them about that.

    You're welcome.
      My Computer


  3. Posts : 43
    Windows 7 x64 (build 7600)
    Thread Starter
       #13

    again me...

    this morning i had again total freezing(not BSOD,couldnt press ctrl+alt+del,only thing left is restart)
    after restart,i heard roar of cooler three times(usually one time),black screen,windows doesnt start,one more restart...now its stuck in bios,and it says something,and after that "changing dram speeds to default",something like that...

    ten minutes ago, i came from college,turn on computer,and 5 seconds after windows started,it freezed again...

    so, my opinion is,that while i was upgrading from RC to RTM,something broke down within hardware part of the computer...im guessing RAM memory...so i took out one module out...i ll see if it going to freeze again...if does,ill switch memories again...after that, i dont know what to do...
      My Computer


  4. Posts : 43
    Windows 7 x64 (build 7600)
    Thread Starter
       #14

    new update:

    i put 2nd modul in memory slot,loged on and left the room...

    now i came back and first heard cooler roaring like its booting(but non-stop)
    and i turned on monitor,nothing happened...and the green light glowed repeatedly(it was always on,all the time,but now was flashing)

    earlier i did microsoft memory diagnostic tool for one and for both moduls...and no problems were shown...


    guess windows 7 dont like 2 same memories...
      My Computer


  5. Posts : 43
    Windows 7 x64 (build 7600)
    Thread Starter
       #15

    i need to bump mine "old" thread,,,

    i got BSOD again...dump file is in attachment... :) help
      My Computer


  6. Posts : 11,840
    64-bit Windows 8.1 Pro
       #16

    Your .dmp file points to a bad graphic card driver.... Remove your current Nvidia driver and check for a newer version...

    Attachment 43683
      My Computer


  7. Posts : 43
    Windows 7 x64 (build 7600)
    Thread Starter
       #17

    Tews said:
    Your .dmp file points to a bad graphic card driver.... Remove your current Nvidia driver and check for a newer version...

    Attachment 43683
    is it possible that i got that bsod cause an overheating? i was playing alot Team Fortress 2 today...and i usually get everyday freezing,which lasts for 10-15 seconds,and than back to normal...but today freeze lasted more,and immediatly bsod after that...
      My Computer


  8. Posts : 11,840
    64-bit Windows 8.1 Pro
       #18

    Yes... This could definitely be a heating problem... download gpuz and tell us what the temps are... make sure that you are getting adequate airflow inside your case.. This is the kind of information that we need before we start troubleshooting ok??
      My Computer


  9. Posts : 28,845
    Win 8 Release candidate 8400
       #19

    nexexcalibur said:
    i need to bump mine "old" thread,,,

    i got BSOD again...dump file is in attachment... :) help


    As tews pointed out the video driver was the likely cause. You do how ever have several drivers that are ancient they need upgrading.

    you should also run a system file check to verify and repair your system files to do that type cmd in search>right click and run as admin>sfc /scannow

    Let us know the results

    Hope this helps

    Ken J+




    Code:
    BIOS64.sys        fffff880`03be7000    fffff880`03bef000    0x00008000    0x3ee27f50    6/7/2003 7:12:00 PM                        
    secdrv.SYS        fffff880`06ce5000    fffff880`06cf0000    0x0000b000    0x4508052e    9/13/2006 8:18:38 AM                        
    amdide64.sys        fffff880`0118d000    fffff880`01194000    0x00007000    0x470ed078    10/11/2007 8:40:08 PM                        
    LHidFilt.Sys        fffff880`034a6000    fffff880`034b9000    0x00013000    0x474e90ad    11/29/2007 5:13:01 AM                        
    LMouFilt.Sys        fffff880`034c7000    fffff880`034da000    0x00013000    0x474e90b1    11/29/2007 5:13:05 AM
    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\K\Desktop\122509-14320-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*d:\symbols*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.16385.amd64fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0xfffff800`02c67000 PsLoadedModuleList = 0xfffff800`02ea4e50
    Debug session time: Fri Dec 25 17:14:44.595 2009 (GMT-5)
    System Uptime: 0 days 9:37:14.390
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ...........................
    Loading User Symbols
    Loading unloaded module list
    .......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 101, {61, 0, fffff880009e9180, 1}
    
    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) 
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    CLOCK_WATCHDOG_TIMEOUT (101)
    An expected clock interrupt was not received on a secondary processor in an
    MP system within the allocated interval. This indicates that the specified
    processor is hung and not processing interrupts.
    Arguments:
    Arg1: 0000000000000061, Clock interrupt time out interval in nominal clock ticks.
    Arg2: 0000000000000000, 0.
    Arg3: fffff880009e9180, The PRCB address of the hung processor.
    Arg4: 0000000000000001, 0.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_2_PROC
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  svchost.exe
    
    CURRENT_IRQL:  d
    
    STACK_TEXT:  
    fffff880`0a42c478 fffff800`02c85443 : 00000000`00000101 00000000`00000061 00000000`00000000 fffff880`009e9180 : nt!KeBugCheckEx
    fffff880`0a42c480 fffff800`02ce15f7 : 00000000`00000000 fffff800`00000001 00000000`00002710 fffff880`13f1f679 : nt! ?? ::FNODOBFM::`string'+0x4e3e
    fffff880`0a42c510 fffff800`02c28895 : fffff800`02c4d460 fffff880`0a42c6c0 fffff800`02c4d460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
    fffff880`0a42c610 fffff800`02cd53f3 : fffff800`02e51e80 00000000`00000001 fffffa80`047f9840 fffff800`02cd4b07 : hal!HalpHpetClockInterrupt+0x8d
    fffff880`0a42c640 fffff800`02c982c9 : fffffa80`047f9a80 fffff800`02cdee52 fffffa80`047f9a80 fffffa80`04858440 : nt!KiInterruptDispatchNoLock+0x163
    fffff880`0a42c7d0 fffff800`02fd3e58 : 00000000`00000000 fffff880`0a42cca0 fffff800`02c67000 00000000`00000011 : nt!KeFlushProcessWriteBuffers+0x65
    fffff880`0a42c840 fffff800`02fd4e49 : 00000000`03e68c90 fffff800`02fd09ee 00000000`00000000 00000000`00000040 : nt!ExpQuerySystemInformation+0x1368
    fffff880`0a42cbe0 fffff800`02cd8153 : fffffa80`04690000 000007fe`fa830be0 ffffffff`fffe7960 000007fe`00000000 : nt!NtQuerySystemInformation+0x4d
    fffff880`0a42cc20 00000000`76f4021a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0179f738 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f4021a
    
    
    STACK_COMMAND:  kb
    
    SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: Unknown_Module
    
    IMAGE_NAME:  Unknown_Image
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE
    
    BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_2_PROC_ANALYSIS_INCONCLUSIVE
    
    Followup: MachineOwner
    ---------
    Last edited by zigzag3143; 25 Dec 2009 at 18:43.
      My Computer


 
Page 2 of 2 FirstFirst 12

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 02:45.
Find Us