Solved BSOD Anytime anywhere on 64bit machine

[WindowsNinja]

Ok The title pretty much sums it up, The story goes like this, on the 23/6/2012 i got my new PC after tossing out my old AMD machine the specs are as followed:

Motherboard - Intel DH67CL (With latest Bios version)
CPU - Core I5 3550 Quad core processor (Ivy Bridge)
RAM - 12 GB RAM
Graphics - Default HD graphics 2500
Audio - Onboard Realtek hd Audio
HDD - 1TB HDD
OS - Windows 7 Ultimate x64 edition SP1
AV - Avg free 2013 - Was 2012

Now for the first 2 months it absolutly rocked i only ever got one BSOD in the entire 2 months and it was due to something stupid i did, besides that it was a perfect machine, anyway Then something happened to my windows (i suspect it was a damaged file or Virus), I had to remove windows and re-install it again i changed nothing, i put the same software, the same drivers, The same everything But ever since then i will constantly be getting random BSOD's at any given time for no apperant reason, even while running idle, sometimes it would run for 2 or three days non stop, then suddenly I'd decide to play a game and it would halt and display the BSOD.

I know i don't have heating issues, the temparature remains well within the 40's so its not getting hot, I tried installing SP1 hoping it would fix it, but no such luck, I take good care of my OS I regularly use cleaning tools like Ccleaner, Regcure, AVG, I defrag my disks every month and so forth but that doesn't seem to solve the problem, I tried running SFC /Scannow, it told me there were problems but could not fix them.

I thought it may have been due to my reinstalling of windows, but i cleaned drive C: completely before doing so, so why would this happen? In the event viewer Its always either Kernel-power or bugcheck.

Just to mention, I am somewhat of a huge gamer, but i also do a lot of internet and work on there so i really need it.

You probably hear this a lot but can someone help me to enjoy my new PC again? thanks.

http://www.sevenforums.com/attachme...time-anywhere-64bit-machine-sf_27-09-2012.rar

 

[koolkat77]

http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

__________________

1. Click on User CP on the top right of this page
2. Click on Edit System Spec
3. Fill in your computer specs
   :ar: http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html

__________________

 

[WindowsNinja]

Heres the file i got from using the SF diagnostic tool:

http://www.sevenforums.com/attachment.php?attachmentid=233879&stc=1&d=1348751737

 

[Vir Gnarus]

A couple things before we approach this. First, defragging is no longer a recommended operation. In fact, it can prove detrimental to drives as the harsh I/O it does can wick away at your drive's life. Windows nowadays does a pretty good job keeping files nice n neat on the drive, so defragging ends up being superfluous. Second, registry cleaners are not preferred. Even CCleaner can have a tendency to clean off registry keys that are important and can cause more harm than good. Please avoid using them.

Now, as for SFC, the problem may be because you haven't run CHKDSK on the drive first. Run CHKDSK /f first, then follow up with SFC. Also, you have a better chance if you run SFC from the recovery environment on the Windows DVD, not from the environment available on the drive itself.

I don't have appropriate information here because your cleaning software has been cleaning out the dump files that we need. I recommend you turn on Driver Verifier and let your system crash a few more times, then send the dumps (located at C:/Windows/Minidump for minidumps, and if you want, MEMORY.DMP for the kernel dump).

 

[WindowsNinja]

Ok, I'll try what you suggested, If it crashes again I'll upload the Minidump file, Thanks.

 

[WindowsNinja]

It just crashed again, It didn't create anything in the Minidump file, But the Memory.dmp is 850 mb in size which is too big to upload, could you perhaps tell me how you read them? Perhaps i can give it a go instead of waiting for this thing to upload.

 

[Vir Gnarus]

We'll need to look at it ourselves; having to walk you through it would take forever. If you can, compress it (it will greatly shrink) and upload it to a 3rd-party filesharing site. Though before you do, confirm the date of the file and see if it's the same time as your most recent crash.

 

[WindowsNinja]

Ok, I see if i can compress it with Winrar, Anyway if it helps i found this in the minidump file, I don't know why i didn't see it before:

http://www.sevenforums.com/attachment.php?attachmentid=233925&stc=1&d=1348769859

 

[Vir Gnarus]

It looks like it was caused by AVG's IDS driver, but the context is so corrupt I don't think even a kernel dump will help us with it. I've seen AVG's IDS driver cause problems for others in the past, so you may wanna look into turning it off (or switch to another AV solution).

 

[WindowsNinja]

Thank you so much for your help Vir Gnarus, I will try your suggestion when i get home today and see what happens.

 

[WindowsNinja]

After Turning off the AVG IDS service the BSOD has not occured since then, so thanks again for all your help, it seemed to have solved the problem.

 

[WindowsNinja]

Hey again, So After taking the last step the problem still continued for a while, then I decided to try changing my RAM, It turned out the problem was not "Faulty" Ram but rather "Incompatible" Ram, So i upgraded my Ram to Kingston which runs at 1600mhz and the problem stopped all together, So it seems sometimes you could be looking in the wrong place.

Anyway Hope this helps others who may have a similar problem.

Thanks for all your help again.

 

[Vir Gnarus]

That would probably explain the corrupted crashdump (though sometimes berserk drivers can do that too), so thanks for the update.