Seemingly random BSODs, different reasons multiple occurences per day

[tizbad2k]

Hi All,

I commonly have BSOD errors, generally with a different error code each time. This is a Win7 install on a fairly old machine. XP used to, and still does, run with no errors (ever). Both operating systems are on the same SSD. I primarily use 7 as the computer is used as an HTPC. I thought the problem might be related to previous overclocking and poor quality ram (XP was overclocked for about 3 years), XP was never able to address all the ram Win7 is 64 bit and can address all the ram, so I thought it may have something to do with the ram. However the error seems to be different every time. Recently I went back into the bios and got rid of "Turbo" for RAm and put the CPU core voltage back to auto (was at a slightly elevated level), I thought this helped but the BSODs returned within about 3 days.

Hopefully the files that I have attached will be helpful.

 

[essenbe]

Hello tizbad2k, I will try to help you with this problem. For Some reason the files you uploaded did not all come through. Please re run the BSOD posting instructions (http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html) and use #2 this time and click the 'Grab All' button and give it long enough to do it's collection. Sometimes it can take a few minutes.

You are correct that all the dumps are a different Stop code. One thing I noticed was in all the dumps, there were references to the file system and I/O procedures. That leads me to believe there may be problems with your hard drives. Please run check disk http://www.sevenforums.com/tutorials/433-disk-check.html on your mechanical drives and make sure your OCZ SSD's firmware is up to date.

Also please open an elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

Several reasons were given in your dump files. I only had time to look at the last 5 or 6 right now,

Use !analyze -v to get detailed debugging information.
BugCheck 19, {3, fffff8a01b1ef010, fffff8a01b1ef010, fffff8a01047fbe0}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+cbb )
Followup: Pool_corruption

Use !analyze -v to get detailed debugging information.
BugCheck 19, {20, fffff8a00e8831a0, fffff8a00e883360, 51c0202}
GetPointerFromAddress: unable to read from fffff800030c7100
GetUlongFromAddress: unable to read from fffff800030c71c0
Probably caused by : [COLOR=red]fltmgr.sys ( fltmgr!DoFreeContextMemory[/COLOR]+6b )

Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff8a014967b60, 1, fffff880012ae9ab, 0}
Could not read faulting driver name
Probably caused by : [COLOR=red]Ntfs.sys ( Ntfs!NtfsFullDeleteLcb+bb[/COLOR] )
Followup: MachineOwner

These last 2 relate directly to your hard drive or the file system, and the first one can. However, the one that is concerning me most is the next one. It can cause any type of error at any time, and you having a different error each time is indicative of this error. Until we rule out the next error, none of the information in the dump files id reliable.

Use !analyze -v to get detailed debugging information.
BugCheck 4E, {2, 2e24e, 127fff, 1}
Probably caused by : [COLOR=red]memory_corruption[/COLOR] ( nt!MiUnlinkPageFromLockedList+8d )
Followup: MachineOwner

In order to rule this out you will need to test it, and it will take a lot of time.

Please Run Memtest86+

   Information

Please download from this site only http://www.memtest.org/ in the middle of the page are the Download links, you can download the ISO.zip or the Auto USB Flash Drive installer.zip

Extract the Zip file. If you chose the ISO image, burn it to a CD using Windows Disk Image Burner or any Image burner you may have. If you downloaded the Auto USB installer, extract it, insert your USB 2.0 Flash Drive and take note of the drive letter. Run the installer, select the Flash Drive Letter, check the format box and press next. It will install memtest86+ to a flash drive. You can use either V4.20 or V5.01. Boot from your selected media. If you use V5.01 it will tell you to press certain buttons at the start, please press no buttons. The test will begin on it's own and continue to run until you stop it. It needs to run for a minimum of 8 complete passes all at the same time or until you receive an error. If you receive an error, stop the test. Even 1 error is a fail. Each pass tests a different part of the ram and each of the 10 tests in each pass tests something different. It takes a minimum of 8 passes to completely test the ram, more passes are better. It is quite a long test and will take several hours depending on how much ram you have. Due to the time length it is best to run overnight. If you have any questions, please do not hesitate to ask​

 

[tizbad2k]

Thank you so much for your response. I changed the setting so that I will get a kernel dump next time. Or if you like I can do a complete dump. For now the files are minidump files. I have attached the set of files gotten using method 2.

The results of sfc /scannow were: "Windows Resource Protection did not find any integrity violations."I will run memtest and diskcheck now and will post about the results as they come in.

Thanks again.

 

[tizbad2k]

Sorry I may have been too hasty in uploading that file. Attached here is the complete file.

 

[essenbe]

You need to set it to Small Memory Dump, not Kernel Dump.

 

[essenbe]

You seem to be getting a lot of errors from ehRecvr.exe, which is the module for watching TV in Media center. Do you have that set up to watch TV and a tuner card?

