Frequent BSOD we can not attribute to anything in particular.

[siss400]

Good evening good people out there, who "know stuff"

My computer has been terribly compromised in the past month or so by frequent BSOD which occur in different times even when nothing is really running on the machine.

Trying to isolate possible problems we could think of, we run every test we could think in regards to malware, disk surface tests and mem test on the ram, even though none of our crash reports even remotely indicated memory failure.

We thought it might be related somehow to the graphics card, or the flash players, as several occured when internet radio was playing in the background. Yet it also occured when nothing of the kind was running. Go figure... :shock:

Please, any ideas? We have been trying to resolve it for weeks and we are at a dead end right now, no joke.

Thank you in advance.

 

[Golden]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff901c07dd220, 0, fffff8000328beb0, 5}


Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!HMFreeObject+105 )

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

Run a minimum of 8 consecutive passes, preferably overnight, or until errors occur using MemTest86+.

Reference:
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

 

[siss400]

Thanks I'll start right now and see what I might come up with tomorrow then!

PS - before reading your reply, I tried to run the driver verification tool, the thing resulted in a HUGE memory.dmp file that makes no sense to me

https://onedrive.live.com/redir?resid=8d3f436a45192b45!126&authkey=!APJUkELvmCuxVPI&ithint=file,DMP

Does this make any sense AT ALL?

 

[siss400]

9 passes and 14 hours later memtest showed nothing.

 

[Boozad]

Hi there, Golden has asked me to take a look at your dumps as he's pretty busy right now. If you bear with me I'll be back to help you out as much as I can this evening when I've finished work.

First off please check to see if you're set to record Small Memory Dumps:

1. Open Advanced System Settings
2. Click on Settings in Startup & Recovery
3. Make sure both boxes indicated below are checked
4. In the dropdown box ensure you're set to record Small Memory Dumps

 

[siss400]

OK here's the thing - I HOPE I resolved it now although I still have some reservations that was all there was to it.

I tried in my despair to run the driver verifier to see whether there was a third party driver causing all of this and so I stressed the thing to the bitter ends of it's abilities with all the non-microsoft drivers selected to be verified. It took a short 15" to crash and come up with the "nvlddmkm.sys" red flag and a BSOD reading error id D5. So I updated the drivers of my graphics card afresh (it was less than a week that I have done it anyway) and reverified and same thing happened. In a final attempt to fix it before smashing it down with the mighty hammer of Thor I went to the system32 folder and expanded manually the driver, the latest one (that was released on April 30 mind you, a month after I started having those issues!) and replaced the one that was already in the system, renaming it .old just in case. Well, to cut a long story short, my PC seems pretty stable ever since!!!

I can not believe that NVIDIA cards can cause or trigger such a sequel of malfunctions. I've been using them for ages and never had any issues before. And whenever I had, the driver update in the normal manner one performs it very now and then always fixed any discrepancies. This time...Go figure!

Anyway, thank you very much for trying to help, if what I did proves not to be the solution to my problems I shall return and request some insight again, if that's OK.

 

[Boozad]

Let us know, we'll be here.

 

[siss400]

A minute ago it just froze and I had to restart manually (button) then it got a blue screen seconds after rebooting and here's the minidump

https://onedrive.live.com/redir?resid=8D3F436A45192B45!127&authkey=!AN4tYsAuQ_fVI9g&ithint=file,dmp

Any ideas?:shock:

 

[Boozad]

Can you run the tool you did in the first post and upload the logs directly to this site please.

 

[siss400]

Sorry I thought I did the same thing

 

[Boozad]

Your nVidia driver has been flagged, try downloading the previous version and follow http://www.sevenforums.com/tutorials/327414-nvidia-drivers-avoid-problems.html for the cleanest possible install.

fffff880`0b354370  fffff880`059c6f01Unable to load image nvlddmkm.sys, Win32 error 0n2
[COLOR=Red]*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys[/COLOR]
 nvlddmkm+0xccf01

Are you running a RAID setup? Intel Rapid Storage is causing problems.

fffff880`0b353038  fffff880`0105e832
[COLOR=Red]*** WARNING: Unable to verify timestamp for iaStorA.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys[/COLOR]
 iaStorA+0x2f832

fffff880`0b352db8  fffff880`019f0a46Unable to load image iaStorF.sys, Win32 error 0n2
[COLOR=Red]*** WARNING: Unable to verify timestamp for iaStorF.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStorF.sys[/COLOR]
 iaStorF+0x1a46