New
#1
Various random BSODs, usually when doing light activity
Hi Guys,
I'm struggling a bit with this one. I've done lots of googling over the past few months and not found a solution.
I put together a long overdue upgrade a couple of months ago.
4770k (second hand)
Z87x-OC (second hand)
16GB Mushkin DDR3
R9 290 (second hand)
Used old:
240gb SSD
2x 750GB HDD in RAID1
I'm having a few problems with the PC:
I've had about 20 BSODs in the last 3 months. These mostly seem to occur when doing light activity. I don't think I've had one occur with heavy load (gaming etc.)
I've also had problems with not resuming from sleep - power comes on but monitor does not wake. Happens very intermittently.
BSODs:
DRIVER_VERIFIER_DETECTED_VIOLATION
IRQL_NOT_LESS_OR_EQUAL
IRQL_NOT_LESS_OR_EQUAL
SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
DRIVER_VERIFIER_DETECTED_VIOLATION
DRIVER_VERIFIER_DETECTED_VIOLATION
DRIVER_VERIFIER_DETECTED_VIOLATION
MEMORY_MANAGEMENT
CRITICAL_OBJECT_TERMINATION
CRITICAL_OBJECT_TERMINATION
PAGE_FAULT_IN_NONPAGED_AREA
SYSTEM_SERVICE_EXCEPTION
MEMORY_MANAGEMENT
ATTEMPTED_WRITE_TO_READONLY_MEMORY
SYSTEM_SERVICE_EXCEPTION
NTFS_FILE_SYSTEM
PAGE_FAULT_IN_NONPAGED_AREA
Caused by:
gdrv.sys
ntoskrnl.exe
ntoskrnl.exe
ntoskrnl.exe
gdrv.sys
gdrv.sys
gdrv.sys
ntoskrnl.exe
ntoskrnl.exe
ntoskrnl.exe
ntoskrnl.exe
atikmdag.sys
ntoskrnl.exe
fltmgr.sys
watchdog.sys
atikmdag.sys
Ntfs.sys
ntoskrnl.exe
I'm run Memtext86+ for >48 hours straight with no errors.
I've run Prime95 for >24 hours with no problems.
Temperatures are fine (water cooled)
I've tried different graphics drivers (14.4, 14.7 beta, 13.12) with a full Display Driver Uninstaller clean each time.
I implemented driver verifier on 16/9/14, which identified the Gigabyte utilities (gdrv.sys) as problematic - I've uninstalled these (which is bloody annoying as I want to run my fans slower than bios will allow.....). I didn't have any BSOD implicating gdrv.sys before turning on driver verifier.
But this hasn't cured the problem.
I don't run antivirus.
Your help is much appreciated.
Code:Welcome to WhoCrashed (HOME EDITION) v 5.02 -------------------------------------------------------------------------------- This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution. Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice. This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems. To obtain technical support visit www.resplendence.com/support Click here to check if you have the latest version or if an update is available. Just click the Analyze button for a comprehensible report ... -------------------------------------------------------------------------------- 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 allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network. Click here for more information on the professional edition. Click here to buy the the professional edition of WhoCrashed. -------------------------------------------------------------------------------- System Information (local) -------------------------------------------------------------------------------- computer name: NICKS windows version: Windows 7 Service Pack 1, 6.1, build: 7601 windows dir: C:\Windows Hardware: Z87X-OC, Gigabyte Technology Co., Ltd., Z87X-OC-CF CPU: GenuineIntel Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz Intel586, level: 6 8 logical processors, active mask: 255 RAM: 17127673856 total -------------------------------------------------------------------------------- Crash Dump Analysis -------------------------------------------------------------------------------- Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Sun 21/09/2014 1:51:18 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\092114-1564986-01.dmp This was probably caused by the following module: gdrv.sys (gdrv+0x1809) Bugcheck code: 0xC4 (0xF6, 0x610, 0xFFFFFA800D555060, 0xFFFFF8800A5DC809) Error: DRIVER_VERIFIER_DETECTED_VIOLATION file path: C:\Windows\gdrv.sys product: Windows (R) Server 2003 DDK driver company: Windows (R) Server 2003 DDK provider description: GIGABYTE Tools Bug check description: This is the general bug check code for fatal errors found by Driver Verifier. A driver references a user-mode handle as kernel mode. 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: gdrv.sys (GIGABYTE Tools, Windows (R) Server 2003 DDK provider). Google query: Windows (R) Server 2003 DDK provider DRIVER_VERIFIER_DETECTED_VIOLATION On Sun 21/09/2014 1:51:18 AM GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: gdrv.sys (gdrv+0x1809) Bugcheck code: 0xC4 (0xF6, 0x610, 0xFFFFFA800D555060, 0xFFFFF8800A5DC809) Error: DRIVER_VERIFIER_DETECTED_VIOLATION file path: C:\Windows\gdrv.sys product: Windows (R) Server 2003 DDK driver company: Windows (R) Server 2003 DDK provider description: GIGABYTE Tools Bug check description: This is the general bug check code for fatal errors found by Driver Verifier. A driver references a user-mode handle as kernel mode. 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: gdrv.sys (GIGABYTE Tools, Windows (R) Server 2003 DDK provider). Google query: Windows (R) Server 2003 DDK provider DRIVER_VERIFIER_DETECTED_VIOLATION On Sun 21/09/2014 1:44:44 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\092114-8112-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0xA (0xFFFFF9800CC1EFD8, 0x2, 0x1, 0xFFFFF8000354E588) Error: 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 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 Sun 21/09/2014 1:43:25 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\092114-11497-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0xA (0xFFFFF9800E6FEFD0, 0x2, 0x1, 0xFFFFF8000355F588) Error: 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 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 Sun 21/09/2014 1:41:04 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\092114-37440-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0xC1 (0xFFFFF98083AC4FC0, 0xFFFFF98083AC45C6, 0x6F4040, 0x23) Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION 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 the driver wrote to an invalid section of the special pool. 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 Tue 16/09/2014 10:13:46 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\091614-6942-01.dmp This was probably caused by the following module: gdrv.sys (gdrv+0x1809) Bugcheck code: 0xC4 (0xF6, 0x37C, 0xFFFFFA8017AA0B30, 0xFFFFF88006B5B809) Error: DRIVER_VERIFIER_DETECTED_VIOLATION file path: C:\Windows\gdrv.sys product: Windows (R) Server 2003 DDK driver company: Windows (R) Server 2003 DDK provider description: GIGABYTE Tools Bug check description: This is the general bug check code for fatal errors found by Driver Verifier. A driver references a user-mode handle as kernel mode. 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: gdrv.sys (GIGABYTE Tools, Windows (R) Server 2003 DDK provider). Google query: Windows (R) Server 2003 DDK provider DRIVER_VERIFIER_DETECTED_VIOLATION On Tue 16/09/2014 10:07:03 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\091614-7628-01.dmp This was probably caused by the following module: gdrv.sys (gdrv+0x1809) Bugcheck code: 0xC4 (0xF6, 0x37C, 0xFFFFFA801723D060, 0xFFFFF88006B2D809) Error: DRIVER_VERIFIER_DETECTED_VIOLATION file path: C:\Windows\gdrv.sys product: Windows (R) Server 2003 DDK driver company: Windows (R) Server 2003 DDK provider description: GIGABYTE Tools Bug check description: This is the general bug check code for fatal errors found by Driver Verifier. A driver references a user-mode handle as kernel mode. 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: gdrv.sys (GIGABYTE Tools, Windows (R) Server 2003 DDK provider). Google query: Windows (R) Server 2003 DDK provider DRIVER_VERIFIER_DETECTED_VIOLATION On Tue 16/09/2014 10:05:30 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\091614-11325-01.dmp This was probably caused by the following module: gdrv.sys (gdrv+0x1809) Bugcheck code: 0xC4 (0xF6, 0x24C, 0xFFFFFA80163DD520, 0xFFFFF88006F05809) Error: DRIVER_VERIFIER_DETECTED_VIOLATION file path: C:\Windows\gdrv.sys product: Windows (R) Server 2003 DDK driver company: Windows (R) Server 2003 DDK provider description: GIGABYTE Tools Bug check description: This is the general bug check code for fatal errors found by Driver Verifier. A driver references a user-mode handle as kernel mode. 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: gdrv.sys (GIGABYTE Tools, Windows (R) Server 2003 DDK provider). Google query: Windows (R) Server 2003 DDK provider DRIVER_VERIFIER_DETECTED_VIOLATION On Tue 16/09/2014 9:54:53 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\091614-54912-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0x1A (0x41284, 0x215CC001, 0x0, 0xFFFFF70001080000) Error: MEMORY_MANAGEMENT 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 severe memory management error occurred. 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 Sat 13/09/2014 8:32:40 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\091314-9937-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0xF4 (0x3, 0xFFFFFA80168D7B30, 0xFFFFFA80168D7E10, 0xFFFFF800037CC270) Error: CRITICAL_OBJECT_TERMINATION 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 process or thread crucial to system operation has unexpectedly exited or been terminated. 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 that cannot be identified at this time. -------------------------------------------------------------------------------- Conclusion -------------------------------------------------------------------------------- 19 crash dumps have been found and analyzed. Only 10 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 Kernel Mode Driver, Advanced Micro Devices, Inc.) gdrv.sys (GIGABYTE Tools, Windows (R) Server 2003 DDK provider) 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.
Quote