Sign in with
Sign up | Sign in
Your question

Browsers crashing.

Last response: in Windows 7
Share
March 26, 2012 5:50:38 PM

Hello! Recently I've been getting some blue screens and constant browser crashing and so I decided to reinstall Windows 7.

So I did and I'm still experiencing frequent browser crashes and have got a blue screen about twice. I don't want to believe it's hardware related! Please help me find a solution to this problem.

More about : browsers crashing

March 27, 2012 12:12:33 AM

szaboaz said:
Any error message/code you can read on the blue screen?

It can be an overheating issue, you should monitor CPU temperature. ( http://www.tomshardware.co.uk/forum/234349-39-best-reli... )

It could also be memory fault (hey, let's think of the cheapest part first...). You can test with Memtest86 ( http://www.memtest.org/ ). There is CD iso image, and USB installer too.


Thanks so much for the reply! I ran memtest86 and no errors there.

I also ran Hmonitor and here's what came up:



Please reply again if you need any more info. I'm worried my GPU may be faulty.

Edit: Not sure how accurate those readings are. I don't have any special temperature sensors installed.
Related resources
March 27, 2012 12:34:02 AM

iknowhowtofixit said:
Post your full system specs


a b $ Windows 7
March 27, 2012 12:45:15 AM

buy specs it means the motherboard the ram the psu an d the graphic card and os use it is a 32 bits or 64 and witch one
a b $ Windows 7
March 27, 2012 12:47:45 AM

gpu report good and temp are very good,what is the browser you use
March 27, 2012 12:48:13 AM

scout_03 said:
buy specs it means the motherboard the ram the psu an d the graphic card and os use it is a 32 bits or 64 and witch one


Sorry what are you asking? I posted the specs in a picture above that has all that info.
March 27, 2012 12:50:32 AM

scout_03 said:
gpu report good and temp are very good,what is the browser you use


It crashes in all of them (Firefox, IE, Chrome). And I use all of them.
a b $ Windows 7
March 27, 2012 12:54:27 AM

open a firefox page and report what you see when it crash
March 27, 2012 12:58:46 AM

scout_03 said:
open a firefox page and report what you see when it crash


It literally just crashes to the bug report screen and asks if I'd like to restart my browser :( 

Sometimes though, with Google chrome, the page just crashes and asks me to reload it.
a b $ Windows 7
March 27, 2012 1:03:17 AM

uninstall chrome and reinstall it
March 27, 2012 1:08:04 AM

scout_03 said:
uninstall chrome and reinstall it


I'll do that and report back when I get a crash. (If I don't in an hour I'll also report back).
a b $ Windows 7
March 27, 2012 1:16:01 AM

be here
March 27, 2012 1:20:27 AM

scout_03 said:
be here


Reinstalled. 5 minutes in the page crashed with an "Aw Snap" message...
a b $ Windows 7
March 27, 2012 1:48:50 AM

at the bottom of page if you sill have problem click on ther link they could give you more help for chrome
a b $ Windows 7
March 27, 2012 8:43:17 AM

You should try to get ahold of some more information about the blue screen. Is it a plain blue screen without any characters on it?

Anyway, you should take a look into C:\Windows\minidump directory, that's where the system crash logs go to die. Maybe there're a couple recent ones, with some error code we can Google around with. Which may also help finding out, if it's hardware or software, or combination.
(If nothing there, check this out:
http://forums.techguy.org/windows-vista/851183-bsod-err... or this:
http://social.technet.microsoft.com/Forums/en-US/w7itpr... )

How come it's the browsers, and only the browsers... What do they have in common... networking? flash? graphics acceleration?

You reported back that Memtest was OK. Have you let it go around for several passes? (I'm looking for errors in the error-finding method now, crazy :p )

You suspect it has something to do with the video cards. If you are comfortable opening up the case (precautions! static charge, etc.), have you thought of removing them and using the IntelHD for a while?
March 27, 2012 6:00:16 PM

szaboaz said:
You should try to get ahold of some more information about the blue screen. Is it a plain blue screen without any characters on it?

Anyway, you should take a look into C:\Windows\minidump directory, that's where the system crash logs go to die. Maybe there're a couple recent ones, with some error code we can Google around with. Which may also help finding out, if it's hardware or software, or combination.
(If nothing there, check this out:
http://forums.techguy.org/windows-vista/851183-bsod-err... or this:
http://social.technet.microsoft.com/Forums/en-US/w7itpr... )

How come it's the browsers, and only the browsers... What do they have in common... networking? flash? graphics acceleration?

You reported back that Memtest was OK. Have you let it go around for several passes? (I'm looking for errors in the error-finding method now, crazy :p )

You suspect it has something to do with the video cards. If you are comfortable opening up the case (precautions! static charge, etc.), have you thought of removing them and using the IntelHD for a while?


Thanks for the help so far. I've uploaded a dump file here http://www.mediafire.com/?d6b6a8711aelwxu

I'm starting to think it's not the fans because it's not crashing with games etc and those are much more intensive, plus my temps are perfectly stable.

Please let me know if you find anything in that dump file and if not I'll try removing the graphics card for a while. Oh and also, I didn't let memtest86 run more than once, I could run it overnight tonight if you think it would increase the chances of finding something.
a b $ Windows 7
March 27, 2012 7:06:31 PM

What you have uploaded is a dump, but we're gonna need a "minidump". This is a quote from one of the above linked pages:

Quote:
Collect Minidump Files
=================
1. Click "Start", input "SYSDM.CPL" (without quotation marks) in the “Search” bar and press “Enter”.
2. Switch to the "Advanced" tab and click the "Settings" button under "Startup and Recovery".
3. Under "Write debugging information" section, make sure the "Small memory dump (128KB)" option is selected.
4. Make sure "%SystemRoot%\Minidump" is in the "Small dump directory" open box and click “OK”.

If the Blue Screen appears again, please refer to the following steps to collect memory dump files:

1. Click “Start”, type “%SystemRoot%\Minidump" (without quotation marks) in “Search” bar and press “Enter”.
2. Go to your Desktop, right-click on it and create a new folder named "Dump".
3. Copy all the memory dump files (looks like [Mini092008-01.dmp]) in Minidump to this folder.
4. Right-click on the Dump folder, click "Send To", and click "Compressed (zipped) Folder".
5. Please send the ZIP file to us.
March 27, 2012 7:33:11 PM

szaboaz said:
What you have uploaded is a dump, but we're gonna need a "minidump". This is a quote from one of the above linked pages:

Quote:
Collect Minidump Files
=================
1. Click "Start", input "SYSDM.CPL" (without quotation marks) in the “Search” bar and press “Enter”.
2. Switch to the "Advanced" tab and click the "Settings" button under "Startup and Recovery".
3. Under "Write debugging information" section, make sure the "Small memory dump (128KB)" option is selected.
4. Make sure "%SystemRoot%\Minidump" is in the "Small dump directory" open box and click “OK”.

If the Blue Screen appears again, please refer to the following steps to collect memory dump files:

1. Click “Start”, type “%SystemRoot%\Minidump" (without quotation marks) in “Search” bar and press “Enter”.
2. Go to your Desktop, right-click on it and create a new folder named "Dump".
3. Copy all the memory dump files (looks like [Mini092008-01.dmp]) in Minidump to this folder.
4. Right-click on the Dump folder, click "Send To", and click "Compressed (zipped) Folder".
5. Please send the ZIP file to us.


Done. I guess I'll have to wait for another blue screen.
a b $ Windows 7
March 27, 2012 8:07:27 PM

Allright. In the meantime, I run a program called "WhoCrashed" (http://www.resplendence.com/downloads) on your dump file, it printed out some information on its report page:

Quote:
On Tue 2012.03.27. 3:01:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032612-36753-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0x3B (0xC0000005, 0x0, 0xFFFFF88006FCFE20, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


Unfortunately, it doesn't tell much, googling not helping either.
Maybe if you could run this program, and we could get some clue from other dump files...
(You have to press the big green Analyze button after installation.)
a b $ Windows 7
March 27, 2012 8:27:29 PM

About the other two things we talked about:
- memtest, let's say 2 passes without errors would certainly convince me
- removing the video cards, I don't think they are faulty, but by removing them, *with their drivers*, it would be a step forward

you know... change something, watch carefully. repeat.
March 28, 2012 2:00:30 AM

szaboaz said:
About the other two things we talked about:
- memtest, let's say 2 passes without errors would certainly convince me
- removing the video cards, I don't think they are faulty, but by removing them, *with their drivers*, it would be a step forward

you know... change something, watch carefully. repeat.


I'll try that, I'm sorry for the late reply.
a b $ Windows 7
March 28, 2012 7:04:49 AM

zackb101 said:
I'll try that, I'm sorry for the late reply.

I'm subscribed to this thread, so I'll get the notification, whenever you come up with someting new.
An intriguing problem you have there.
a b $ Windows 7
March 28, 2012 7:10:55 AM

One more thing. In case it's a driver conflict, have you tried browsing in "Safe mode with networking"?
You know, in Safe mode, Windows uses generic VGA drivers (hence the low screen resolution). But that might be just fine for us to see, if you can have it crashed with some web browsing.

The next "extreme" thing I would try, is booting into Ubuntu Live CD/USB, and using it for a while. I certainly wouldn't expect it to crash during browser use (it has Mozilla Firefox included). But if it does, then...

Hey, I'm full of fresh ideas this morning. What about running a virtual OS, VirtualBox or VmWare. I wonder if the browser inside of the virtual OS would still crash.
If it won't, then at least you'll be able to browse the internet without crashing, until you find the solution.
March 31, 2012 5:30:33 PM

szaboaz said:
One more thing. In case it's a driver conflict, have you tried browsing in "Safe mode with networking"?
You know, in Safe mode, Windows uses generic VGA drivers (hence the low screen resolution). But that might be just fine for us to see, if you can have it crashed with some web browsing.

The next "extreme" thing I would try, is booting into Ubuntu Live CD/USB, and using it for a while. I certainly wouldn't expect it to crash during browser use (it has Mozilla Firefox included). But if it does, then...

Hey, I'm full of fresh ideas this morning. What about running a virtual OS, VirtualBox or VmWare. I wonder if the browser inside of the virtual OS would still crash.
If it won't, then at least you'll be able to browse the internet without crashing, until you find the solution.


I got a Blue screen of death and this is the link to the minidump:

http://www.mediafire.com/?q22xqkb5vm18c4b

It should be noted I was running Microsoft Security Essentials Full scan when it happened.

Also I'm noticing Windows Desktop Manager crashing frequently.
a b $ Windows 7
March 31, 2012 6:25:19 PM

This gave the exact same message as the previous one.

Do you have UAC (User Account Control) enabled? How about disabling it for a little while (or rather until the next crash :p ). This "transitions from non-privileged code to privileged code" text gave this idea.
http://windows.microsoft.com/en-US/windows7/Turn-User-A...
March 31, 2012 7:31:58 PM

szaboaz said:
This gave the exact same message as the previous one.

Do you have UAC (User Account Control) enabled? How about disabling it for a little while (or rather until the next crash :p ). This "transitions from non-privileged code to privileged code" text gave this idea.
http://windows.microsoft.com/en-US/windows7/Turn-User-A...


My UAC has always been disabled.
a b $ Windows 7
March 31, 2012 8:42:20 PM

I see...

I'll be out of ideas soon. :)  Have you checked the hard disk drives for errors? If it can't finish in Windows because of crash, then it should be scheduled to the next system start.

Another one, just popped into my head. When you re-installed Windows, did you use the same installer disk that you used for the previous one? Maybe it is corrupt, you could download an iso image, and try a new install with that.

But... err, that may not be the likely cause, because all this crashing wasn't always there. What do we know about the history (I sound like Dr. House now :D ). Was it always like this? I guess not. Can you think of a hardware change that could have caused this?
a b $ Windows 7
March 31, 2012 8:52:08 PM

since your uac is off you could have catch something while browsing the net ,do a full virus scan in safe mode without network and use malwarebytes for spyware. use google and look for browser virus
June 18, 2012 2:25:42 PM

I would really like to know if the OP got a solution to this as this is happening to me now on my new machine I just built :( 
a b $ Windows 7
June 18, 2012 3:42:29 PM

The first thing that comes to mind when seeing this kind of "paranormal" activity is certainly virus or other malware. But the Original Poster had this before and *after* reinstalling his system, that's why I started elsewhere.

@donfarrell
Does the problem come up on a freshly installed system? Any chance that you installed something which could happen to be infected with some malware?
!