BSOD Errors! Multiple, please help!

Status
Not open for further replies.

Jakester93

Distinguished
Oct 30, 2012
71
0
18,630
Here is my build:

CPU: i5-3570K @4.00GHz

RAM: Corsair XMS 3 16gb 1600Mhz

GPU: NVIDIA GeForce GTX 670 FTW Edition

MOBO: Asus P8Z77-V LE PLUS

Power Supply: Corsair TX650M

COOLING: Antec Kuhler h2o 620

STORAGE: Western Digital WD Black 1TB 7200 RPM 64MB Cache SATA 6.0Gb/s
Western Digital WD Black 2TB 7200 RPM 64MB Cache SATA 6.0Gb/s
Samsung Evo 850 250GB SSD

----------------------------

I seem to be having issues lately with my PC and i don't know why! I feel like my ram is part of the issue. Yesterday, I noticed my ram timings were off from what they should be.
My ram timings in BIOS say they should be 9-9-9-24-1. Though in the actual box they read 11-11-11-30-2.

I tried switching them to the correct timings (XMP enabled). And the XMP Profile for some reason, keeps trying to put them at the 11-11-11-30-2 timings. So i switched it anyways. And BAM. BSOD. It was a continuous reboot of blue screens giving me multiple different errors. I was assuming this was from changing the timings?? I couldnt boot. So i ran a memory diagnostic all night, and in the morning im able to boot. Though my PC did shut off once. And it gave an error

" System

- Provider

[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}

EventID 41

Version 3

Level 1

Task 63

Opcode 0

Keywords 0x8000200000000002

- TimeCreated

[ SystemTime] 2015-08-28T20:20:41.628237800Z

EventRecordID 4323

Correlation

- Execution

[ ProcessID] 4
[ ThreadID] 8

Channel System

Computer Jake-PC

- Security

[ UserID] S-1-5-18


- EventData

BugcheckCode 209
BugcheckParameter1 0xfffff80142c77838
BugcheckParameter2 0x2
BugcheckParameter3 0x8
BugcheckParameter4 0xfffff80142c77838
SleepInProgress 0
PowerButtonTimestamp 0
BootAppStatus 0 "


------------------------------------

Above is just one of the many errors in my event log.
What is causing this issue?
I got multiple errors last night on my blue screens. I don't remember what they were exactly, but i think they were:

"srttrail" (Something about a srt/srttail.txt)
"kmode exception not handled"
"kernel security check failure"
"fault in nonpaged area"

--------------------

I think those were it mainly. Can someone help me out? I'm just assuming these are from my ram? Unless they arent! Please help! I'm still having issues!
 
First, download MemTest. Second, download BlueScreenView. Third, run BSV on your computer, it will check the dump files to help determine the cause of your BSOD, if the problem is software related. When you can step away from your computer for several hours, run MT86+, since the recommendation is 4-6 'passes'. By "passes", I mean how many times the test cycles, so to speak.
 

Jakester93

Distinguished
Oct 30, 2012
71
0
18,630
Here is the Crash Dumps, this is just all greek to me, I have no idea what it means though. If someone can help, I would greatly appreciate it. I'm not sure exactly how this program works, but in the "Event Viewer" I sure seem to have a lot more errors/issues/logs. Though i just copied and pasted the crash dump analysis from WhoCrashed.

-----------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Fri 8/28/2015 8:20:07 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082815-7703-01.dmp
This was probably caused by the following module: iccwdt.sys (ICCWDT+0x7838)
Bugcheck code: 0xD1 (0xFFFFF80142C77838, 0x2, 0x8, 0xFFFFF80142C77838)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\iccwdt.sys
product: Intel(R) Watchdog Timer Driver (Intel(R) WDT)
company: Intel Corporation
description: Intel(R) Watchdog Timer Driver (Intel(R) WDT)
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: iccwdt.sys (Intel(R) Watchdog Timer Driver (Intel(R) WDT), Intel Corporation).
Google query: Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Fri 8/28/2015 8:20:07 PM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: iccwdt.sys (ICCWDT+0x7838)
Bugcheck code: 0xD1 (0xFFFFF80142C77838, 0x2, 0x8, 0xFFFFF80142C77838)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\iccwdt.sys
product: Intel(R) Watchdog Timer Driver (Intel(R) WDT)
company: Intel Corporation
description: Intel(R) Watchdog Timer Driver (Intel(R) WDT)
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: iccwdt.sys (Intel(R) Watchdog Timer Driver (Intel(R) WDT), Intel Corporation).
Google query: Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Fri 8/28/2015 6:17:12 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082715-7078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xD1BD2)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800EA4D6BD2, 0xFFFFD00160D4D328, 0xFFFFD00160D4CB40)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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.
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 8/28/2015 4:17:22 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082715-7265-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DD00)
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 that cannot be identified at this time.



On Thu 8/27/2015 10:10:20 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082715-7281-01.dmp
This was probably caused by the following module: iccwdt.sys (ICCWDT+0x7838)
Bugcheck code: 0xD1 (0xFFFFF800FD077838, 0x2, 0x8, 0xFFFFF800FD077838)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\iccwdt.sys
product: Intel(R) Watchdog Timer Driver (Intel(R) WDT)
company: Intel Corporation
description: Intel(R) Watchdog Timer Driver (Intel(R) WDT)
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: iccwdt.sys (Intel(R) Watchdog Timer Driver (Intel(R) WDT), Intel Corporation).
Google query: Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL





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

5 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:

iccwdt.sys (Intel(R) Watchdog Timer Driver (Intel(R) WDT), Intel Corporation)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by 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 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.

------------------
 
Status
Not open for further replies.