63 replies to this topic

[eniparadoxgma]

Howdy. Long time no see and all dat mess. (Skewl is kickin my butt)

Anyhow...after going from XP Pro 32bit to Vista64 I just recently went back to XP Pro 32bit. (XP > Vista)

Well now (about 2 weeks after the reformat/OS change back) I'm starting to get some serious issues that I washaving directly before going to Vista64.

THE BLUE SCREENS HAVE CAME FOR ME!!!!

Without warning or provocation my computer will just BAM! Blue screen out of nowhere!!! There are different stop messages, sometimes no STOP at all, just a blue screen, etc. No rhyme, no reason. Doesn't matter what I'm doing. Playing a video game? BAM! Blue screen! Leaving the computer on with bit torrent overnight! BAM! Wake up to a blue screen! Surfin' the net? BAM! Blue screen! On average it blue screens about every day or two, but sometimes 5 times in one day, or 3 times in one hour. No rhyme...no reason.

I have dl'ed Microsoft's Debugger and ran the memory dumps. THERE IS NO RHYME OR REASON! All kinds of possibilities from memory corruption to pool corruption to driver faults to irq issues to...you name it.

What I have done is killed my overclock. BAM! Blue screen anyway! (so it's not the OC)

I have also ram memtest86 overnight. No errors. RAM seems clean.

Strange thing is, with Vista64 I never had any problems of this sort. Occasionally I would get an error pop-up that would say one of my hard drives had a critical error...but it wouldn't cause any problems. And for some reason I thought that if one of the hard drives in my RAID array +0 had a critical error that my array would crash and I'd be screwed. But alas, nothing of the sort has occurred. I just get the blue screen torture.

I know the issue is completely ambiguous but I have all my memory dumps and what not and was wondering that if no one here had an idea if anyone knew a good site for analyzing the dumps they could recommend.

I could also up some of that crap here, but I won't do that unless someone here thinks it would help.

For the record, I'm currently running:

Opteron 148 (single-core ftw) at 2.815
2 x 1gb DDR500 @ 512
Asus A8n SLI Premium
2 x 200 gb Maxtor SATA on Nvidia RAID controller
ATI AIW x1900
580watt Raidmax Aurora PSU

And here are some of the myriad of blue screen reasons so far:

#1:
BugCheck 1000007E, {c0000005, 8064af16, bacd7c0c, bacd7908}
Probably caused by : memory_corruption
Followup: memory_corruption
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem.

#2
BugCheck 1000008E, {c0000005, 80543a03, a019baf0, 0}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+fd )
Followup: Pool_corruption
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)

#3
BugCheck 1000007E, {c0000005, 80526331, ba423c24, ba423920}
Probably caused by : afd.sys ( afd!AfdFreeConnectionResources+4f )
Followup: MachineOwner
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)

#4
BugCheck 1000007F, {d, 0, 0, 0}
Probably caused by : memory_corruption
Followup: memory_corruption
UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault).

#5
BugCheck 1000008E, {c0000005, 80631602, 945828f8, 0}
Probably caused by : ntkrnlpa.exe ( nt!CmpRemoveFromDelayedClose+32 )
Followup: MachineOwner
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)

#6
BugCheck FC, {b302b238, 18f09163, b302b00c, 1}
Probably caused by : sr.sys ( sr!SrWrite+aa )
Followup: MachineOwner
ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
An attempt was made to execute non-executable memory. The guilty driver is on the stack trace (and is typically the current instruction pointer). When possible, the guilty driver's name (Unicode string) is printed on the bugcheck screen and saved in KiBugCheckDriver.

#7
BugCheck 1000000A, {8a95dd6c, ff, 0, 80531b92}
Probably caused by : ntkrnlpa.exe ( nt!ExAcquireResourceExclusiveLite+36 )
Followup: MachineOwner
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses.

#8
BugCheck A, {8afdc6bc, 2, 0, 80503298}
Probably caused by : TDI.SYS ( TDI!CTEpEventHandler+32 )Followup: MachineOwner
IRQL_NOT_LESS_OR_EQUAL (a)

#9
BugCheck 4E, {2, 28113, 7ffef, 1}

Unable to load image SiWinAcc.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SiWinAcc.sys
*** ERROR: Module load completed but symbols could not be loaded for SiWinAcc.sys
*** WARNING: Unable to verify timestamp for aswMon2.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswMon2.SYS
Probably caused by : memory_corruption ( nt!MiUnlinkPageFromList+40 )
Followup: MachineOwner
PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling MmUnlockPages twice with the same list, etc).

