[SOLVED] Sysnative jcgriff2 BSOD File Collection app problem

Hi,

This happens sometimes. For now, running the processing app is not necessary, and we'll only ask for it afterwards if need be. For now, please go ahead and manually zip up and attach any crash dumps from C:\Windows\Minidump

Regards,

Patrick
 
Hi Patrick,


OK, here are my dumpsView attachment Minidump.rar

I'll describe the situation:

I've been using this PC with XP since I assembled it, about 5 years ago. A couple of months ago I installed win 7 on it, and since then I'm having random BSOD's. First I'll tell you what I've already tried and then I'll describe my hardware:


Solutions I tried that DIDN'T WORK:


-Installed latest GeForce driver (v335 dot something)
-Installled oldest available driver for my card from nvidia's driver archives (v314 dot something)
-Uninstalled every nvidia driver and installed windows WDDM driver
-Uninstalled nvidia's chipset & network driver, leaving microsoft's ones installed
-The same with audio card (WDDM driver, latest official, etc)
-Ran Memtest86+, Samsung ESTOOL to chechk RAM & disk -> everything OK
-Disabled SystemExplorer from autostarting, used my PC without it running on background
-Updated my TP-LINK USB wifi card's driver to latest
-Restored BIOS defaults
-Disabled Silicon eSATA ports from BIOS (many dumps seem to point to disk/store problems)
-Changed from ESET antivirus v7 to Avast free

I am surely forgetting something....

Hard details:
ASUS crosshair
AMD Athlon X2 6000+
2GB DDR2 800
320GB Samsung HDD
Win7 x86


I've been messing around with windbg, driver verifier, resplendecense's whoCrashed.... but had no luck so far....


Thankyou very much for your time guys,

greetings,

Pablo
 
Thanks!

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)

This bug check indicates that a kernel-mode application generated an exception that the error handler did not catch.

