Beiträge von sb1984

    Home Edition Notice
    --------------------------------------------------------------------------------

    This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which also allows analysis of crashdumps on remote drives and computers on the network and offers a range of additional features.

    Click here for more information on the professional edition.
    Click here to buy the the professional edition of WhoCrashed.


    --------------------------------------------------------------------------------
    System Information (local)
    --------------------------------------------------------------------------------


    windows version: Windows 7 Service Pack 1, 6.1, build: 7601
    windows dir: C:\Windows
    CPU: GenuineIntel Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz Intel586, level: 6
    4 logical processors, active mask: 15
    RAM: 6407987200 total
    VM: 2147352576, free: 1911238656


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

    Crash dump directory: C:\Windows\Minidump

    Crash dumps are enabled on your computer.

    On Sun 08.09.2013 06:50:39 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\090813-10155-01.dmp
    This was probably caused by the following module: atikmpag.sys (atikmpag+0xACF0)
    Bugcheck code: 0x116 (0xFFFFFA8008B7E3B0, 0xFFFFF8800460ACF0, 0x0, 0x2)
    Error: VIDEO_TDR_ERROR
    file path: C:\Windows\system32\drivers\atikmpag.sys
    product: AMD driver
    company: Advanced Micro Devices, Inc.
    description: AMD multi-vendor Miniport Driver
    Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
    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: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
    Google query: Advanced Micro Devices, Inc. VIDEO_TDR_ERROR


    On Sun 08.09.2013 06:50:39 GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: atikmpag.sys (0xFFFFF8800460ACF0)
    Bugcheck code: 0x116 (0xFFFFFA8008B7E3B0, 0xFFFFF8800460ACF0, 0x0, 0x2)
    Error: VIDEO_TDR_ERROR
    file path: C:\Windows\system32\drivers\atikmpag.sys
    product: AMD driver
    company: Advanced Micro Devices, Inc.
    description: AMD multi-vendor Miniport Driver
    Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
    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: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
    Google query: Advanced Micro Devices, Inc. VIDEO_TDR_ERROR


    On Sun 08.09.2013 02:41:56 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\090813-10779-01.dmp
    This was probably caused by the following module: atikmdag.sys (atikmdag+0x7AB99)
    Bugcheck code: 0x1000007E (0xFFFFFFFFC0000094, 0xFFFFF88004C82B99, 0xFFFFF880029DD878, 0xFFFFF880029DD0D0)
    Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
    file path: C:\Windows\system32\drivers\atikmdag.sys
    product: ATI Radeon Family
    company: Advanced Micro Devices, Inc.
    description: ATI Radeon Kernel Mode Driver
    Bug check description: This indicates that a system thread 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.
    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 Kernel Mode Driver, Advanced Micro Devices, Inc.).
    Google query: Advanced Micro Devices, Inc. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M


    On Wed 04.09.2013 18:05:40 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\090413-11481-01.dmp
    This was probably caused by the following module: atikmpag.sys (atikmpag+0xACF0)
    Bugcheck code: 0x116 (0xFFFFFA8008803010, 0xFFFFF88003F71CF0, 0x0, 0x2)
    Error: VIDEO_TDR_ERROR
    file path: C:\Windows\system32\drivers\atikmpag.sys
    product: AMD driver
    company: Advanced Micro Devices, Inc.
    description: AMD multi-vendor Miniport Driver
    Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
    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: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
    Google query: Advanced Micro Devices, Inc. VIDEO_TDR_ERROR


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

    4 crash dumps have been found and analyzed. 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:

    atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.)
    atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.)

    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.


    Problems with atikmpag.sys - Graphics Cards - Graphics & Displays

    If AMD Catalyst causes BSoD and I want this to ... | AMD Developer Forums

    irgendwie nervt mich das total, ich werde nie mehr daran denken amd zu kaufen

    System Information (local)
    --------------------------------------------------------------------------------


    windows version: Windows 7 Service Pack 1, 6.1, build: 7601
    windows dir: C:\Windows
    CPU: GenuineIntel Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz Intel586, level: 6
    4 logical processors, active mask: 15
    RAM: 6407987200 total
    VM: 2147352576, free: 1913511936


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

    Crash dump directory: C:\Windows\Minidump

    Crash dumps are enabled on your computer.

    On Wed 04.09.2013 18:05:40 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\090413-11481-01.dmp
    This was probably caused by the following module: atikmpag.sys (atikmpag+0xACF0)
    Bugcheck code: 0x116 (0xFFFFFA8008803010, 0xFFFFF88003F71CF0, 0x0, 0x2)
    Error: VIDEO_TDR_ERROR
    file path: C:\Windows\system32\drivers\atikmpag.sys
    product: AMD driver
    company: Advanced Micro Devices, Inc.
    description: AMD multi-vendor Miniport Driver
    Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
    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: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
    Google query: Advanced Micro Devices, Inc. VIDEO_TDR_ERROR


    On Wed 04.09.2013 18:05:40 GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: atikmpag.sys (0xFFFFF88003F71CF0)
    Bugcheck code: 0x116 (0xFFFFFA8008803010, 0xFFFFF88003F71CF0, 0x0, 0x2)
    Error: VIDEO_TDR_ERROR
    file path: C:\Windows\system32\drivers\atikmpag.sys
    product: AMD driver
    company: Advanced Micro Devices, Inc.
    description: AMD multi-vendor Miniport Driver
    Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
    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: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
    Google query: Advanced Micro Devices, Inc. VIDEO_TDR_ERROR


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

    2 crash dumps have been found and analyzed. A third party driver has 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:

    atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.)

    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.

    HD Tune: OCZ-OCTANE S2 Health

    ID Current Worst ThresholdData Status
    (01) Raw Read Error Rate 7 0 0 7 Ok
    (03) Spin Up Time 100 100 0 0 Ok
    (04) Start/Stop Count 100 100 0 0 Ok
    (05) Reallocated Sector Count 100 100 0 0 Ok
    (09) Power On Hours Count 100 100 0 599 Ok
    (0C) Power Cycle Count 100 100 0 1150 Ok
    (E8) (unknown attribute) 100 100 0 80 Ok
    (E9) (unknown attribute) 100 0 0 100 Ok

    Power On Time : 599
    Health Status : Ok

    hallo ich habe seit mehreren wochen das problem das mein pc nicht mehr richtig funktioniert.
    zuerst war es nur bei videos und im chrome.
    diablo 3 läuft stundenlang ohne probleme.
    das system wurde vor ca 2 wochen neu aufgespielt und alle aktuellen treiber installiert.
    neuerdings schreibt er keine minidumb dateien mehr.
    wir wollen morgen ein neues netzteil einbauen
    ich bedanke mich schonmal im voraus
    ich habe who crashed installiert und hier das ergebnis :

    On Mon 02.09.2013 19:04:58 GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: Unknown (0xFFFFF88001A4449C)
    Bugcheck code: 0xD1 (0x9, 0x2, 0x0, 0xFFFFF88001A4449C)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    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.
    A third party driver was identified as the probable root cause of this system error.
    Google query: DRIVER_IRQL_NOT_LESS_OR_EQUAL


    On Sun 01.09.2013 11:44:15 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\minidump 2.9.2013\090113-13899-01.dmp
    This was probably caused by the following module: tcpip.sys (0xFFFFF88001C4449C)
    Bugcheck code: 0xD1 (0x9, 0x2, 0x0, 0xFFFFF88001C4449C)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\tcpip.sys
    product: Betriebssystem Microsoft® Windows®
    company: Microsoft Corporation
    description: TCP/IP-Treiber
    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 Sun 01.09.2013 11:44:15 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\090113-13899-01.dmp
    This was probably caused by the following module: tcpip.sys (0xFFFFF88001C4449C)
    Bugcheck code: 0xD1 (0x9, 0x2, 0x0, 0xFFFFF88001C4449C)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\tcpip.sys
    product: Betriebssystem Microsoft® Windows®
    company: Microsoft Corporation
    description: TCP/IP-Treiber
    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 Thu 29.08.2013 20:38:53 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\minidump 2.9.2013\082913-13447-01.dmp
    This was probably caused by the following module: tcpip.sys (0xFFFFF88001C446A3)
    Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88001C446A3)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\tcpip.sys
    product: Betriebssystem Microsoft® Windows®
    company: Microsoft Corporation
    description: TCP/IP-Treiber
    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 Thu 29.08.2013 20:38:53 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\082913-13447-01.dmp
    This was probably caused by the following module: tcpip.sys (0xFFFFF88001C446A3)
    Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88001C446A3)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\tcpip.sys
    product: Betriebssystem Microsoft® Windows®
    company: Microsoft Corporation
    description: TCP/IP-Treiber
    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 Thu 29.08.2013 13:41:02 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\minidump 2.9.2013\082913-13930-01.dmp
    This was probably caused by the following module: tcpip.sys (0xFFFFF88001C446A3)
    Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88001C446A3)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\tcpip.sys
    product: Betriebssystem Microsoft® Windows®
    company: Microsoft Corporation
    description: TCP/IP-Treiber
    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 Thu 29.08.2013 13:41:02 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\082913-13930-01.dmp
    This was probably caused by the following module: tcpip.sys (0xFFFFF88001C446A3)
    Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88001C446A3)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\tcpip.sys
    product: Betriebssystem Microsoft® Windows®
    company: Microsoft Corporation
    description: TCP/IP-Treiber
    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 Wed 28.08.2013 11:50:30 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\minidump 2.9.2013\082813-13400-01.dmp
    This was probably caused by the following module: tcpip.sys (0xFFFFF88001C446A3)
    Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88001C446A3)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\tcpip.sys
    product: Betriebssystem Microsoft® Windows®
    company: Microsoft Corporation
    description: TCP/IP-Treiber
    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 Wed 28.08.2013 11:50:30 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\082813-13400-01.dmp
    This was probably caused by the following module: tcpip.sys (0xFFFFF88001C446A3)
    Bugcheck code: 0xD1 (0x8, 0x2, 0x0, 0xFFFFF88001C446A3)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\tcpip.sys
    product: Betriebssystem Microsoft® Windows®
    company: Microsoft Corporation
    description: TCP/IP-Treiber
    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 Wed 28.08.2013 11:10:58 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\minidump 2.9.2013\082813-13743-02.dmp
    This was probably caused by the following module: e1q62x64.sys (e1q62x64+0x1BA03)
    Bugcheck code: 0xD1 (0x90, 0x2, 0x1, 0xFFFFF8800461BA03)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\e1q62x64.sys
    product: Intel(R) Gigabit Adapter
    company: Intel Corporation
    description: Intel(R) Gigabit Adapter NDIS 6.x 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.
    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: e1q62x64.sys (Intel(R) Gigabit Adapter NDIS 6.x driver, Intel Corporation).
    Google query: Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL


    On Wed 28.08.2013 11:10:58 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\082813-13743-02.dmp
    This was probably caused by the following module: e1q62x64.sys (e1q62x64+0x1BA03)
    Bugcheck code: 0xD1 (0x90, 0x2, 0x1, 0xFFFFF8800461BA03)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\e1q62x64.sys
    product: Intel(R) Gigabit Adapter
    company: Intel Corporation
    description: Intel(R) Gigabit Adapter NDIS 6.x 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.
    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: e1q62x64.sys (Intel(R) Gigabit Adapter NDIS 6.x driver, Intel Corporation).
    Google query: Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL


    On Wed 28.08.2013 02:11:42 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\minidump 2.9.2013\082813-13993-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
    Bugcheck code: 0x19 (0x22, 0xFFFFFA8000000000, 0x0, 0x0)
    Error: BAD_POOL_HEADER
    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 pool header is corrupt.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


    On Wed 28.08.2013 02:11:42 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\082813-13993-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80)
    Bugcheck code: 0x19 (0x22, 0xFFFFFA8000000000, 0x0, 0x0)
    Error: BAD_POOL_HEADER
    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 pool header is corrupt.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.


    On Wed 28.08.2013 02:05:15 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\minidump 2.9.2013\082813-12994-01.dmp
    This was probably caused by the following module: e1q62x64.sys (e1q62x64+0x1BA03)
    Bugcheck code: 0xD1 (0x90, 0x2, 0x1, 0xFFFFF88003EAFA03)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\e1q62x64.sys
    product: Intel(R) Gigabit Adapter
    company: Intel Corporation
    description: Intel(R) Gigabit Adapter NDIS 6.x 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.
    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: e1q62x64.sys (Intel(R) Gigabit Adapter NDIS 6.x driver, Intel Corporation).
    Google query: Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL


    On Wed 28.08.2013 02:05:15 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\082813-12994-01.dmp
    This was probably caused by the following module: e1q62x64.sys (e1q62x64+0x1BA03)
    Bugcheck code: 0xD1 (0x90, 0x2, 0x1, 0xFFFFF88003EAFA03)
    Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\drivers\e1q62x64.sys
    product: Intel(R) Gigabit Adapter
    company: Intel Corporation
    description: Intel(R) Gigabit Adapter NDIS 6.x 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.
    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: e1q62x64.sys (Intel(R) Gigabit Adapter NDIS 6.x driver, Intel Corporation).
    Google query: Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL