Several BSODs since 9/3/2013 - Memtest and Dell diagnostics both pass.

[netman74501]

I have a Dell Inspiron 1764 with Windows 7 Home Premium Service Pack 1 (64-bit, 4GB RAM) that is experiencing apparently random BSODs occurring since 9/3/2013. I have reseated the RAM and performed four passes of memtest plus the built-in diagnostics from Dell for BSODs. Everything passes. All Windows Updates have been performed. Checkdisk has been performed also.

Avast! is mentioned in the mini-dump from 9/3/2013 which was bug check 0xc4 (at least according to BlueScreenView). Avast! had a program update and that has been performed since that specific BSOD occurred. I thought about removing Avast! altogether but, nothing seems to point to Avast! anymore (not in BlueScreenView or any other diagnostic tool I've tried) so I have not yet done so.

I have attached the output from SF Diagnostic Tool in hopes that someone can help me solve these errors. Thanks in advance!

 

[koolkat77]

Welcome to the forum.

It seems that Avast! is causing problems for you. Please uninstall it and use MSE. Microsoft Security Essentials & the Free version of Malwarebytes, update and make full scans separately:

• Uninstallers (removal tools) for common antivirus software - ESET Knowledgebase
• Help protect your PC with Microsoft Security Essentials
• Malwarebytes Free

   Note

:info: Do not start the trial version of MalwareBytes

You may also take a look at:

• Good & Free System Security Combination

------------------------
Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:

• Click on the rb:
• Type CMD on Search
• Left click and Run as Administrator
• Type SFC /scannow - read here

Run Disk Check on your Hard Drive for file system errors and bad sectors on it - read here
------------------------
Make scans with these tools -

• TDSSKiller Rootkit Removal Utility Free Download | Kaspersky Lab US
• Online Virus Scanner Eset

------------------------
Reduce the start-up items, Antivirus software is basically whats required.

• Remove Startup Programs in Windows 7
• Clean Startup in Windows 7

Drivers:

The drivers below aren't updated. Please update them to their latest version. If no updates are available then uninstall the driver and its software completely.

MRESP50a64.SYS Sat Nov 19 14:14:28 2005 (437EDEE4)
PCAUSA Rawether for Windows
Driver Reference Table - MRESP50a64.SYS

CtClsFlt.sys Mon Jun 15 11:06:41 2009 (4A35D6E1)
Creative Camera Class Upper Filter Driver
Driver Reference Table - CtClsFlt.sys

PxHlpa64.sys Wed Jun 24 05:16:35 2009 (4A416253)
Sonic CD/DVD driver (used by many different CD/DVD programs)
Driver Reference Table - PxHlpa64.sys

BCM42RLY.sys Wed Jul 8 06:34:55 2009 (4A53E9AF)
Broadcom iLine10(tm) PCI Network Adapter
Driver Reference Table - BCM42RLY.sys

bcmwl664.sys Wed Jul 8 06:45:04 2009 (4A53EC10)
Broadcom 802.11g Network Adapter - Dell Wireless 1390 WLAN Mini-Card
Driver Reference Table - bcmwl664.sys
------------------------
To perform a clean install of a driver, follow this tutorial:

• How to Clean Left Over Driver Files with Driver Sweeper

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

   Information

Download

and install Revo Uninstaller.

• Opt for "Advanced Mode" and uninstall the software (also delete the leftover registry entries).

Let us know the results.

BSOD BUGCHECK SUMMARY

Debug session time: Sun Sep 22 06:09:21.524 2013 (UTC + 6:00)
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
System Uptime: 0 days 0:34:33.616
*** WARNING: Unable to verify timestamp for aswMonFlt.sys
*** ERROR: Module load completed but symbols could not be loaded for aswMonFlt.sys
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+a53 )
BugCheck 19, {3, fffffa8003add9e0, fffffa8003add9c0, fffffa8003add9c0}
BugCheck Info: BAD_POOL_HEADER (19)
Bugcheck code 00000019
Arguments: 
Arg1: 0000000000000003, the pool freelist is corrupt.
Arg2: fffffa8003add9e0, the pool entry being checked.
Arg3: fffffa8003add9c0, the read back flink freelist value (should be the same as 2).
Arg4: fffffa8003add9c0, the read back blink freelist value (should be the same as 2).
BUGCHECK_STR:  0x19_3
PROCESS_NAME:  iexplore.exe
FAILURE_BUCKET_ID:  X64_0x19_3_nt!ExDeferredFreePool+a53
MaxSpeed:     2130
CurrentSpeed: 2128
BiosVersion = A13
BiosReleaseDate = 03/29/2011
SystemManufacturer = Dell Inc.
SystemProductName = Inspiron 1764
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Wed Sep 18 05:56:31.137 2013 (UTC + 6:00)
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
System Uptime: 0 days 0:01:02.510
Probably caused by : ntkrnlmp.exe ( nt!KiTimerExpiration+d9 )
BugCheck A, {fffff800c3e29f88, 2, 0, fffff80002c924f9}
BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
Bugcheck code 0000000A
Arguments: 
Arg1: fffff800c3e29f88, 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: fffff80002c924f9, address which referenced memory
BUGCHECK_STR:  0xA
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nt!KiTimerExpiration+d9
MaxSpeed:     2130
CurrentSpeed: 2128
BiosVersion = A13
BiosReleaseDate = 03/29/2011
SystemManufacturer = Dell Inc.
SystemProductName = Inspiron 1764
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Sat Sep  7 21:52:02.452 2013 (UTC + 6:00)
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Built by: 7601.18205.amd64fre.win7sp1_gdr.130708-1532
System Uptime: 0 days 0:38:21.545
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Probably caused by : ntoskrnl.exe ( nt+4ddf5 )
BugCheck 50, {fffff100108b1f61, 1, fffff80002ca6df5, 7}
BugCheck Info: PAGE_FAULT_IN_NONPAGED_AREA (50)
Bugcheck code 00000050
Arguments: 
Arg1: fffff100108b1f61, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff80002ca6df5, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000007, (reserved)
BUGCHECK_STR:  0x50
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
MaxSpeed:     2130
CurrentSpeed: 2128
BiosVersion = A13
BiosReleaseDate = 03/29/2011
SystemManufacturer = Dell Inc.
SystemProductName = Inspiron 1764
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Thu Sep  5 10:09:04.014 2013 (UTC + 6:00)
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Built by: 7601.18205.amd64fre.win7sp1_gdr.130708-1532
System Uptime: 0 days 2:27:24.107
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Probably caused by : ntoskrnl.exe ( nt+8759e )
BugCheck 3B, {c0000005, fffff80002cd459e, fffff880073629a0, 0}
BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
Bugcheck code 0000003B
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002cd459e, Address of the instruction which caused the bugcheck
Arg3: fffff880073629a0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
MaxSpeed:     2130
CurrentSpeed: 2128
BiosVersion = A13
BiosReleaseDate = 03/29/2011
SystemManufacturer = Dell Inc.
SystemProductName = Inspiron 1764
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Debug session time: Wed Sep  4 09:20:26.624 2013 (UTC + 6:00)
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Built by: 7601.18205.amd64fre.win7sp1_gdr.130708-1532
System Uptime: 0 days 2:32:50.091
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Probably caused by : ntoskrnl.exe ( nt+75b80 )
BugCheck C4, {91, 0, fffffa8003b69a20, 0}
BugCheck Info: DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Bugcheck code 000000c4
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
Arguments: 
Arg1: 0000000000000091, A driver switched stacks using a method that is not supported by
	the operating system. The only supported way to extend a kernel
	mode stack is by using KeExpandKernelStackAndCallout.
Arg2: 0000000000000000
Arg3: fffffa8003b69a20
Arg4: 0000000000000000
BUGCHECK_STR:  0xc4_91
MaxSpeed:     2130
CurrentSpeed: 2128
BiosVersion = A13
BiosReleaseDate = 03/29/2011
SystemManufacturer = Dell Inc.
SystemProductName = Inspiron 1764
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

 

[netman74501]

I have uninstalled Avast! and installed MSE along with Malwarebytes. I performed a full scan with each and they both came up clean.

SFC says it did not find any integrity violations.

TDSSKiller is clean.

Startup items are already reduced.

I'm not sure what uses the driver MRESP50a64.sys but, I believe it to be the AT&T troubleshooting software so I have uninstalled it. I am also not sure what uses the driver PxHlpa64.sys and therefore do not know how to update it. All other drivers listed are already at their latest as far as I can tell.

Let's hope it is simply Avast! that is the culprit and by uninstalling it that the issue is resolved. I will let you know if I get another stop error within the next couple of weeks.

 

[koolkat77]

OKay, thanks for the update
Good luck

 

[netman74501]

Okay... So, now the computer has blue screened once and shutdown (not reboot) several times. Since posting, one of the blue screens (APC_INDEX_MISMATCH) happened when I tried to run driver verifier after I initially started this thread so I think we can ignore that one but, the latest blue screen (BAD_POOL_CALLER) is new. It happened on the third.

I have no idea why the computer has started shutting down instead of blue screening if something is wrong. The only thing being done on this computer is facebook and some word processing. Nothing intensive. To me, it sounds like it is overheating but, I have checked the fan and it is running and visually looks clean. It seems to have a healthy airflow too. One time, instead of shutting down, the screen simply froze. The computer had to be hard reset. Any ideas as to what this new problem could be?

I've attached new logs.

 

[koolkat77]

No new dumps were collected.

First, we want to make sure the computer is saving your dump files. Go to Control Panel -> System -> Advanced System Settings -> Startup and Recovery [Settings] Make sure that "Write Debugging Information" is set to Small Memory Dump (256kb) if it is not already.

• Create a Dump File when you get a BSOD

Next, make sure that the folder C:\Windows\Minidump exists. If not, create it (allow permission if asked). Make sure any dumps you want to analyze, whether yours or others', are in this folder. You can ZIP/RAR the files and send them to someone else to analyze as well.

The driver detected a controller error on \Device\Harddisk1\DR4.

Upload a screenshot using:

• CrystalDiskInfo:tip: For how to upload a screenshot or file, read here

Test your Hard Drive(s) by running:

• Hard Drive Diagnostic Procedure

Monitor hardware temperature with system monitoring software like Speccy or HWMonitor. Upload a screen shot of the Summary tab as well:

• Piriform - Speccy
• CPUID - HWMonitor

• :info: For how to upload a screenshot or file, read here

------------------------
Test and Diagnose RAM Issues with Memtest86+:

• RAM - Test with Memtest86+

   Tip

• :info: Pay close attention to Part 3 of the tutorial "If you have errors"
• :tip: Test the RAM with Memtest86+ for at least 7-10 passes. It may take up to 22 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold.

 

[netman74501]

I've attached a zip file containing screenshots of CrystalDiskInfo and Speccy and the single dump file I was referring to as being new. The computer is still set to save dumps, it just isn't blue screening when it freezes or shuts down for some reason. With the screen freezing and it simply shutting down, this sounds more like an overheating issue to me but, the computer really didn't feel that hot.

I already ran memtest86+ for several more passes after my initial post but, I will run it again. Total, it has already run for 8 passes.

The hard drive was tested when I ran the Dell Diagnostics (as well as several other things, including memory). It did a short test and a long test. If my memory serves me correctly, the long test was a surface test. Do I really need to run another test on the drive?

Also, I did a scandisk before posting, I just failed to mention it. That came back with some unused indexes being cleaned up but, was otherwise fine.

 

[koolkat77]

Enable Driver Verifier to see if it catches any misbehaving driver:

• :tip: Driver Verifier - Enable and Disable
• :info: Using Driver Verifier to identify issues with Drivers

 

[netman74501]

Unfortunately Driver Verifier doesn't find anything. I ran memtest86+ for 36 hours this time. It still finds nothing.

I also downloaded and ran OCCT on the GPU (screenshot attached). I did this because I was suspecting the GPU to be a possible cause since the screen simply froze the one time. However, the computer didn't exhibit any problems while testing.

So, to recap:

I have ran Windows Update, Driver Verifier, SFC, checkdisk, memtest86+, OCCT, and everything in Dell Diagnostics (which ran a number of tests that included hard drive, CPU, CPU cache, battery, fans, sensors, etc.) I have also replaced Avast! with MSE and ran multiple virus and malware scans, utilizing both online virus scans and the anti-virus on the machine. I have also ran Malwarebytes. Lastly, as far as I can tell, all drivers are up-to-date.

That's a lot of stuff. Any other suggestions for finding the cause of the random blue screens or shutdowns?

 

[essenbe]

Netman, if you would would you fill out your system specs as completely as possible. At the bottom left of your last post click on my system soecs, there you will also see a link update system specs, click on that and fill out the info as completely as possible then be sure to scroll to the bottom of the page and click save. You can click on system specs on this post and see mine for an idea of what we would like.

This tutorial will tell you how to upload screenshots in Seven Forums http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

Please download Core temp to keep an eye on your CPU temp.
also download and install CPUz if you don't already have it. Pleas post screenshots of the main tab, memory and SPD tabs. Also, if you think you are having graphics problems, download Gpuz.

Is there anything specific you are usually doing when the computer freezes or blue screens? Is there any software that you use that will usually make it freeze?

Also download and run the Toshiba hard drive diagnstic tool from Tacktec. It will be Toshiba/fujitsu. The DOS version is best as the hard drive is not in use.

 

[netman74501]

There is no specific program or event when the bluscreen/freeze/shutdown occurs.The bluescreens and shutdowns appear to be random. The freezing only happened once. One time Microsoft Word was the only thing open, the other facebook, others just general browsing.

I tried running the Toshiba hard drive tool in Windows even though their site doesn't list Windows 7 as being compatible. I could see the drive in the list but, not select it. So, I tried the dos version. The dos version couldn't detect the drive at all. I am wondering why I even need to run this tool as it appears to do the same exact thing as what the Dell Diagnostics does. I feel like I am taxing the hard drive when I run test after test on it.

I have attached the requested screenshots.

 

[essenbe]

Netman, I honestly can't say for sure, but I really doubt checking a hard drive for errors damages it. The Crystal disk info shot, does not check it. It simply reads the AMART readings given off by the drive itself. Dell uses many diffferent brands of drives and has to use a generic hard drive test. The manufacturer's test is much better. They made the drive, so should know the specifics of what to look for. One of your dumps pointed to the hard drive specifically. So, that is why I was looking at the drive. I hope that explains it a little better.

The screenshots you posted look OK. I hope you are monitoring your CPU temps. Also, please use this tutorial and fill out your system specs. It will help us to help you. http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html

All of the tests you've run so far have found no problems. Either the core temp, for CPU temps, or cupid HW monitor Koolkat linked to will show your CPU temps as well as the GPU temps. Please keep an eye on those and let us know what they are reading. How often do you have the BSODs? Have you ever used Linux before, or do you have an extra hard drive? I ask because I'd like to seperate the OS from the hardware as much as I can. You can use a live linux distro that runs from ram and the OS on your hard drive is not involved at all, but all of your hardware is. But, Linux is a lot different than Windows and many windows users find it difficult to use.

 

[netman74501]

I am a computer technician so I understand what you are saying. I didn't really mean actual damage, it's just that I have always had the belief that it is needless wear and tear (I don't know this to be fact, just have that opinion for some reason and it is the reason I asked if it was necessary). Kinda the same feeling about defragmenting over and over and over.

I myself run Ubuntu as my main OS but, the machine I have been posting about is a friend's. I have had the machine for over a week and have run test after test on the hardware hoping to find something. When I couldn't find the problem, I turned to the forums for help with the BSODs and the new problem of shutdowns.

A while ago, I replaced the hard drive for her. So, I am now wondering how old the dump was where you saw the reference for the hard drive. (I don't deal with BSODs much. When I was in school, I was taught to simply re-install Windows if you couldn't quickly fix it.)

I have had CoreTemp on the machine since I got it and the highest CPU temp I have seen is when I was stressing the GPU with OCCT. It was at 81 Celsius. During that time, the machine was hot to the touch but, never shutdown or became unstable. I haven't really paid attention to GPU temps as I don't really suspect it. I only tested it because it is the one thing Dell Diagnostics can't test and it was the only thing I could think of that I hadn't tested.

In all my testing, I haven't had a single issue. However, this will be my third time to give the machine back to her saying I can't find anything wrong or reproduce the bluescreens/shutdowns. She claims the only thing she is doing is word processing and internet browsing. No peripherals or extra hardware attached. She called me one night saying it had just shutdown 6 times in a row. By shutdown, I mean it completely shut off without warning and did not boot back up. Almost as if it was overheating but, she says it wasn't hot to the touch.

I am completely out of ideas as to what to do aside from a re-install of Windows. I'd rather avoid that for this machine.

 

[essenbe]

I'm sure you realize my thinkng with Linux. Running a live SO would seperate the hardware from the OS as much as is possible. If it runs without shutdown on the live ISO, it should indicate something in the windows installation or the hard drive itself. If it crashes during use, then it indicates a hardware problem. Failing that, do you have a spare hard drive you could do a clean install on?. I would try a minimal install, only what was necessary for it to be functional. See if you get a shutdown then. I'm really not familar with the Occult test. I use Furmark or run benchmarks with Mark 3D 11 or Ungine Heaven. The occult test screenshot you showed looked strange to me. Everything was jumping up and down. But, that may be the way the test is structured. If you think video, GPUZ is excellent. Create a folder on your desktop and name it whatever you want. Open GPUz and click the sensor tab. At the bottom of the page is a checkbox named log to file. As soon as you click that a dialogue box will appear. Navigate to the new folder you just created, then run a graphics intensive program or benchmark and hope it BSODs. When finished, uncheck the box in GPUz and open the folder you selected. Almost everything about the graphics will be logged there in about 1 second intervals. If it does crash, you will be able to see exactly what happened.

As I'm sure you know, you can spend weeks running down the problems and then fixing them if it is a problem with Windows or drivers. It can be much quicker to do a clean install. That's why I was asking about another hard drive. If it runs fine, you are pretty much assured it is something in the windows installation or the drive itself. It would be a much quicker test than 'chasing rabbits'. I do a lot of testing and other things on my computer and mess it up quite often. If something happens that I can't easily fix, I will do a clean install very fast. As a matter of course I usually do a clean install every couple of monthe for that reason. But, a spare hard drive with a minimal clean install would let you know a lot.

One thing that hasn't been mentioned is the power supply. That could cause exactly what I understand is happening.

 

[netman74501]

I see your reasoning but, the machine has never had a problem while I have had it in my possession so I am doubting Linux will fail. I guess I could go ahead and look at dmesg, syslog and others though. Maybe they would contain a clue as to what it could be.

As I'm sure you know, you can spend weeks running down the problems and then fixing them if it is a problem with Windows or drivers.

This is exactly the reason I was always taught to re-install and move on if it couldn't be fixed quickly. I was just trying to avoid that.

 

[essenbe]

netman, please keep us informed of your progress and what you have elected to do. First and foremost, I think we need to seperate a software or a hardware problem. Just keep us advised, please.

 

[netman74501]

I've explained the situation to her and told her that if it happened again, we would just re-install Windows as I was taught to do in the first place. I was just hoping to avoid that this time but, this has become too time consuming.

I don't believe it to be a hardware problem at this point. As I stated earlier, it hasn't had a single hiccup while in my possession. Plus all tests have passed.

 

[essenbe]

Well, maybe you could find a restore point to before the problem started and try that and there is also a repair install (http://www.sevenforums.com/tutorials/3413-repair-install.html). Some people have has success with it, but I never had. I only assume it comes down to what is wrong with it. But, it could be worth a try.

 

[netman74501]

I thought of System Restore. Unfortunately, it was not enabled. I also thought about a repair install but, things seem to get messed up more when doing that. Might as well just re-install.

Right now, I am waiting to see if she is going to have any more problems. If so, I'll just re-install Windows as I am tired of dealing with it.

Thank you all for your help.

 

[essenbe]

Hope everything works out for you. If you need any assistance, we will be right here. Just curious why she has issues and you don't with that computer.