Multiple BSOD of various errors with internet/videos/music

Recently, I have had MANY BSOD consecutively. Recently, I have had about 9 BSOD over about 5 days (although the report lists a break between my BSOD between 2/21 and 3/27 because I was on break for most of this). In the past I have gotten BSOD while playing games, but the recent ones have been while doing mundane tasks such as browsing the internet or watching YouTube videos.

I have used BlueScreenView to try to discover the cause of my problem, but every BSOD seems to have a different error and file associated with it. Many of them are blamed on ntoskrnl.exe, but have different error messages. Some are from different files.

I am running Windows 7 64 bit on a desktop I built about 15 months ago. Since then, I have gotten many error messages, but more recently. I have 8 GB of RAM, GEFORCE GTX 470, AMB Phenom II Black multicore processor, and Gigabyte 890GPA-UD3H Motherboard. I assembled the desktop components and installed all software new onto the computer.

Things I have tried recently: resetting the RAM in different slots, running antivirus (I have AVG free, malwarebytes, and spybot), cleaning the computer fans, uninstalling/DriverSweeping the video card drivers and reinstalling, disabling the motherboard sound card through BIOS so the external sound card I have installed does not interfere, running cmd /chkdsk with fix to try to correct any errors found.

Any help would be appreciated. I have been dealing with BSOD a lot frequently, although it has usually only been about 1 per week in the past. These are extremely frequent recently with multiple per day and it is interfering with my work. Attached are the files requested. I will check this thread multiple times per day so please let me know if you have any other questions or comments!

Thank you!

Two main issues. AVG (blamed in about 6) and a memory exception. Please remove and replace AVG with MSE, and perform these two tests.

I note you have AVG.
AVG can be a contributing cause of BSOD'S .
Please remove and replace with Microsoft Security Essentials AT LEAST TO TEST

Download tools and utilities | AVG Worldwide[/B]

Microsoft Security Essentials - Free Antivirus for Windows





These crashes were caused by memory corruption/exception (cx05) probably a driver.
Please run these two tests to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

RAM - Test with Memtest86+



Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Thank you for the prompt reply.

I am uninstalling AVG now, I have not heard of that as a problem before but that is an easy fix for me to try.

In the past, I used memtest to test my 2 4GB sticks of RAM and had mixed results with it. I let it run several times overnight and found an error with both sticks of RAM in that I could not recreate with either stick in alone. I tested every RAM slot with the individual sticks before resetting both RAM sticks into slots 1+3 out of the 4 on my motherboard.

I just had another BSOD with the same error as before (KMODE_EXCEPTION_NOT_HANDLED 0x0000001e caused by ntoskrnl.exe). Again, this was while listening to music on YouTube. I took my sound card out to see if that would make a difference also.

Will keep you posted on the updates. Any other suggestions please let me know.

Also, what does it mean if it says I have a "problem starting \3\DLCQtime.dll. The specified module could not be found."? I have gotten this error a few times after restarting. Could this be related to removing my sound card recently or is it something different?

GiveMeTaffy said:

Also, what does it mean if it says I have a "problem starting \3\DLCQtime.dll. The specified module could not be found."? I have gotten this error a few times after restarting. Could this be related to removing my sound card recently or is it something different?

See Solved Error Message - Vista Forums for your error. That thread has a solution. You could try the free version (do not start the trial) of malwarebytes to scan for the problem, as well.

zigzag3143 said:

Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen.
Continue to use your system normally, and if you know what causes the crash, do that repeatedly.
The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.
If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

For some reason, I am not getting the crash within the past 3 days with these settings. Is there any danger in keeping these settings on for a few more days to wait for the inevitable crash?

No danger is caused by Verifier. This is one of the reasons it is said to be an iffy proposition. Sometimes, it causes a lot of crashes and makes it annoying for the person running it, and other times it does not cause crashes making it difficult for us to narrow down the cause. It could be some of the changes made before or while running Verifier provided more stability to the system. Time will tell.

Here is the first blue screen I have gotten with since turning on Verifier. I am not sure if this is completely coincidental or if it is related, but it occurred about an hour after reinstalling the drivers for my Dell Printer which I had uninstalled during the previous set of blue screens. I do not want to mislead you though, because I am not sure that this is related--it could have been a coincidence.

Let me know what you think.

