Author Topic: All browsers and random games crash (Read 41309 times)

timscape · « **on:** January 20, 2014, 08:54:31 am »

All browsers crash randomly (CTD), as do some games. Once in a while I get the BSOD--but today I have had three.

I've spent many hours chasing this down and trying all sorts of fixes.

Sometimes it goes away for a day or following a fix, then it comes back. I switched out drivers one by one, and now I"m using your tool to set my services at their defaults (but your program said it was done in 14 seconds, but when I hit stop, it says it won't stop until it is done. It has just been sitting there for half an hour now)

Any ideas?

Win 7 home premium
8GB RAM
Intel dual core 2.6ghz
Radeon HD 7850 2GB

Thanks,

Tim

Shane · « **Reply #1 on:** January 20, 2014, 10:35:05 am »

Lets first find out what caused the blue screen

This tool should be able to tell you what caused the last blue screen
http://www.resplendence.com/whocrashed

Or it could be something as simple as a bad memory stick. But lets go one step at a time

Shane

timscape · « **Reply #2 on:** January 20, 2014, 11:57:18 am »

Thank you, Shane, you're great.

Here's the report. (I'll wait to hear back from you before I buy the pro version of WhoCrashed, if I can affford it) -- Tim

System Information (local)
--------------------------------------------------------------------------------

computer name: TIM-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: EP45-UD3L, Gigabyte Technology Co., Ltd.
CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU E7400 @ 2.80GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 8588353536 total
VM: 2147352576, free: 1924296704

--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 1/20/2014 2:55:27 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012014-77579-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xD1 (0xFFFFFFFF, 0x2, 0x8, 0xFFFFFFFF)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 that cannot be identified at this time.

On Mon 1/20/2014 2:55:27 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x2F89)
Bugcheck code: 0xD1 (0xFFFFFFFF, 0x2, 0x8, 0xFFFFFFFF)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

On Mon 1/20/2014 2:13:19 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011914-31122-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xD1 (0xFFFFFFFF, 0x2, 0x8, 0xFFFFFFFF)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 that cannot be identified at this time.

On Sat 1/18/2014 4:17:20 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\011714-49233-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xD1 (0xFFFFFFFF, 0x2, 0x8, 0xFFFFFFFF)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 that cannot be identified at this time.

--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

4 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.

Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

Shane · « **Reply #3 on:** January 20, 2014, 12:04:52 pm »

DRIVER_IRQL_NOT_LESS_OR_EQUAL

means a driver problem. BUT a driver problem can be caused by bad memory or bad hardware.

First thing to do is to test the memory in the system and then check the hard drive for any bad sectors.

Try the MS memory tester
http://www.softpedia.com/get/Tweak/Memory-Tweak/Microsoft-Windows-Memory-Diagnostic.shtml

You will follow the directions and burn it to a cd, then boot off the cd and have it test.

The test never ends, so let it complete a few passes and if no errors then memory is fine and we will go from there

Shane

timscape · « **Reply #4 on:** January 20, 2014, 12:30:40 pm »

Wow, OK. I'm not sure I even have any CD-Rs in the house anymore. The windows Memory Diagnostic Tool in Win 7 is not good?

At any rate, this could take a while. Off to the store, I guess!

Tim

Shane · « **Reply #5 on:** January 20, 2014, 12:44:50 pm »

The tool in Windows 7 is the same one, just good idea to boot off a cd and not have anything from windows loaded up

Shane

timscape · « **Reply #6 on:** January 20, 2014, 01:59:19 pm »

First, thank you so much for the help.

Next, the memory test showed no errors. I ran Windows Scandisk on a reboot with no errors on my hard drive.

Now, it's Sherlock time, eh?

Tim

timscape · « **Reply #7 on:** January 21, 2014, 04:30:21 pm »

I am replying to my own reply (and my browser just crashed twice). Went into my computer in safe mode with networking and could not replicate the problem.

timscape · « **Reply #8 on:** January 22, 2014, 09:58:28 am »

I ran a portable utility called BlueSceenView that displays crashes and the drivers involved.
Attached is the report on my last three crashes. Not sure what to do about it. Do you have some advice?

Shane · « **Reply #9 on:** January 22, 2014, 12:29:02 pm »

So you couldnt get it to crash in safe mode?

Safe mode only loads the bare minimum drivers and programs, so at least we know it should be windows but instead a driver or program.

The only thing to do is to try one thing at a time and go down the list till the problem goes away and we know which driver or program caused it.

First thing would be to uninstall the antivirus and reboot and try it, a lot of antiviruses install their own system drivers and such. So thats the first to test.

After that if you still have the problem is to us msconfig.exe and disable any and all startup programs and services you dont need to see if it might be a program doing it.

And then if that doesnt work it is time to start removing drivers, video first and then use the MS standard drivers for it and then move on to sound.

Shane

timscape · « **Reply #10 on:** January 22, 2014, 12:41:56 pm »

Thanks, Shane. I used the Driver Verifier built into Windows and it told me I have no uncertified drivers on my system.

I have only one thing in my Start menu, the video card's Catalyst program. It is now off.

Are you familiar with the BlueScreenView utility I mentioned?

I'm thinking I should reinstall Windows. I haven't done it in a couple of years.

Shane · « **Reply #11 on:** January 22, 2014, 12:46:18 pm »

I reinstall my system once a year lol.

Even though the drivers are all signed doesnt mean there might be a wrong version file somewhere or a bad reg setting. Could even be a rootkit virus that installed a low level system driver on the system.

