Continual BSOD's over a 12 month period

[pat5zero]

Hello.
I have tried unsuccessfully to understand and correct the multiple BSOD I have been having since may 2010 on this particular system.
I have had the x58a-udr3 MB replaced RMA, may this year. I have had the ram replaced and have removed every device to the bear minimum and am still having some BOSD's.
I have recently bought a Corsair Force 3 sata III 120GB SSD. I have applied the recommended firmware 1.3 update in the hope that this might correct the situation.
Before anyone jumps in with the normal procedure of memtest and verifier.exe. I have done this all. I have replaced and renewed up to this day, all drivers.
I did have a 1 bay removable HDD rack which I used to run a Seagate 1.5TB & 1TB hard drives, which I have removed as a possible problem, I have noticed strange noises and sometimes a lag in response for the particular HDD rack and suspected the racks little sata controller interface. I have also turned off the USB 3.0 in the Bios to see if that eliminates the problem.
I have tried several other forums Gigabyte and Corsair etc with no luck and I find with google searches that I always end up here in this forum with some interesting aspects and advice on BSOD's. But not specific to my problem.
I hope you can help me.

 

[zigzag3143]

One thing you did miss is sptd.sys

Please remove any CD visualization programs such as Daemon Tools and Alcohol 120%.

They use a driver, found in your dmp, called sptd.sys, that is notorious for causing BSODs.

Use this SPTD uninstaller DuplexSecure - Downloads DuplexSecure - FAQ

when you're done you can use this Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) in its place.


BTW none of these DMP files say driver verifier was enabled.

 

[pat5zero]

One thing you did miss is sptd.sys

Please remove any CD visualization programs such as Daemon Tools and Alcohol 120%.

They use a driver, found in your dmp, called sptd.sys, that is notorious for causing BSODs.

Use this SPTD uninstaller DuplexSecure - Downloads DuplexSecure - FAQ

when you're done you can use this Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) in its place.


BTW none of these DMP files say driver verifier was enabled.

Just two night ago I uninstalled the version of sptd driver I had for the latest one that is suppose to be bug free.
I bought alcohol 120% and have used it for some years now. I am aware of its reported problems with windows 7.

But to get to the bottom of these problems I will remove it for now. I would just like to add to understand my situation. I have used under suggestion in the past MagicISO, UltraISO and a plethroa of other emulators (in other words all) and have still received copious amounts of BSOD's.

As of this moment I have uninstalled the sptd driver and have removed the associated program (Alchol 120%). Please bear with me and I will get back to you if anything occurs in the next 24hrs.

Also are you suggesting I turn back on the verifier.exe program as it was stopping me from booting the computer.
I don't fully understand the right settings, do you or might you have a suggestion for the correct settings to test the system with verifier.exe?

I have just one more query, I have been getting these event notices and am wondering if you can enlighten me into some aspects of where I stand with this marvel 9128 sata 3 controller I run the 2 sata 3 drives off. I have run the WD 1TB drive as OS in the past and have just bought the SSD drive and am running that off the marvell 9128 too. I have attached one of about 10 event logs on this problem.

 

[zigzag3143]

Obviously a driver. Verifier is supposed to crash when it finds an offending driver.

If you system crashes after turning verifier on (you can check by typing verifier /query in cmd) then turn it off and upload the dmp files.

 

[pat5zero]

Obviously a driver. Verifier is supposed to crash when it finds an offending driver.

If you system crashes after turning verifier on (you can check byt typing verifier /query in cmd) then turn it off and upload the dmp files.

Well from the time you pointed out my problems and my correction under your instructions. I have left the system running for some 12 hours now and not one BSOD.

I am a bit bewildered that only this driver was the problem, because on average I received up to 10-12 BSOD a day.
I wonder why they market this sptd driver when it causes so much problems.

So by rights now I should turn on in the BIOS the USB 3.0 controller, I will in the next day or two buy a new HDD removable rack as the one I have had in the system is some 3-4 years old and they are not that expensive to replace.

Also with driver verifier, should I, for peace of mind switch it on to just defaults (create a standard settings only) and test what happens?


Hey BTW thanks in advance for your quick response and help, you have made one happy computer user. Your worth more money! !

 

[pat5zero]

I knew that just removing the sptd.sys driver was too easy. I have since had two BSOD's today. Here is the report.

 

[zigzag3143]

I knew that just removing the sptd.sys driver was too easy. I have since had two BSOD's today. Here is the report.

Most recent DMPS (5) say memory corruption. Still probably caused by a driver.

 

[pat5zero]

