Inconsistent but frequent BSOD errors.

[inkyj]

I wonder if someone might be able to help me with BSOD errors that I've been getting for the last 2 months. I've tried pretty much everything I can think of, and I'm having no luck figuring out what problem is.

The crashes are pretty random, constant, and the error codes (dump file attached), are inconsistent. Occasionally the comptuer will just freeze rather than BSOD, but that's not too frequent. I often get numerous crashes right when turning on the computer, but after 3-5 attempts, I can usually get it to fully boot, and stay on long enough to work on. But then it'll BSOD later.

The only thing I've noticed with the BlueScreenView results is that under the "caused by driver" category, I see ntoskrnl.exe more often than anything else. I've googled this, but haven't yet found any solution.

The Bug Check Strings are all over the place... nothing jumps out as being seen too often.


Sofar here is what I've tried.

Thoroughly scanned my computer for possible viruses or malaware - no issues found

Cleaned the dust out of my computer and fans - no improvement

Scanned my HD for bad sectors - no issues found

Installed all relevant windows updates - no improvement

Removed new USB 3.0 PCIe Expansion Card (this was the ony new hardware I added in the last

several months) - removing the card made no improvements

updated my video card driver - no improvement

updated my motherboard drivers - no improvement

ran memory tests - on the 2nd run it found 1 issue, but after that, I let it run the entire night, and it didn't find one more. Not sure if that 1 issue could be the problem, or just a fluke.

I went into MSConfig and disabled all services and startup programs that are not Microsoft. (though some McAfee services always seems to turn back on)

Ran Hot CPU tester, no issues found

Ran Windows Registry repair - many issues found, but there was no improvement when I fixed these issues.

I'm VERY close to wiping the system, but I'm not yet confident it'll help, and I don't want to hassle with that unless I need to.

I'm sure there are more things that I've done, but since this has been going on for over 2 months, I can't remember all of the steps I've taken.


I tried creating a System Health Report to add to this post, but I kept receiving time out errors, and after trying to fix that problem for a couple hours, I gave up.



System Specs

Self BUilt Desktop - built in January 2010, with mostly new components

Windows 7 Ultimate 64bit
AMD Phenom(tm) II X4 955 Processor, 3210 Mhz, 4 Cores
ASUS Crosshair III Formula AM3 AMD 790FX ATX AMD Motherboard
G.SKILL 8GB (4 x 2GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 1280)
Radeon HD 4670 1GB 128-bit DDR3 PCI Express 2.
ATI High Definition Audio Device - built into motherboard
dual displays, dell 19 inch, and Asus 24 inch
resolution - 1280 x 1024 x 60 hertz

Hard Drives
C: Size 811.57 GB
Free Space 590.31 GB

F: Size 104.01 GB
Free Space 37.93 GB

G: Size 481.68 GB
Free Space 202.14 GB

If I've forgotten anything, or if I can provide any additional info, please let me know.
Thanks!!!!

 

[inkyj]

Anyone have ANY thoughts on how to approach fixing this?

 

[panais]

Anyone have ANY thoughts on how to approach fixing this?

Hi inkyj welcome to SF

Uninstall Macfee from your system ,then clean any remaining fragments using the http://download.mcafee.com/products/licensed/cust_support_patches/MCPR.exe

Download and install MSE Virus, Spyware & Malware Protection | Microsoft Security Essentials

Enable windows firewall.

------------------------
Finish with the above steps and post back with any results.

 

[zigzag3143]

I do agree with Panais about removing McAffee.

Most of your crashes point to memory corruption (probably caused by a driver). In addition to Macaffee please run these two tests.


Memory corruption probably caused by a driver. please run these two tests



1-Memtest. Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.

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.



2-Driver verifier

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).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

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 "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 (an estimate on my part).

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.

 

[inkyj]

Thanks for the help! I've uninstalled McAfee, and I've also gone through the Driver Verifier steps. Right now I'm just waiting for another BSOD, as instructed in the verifier steps.