When I had a system of mine a while bad crash during a game it was because I had the cpu over clocked. The another time it was a bad video card, but the blue screen would show the video driver file when that happened.

Some times it can be heat, over clocking, bad hardware or just OS that could use a reinstall. Now if you did a reinstall and you STILL had the problem then you know it is bad hardware for sure.

Shane

timscape · « **Reply #12 on:** January 22, 2014, 01:12:36 pm »

A number of years back, another computer was getting chronically worse and worse, doing crazy things--game graphics were tearing, desktop would vanish. Turns out it was the power supply--the last thing I tested.

This is applying the process of elimination to leave the guilty standing alone--the Sherlock Holmes method.

Out loud: I think I'm in the mood for a reinstall.
Inside: I think I deserve a new computer.

But I'll reinstall first. Thank you.

Shane · « **Reply #13 on:** January 22, 2014, 01:16:45 pm »

You could try a repair install first.

First you need a cd with SP1 already on it, you can grab it here
https://sites.google.com/site/linuxlablibrary/windows-iso

Then follow this
http://www.sevenforums.com/tutorials/3413-repair-install.html

Shane

timscape · « **Reply #14 on:** January 22, 2014, 01:30:09 pm »

That is an excellent idea. Will do.

timscape · « **Reply #15 on:** January 22, 2014, 05:29:13 pm »

I did the repair/upgrade. Near the end, it rebooted and opened a browser...which crashed. Then it told me my version of Windows was not genuine. I had to close that out and go to Microsoft site to validate my install, which it did.

I did find out that Framework 4.5 needed to be reinstalled, but nothing else enlightening.

We'll see if this works, but I'm not too confident.

I have a good tutorial on clean boot testing, if this doesn't work. I have a feeling I'm heading toward a reformat.

Thanks again.

Shane · « **Reply #16 on:** January 23, 2014, 10:01:48 am »

The repair install may have kept the drivers and so that could show that it is a driver problem.

ONLY way to know for sure is a fresh install. Backup your non replaceable files, and when you do the install make sure to delete the partitions and have windows recreate them. This way if there is some sort of boot sector virus it will get wiped when you kill the partitions

Shane

timscape · « **Reply #17 on:** January 23, 2014, 06:23:33 pm »

No crashes all day--browsers, games, Steam, nothing.

Still, I'm up for a reinstall. I've been preparing for it for a week.

Thanks for your kind assistance. I'll mark this solved after a few more days of pushing it.

Best,
Tim

timscape · « **Reply #18 on:** January 25, 2014, 11:52:37 am »

Update. Browsers and games were still crashing. I was looking at the drivers in Device Manager when a screen pops up, telling me that .NET Framework 4.5 is damaged and I am not to restart my computer until setup is complete.

So I waited. It felt like too long, but sure enough, the screen vanished and I was asked to restart. That was 10 hours ago. No crashes, and I have tried.

...........5 hours later, the crashes continued.

Shane · « **Reply #19 on:** January 27, 2014, 11:44:35 am »

A repair install does keep drivers. So a fresh install may be needed after all.

If you still have crashes after a fresh install then it is a hardware problem for sure.

Shane

timscape · « **Reply #20 on:** February 01, 2014, 04:28:25 pm »

Update.

I did a fresh install. It was fine for a couple of days, but still I loaded very few applications and files.

Today, my browser crashed twice. Then BSOD. The Events Log mentions a WMI error message. Microsoft has a good WMI Diagnostic Tool, but it is just too complicated for me to handle. Their directions don't even mention how or where to install it (that I can find).

I ran a 8-test Memtest 86+ for each of my four chips of RAM. Clean. I downloaded a hard drive analyzer that took and hour and a half and told me my hard drive has no errors. I have a multimeter and my PSU is apparently in fine shape.

What's left? Motherboard? A driver that self-installed? I routinely turn off all automatic updates of anything. My msconfig start menu has one item in it, Malwarebytes. Nothing at at all on my PC is scheduled to run, although I can't prevent everything. Chrome and Google products update whenever they want.

So I ordered a new computer. I'll still tinker with it my current one, but I can't afford the time anymore.

Just thought you'd like an update of this mystery.

Tim

Shane · « **Reply #21 on:** February 03, 2014, 01:10:13 pm »

Is the video part of the mother board or is it a card?

Shane

timscape · « **Reply #22 on:** February 03, 2014, 01:49:37 pm »

I have a brand-new Radeon HD 7970 I installed last weekend. Didn't solve the problem. I've tried various drivers. I have had this problem for about 6 weeks now.

It's funny that after the clean install, it ran great. Then one morning, bam. I'm wondering whether something corrupt self-installed again. I've also run numerous virus and malware checks with Pro versions of each.

As I said, I was due for a new rig anyway. I built it in 2008. Still, I'd love to solve the mystery.

Thanks, Shane.

Shane · « **Reply #23 on:** February 03, 2014, 02:17:39 pm »

Repair install - still happens, all programs where kept.
Fresh install - Worked for a few days then started happening again, hardware doesn't seem to be the problem, possible program or add on for the browser perhaps?

Also what about DEP do you have it enabled?

Shane

timscape · « **Reply #24 on:** February 03, 2014, 03:10:57 pm »

I have browser plugins and extensions off. But since this happens to all browsers, it must be something in common with them. It also happens to Steam games and YouTube videos.

DEP is on by default for essential Windows programs and services.

Maybe tonight, I'll again see if I can replicate it in Safe Mode with Networking.