Right your first post gave me ideas.
1. I enabled driver verifier with all non Microsoft drivers flagged according to your forum's instructions.
2. Started the system and went on my merry way. NO problems.
3. I started my favourite TV program called DVBviewer and bingo, immediate BSOD.
4. Rebooted and used other programs with no BSOD.
4. Used the Divco FusionHDTV DVB-T Dual Express TV card default program and straight away a BSOD.
5. Blue-screen said the offending driver was zl885x64.sys, which is the driver for the TV card.
I attached the latest dumps for your consideration.
I have had this TV card for some 3-4 years now. I have too, for my laptop a Compro u90 USB TV stick.
Might take out the Dvico TV card and try the Compro USB TV stick to see if a BSOD occurred.
LOL as I was writing this message I had the TV program running and it BSOD. never a dull moment..

Right I have removed the TV card and Divco software and zl885x64.sys diver and have tried my Compro U90 usb tv stick. Guest what? NO BSOD!

I have driver verifier enabled and will let it run the standard 48hrs to see if anything else occurs but I am assuming this might be the problem as I have never removed the Dvico TV card through all the systems I have had over the past 3-4 years, because it always worked.

If this is the problem I feel bad now as I hassled the hell out of my vendor to replace both motherboard and ram over this ongoing problem of BSOD's. Yes I did get a new GA-X58A-UDR3 and the 6gig corsair ram exchanged.

 

[pat5zero]

