New
#1
BSOD from unknown reasons, bug check 0x0000007a
I'm not a techie but I know how to use common stuff like BlueScreenView.
Any ideas?
I'm not a techie but I know how to use common stuff like BlueScreenView.
Any ideas?
Additional information is required.
1. Download the DM Log Collector application to your desktop by clicking the link below
DM Log Collector.exe
2. Run it by double-clicking the icon on your desktop, and follow the prompts.
3. Locate the .ZIP file that is created on your desktop, and upload it here in your next reply.
Here it is. Thanks for replying so fast!
Replace Avast with MSE, which has never been shown to cause BSOD's. Use this tool to completely remove Avast from your system.Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 7A, {c06131b0, c000000e, 914da8c0, c2636ff4} *** WARNING: Unable to verify timestamp for aswSnx.sys *** ERROR: Module load completed but symbols could not be loaded for aswSnx.sys Probably caused by : aswSnx.sys ( aswSnx+19ea0 ) Followup: MachineOwner ---------
Are you sure this is all Avasts' fault? If so, I guess I'll try anything BUT MSE. I'll stick to Kaspersky since MSE eats up my memory.
Driver Reference Table - aswSnx.SYS
Kaspersky is far more resource hungry than MSE, but its your choice.
I really don't know where else its coming from.
DMLog posted.
BlueScreenView
Bump Because the Previous solution didn't help.
Attachment : New BluescreenView.
Its getting more constant now.
Run the SHORT test of the DOS version of SeaTools:Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck F4, {3, 8569b8a8, 8569ba14, 8305dec0} ----- ETW minidump data unavailable----- Probably caused by : hardware_disk Followup: MachineOwner ---------
SeaTools for DOS and Windows - How to Use
I did a Short test and it was good.
Can the RAM be a culrpit in the BSOD? Because I still have another issue with my Onboard Graphics Card which is in another thread. Care to check it out? Could it be that these two seperate issue can be caused by the RAM?
Intel HD 4600 - Distorted Pixels and Constant Crashing