Beiträge von Timon17

    Hey ich wollte fragen ob ihr mir ein gutes Motherboard bis 60-70 euro empfehlen könnt.
    Habe 4gb DDR2 Ram, 400Watt Netzteil,Amd Athlon 64 X2 Dual Core Processor 5200+ und eine Grafikkarte die über PCI-Express läuft.

    Ja habe ich dann läd er nur einen für die x1650 runter und der Bluescreen kommt immernoch. Ich glaube ja immernoch das es evtl iwas mit den Ram Slot zutuhn hat weil der eine ja nicht Funktioniert aber beide Ram teile heile sind.

    Protokollname: Microsoft-Windows-MemoryDiagnostics-Results/Debug
    Quelle: Microsoft-Windows-MemoryDiagnostics-Results
    Datum: 23.10.2013 21:18:39
    Ereignis-ID: 2001
    Aufgabenkategorie:Keine
    Ebene: Informationen
    Schlüsselwörter:
    Benutzer: SYSTEM
    Computer: Timon2-PC
    Beschreibung:
    Ergebnisse der Windows-Speicherdiagnose
    Ereignis-XML:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="Microsoft-Windows-MemoryDiagnostics-Results" Guid="{5F92BC59-248F-4111-86A9-E393E12C6139}" />
    <EventID>2001</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2013-10-23T19:18:39.343750000Z" />
    <EventRecordID>2</EventRecordID>
    <Correlation />
    <Execution ProcessID="2060" ThreadID="2064" />
    <Channel>Microsoft-Windows-MemoryDiagnostics-Results/Debug</Channel>
    <Computer>Timon2-PC</Computer>
    <Security UserID="S-1-5-18" />
    </System>
    <UserData>
    <Results xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://manifests.microsoft.com/win/2005/08/wi…Postboot/Events">
    <MemDiagRawData>FF070000000000000200000003000000050000000C000000230F0000160000000200000000000000E9FA070065040000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000400100001026240001000000400100000000000040010000000000001600000038000000DD070A00170013000A00390000000700E9FA070065040000010000C0000001000A00010000000000020001001800010000000000040001001A0001000000000006000100240001000000000001000100500001000000000003000100C500010000000000000000004100010000000000080001003B0001000000000007000100230101000000000005000100B70201000000000006000000C601010000000000000001000A00020000000000020001001800020000000000040001001A0002000000000006000100240002000000000001000100500002000000000003000100C500020000000000000000004100020000000000080001003B0002000000000007000100230102000000000005000100B80202000000000006000000C601020000000000</MemDiagRawData>
    </Results>
    </UserData>
    </Event>

    Hey Danke für eure vielen Antworten hatte leider 2 Tage kein Internet. Ich Spiele mit einer Ati Readon 1700fx und meine Festplatte ist eigl. noch ziehmlich neu. Was mir wieder aufgefallen ist ich habe 4 Steckplätze für RAM Speicher 2 für meine die ich benutze und 2 andere das Problem ist ich kann nur einen von meinen benutzen bei einem zeigt er einfach nichts mehr an. aber in dem einen Slot gehen beide wenn ich sie einzelnd teste. Hier der Report:
    System Information (local)
    --------------------------------------------------------------------------------

    computer name: TIMON2-PC
    windows version: Windows 7 , 6.1, build: 7600
    windows dir: C:\Windows
    CPU: AuthenticAMD AMD Athlon(tm) 64 X2 Dual Core Processor 5200+ AMD586, level: 15
    2 logical processors, active mask: 3
    RAM: 2146754560 total
    VM: 2147352576, free: 1997414400


    --------------------------------------------------------------------------------
    Crash Dump Analysis
    --------------------------------------------------------------------------------

    Crash dump directory: C:\Windows\Minidump

    Crash dumps are enabled on your computer.

    On Sun 20.10.2013 11:18:35 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\102013-16546-01.dmp
    This was probably caused by the following module: atikmdag.sys (atikmdag+0xDBDE8)
    Bugcheck code: 0x50 (0xFFFFFFFFFFFFFE43, 0x1, 0xFFFFFFFF91FEF761, 0x0)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    file path: C:\Windows\system32\drivers\atikmdag.sys
    product: ATI Radeon-Familie
    company: ATI Technologies Inc.
    description: ATI Radeon-Kernelmodustreiber
    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.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon-Kernelmodustreiber, ATI Technologies Inc.).
    Google query: ATI Technologies Inc. PAGE_FAULT_IN_NONPAGED_AREA


    On Sun 20.10.2013 11:18:35 GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: atikmdag.sys (atikmdag+0xDBDE8)
    Bugcheck code: 0x50 (0xFFFFFFFFFFFFFE43, 0x1, 0xFFFFFFFF91FEF761, 0x0)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    file path: C:\Windows\system32\drivers\atikmdag.sys
    product: ATI Radeon-Familie
    company: ATI Technologies Inc.
    description: ATI Radeon-Kernelmodustreiber
    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.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon-Kernelmodustreiber, ATI Technologies Inc.).
    Google query: ATI Technologies Inc. PAGE_FAULT_IN_NONPAGED_AREA


    On Sun 20.10.2013 11:09:44 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\102013-15234-01.dmp
    This was probably caused by the following module: ntkrnlpa.exe (nt+0x3D21C)
    Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8285521C, 0xFFFFFFFF9B83BA34, 0x0)
    Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
    file path: C:\Windows\system32\ntkrnlpa.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
    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 that cannot be identified at this time.


    On Sat 19.10.2013 22:43:09 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\102013-14765-01.dmp
    This was probably caused by the following module: ntfs.sys (Ntfs+0x14355)
    Bugcheck code: 0x24 (0x1904FB, 0xFFFFFFFF9B89F7DC, 0xFFFFFFFF9B89F3C0, 0xFFFFFFFF887A7885)
    Error: NTFS_FILE_SYSTEM
    file path: C:\Windows\system32\drivers\ntfs.sys
    product: Betriebssystem Microsoft® Windows®
    company: Microsoft Corporation
    description: NT-Dateisystemtreiber
    Bug check description: This indicates a problem occurred in the NTFS file system.
    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 that cannot be identified at this time.


    On Sat 19.10.2013 21:41:22 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\101913-14359-01.dmp
    This was probably caused by the following module: amdk8.sys (amdk8+0x1BB6)
    Bugcheck code: 0xD1 (0xFFFFFFFFFFFFFFFF, 0xFF, 0x8, 0xFFFFFFFFFFFFFFFF)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\amdk8.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Processor Device Driver
    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 that cannot be identified at this time.


    On Sat 19.10.2013 00:33:10 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\101913-14875-01.dmp
    This was probably caused by the following module: ntkrnlpa.exe (nt+0x45ABB)
    Bugcheck code: 0xA (0x4, 0x2, 0x1, 0xFFFFFFFF828A5B86)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\ntkrnlpa.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


    On Fri 18.10.2013 14:11:25 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\101813-14968-01.dmp
    This was probably caused by the following module: hal.sys (hal+0xBACE)
    Bugcheck code: 0xA (0xFFFFFFFFFFFFFF7C, 0x2, 0x1, 0xFFFFFFFF82C1CACE)
    Error: IRQL_NOT_LESS_OR_EQUAL
    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.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hal.sys .
    Google query: hal.sys IRQL_NOT_LESS_OR_EQUAL


    On Fri 18.10.2013 13:50:57 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\101813-15171-01.dmp
    This was probably caused by the following module: hal.sys (hal+0xBACE)
    Bugcheck code: 0x1000007F (0x8, 0xFFFFFFFF801DB000, 0x0, 0x0)
    Error: UNEXPECTED_KERNEL_MODE_TRAP_M
    Bug check description: This indicates that a trap was generated by the Intel CPU and the kernel failed to catch this trap.
    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.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hal.sys .
    Google query: hal.sys UNEXPECTED_KERNEL_MODE_TRAP_M


    On Fri 18.10.2013 12:39:17 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\101813-18296-01.dmp
    This was probably caused by the following module: ntkrnlpa.exe (nt+0x45ABB)
    Bugcheck code: 0xA (0x282828FB, 0x2, 0x0, 0xFFFFFFFF82885B3F)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\ntkrnlpa.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


    On Fri 18.10.2013 10:48:41 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\101813-13343-01.dmp
    This was probably caused by the following module: ntkrnlpa.exe (nt+0x45ABB)
    Bugcheck code: 0xA (0x2FD8, 0x2, 0x1, 0xFFFFFFFF81CABDA5)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\ntkrnlpa.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


    On Fri 18.10.2013 10:14:04 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\101813-12859-01.dmp
    This was probably caused by the following module: ntkrnlpa.exe (nt+0x84AA3)
    Bugcheck code: 0x50 (0xFFFFFFFFD654194B, 0x0, 0xFFFFFFFF81CAFFC1, 0x2)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    file path: C:\Windows\system32\ntkrnlpa.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 that cannot be identified at this time.


    On Fri 18.10.2013 01:14:58 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\101813-18031-01.dmp
    This was probably caused by the following module: ntkrnlpa.exe (nt+0x4353B)
    Bugcheck code: 0x7F (0x0, 0x0, 0x0, 0x0)
    Error: UNEXPECTED_KERNEL_MODE_TRAP
    file path: C:\Windows\system32\ntkrnlpa.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


    On Thu 17.10.2013 23:43:03 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\101813-16312-01.dmp
    This was probably caused by the following module: amdk8.sys (amdk8+0x1BB6)
    Bugcheck code: 0xA (0x2974B44, 0x1F, 0x0, 0xFFFFFFFF828E9290)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\amdk8.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Processor Device Driver
    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 that cannot be identified at this time.


    On Thu 17.10.2013 23:21:17 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\101813-13968-01.dmp
    This was probably caused by the following module: amdk8.sys (amdk8+0x1BB6)
    Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
    Error: UNEXPECTED_KERNEL_MODE_TRAP
    file path: C:\Windows\system32\drivers\amdk8.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Processor Device Driver
    Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
    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 that cannot be identified at this time.


    On Thu 17.10.2013 22:55:45 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\101813-15250-01.dmp
    This was probably caused by the following module: hal.sys (hal+0xBACE)
    Bugcheck code: 0xA (0xFFFFFFFF807EFF7C, 0x2, 0x1, 0xFFFFFFFF8281DACE)
    Error: IRQL_NOT_LESS_OR_EQUAL
    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.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hal.sys .
    Google query: hal.sys IRQL_NOT_LESS_OR_EQUAL


    --------------------------------------------------------------------------------
    Conclusion
    --------------------------------------------------------------------------------

    32 crash dumps have been found and analyzed. Only 15 are included in this report. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

    atikmdag.sys (ATI Radeon-Kernelmodustreiber, ATI Technologies Inc.)
    hal.sys

    If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


    Read the topic general suggestions for troubleshooting system crashes for more information.

    Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

    Sorry hatte nicht gemerkt das ich nicht angemeldet bin habe im Gerätemanager jeden treiber manuel versucht zu Updaten ging bei keinem alle auf dem neusten Stand weiß echt nicht mehr was ich machen soll :/
    Meißtens tritt das Problem nur auf wenn ich Spiele,Surfe oder Videos gucke. Ab und zu macht er auch mal so ein Bluescreen kurz nach dem Start.