You also seem to have more programs than necessary running at startup. You can type msconfig in a run box (hold down the hey with the Windows flag and press R ) go to the startup tab and deselect everything you do not want running at startup. It will use less resources and give you a quicker startup. The programs you de select will still work just fine, they just won't run at startup but will run when you need them to. I have only Windows Sidebar and my Antivirus run at startup, nothing else.

 

[tizbad2k]

You need to set it to Small Memory Dump, not Kernel Dump.

Thank, I'll double check when I get back home. Currently I believe that the dump files are 256k so they may indeed be mini dump files.

 

[tizbad2k]

You seem to be getting a lot of errors from ehRecvr.exe, which is the module for watching TV in Media center. Do you have that set up to watch TV and a tuner card?

You also seem to have more programs than necessary running at startup. You can type msconfig in a run box (hold down the hey with the Windows flag and press R ) go to the startup tab and deselect everything you do not want running at startup. It will use less resources and give you a quicker startup. The programs you de select will still work just fine, they just won't run at startup but will run when you need them to. I have only Windows Sidebar and my Antivirus run at startup, nothing else.

Thank you, I'll trim down the startup settings.

I do indeed use a tuner card with wmc. Which often crashes,but not necessarily more than anything else.

 

[essenbe]

The last date of errors in your msinfo file was 12/11. on that date there were about 30-35 errors listing ehRecvr.exe. I understand wanting to watch TV on the computer and have done so myself. But, the error codes say there is a problem with hardware, software or maybe the way it is set up. It could even be bad codex, possibly.

 

[tizbad2k]

I see. The computer is the only piece of HW in the house capable of watching TV and it is primarily used for that purpose. Do you think that I should look into newer drivers for the tuner card? As far as software I can only think of looking for updates to WMC, otherwise nothing else comes to mind.

I am still waiting on the results of the memtest.

 

[essenbe]

Yes, I think I would see if I could find updated drivers for all of thee hardware you use for watching TV, especially the tuner.

 

[tizbad2k]

I had to stop memtest because it was taking too long. I will run it again tonight and then check it tomorrow evening. It had gotten through 5 passes with 0 errors.

I will run chkdsk now.

I was able update the firmware for the TV tuner.
I am running windows update, but the only relevant update may be the graphics card driver.

BTW I noticed that in your first post you said I have an OCZ SSD. I actually have a Crucial SSD, I used to have an OCZ SSD on which I had XP32, and then I got a larger Crucial SSD onto which I imaged the XP32 and Win7_64 (from a mechanical drive), just FYI not sure if it is relevant.

 

[essenbe]

OK, I just looked in your system specs which states both an OCZ and a Crucial. Make sure both are updated. Also, when you run memtest, you have to start over and run the full 8i passes all at the same time. Most people run it at night and let it run overnight.

I recommend running all of the important and recommended and important updates except the Graphics driver. If you ran the graphics driver, just try it and see how it goes. The majority of the rest of the updates are to make the computer safer and more stable.

 

[tizbad2k]

Sorry, could you please tell me where you see an OCZ drive? I dont have one in my case. I only have a crucial and I just checked System Information Components->Storage->Disks. I wonder if the computer thinks it has an another SSD in it.

There is no update for the SSD.

Just finished all the important updates in windows update.

The plan is to run memtest tonight through at least 8 passes.

 

[essenbe]

Your system specs are in the bottom left corner labeled 'My System Specs' That should always be kept current so we will know what hardware we are dealing with. If you will click that and look at Hard drives, the first entry is an OCZ agility 3.

 

[tizbad2k]

Your system specs are in the bottom left corner labeled 'My System Specs' That should always be kept current so we will know what hardware we are dealing with. If you will click that and look at Hard drives, the first entry is an OCZ agility 3.

My mistake, thanks for pointing it out. I believe it is now correct.

FYI chkdsk found some problems with file system errors on some of my storage drives but no errors with bad sectors yet.

 

[essenbe]

Did ckeck disk correct the errors? No problem about the system specs, I'm just glad they are current now.

 

[tizbad2k]

It was able to fix the errors that it found. I have run it in about half of my partitions so far., but not for bad sectors yet. I stopped it for now so that I could run memtest overnight. FYI I had a failing drive a while ago and I ran seatools. All drives but that one drive passed, this was about 2 months ago.

 

[essenbe]

Ok, let's get memtest86+ run. I hope you downloaded it from the link I gave in the instructions. However, other than the memory corruption, all of the other errors blamed in your crash dumps were related to your hard drive and file system. Also, with memtest, it needs to run for a minimum of 8 passes. It is not the same test 8 times. Every test on every pass checks something different. It takes 8 passes all at once to completely check the ram one time. If you start it again, the tests start over.

 

[tizbad2k]

memtest86+ went through 11 passes with 0 errors. I am continuing chkdsk on my remaining partitions.