Code: 
1: kd> k
ChildEBP RetAddr  
a61c055c 84f95d0a nt!ExAllocatePoolWithTag+0x49d
a61c057c 84f96771 fltmgr!FltpAllocateFileNameInformation+0x22
a61c0594 84f80b21 fltmgr!FltpCreateFileNameInformation+0x8d
a61c05c4 84f96cd9 fltmgr!FltpGetFileNameInformation+0x321
a61c05d8 9b343964 fltmgr!FltGetFileNameInformationUnsafe+0x59
a61c05f8 84f95f27 luafv!LuafvGenerateFileName+0x6a
a61c0628 84f9675d fltmgr!FltpCallOpenedFileNameHandler+0x4f
a61c0640 84f80b21 fltmgr!FltpCreateFileNameInformation+0x79
a61c0670 84f96cd9 fltmgr!FltpGetFileNameInformation+0x321
a61c0684 8be4066d fltmgr!FltGetFileNameInformationUnsafe+0x59
WARNING: Stack unwind information not available. Following frames may be wrong.
a61c06cc 84f95f27 [COLOR=#ff0000]aswSnx+0x166d[/COLOR]
a61c06fc 84f98ac0 fltmgr!FltpCallOpenedFileNameHandler+0x4f
a61c075c 84f98c59 fltmgr!FltpExpandFilePathWorker+0x342
a61c0774 84f98dc3 fltmgr!FltpExpandFilePath+0x19
a61c0790 84f99505 fltmgr!FltpGetNormalizedFileNameWorker+0x7d
a61c07a8 84f96765 fltmgr!FltpGetNormalizedFileName+0x19
a61c07c0 84f80773 fltmgr!FltpCreateFileNameInformation+0x81
a61c07e0 84f808c7 fltmgr!HandleStreamListNotSupported+0x125
a61c0810 84f80fa3 fltmgr!FltpGetFileNameInformation+0xc7
a61c0838 8bf5a8ae fltmgr!FltGetFileNameInformation+0x12b
a61c0880 8bf5a423 [COLOR=#ff0000]aswSP+0x5a8ae[/COLOR]
a61c08b4 84f7aaeb [COLOR=#ff0000]aswSP+0x5a423[/COLOR]
a61c0920 84f7d9f0 fltmgr!FltpPerformPreCallbacks+0x34d
a61c0938 84f911fe fltmgr!FltpPassThroughInternal+0x40
a61c094c 84f918b7 fltmgr!FltpCreateInternal+0x24
a61c0990 82d364d9 fltmgr!FltpCreate+0x2c9
a61c09b4 82a3bbd5 nt!IovCallDriver+0x73
a61c09c8 82c4b506 nt!IofCallDriver+0x1b
a61c0aa0 82c2ad1e nt!IopParseDevice+0xee6
a61c0b1c 82c3b147 nt!ObpLookupObjectName+0x4fa
a61c0b78 82c5de6e nt!ObOpenObjectByName+0x165
a61c0d24 82a428c6 nt!NtQueryAttributesFile+0x121
a61c0d24 770570f4 nt!KiSystemServicePostCall
0012f608 00000000 0x770570f4

aswSP.sys is the avast! Self Protection driver.


1. Remove and replace avast! with Microsoft Security Essentials for temporary troubleshooting purposes as it's causing file system conflicts:

avast! removal - avast! Uninstall Utility | Download aswClear for avast! Removal

MSE - Microsoft Security Essentials - Microsoft Windows

2. Uninstall any/all Asus software (for example, I see PC Probe/Ai Suite).

3. Uninstall Silicon drivers/software.

Regards,

Patrick
 
When I had ESET, a BSOD pointed to it, that's why I changed to Avast.... just uninstalled Avast, and installed MSE. I also uninstalled ASUS Cool&Quiet (Which also disabled from BIOS some time ago). As I'm not using eSATA, I left those ports disabled, and I can't find nothing from Silicon to uninstall.

What's next?
 
Silicon is utter crapware IMO as it's almost impossible to remove without renaming drivers which we will do if it becomes a problem.

For now however, we wait and see. Please keep me updated.

Regards,

Patrick
 
Ok, I'll test and let you know the results.

Just in case the BSOD reappears, I have a full memory dump... If you want to analyze it tell me and I upload it (zipped weights 1,2GB)

Regards,

Pablo
 
I can DL that no problem, just so long as you can upload it without a problem as well.

Regards,

Patrick
 
Pablo, would you mind uploading that to Onedrive as opposed to Dropbox? I always have download issues with Dropbox (i.e being extremely slow), but with Onedrive it will finish within 1-2 minutes.

Regards,

Patrick
 
With my 100KB/s upload speed it will take another 3hours... but hey! you are giving me hell of a hand!!!

tomorrow I'll post the onedrive link

Greetings,

Pablo
 
Patrick, I finally uploaded it. Here you go

http://1drv.ms/1iSVVb6

It gave me an error when got to 100%... so I hope the RAR it's not corrupt... If it is then I would please ask you to download it from dropbox, it would take me a lot of time to upload it one more time!


Thanks for your time,

Pablo
 
I have the kernel-dump in possession, Pablo. To be clear, you have not yet crashed, correct?

Regards,

Patrick
 
kernel-dump? I've sent you a Full memory dump...
Nope, no crashes since last friday (May 9th). With Avast installed the record was about 9 days without crashing.


Greetings,

Pablo
 
Sorry, that's what I meant! : )

Great, if we do crash again, I'll debug/explain the full memory dump as it will be pretty long. Keeping it saved just in case.

Regards,

Patrick
 
Great, thanks! If the 23rd (2 weeks sounds reasonable) still no BSOD has appeared, I'll come back for answers to why the hell those Antivirus don't get along with my machine... I'm not feeling safe with MSE...

Regards,

Pablo
 
Not a problem, I'll look forward to your reply and then answer whatever questions you may have.

Regards,

Patrick
 
Here I am again Patrick! The good news are: No more BSOD's since May 9th :D
The bad news: Which decent antivirus can I use???! or what I would prefer: Is there something I can do to use ESET or Avast?


Thank you one more time Patrick, I really appreciate your uninterested help, more people like you is needed in this insane world...

Greetings,

Pablo
 
Glad to hear, and it's been my pleasure.

As far as what antivirus to use, you have a lot of options. Stay away from McAfee and Norton. MSE despite what many say is a fine antivirus, although I won't of course lie to you and say it's the best protection offered. If you pair MSE with Malwarebytes, it's great protection. Realistically, the most important thing aside from worrying about what AV to use is to ensure you understand proper methods to avoid being infected with malware, and proper prevention methods.

Regards,

Patrick
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top