Hi guys,
I have encountered a second crash in under 3 weeks with the BSOD code 3b. I'm certain my chipset drivers are up to date, as are my graphics drivers. Windows drivers are also up to date. Generally speaking, I've been keeping drivers up to date.
I have attached the dump files for both 18/02/15 and 01/02/15. I would really appreciate help on analysis with this, as I haven't been able to solve it.
Thanks!
Click on button below ....
It will download the DM log collector. Right click on the application and run as administrator. It will generate a .zip file on your desktop. Upload the .zip.
Screenshots and Files - Upload and Post in Seven Forums
I've attached the zip file as required.
Analysing the dump files (for reference), both are memory related:
021815-21169-01 report:
030115-19624-01 report:Code:Probably caused by : ntkrnlmp.exe ( nt!FsRtlAcquireFileExclusiveCommon+4b ) BUGCHECK_STR: 0x34 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: System ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
Code:Probably caused by : ntkrnlmp.exe ( nt!IopFreeBandwidthContract+17 ) BUGCHECK_STR: 0x3B IMAGE_NAME: ntkrnlmp.exe DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: IAStorDataMgrS EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
Cheers
Analysis is not needed. We will do it as per our way.What is aswmonflt.sys ? | System ExplorerCode:fffff880`0379a418 fffff880`072c9649Unable to load image \SystemRoot\system32\drivers\aswMonFlt.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for aswMonFlt.sys *** ERROR: Module load completed but symbols could not be loaded for aswMonFlt.sys aswMonFlt+0x1d649
Uninstall Avast using Avast Uninstall Utility. At least on a test basis. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
Let us know for any further BSOD. Further steps might be needed depending on the situation.
I'll try that then, thanks. For future reference, in which file did you find this error?
Is it an important info for the troubleshooting?
Please do what suggested and report accordingly.
No, I would just like to know where this error was located, so I can check things like this for myself in future? Thanks
I understand. Nice.
But mate, I really dont have the time right now to look them back again. From the next time I will try to document things more elaborately, as you want to learn. I can say it was in the raw stack of the stop 0x34 dump, but cannot reming more details now.
I astonished because generally people does not ask for such questions. I would appreciate it.
I appreciate you taking the time to do so, but I would like to verify details like this so I can make informed decisions. Within the 0x34 dump I cannot see anything related to aswMonFlt.sys when looking through WinDbg. Are there setup configurations on my side that are incorrect?
You need to teach yourself to go that deep of a minidump. It takes a good time and effort.
Perhaps that is why people ask others to read those; they does not know.
If you pay that time and effort, you also will know.
In the mean time, let us know for any further BSOD after applying the suggested change.
Quote