Tweaking.com Support Forums
Main Forum => General Computer Support => Topic started by: 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
-
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 :wink:
Shane
-
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.
-
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 :wink:
Shane
-
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
-
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
-
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
-
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.
-
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?
-
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
-
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.
-
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
-
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.
-
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
-
That is an excellent idea. Will do.
-
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.
-
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
-
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
-
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.
-
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
-
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
-
Is the video part of the mother board or is it a card?
Shane
-
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.
-
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
-
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.
-
Youtube videos use flash, which uses the video card for performance (Hardware Acceleration). Steam games (All games) use the video card. And when in safe mode the video card drivers are not loaded.
So far the common factor is the video card/drivers.
One test for youtube and flash would be to turn off the hardware acceleration
http://www.macromedia.com/support/documentation/en/flashplayer/help/help01.html
Shane
-
My Steam problems were a mod conflict in Skyrim. Not related to the core problem, I don't think. I solved it and Skyrim runs great now.
I deactivated hardware acceleration....and I'm waiting for a crash. Nothing yet. I'm about to hit YouTube hard.
Still this is the pattern: I make a fix, it is fine for a time, then it comes back, as if something is reinstalled.
We'll see. Tonight, so far, I am sailing fine.
Thank you.
-
Browsers, Flash ads crashing all over the place tonight, including here. Hardware accel off.
Now Steam crashing, too. Something is affecting everything.
BTW, I've also reseated my RAM and cards. I'm going to fool around with the sound settings and driver
Just in....
I went into Safe Mode with Networking. All was well. Then, I re-enabled the Flash plugin in Chrome. Flash crashed.
So I reverted to a Restore save from yesterday, and everything is working fine. What loaded in the last 24 hours?
-
What about temps? How is the heat on the cpu and card during all this? After all when gaming and videos the video card will heat up and if it gets hot things will crash. Same for the CPU. Heat is one thing I dont think we checked all the way.
You need to see what the temps are at the times of the crashes.
Shane
-
I monitor temps all the time. They rarely go above 40 degrees C.
-
Damn, was hoping it was that LOL
Ok, now we have to start looking at hardware. Had drive has no bad sectors and memory tested good.
So before we say motherboard lets verify if it is the MB or the video card with 1 simple test.
Do you have a different video card you can try?
By trying another video card, if the problem goes away we know it is the video card. If the problem stays it is the MB.
The MB itself also can heatup, I know some of the chips that have heat sinks can get too hot. I notice all the crashes only seem to happen when the system is under more of a load. Granted playing videos isnt much of a load, but any game would be.
It is always possible it is the CPU as well, but normally when it is the CPU we get a total system crash. MB we normally get a system crash as well, and heck even with any type of hardware we can get a total system crash. But depending at what part is bad then the game or program using that part of the hardware would be the only one to crash since Windows wasnt using it.
Did that make any sense at all? LOL
Shane
-
Makes perfect sense. Just last week, I installed a new video card, and I've had this crashing thing for a lot longer than that. So I think we can rule out the video card.
I use a nice utility called Core Temp to monitor my, um, core temp. http://www.alcpu.com/CoreTemp/ Always low readings.
My motherboard is a Gigabyte. Maybe they have an update and diagnostic tool of some kind.
Turns out, I'm not alone: http://community.spiceworks.com/topic/361282-all-browsers-crashing-randomly
Somebody found a fix:
http://www.bleepingcomputer.com/forums/t/439021/both-firefox-and-ie-crash-upon-launch-even-in-safe-mode/
-
Unless you got infected again then yes. But when you did the fresh install did you make sure to delete the partitions first in the setup? This way the file system and MBR are destoried getting rid of any MBR virus.
TDSSkiller is one tool I use and the other is malwarebytes anti rootkit and then combofix. Those 3 normally get the job done.
So after the fresh install everything worked, did you somehow get your self infected again? If not then it is a hardware problem, if somehow you did then it is a virus problem. But even with a virus I have never seen it crash a game. Normally the rootkits that TDSSkiller look for are ones that hijack the network and dns and redirect your search results to bull crap pages to make money from ads. TDSS rootkit use to have a side effect where in the device manager the hard drives or the cd rom drives didnt show up at all. When ever I see that I know it was the TDSS rootkit.
Shane
-
Interesting stuff.
I already forgot I did a clean install, lol. Yes, partitions went first. I have no idea whether I'm infected. AVG, MalwarebytesPro, and Glary Utilities all scan clean.
The fact that I crashed in Safe Mode is kind of freaky. I was hoping it was RAM, but two memtests say no.
The game was crashing because I had conflicting mods. I don't think it has anything to do with this issue.
Thanks,
Tim
-
Safe mode can still heat things up, and if it is hardware it will crash in safe mode as well.
AVG sucks lol Run the 3 tools I do just to double check things before we go digging into hardware.
Shane
-
Ok, will do.
Yeah, I don't normally even run an antivirus, just MB. I just downloaded AVG for quick scan. It's gone now.
-
http://www.av-comparatives.org/
I honestly just run Microsoft Security Essentials :-)
Shane
-
TDSSKiller found nothing
Malwarebytes Rootkit stopped working halfway through, twice.
ComboFix deleted a folder and a dozen files called AutoCompletePro, as well as a few orphans
-
Now that is interesting.
After combofix and a reboot can malwarebytes finish its scan?
Shane
-
Just got home (I'm in Virginia). I'll let you know about the MB
...
Nope. Rebooted and ran MB three more times. It stopped working in different places.
.....
Having trouble posting here. Constant crashes.
Ran Intel Processor Diagnostic Tool and passed the CPU load and Temperature tests.
Now all my games are crashing. Has to be hardware.
--------
Games, browsers, everything is now crashing. Must be hardware.
-
Just to cover all bases, out your old video card back in.
Shane
-
Really? I took it out my old card because of the crashing. I've also tried numerous drivers. In fact, I also tested a third vid card I have. Got crashes with all of them.
Well, I have to take out my new card anyway to put in my new rig.
-
I followed this conversation for a while and it seems now we're down to the memory. I had a similar problem. I had 2x 4 GB of memory. The 2 memory modules were OK but the hardware that controlled one of the 2 modules/banks stopped working properly in november last year. After removing one memory module the system was back to normal.
You have 8 GB of memory. But how many memory modules ? Remove (one by one) those memory modules. It gives you a clue which memory bank is faulty. Perhaps more than one memory bank hardware is faulty.
-
Thanks for the advice. I have 4x2 GB. I did a memtest for each individual stick and got no errors. But, yeah, it seems to me it almost has to be a memory issue.
I'll take your advice and just remove them one by one and reboot and see what happens. Much appreciated.
-
And please DO post a reply when you've solved your problem.
-
Not sure I will solve the problem, but I'll post if I do. I will try your RAM idea when I get home tonight.
Also, if you Google this problem you'll see that a fair number of others have identical symptoms. Most find a solution, then the problem returns. And that is my experience, as well.
-
No solution. I now have an entirely new rig and loving it. I may go back to my old computer and try to find out what was causing the crashes, but I honestly don't want to spend hours of my life doing that.
There appear to be many others with a similar problem, so it is probably something pretty subtle.
Thank you very much for your time and help. Really amazing the service your provide here.
All the best,
Tim
-
It is differently a hardware problem on your old rig.
Either weak power supply, faulty CPU or bad motherboard. But without replacement parts to swap out to find out which one it is then you may never know for sure.
Honestly, if you tried a different power supply and the problem still happened I would say it is the motherboard for sure. The reason why I say that is I have seen plenty of times where a power supply is going bad and isnt giving out enough power and so hardware doesnt work like it should and things crash or lock up. I have also seen parts of a motherboard go bad. I had a laptop a few years back that blue screened on anything you tired. I tested memory and hard drive and couldnt find what was doing it.
I then got a hold of a hardware tester software that tested everything and I mean everything, things like DMA access on the motherboard and all kinds of different sections. While running that test EVERYTHING came out fine, then it got to the DMA test and sure enough it failed every time. DMA is on the motherboard and is used for direct memory access. And so I found the problem, it was the motherboard. But I would have never of known why the board was bad without that tester.
I still use a older version of the program after all these years, it is expensive to get the new one lol
QuickTech Pro PC Diagnostic Tools
http://www.uxd.com/qtpro.shtml
Shane