It's actually been running very well today. I've only had one crash since I disabled all of the non microsoft services, and eliminated all of the starup items using MSConfig.

Now that I have taken the driver verifier steps, assuming I do get another crash, what is the next step?

Thanks again for the help!

 

[panais]

Thanks for the help! I've uninstalled McAfee, and I've also gone through the Driver Verifier steps. Right now I'm just waiting for another BSOD, as instructed in the verifier steps.

It's actually been running very well today. I've only had one crash since I disabled all of the non microsoft services, and eliminated all of the starup items using MSConfig.

Now that I have taken the driver verifier steps, assuming I do get another crash, what is the next step?

Thanks again for the help!

For the Driver Verifier steps just wait,work play as usual and if you had/have any new bsod upload the new bsod file.


If the bsod stops,disable Driver Verifier, and if is that the case,macfee propably was the bsod source.

 

[inkyj]

I did have another crash a few minutes ago, but unfortunately the BSOD didn't complete it's dump... it froze in the middle of it, so the crash wasn't reported. Actually, now that I look at the dates in BlueScreenView, I'm only seeing the dump file from one crash since August 1st. But I've had a lot of BSODs since then. Is there a more reliable way to view my dump files than with BlueScreenView?

 

[inkyj]

I got around to running memtest-86 again. The last time, I ran it overnight and only had 1 error. This time I'm getting TONS of errors. Every combination of memory sticks and slots gives me errors. So either I've got multiple bad memory sticks, or multiple bad slots... or something else is wrong entirely.

In the memtest documentation it says that in addition to testing the RAM modules, the program automatically tests the CPU and L1, L2 cache, and the motherboard. Is there any way to tell where the issue is, based on the results memtest gives me?

Thanks!!

 

[panais]

I got around to running memtest-86 again. The last time, I ran it overnight and only had 1 error. This time I'm getting TONS of errors. Every combination of memory sticks and slots gives me errors. So either I've got multiple bad memory sticks, or multiple bad slots... or something else is wrong entirely.

In the memtest documentation it says that in addition to testing the RAM modules, the program automatically tests the CPU and L1, L2 cache, and the motherboard. Is there any way to tell where the issue is, based on the results memtest gives me?

Thanks!!

Dont do a combination,just test one stick at the time,and every time you find a good stick test it with all the slots.

Ram test identify whether it is a bad stick of RAM, a bad motherboard memory slot, or incompatibility between the sticks.

 

[inkyj]

Sorry, I didn't explain that well. When I said that I was trying combinations, i just meant that I was trying different sticks in different slots. But just one at a time.

Every test I ran last night came up with errors. I didn't try every stick in every slot (didn't have enough time), but I tried a bunch, and at times I was literally getting 200,000+ errors. The numbers would have kept climbing, but I stopped it when i saw so many errors.

But today... even when trying the same exact cards, in the same exact slots, I can't get a single error.

I'm thoroughly confused, and have no clue what to do now.

 

[panais]

Sorry, I didn't explain that well. When I said that I was trying combinations, i just meant that I was trying different sticks in different slots. But just one at a time.

Every test I ran last night came up with errors. I didn't try every stick in every slot (didn't have enough time), but I tried a bunch, and at times I was literally getting 200,000+ errors. The numbers would have kept climbing, but I stopped it when i saw so many errors.

But today... even when trying the same exact cards, in the same exact slots, I can't get a single error.

I'm thoroughly confused, and have no clue what to do now.

Update motherboard chipset and bios.

Then ran the MEMTSET

Test one stick at the time,and every time you find a good stick test it with all the slots.

That way you can have a conclusion,about bad ram or bad slot (motherboard).

 

[inkyj]

I had already updated the motherboard chipset and bios. But it didn't help.

And I tested one ram stick at a time, but now none of the sticks are giving me errors. But last time when I was trying one stick at a time, no matter which stick i tried and no matter which slot, I had errors every time. I didn't make any changes at all, but I can't get it to report any errors anymore.

 

[inkyj]

any last suggestons on this? Or do I need to just get a new MOBO and/or ram?
Thanks!