Super-awesome fun time!

Anyhow, another strange issue that occurred directly after one of these blue screens is that my mouse stopped working. I have a Logitech G-7, and after restarting it still wouldn't work. I had to physically move the USB receiver for the mouse to a different USB port in order to get it working. This same thing happened today as well. (I had to move it again)

Personally, my guess is that it's driver or software related. I mean, Vista should've had some troubles too if it was purely hardware related right? Bah, I really have no clue.

So, do I get an award for longest post ever?!?! or!?!?

Anyone that read the whole thing should.

Thanks.

[brewin]

Do you have any software running that uses a driver. Some sort of drive encryption utility or Daemon Tools maybe?

[eniparadoxgma]

brewin, on Sep 25 2007, 09:02 PM, said:

Do you have any software running that uses a driver. Some sort of drive encryption utility or Daemon Tools maybe?

Daemon Tools is running, yup. Should I uninstall the sucker to see if it clears up?

Thanks for the reply, btw. Blue screen hell is no way to go through life, son.

[brewin]

eniparadoxgma, on Sep 25 2007, 08:04 PM, said:

Daemon Tools is running, yup. Should I uninstall the sucker to see if it clears up?

Thanks for the reply, btw. Blue screen hell is no way to go through life, son.

That's my best guess. It seems to be screwing with your sata driver. Could also be Avast doing something weird. If you have the latest mobo drivers, then yeah, get rid of Daemon Tools to see if that's the culprit. If not, get rid of Avast.

[m.oreilly]

are you using avast, and are your drives connected to a silicon image controller?

[m.oreilly]

haha, brew beat me to it...

[eniparadoxgma]

Haha! You guys rock.

Just uninstalled Daemon Tools. I am using Avast right now, but I think I was using NOD32 when the problem started (before the VISTA64 experiment). I can always go to AVG or back to NOD32 if Avast is giving me static.

As far as the SATA/RAID controllers, I have the RAID array and a JBOD 500gb SATA on the Nvidia and all I have on the Silicon is a Plextor 712 SATA DVD burner.

How could you guys tell it had anything to do with the SATA controllers?!?! (I can't ascertain that from the dump files)

Thanks, guys.

[eniparadoxgma]

Btw, is was the banj0 guy that told me you didn't need Alcohol because you could just use Daemon Tools for free.

Thanks a lot, banj0!!!

[m.oreilly]

eniparadoxgma, on Sep 25 2007, 06:34 PM, said:

Btw, is was the banj0 guy that told me you didn't need Alcohol...

heresy!
someone give that man a drink!

[eniparadoxgma]

lmao @ the java virus quote. Stay away from x64bit! They'll hack you with a java virus when you come to their site!

[brewin]

eniparadoxgma, on Sep 25 2007, 08:29 PM, said:

How could you guys tell it had anything to do with the SATA controllers?!?! (I can't ascertain that from the dump files)

SiWinAcc.sys is the sata driver.

aswMon2.SYS is the Avast driver.

Daemon Tools was just a good guess. It could be a conflict between Avast and Daemon Tools. So uninstalling either one might work.

[m.oreilly]

brewin, on Sep 25 2007, 06:47 PM, said:

SiWinAcc.sys is the sata driver.

aswMon2.SYS is the Avast driver.

Daemon Tools was just a good guess. It could be a conflict between Avast and Daemon Tools. So uninstalling either one might work.

[eniparadoxgma]

brewin, on Sep 25 2007, 09:47 PM, said:

SiWinAcc.sys is the sata driver.

aswMon2.SYS is the Avast driver.

Daemon Tools was just a good guess. It could be a conflict between Avast and Daemon Tools. So uninstalling either one might work.

Strange. I spent some time googling the .sys files I saw come up and they all ended up being windows system files of some sort. I guess I just didn't google the right ones.

Thanks again, fellers.

[David_Heavey]

brewin, on Sep 26 2007, 02:47 AM, said:

It could be a conflict between Avast and Daemon Tools. So uninstalling either one might work.

Would I not be getting the same conflict? Because I'm not ... never have.

Here's a thought. My bro has a laptop and he was getting those same errors. Various and completely random BSOD. Turned out to be damaged sectors on his HDD. MIGHT be your problem too??

[banj0]

I use Avast and Daemon Tools together just fine. X64 and Vista64. Alcohol?!? Discs are dead dude.

What type of juice are you giving your memory? I know you said it passed memtest but try upping the juice by just a little bit. Can't hurt unless you're already really high.