Still getting regular BSOD's and have tried to pinpoint the problem with turning off the Marvell 9128 Sata 3 controller and putting all the HDD's and SSD on the Intel sata 2 controller.
Removed the Dvico TV card offending driver (zl885x64.sys
Un-installed Ultra ISO before latest BSOD's as Bluescreen viewer said it was an offending driver. (ISODrv64.sys)
I even had a BOSD and driver conflict with (LHidFilt.Sys) which is the driver for a brand new KB/mouse combo from Logitech.
I am bewildered over this continual blue screening. What gets me is this has been happening from day one (01-06-2010). That is well over 18 months.
Surly there is an explanation?
I really need some help, it is driving me mad. I can't do any work as I fear the abrupt BSOD's will happen at any moment.
Bloody hell as I was writing this note I got another BSOD.
Here are the latest BSOD's to this moment.

 

[pat5zero]

I ran memtest this afternoon for some 3.30 hrs.
The following pictures are the results so far. However I have been told this could be false what do you reckon zigzag?
BTW this test was run at what the MB choose as defaults for the memory.
8-8-8-24 1T 1.5v and reads 1066mhz
But the memory is capable 1600mhz and the correct timings are 9-9-9-24 1T 1.65v

But when I either set manually the timings to its specifications or use the XMP profile1 the computer immediately BSOD's

BTW I have other pictures of running the memtest with the xmp settings and I got two faults in the test within 5mins.
I am trying a few ideas this afternoon. I have run the intel processor diagnostic tool and cpu passes OK.
I have got the latest stable BIOS update and flashed the BIOS from version FD to FF.
Also Corsair have added a new firmware update for the SSD drive I have and the update suggests that the SSD might be causing BSOD's.

 

[pat5zero]

LOL, more BOSD's since I last posted and very frequently. So I was ready to RMA the RAM. But first off to cover all angles, I made a thread in the Corsair forums about this matter and got a reply back about changing the QPI voltage, increasing it till there is no more BSOD's.

I have never worried about overclocking this system as its too complex and beside that I have the Sata 3 SSD and fast CPU and am satisfied with the present speed.

So I did a search for references to my RAM and MB in the Corsair forum and found a link to this explanations for BSOD's
Most of the BSOD error codes I have experienced are referenced below. What I have done is go to the RAM settings and set them as stock standard settings and raised the RAM voltage till there was no more BSOD's.

If there is no more BSOD's in the next 24hrs, I will then run memtest to see if I am still getting faulty memory.

BSOD Codes for i7 x58 chipset
0x101 = increase vcore
0x124 = increase/decrease QPI/VTT first, if not increase/decrease vcore...have to test to see which one it is
0x0A = unstable RAM/IMC, increase QPI first, if that doesn't work increase vcore
0x1A = Memory management error. It usually means a bad stick of Ram. Test with Memtest or whatever you prefer. Try raising your Ram voltage
0x1E = increase vcore
0x3B = increase vcore
0x3D = increase vcore
0xD1 = QPI/VTT, increase/decrease as necessary, can also be unstable Ram, raise Ram voltage
0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances
0x50 = RAM timings/Frequency or uncore multi unstable, increase RAM voltage or adjust QPI/VTT, or lower uncore if you're higher than 2x
0x109 = Not enough or too Much memory voltage
0x116 = Low IOH (NB) voltage, GPU issue (most common when running multi-GPU/overclocking GPU)
0x7E = Corrupted OS file, possibly from overclocking. Run sfc /scannow and chkdsk /r

BSOD Codes for SandyBridge
0x124 = add/remove vcore or QPI/VTT voltage (usually Vcore, once it was QPI/VTT)
0x101 = add more vcore
0x50 = RAM timings/Frequency add DDR3 voltage or add QPI/VTT
0x1E = add more vcore
0x3B = add more vcore
0xD1 = add QPI/VTT voltage
“0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances”
0X109 = add DDR3 voltage
0x0A = add QPI/VTT voltage

Please feel free to comment, advise, correct, and add to this list. I am not the original author and will not take credit for it. I simply thought that it should be posted by itself. I am only repeating the info that I got here at OCN. This is currently for Intel i7 systems, but I would like for everyone to help me set it up for other systems as well.

Thanks, just giving back,
/eVo/HaMMeR=GoM=

Here is the link to further discussion on these types of BSOD codes.
The OverClockers BSOD code list

 

[pat5zero]

Do you get a prize for the most BSOD's in a week.

I counted 50 BOSD's so far.

Can anybody get their heads around this problem or problems.

I have adjusted the CPU Vcore voltage to compensate for the voltage settings of my memory and am still getting BOSD codes of 0x1a and 0x7E.

The BOSDs codes above are suggesting from the table above this is either wrong voltage or corrupt memory stick?
I have since installed the Gigabyte easytune6 program to adjust the voltage values, so I can actually see what the different voltages are running at, here is a picture of what the actually present voltages are set at. Also the latest BSOD's.

 

[zigzag3143]

Pat

I do appreciate your situation but adjusting the voltage may fix the problem or make it worse.

A 124 error is a generic hardware error, not just a ram error. By changing the voltage you may actually make it worse.

 

[pat5zero]

Pat

I do appreciate your situation but adjusting the voltage may fix the problem or make it worse.

A 124 error is a generic hardware error, not just a ram error. By changing the voltage you may actually make it worse.

Sorry I use a user name on forums, my name its actually Paul and Yes I didn't achieve anything with those codes and their supposed explanations by upping the voltage. I have never overclocked this system as for a start it was too unstable.

I went back to Corsair forums and started a new thread about tests on the RAM with memtest, I had done yesterday and got all sorts of opinions on what and might be the cause.
Finally "Wired" the Corsair forums Admin said just take each stick of ram and check them individually in the first slot on the MB.
18 months of BSOD's with CMX6CX3M3A1600C9 - The Corsair Support Forums

The results are below. I have just posted on their forum and am hoping they will do a RMA on the RAM. The first two sticks reported no errors but the third one did.

 

[zigzag3143]

Paul

If you pull the memory that fails does the system still crash?

Would be nice if it were as simple as one ram stick

Ken

 

[pat5zero]

Paul

If you pull the memory that fails does the system still crash?

Would be nice if it were as simple as one ram stick

Ken

I hope I am not stuffing the system but I looked at my MB book/manual and read slots 1 and 3 will run duel memory and put the two good sticks in and am using the system to write this reply.

I still think a 24hrs period will tell all, but right now with the XMP profile1 set in the MB BIOS and running the MB at defaults. The RAM is set to its specs at 9-9-9-24 2T 1.65v 1600Mhz without a instant BSOD as soon as the desktop comes up sort of indicates it might have been the problem all a long.

As you said if its just one stick of RAM I have wasted the last 12 months of pulling my hair out tiring different fixes and checks.

I can't count how many times I have re-installed Windows 7 and all the time windows 7 adviser was saying run a memory test but when I did it came back with no errors. I suppose too, I won't really know everything is right till I hopefully get a RMA off Corsair and try the triple channel memory that they give me as a replacement.

 

[pat5zero]

@zigzag3143
I wonder too...
If it is this problem with a defective ram stick.
That the Dvico TV card I removed and the Marvell sata 3 controller that I have disable should be switched back on and used to see if I get any more BSODs.?

 

[zigzag3143]

@zigzag3143
I wonder too...
If it is this problem with a defective ram stick.
That the Dvico TV card I removed and the Marvell sata 3 controller that I have disable should be switched back on and used to see if I get any more BSODs.?

Perhaps without the suspect stick. Have you tested each mobo slot with a known good stick?

 

[pat5zero]

No, But I have been off doing things on this computer for the past 2 hrs without one single BOSD.
I am just about to re-slot the PCIe TV card and also if that works fine. I will change the both sata 3 drives back onto the Marvell 9128 sata 3 controller and see if they cause a BSOD.

I am presuming that the stick of RAM was the problem.

@zigzag
What your saying is try "A' stick of RAM in each slot at a time, then turn on the system?

 

[zigzag3143]

No, But I have been off doing things on this computer for the past 2 hrs without one single BOSD.
I am just about to re-slot the PCIe TV card and also if that works fine. I will change the both sata 3 drives back onto the Marvell 9128 sata 3 controller and see if they cause a BSOD.

I am presuming that the stick of RAM was the problem.

@zigzag
What your saying is try "A' stick of RAM in each slot at a time, then turn on the system?

I am saying that to ensure it isnt the mobo slot (it isnt) try a known good stick only in each slot.