[SOLVED] BSOD Win7 x32 machine while browsing with Chrome

mikon

New member
Joined
Aug 17, 2013
Posts
3
  • OS - Windows 7 SP1
  • x86 (32-bit)
  • What was original installed OS on system? - Same as above
  • Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)? - Full Retail Edition
  • Age of system (hardware) - Around 1 and a half year I guess
  • Age of OS installation - have you re-installed the OS? Not in the last year

  • CPU - Intel Core i5 2500k
  • Video Card - Zotac NVIDIA GTX 560 TI 2GB
  • MotherBoard - ASUS P8Z68 V Pro/Gen3
  • Power Supply - Corsair TX750
  • System Manufacturer - Assembled

Problem started a few days ago. Randon BSOD's while I was surfing the net using Google Chrome. Error messages would vary from DRIVER_IRQL_NOT_LESS_OR_EQUAL, ATTEMPTED_WRITE_TO_READONLY_MEMORY, IRQL_NOT_LESS_OR_EQUAL. Initially though Comodo Firewall was at fault and uninstalled it but still didn't help. Later tried uninstall Asus Suite II but again no go.
Funny thing is there are no problems while gaming just while surfing the internet.
Hopefully this can be resolved soon.

View attachment 4933
 
Hi,

Most if not all of the attached DMP files are of the IRQL_NOT_LESS_OR_EQUAL (a) bugcheck.

A kernel-mode driver or process attempted to access a protected memory location it does not have permission for, or a kernel interrupt request level (IRQL) attempted to access a memory address that is too high.

This bugcheck usually occurs when a driver uses an incorrect memory address. Other possible causes of this error include: bug in a device driver, system service, the BIOS, an old Anti-virus program or backup tool, or possibly memory issues.

BugCheck A, {20707249, 2, 1, e38cdec3}

I see in a fair bit of them you have verifier enabled, but it's failing to flag a driver. I see various driver calls in the stack as well as the function pointing to the ecx register being the same as the address which referenced memory (1st parameter) -

Code:
0: kd> .trap 0xffffffffee2df72c
ErrCode = 00000002
eax=14260000 ebx=cead75d4 [COLOR=#ff0000][U][B]ecx=20707249[/B][/U][/COLOR] edx=00000000 esi=14260000 edi=cead0000
eip=e38cdec3 esp=ee2df7a0 ebp=ee2df7b0 iopl=0         nv up ei ng nz ac po cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010293
nt!KiSignalSynchronizationObject+0x1c:

In my opinion, from looking at this, it could still be driver related. However, memory is possible as well. We will see...

I am seeing some NETIO.sys culprits in a few *A dumps and I am wondering if avast! has anything to do with that as we usually see 3rd party antiviruses and firewalls causing NETIO.sys culprits. I also spy a few more drivers in the modules list that would cause issues.

1. I recommend for temporary troubleshooting purposes that you remove avast! and replace it with Microsoft Security Essentials.

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

MSE - Microsoft Security Essentials - Microsoft Windows

2. In your loaded drivers list, dtsoftbus01.sys is listed which is the Daemon Tools driver. Daemon Tools is a very popular cause of BSOD's in 7/8 based systems. Please uninstall Daemon Tools. Alternative imaging programs are: MagicISO, Power ISO, etc.

3. I see networx.sys in the loaded modules list, this is also a very big flag raiser to me. This is the driver for NetFilter SDK's framework for transparent filtering the data packets transmitted via network on Windows. In my time as an analyst, I have seen this cause problems before. I recommend temporarily removing this for troubleshooting purposes as well.

Let me know how the system behaves after following the above.

Regards,

Patrick
 
Thanks for the prompt reply. Didn't expect it so soon to be honest.

Anyways I am following the steps you outlined and am uninstalling Avast, Daemon Tools Lite and Networx from my PC forthwith. Installing Microsoft Security Essentials instead.

Since I am not sure which actually triggers the BSOD I'll just continue to surf and hopefully be back with a all clear tomorrow.

Thanks again for the prompt support
 
Well its been a few days and there have been ZERO BSOD in the meantime. I am guessing any one of the three (Avast!, Daemon Tools or Networx) was responsible for the frequent crashing. Going to look for alternatives in the meantime. Thanks for the help Patrick. Real load of my mind.
 
Hi,

Thank you for the update, and good work. It was my pleasure. Glad to hear everything's okay.

If you feel or are confident enough that your problem is solved, please navigate to 'Thread Tools' at the top of the thread and select 'Mark this thread as solved'.

Regards,

Patrick
 

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

Back
Top