Rare bsods with different error messages

[techadv]

Hi! I have Win10 most time stable, but rare (1 times per week approx) i have a bsods each time with varios error codes and messages. I have check my memory and there is no errors.
I have attached last time bsod minidump and ask help from community to detect a reason,

https://drive.google.com/open?id=0B5vJtmefDcIgQk03a01tZG85dnc

Thanks.

 

[techgeek]

First off, you should provide system specs. Next off, stipulate whether you are overclocking or not. These are important factors when considering stability.

 

[techadv]

Thanks for reply!
My specs are:
MB: Asus P7p55D PRO (s1156)
CPU: Xeon x3440@3.8Ghz oc
Memory: 8Gb DDR3 Kingston value ram
Video: HIS radeon 7950
SSD (system): corsair 60 GB
SSD (second drive) adata 120 GB
HDD: 1tb western digital
Audio: Asus Xonar DS pci card

I tried to reset bios defaults but it bsods sometimes anyway. So at current moment i have an overclock, it don't change bsods frequence for me.

 

[techgeek]

Are you running any ASUS monitoring software for you motherboard (ASUS Ai Suite)?

 

[techadv]

Are you running any ASUS monitoring software for you motherboard (ASUS Ai Suite)?

No, only asus xonar ds driver panel

 

[techgeek]

I had a similar issue with my Maximus VI Hero and it turned out it was a driver that was part of AI Suite III. It was a very infrequent crash, not always the same BSOD either. When I finally got fed up enough, I tried Driver Verifier and found that AsIO.sys was at fault. When I removed AI Suite, my BSOD's went away.

It's possible that your issue is related to a bad driver, especially if they are rare. I would think if you had a hardware issue that it would be more frequent. If you are interested in giving Driver Verifier a try, here is the link that I used to set it up:

Driver Verifier

Basically as the link explains, it stresses your drivers. If there is a sketchy driver, it will cause it to BSOD. Then you can usually find the faulty driver named in the dump file. Often under normal conditions, the dump file doesn't single out the faulty driver, but Driver Verifier is very good at causing a BSOD so that it can isolate a driver in the dump.

 

[techadv]

I run driver verifier for a few days, no bsods. Another guy from my job says after see dump file that probably it is SSD

 

[techgeek]

I personally haven't had any storage related BSOD's, I've had hitching caused by failing storage, but no BSOD's. That's not to say that it couldn't happen, just hasn't happened to me. Is the SSD in question your boot drive?

If you've tried Driver Verifier and nothing happened (particularly for a few days), then your drivers aren't likely the cause. In my case, after I re-booted with Driver Verifier turned on, I got my BSOD in less than 5 minutes. The funny thing was after putting up with the BSOD's for so long, I had always been suspicious of Ai Suite, so it was no surprise.

 

[techadv]

I will replace sata cables and try to run Driver Verifier again. Yes, my first SSD is the system.
Previous minidumps i have and try read myself says something about hard disk drives.
Also when i have start to recieve first bsods, i have 4 sticks of 4gb, and one of them run faulty when test with memtest86. So i remove it and another good stick. So now i am with 2x4 gb sticks that pass memtest86.

 

[techgeek]

How are you overclocking your Xeon? I'm not completely familiar with Xeon's but I thought they were multiplier locked. If this is the case, then that means you are overclocking via the base clock (BCLK). This can cause issues if you've raised the base clock from 100MHz as this clock is used to clock other buses like PCI-E, USB, DMI, etc. Some motherboards have separate clocks for these auxiliary buses, but if yours doesn't it could be putting all the other buses out of spec.

Graphics cards seem to be particularly sensitive to PCI-E overclocking, even a few MHz has been known to cause system instability. The SATA controller also can have issues for DMI bus out of spec.

 

[johnbl]

the system bugchecked because csrss.exe detected something corrupted it.
looks like your CPU is running faster than the max clock rate🙁 2.93 GHz) reset the BIOS to defaults or update the BIOS.


machine looks very old, no new driver updates after windows 8.1 (even those were very limited) You will have to go to each chip vendor to see if you can get updated drivers.

old drivers:
ISODrv64.sys Tue Feb 10 01:22:18 2009 ( I would just remove this ISO CD-ROM Device Driver - ISODrive)
lvrs64.sys Mon Oct 22 19:11:24 2012 Logitech Camera driver, update if you can
iaStor.sys Tue Apr 26 11:06:18 2011 (old Intel Storage drivers, update from motherboard vendor or intel)
rtwlanu.sys Wed Dec 05 05:55:15 2012 (wireless USB 2 device)

machine info:
BIOS Version 2101
BIOS Starting Address Segment f000
BIOS Release Date 09/27/2012

Manufacturer ASUSTeK Computer INC.
Product P7P55D PRO
Version Rev 1.xx

Processor Version Intel(R) Xeon(R) CPU X3440 @ 2.53GHz
Processor Voltage 8ah - 1.0V
External Clock 190MHz
Max Speed 3800MHz
Current Speed 3809MHz

 

[techadv]

Thanks! I run driver verifier again and no problem. I have a latest bios. Most of the drivers are old, but also are latest that was produced by manufacturer. I have lower the OC to 166mhz BCLK. Also under stress test like prime95 and intel burn test system is stable. Will wait if new bsod happens