Thank you!!

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\GiveMeTaffy\040812-42057-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`03066000 PsLoadedModuleList = 0xfffff800`032aa650
Debug session time: Sun Apr  8 20:03:55.612 2012 (UTC - 6:00)
System Uptime: 4 days 15:07:55.000
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
...............................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {ffffd88007438ba8, 2, 0, fffff8000310b0d5}

Probably caused by : ntkrnlmp.exe ( nt!CcCanIWrite+165 )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: ffffd88007438ba8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8000310b0d5, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003314100
 ffffd88007438ba8 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!CcCanIWrite+165
fffff800`0310b0d5 48394128        cmp     qword ptr [rcx+28h],rax

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff880084f58c0 -- (.trap 0xfffff880084f58c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000100 rbx=0000000000000000 rcx=ffffd88007438b80
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000310b0d5 rsp=fffff880084f5a50 rbp=fffff80003282200
 r8=0000000000000000  r9=fffff800032e37ff r10=00000000000002ed
r11=0000000000000060 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!CcCanIWrite+0x165:
fffff800`0310b0d5 48394128        cmp     qword ptr [rcx+28h],rax ds:ffffd880`07438ba8=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030e22e9 to fffff800030e2d40

STACK_TEXT:  
fffff880`084f5778 fffff800`030e22e9 : 00000000`0000000a ffffd880`07438ba8 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`084f5780 fffff800`030e0f60 : 00000000`00000206 fffff800`03101b63 12100001`dfe0b500 00000000`00001000 : nt!KiBugCheckDispatch+0x69
fffff880`084f58c0 fffff800`0310b0d5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`084f5a50 fffff800`031288f5 : fffffa80`0cd43b60 00000000`00000000 fffff800`03282260 00000000`00000005 : nt!CcCanIWrite+0x165
fffff880`084f5b20 fffff800`03127dc9 : fffff880`000000a2 fffffa80`0cd43b60 00000000`0000005d fffffa80`0b877240 : nt!CcLazyWriteScan+0x7c1
fffff880`084f5c00 fffff800`030ec471 : fffffa80`0745d190 fffff800`033d8701 fffff800`032e38a0 fffff800`00000002 : nt!CcWorkerThread+0x1f9
fffff880`084f5cb0 fffff800`0337cf7a : fffffa80`00000003 fffffa80`0cd43b60 00000000`00000080 fffffa80`069eb040 : nt!ExpWorkerThread+0x111
fffff880`084f5d40 fffff800`030d39c6 : fffff880`02fd5180 fffffa80`0cd43b60 fffffa80`07f68960 fffff880`0125c384 : nt!PspSystemThreadStartup+0x5a
fffff880`084f5d80 00000000`00000000 : fffff880`084f6000 fffff880`084f0000 fffff880`084f59e0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!CcCanIWrite+165
fffff800`0310b0d5 48394128        cmp     qword ptr [rcx+28h],rax

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!CcCanIWrite+165

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ec79dd2

FAILURE_BUCKET_ID:  X64_0xA_VRF_nt!CcCanIWrite+165

BUCKET_ID:  X64_0xA_VRF_nt!CcCanIWrite+165

Followup: MachineOwner
---------

The above crash occurred with Verifier enabled, which is good. Unfortunately, it blames a system file. When Verifier enabled crashes blame system files, it means either Windows has corrupted files or hardware is causing the crashes. The bugcheck itself has a possible cause of hardware, as well, leading to a conclusion that it is likely hardware causing the crashes.

• For now, disable Verifier: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:
  verifier /reset
  -> Restart your computer.
  
  
• Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations.
  
  
• Monitor temperatures during the following tests.
  
  Use the following programs to monitor the temperatures.
  • Real Temp is a good CPU temperature monitor.
  • Speccy - System Information - Free Download will monitor all hardware temperatures.
  • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
  
  
  • Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). The goal is to get a steady temperature, find out if the GPU is overheating, or to see if there are any artifacts present in the test itself: look for strange pixelated patterns on the screen or colors that do not look like they belong. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
    
    
  • Run Hardware - Stress Test With Prime95 to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
    
    
  • Follow the steps for doing a CPU stress test using IntelBurnTest

Just ran the sfc command with no errors found. Here is what I did for reference:

Start, typed "cmd", right click-->run as administrator, typed sfc /scannow, verification complete with the message "Windows Resource Protection did not find any integrity violations".

I ran this twice to make sure the first time wasn't a fluke.

I have not run the temperature stress tests yet, although I have a program called HWMonitor which I used in the past which I could use for this if that is fine.

Let me know what you think about the scan results.