Resultat 1 till 2 av 2

Processor överhettas

Detta är en diskussion som rör Processor överhettas i Stationära datorer (felsökning och köpråd)-forumet, som är en del av System-kategorin; Hej! Undrar om det finns någon vänlig själ som skulle kunna hjälpa mig? =) Mitt system: Operativsystem: Windows 7 Ultimate ...

  1. #1
    Registrerad användare
    Reg.datum
    dec 2010
    Inlägg
    1
    Rykteskraft
    0

    Standard Processor överhettas

    Hej!

    Undrar om det finns någon vänlig själ som skulle kunna hjälpa mig? =)

    Mitt system:
    Operativsystem: Windows 7 Ultimate 64bit
    Processor: AMD Athlon II X2 245 2.9GHz
    Moderkort: Asus M4A78 PRO
    Minne: Corsair 2x 2Gb
    Grafikkort: ATI Radeon HD 4870
    Hårddisk: Seagate 500Gb
    Nätaggregat: FSP Epsilon 600 ATX

    Det är så att jag får olika blue screens när jag spelar Star Craft 2 och WoW, hinner spela max 10 min sen är det kört.
    Men jag kan använda datorn utan problem för att surfa etc.
    Det finns inget damm i datorn, den känns heller inte varm inuti. Fläkten går för fullt.
    Köpte datorn för 1,5 år sen
    Körde ett CPU test med OCCT och fick då upp occt error detected on core #0
    Datorn startar om efter 2.44 min in i testet.

    http://img691.imageshack.us/img691/1...115h49cpu1.png

    http://img405.imageshack.us/img405/2...115h49cpu2.png

    http://img4.imageshack.us/img4/7592/...115h49gpu1.png

    http://img508.imageshack.us/img508/2...15h49volt5.png



    Har en crash dump från WhoCrashed som någon kanske kan hjälpa mig med?

    On Wed 2010-12-01 15:26:34 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\120110-67252-01.dmp
    This was probably caused by the following module: watchdog.sys (watchdog+0x122F)
    Bugcheck code: 0x10E (0x1F, 0xFFFFF8A00AFB17C0, 0x0, 0x1F25F)
    Error: VIDEO_MEMORY_MANAGEMENT_INTERNAL
    file path: C:\Windows\system32\drivers\watchdog.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Watchdog Driver
    Bug check description: This indicates that the video memory manager has encountered a condition that it is unable to recover from.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


    On Wed 2010-12-01 14:13:01 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\120110-19593-01.dmp
    This was probably caused by the following module: ndis.sys (ndis+0xBE19A)
    Bugcheck code: 0xD1 (0xFFFFFFFFFFFFFFC4, 0x2, 0x1, 0xFFFFF880016DD19A)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\ndis.sys
    product: Operativsystemet Microsoft® Windows®
    company: Microsoft Corporation
    description: NDIS 6.20-drivrutin
    Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


    On Tue 2010-11-30 10:14:23 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\113010-16411-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
    Bugcheck code: 0x50 (0xFFFFF880B78714D0, 0x8, 0xFFFFF880B78714D0, 0x5)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that invalid system memory has been referenced.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


    On Tue 2010-11-30 09:04:40 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\113010-25537-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
    Bugcheck code: 0x101 (0x61, 0x0, 0xFFFFF880009E9180, 0x1)
    Error: CLOCK_WATCHDOG_TIMEOUT
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


    On Mon 2010-11-29 13:00:17 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\112910-15787-01.dmp
    This was probably caused by the following module: hal.dll (hal+0x1F83)
    Bugcheck code: 0xA (0xFFFFFA7F8D2B5563, 0x2, 0x1, 0xFFFFF800033F3F83)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\hal.dll
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Hardware Abstraction Layer DLL
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


    On Fri 2010-11-26 11:53:00 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\112910-15085-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
    Bugcheck code: 0xD1 (0x0, 0x2, 0x8, 0x0)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


    On Fri 2010-11-19 15:20:44 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\111910-21590-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
    Bugcheck code: 0x50 (0xFFFFF8A01B27FAC4, 0x1, 0xFFFFF880012CDB69, 0x0)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that invalid system memory has been referenced.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

    Hoppas jag inte missat något.

    Tack på förhand!

  2. #2
    Registrerad användare
    Reg.datum
    nov 2008
    Ort
    Linköping
    Ålder
    22
    Inlägg
    5 295
    Blogginlägg
    29
    Rykteskraft
    0

    Standard

    Installera om grafikkortets drivrutiner, gör en Clear CMOS och se om det blir bättre det tror ja hjälper åt de där crashdumparna...

    Gällande överhettning finns det väl inte så mycket att göra förutom att köpa ny kylare eller skapa ett bättre luftflöde i chassit? Annars kan du gå in i BIOS och undervolta processorn lite och se om det hjälper?

Bokmärken

Behörigheter för att posta

  • Du får inte posta nya ämnen
  • Du får inte posta svar
  • Du får inte posta bifogade filer
  • Du får inte redigera dina inlägg
  •  

Sökmotoroptimering    SmartViper Certified Website