Sign in with
Sign up | Sign in
Your question

BSOD Randomly

Tags:
  • Computers
  • Blue Screen
  • Windows 7
Last response: in Windows 7
Share
January 16, 2013 3:33:08 PM

I was given a computer by a friend I knew had this issue prior to him giving it to me. So the random BSODs have been going on for 1-2 years. Hes never really bothered to fix it so I'm giving it a crack.
The BSODs happen at completely random times, even when I'm not on the computer and nothing is running it can do it. It has happened on both Windows 7 64-bit and 32-bit. The system is currently on 32-bit.

Heres the Dxdiag
http://pastebin.com/Wr7T43Mv

And the crash reports from WhoCrash
http://pastebin.com/nE8zhvaA

More about : bsod randomly

January 16, 2013 3:35:52 PM

What are your memory timings?
January 16, 2013 3:44:35 PM

How do I check?
Excuse the ignorance :p 
Related resources
a b $ Windows 7
January 16, 2013 6:38:40 PM

That bugcheck can often be associated with bad RAM. I would start by eliminating RAM as a problem.

Download this - MemTest86+

Burn it to a cd or dvd. If you need software to do this, I recommend - ImgBurn

Restart the computer and boot from this disk. It will start testing your RAM and keep going until you tell it to stop. Let this run for at least a couple of hours, preferably overnight.

If no errors are found, we can move on to looking for bad drivers.
January 16, 2013 6:49:38 PM

Okay I'll run the program tonight and post the results in the morning
January 16, 2013 7:20:02 PM

So from what I gather, you have done a clean install of both Win 7 32Bit and 64Bit but still having the same BSOD issue ?

Please go to Windows 7 "Action Center", select the "Maintenance Tab", then go to "View Reliability History" link.

This should open some kind of a graph with Blue Informational Events & Red Critical Events Circles.

Identify a date that corresponds to one of the Critical Event Circles then click it. This should further open both type of events at the bottom of the graph.

Now the "Action" section of the table should allow you to view Technical details of the issue and be able to copy.

Please post the error here if possible
January 16, 2013 8:19:39 PM

Okay so I've found a couple of the critical events. Here are some of the descriptions.

Quote:
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e (0xc0000005, 0x828b3c50, 0x8e147974, 0x8e147550). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 011613-25724-01.


Quote:
Problem signature
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 2057

Extra information about the problem
BCCode: 1000007e
BCP1: C0000005
BCP2: 828B3C50
BCP3: 8E147974
BCP4: 8E147550
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1


Quote:
Description
Faulting Application Path: C:\Windows\System32\dwm.exe

Problem signature
Problem Event Name: APPCRASH
Application Name: Dwm.exe
Application Version: 6.1.7600.16385
Application Timestamp: 4a5bc225
Fault Module Name: dwmcore.dll
Fault Module Version: 6.1.7600.16385
Fault Module Timestamp: 4a5bda08
Exception Code: c000001d
Exception Offset: 0001720f
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 2057
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
January 17, 2013 1:00:59 AM

Use a program called CPUZ to get your memory timings. One of the tricks to try when having random BSODs that are unreproducible on command, is to make sure your memory timings are nice and loose, including having a 2T command rate.
January 17, 2013 9:11:27 AM

Do you have any of the following hardware installed :

Graphics Card
TV or Freeview Card Installed

Can you please tell me the Specs of your PC ?
January 17, 2013 10:25:07 AM

I've got a graphics card installed, not a TV or Feeview card. Specs should be in dxdiag I linked.
January 17, 2013 11:02:52 AM

The cause of your BSOd is the Graphics Card. Either the Ram on the Card is bad or the Drivers are corrupted.

Are you using Windows 7 Default Graphics drivers or ATi Specific drivers from their website ?

The best course of action is to :

1. Uninstall any ATi Drivers on the system, find a Driver Sweeper or Total Uninstaller Software, then remove every trace of the ATi drivers.

2. Go to Device Manager and uninstall the windows Default Graphics driver, then reboot the PC so Windows 7 can install a new Default Graphics Driver.

3. I also realize there are quite a lot of BIOS updates for this motherboard and you might want to make sure you have all of them as they do fix some major issue including some for DRAM and Ram Compatibility. You can find them all in the link below;

http://www.gigabyte.com/products/product-page.aspx?pid=...

If successful, test the PC with the Default Driver to see if the BSOD still exists.
January 17, 2013 12:17:08 PM

Right all those steps have been completed, will let you know if it BSODs.
January 17, 2013 12:20:53 PM

I also just got CPU-Z to update you on the timings.

DRAM Frequency: 553.3MHz
FSB:D RAM: 1:2
CAS# Latency: 5.0 Clocks
RAS# to CAS# Delay: 5 Clocks
RAS# Precharge: 5 Clocks
Cycle time: 15 Clocks
Row Refresh Cycle time: 68 Clocks
Command Rate: 2T
January 17, 2013 1:33:54 PM

Okay the computer just BSOD
January 17, 2013 1:46:17 PM

From what I can see, your motherboard does not have Integrated Graphics. Am I right ? Is the Win 7 on the PC a Clean install ? An finally, No offence but your Win 7 copies are legit or at least clean right ?

If that's the case, the fault is with your Graphics Card. The only other thing I can suggest is swapping Ram modules or restarting the PC with just a module first, if the BSOD still exist, then use a different module or slot and vice versa.

Another major thing you can do if you haven't already, is uninstall any current Anti Virus software, then install Avast Free then do a Boot Time Scan if the Current OS is not Clean installed or has been used by someone else previously. I'm getting the feeling there might be an infection here.

Let me know if anything changes. By the way do you have a spare Graphics Cards to test ?
January 17, 2013 3:53:18 PM

Its all a clean install. Installed it myself the other day. Its been happening with and without loads of different anti virus software. I'll try to find an old graphics card laying around and report when its done
January 17, 2013 5:48:05 PM

Please keep me updated when you try a different Graphics Card.

Good Luck and hopefully that solves the BSOD issue.
January 18, 2013 9:06:54 AM

Right the new card was installed this morning, no BSOD yet, lets hope it keeps going like this :D 
January 18, 2013 9:12:49 AM

Okay spoke to soon, just got a BSOD. Its not just a BSOD either anymore, its started to just completely freeze and the only way to get it to do anything I have to hold the power button down.
Also the motherboard does have integrated graphics
January 18, 2013 12:11:24 PM

Have you tried with the Integrated Graphics Card on the Motherboard ? I suggest you stick with the New Graphics Card then do a Registry clean as it didn't give you any BSOD's for quite a while :

I'm guessing you used a good uninstaller to completely remove remnants of the old ATi drivers before installing the new Card and Drivers

Here are a couple of suggestions :

1. Find a very good Registry Cleaner and give your Registry a very good clean (Run in both Safe Mode and in Windows)
2. Also can you check and Post Idle Temps of the PC please ? (CPU, GPU & any other Temps available)

Can you run the PC long enough to know if the frequency of the BSOD has changed ?

Its starting to look like a definite Software or Driver Issue but I don't want to rule out Hardware yet.

a b $ Windows 7
January 18, 2013 4:48:13 PM

Quote:
0x0000007E SYSTEM_THREAD_EXCEPTION_NOT_HANDLED


So driver or RAM, possibly GPU (especially if the Desktop Window Manager is always the module that crashes).
a b $ Windows 7
January 18, 2013 4:53:11 PM

Sorry for not getting back to this thread earlier. Quick suggestion for clearing out old drivers - Driver Sweeper from Guru3D

Could your try clean booting and see if it continues to BSOD.

Just follow Step 1 in this guide - http://support.microsoft.com/kb/929135
January 18, 2013 6:35:40 PM

Will need to wait until tomorrow to remove the graphics card and just run without one. But I do have the reports from WhoCrash

http://pastebin.com/hn6vr8Hb
January 18, 2013 7:19:22 PM

Once again, everything leads to a Graphics Driver as I can see from the WhoCrash report.

If you haven't done the registry clean already, I suggest you get onto that as there is still a corrupted driver stuck in there creating issues.
January 18, 2013 8:02:32 PM

Is CCleaner a decent enough registry cleaner?
January 18, 2013 11:00:15 PM

Yea CCleaner is not bad but try Wise Registry Cleaner. I like Wise Registry Cleaner because it doesn't delete important items in registry, and its free

http://www.wisecleaner.com/index.html

If you are comfortable with CCleaner then use it.

January 20, 2013 7:22:40 AM

Well I went to use the integrated graphics card, realised it didn't have one. Bit of a fail there. So I've put the original graphics card back in because its just better.
If its any help, I mainly use the computer for playing WoW and if the computer isn't BSODing then WoW is just crashing with error code #132
I'll leave the computer on overnight tonight and post temps in the morning. I've also ran CCleaner yesterday morning but still BSODing
January 20, 2013 2:06:00 PM

As I said in an earlier post, I was aware your Motherboard did not an onboard Graphics Card.

I believe error #132 is DirectX error. Try the following steps when playing WoW and let's see :

Check if IPV6 is checked in your Network Card Properties in Windows 7
Change WoW DirectX setting from DX11 to DX9 and restart the game (Instructions Below)
Go into WoW settings and make sure the "Use IPV6" setting is checked

Start the WoW Launcher
Click on "Options" located in the top left hand corner
Select "Game Preferences"
Select "DX9" from the "Graphics API" drop down menu
Click OK

Let me know how it goes.
January 20, 2013 3:05:08 PM

Right all those corrections have been made, only needed to turn on IPV6 within WoW. Tons of BSODs today.
http://pastebin.com/Q7AGCWSn
January 20, 2013 4:01:54 PM

I believe the spare Graphics Card was better than the current one as I don't think you were having so many BSOD's with that one.

You might want to stick to the other card for now as we are only trying to get to the bottom of the issue.

BSOD is caused by the same driver as before. Have you tested different Rams apart from what you already have in the system ?

You have to be able to tell which Graphics Card causes BSOD's more frequently and from what I have seen, the Cards you have now seem to crash more than the spare.
a c 426 $ Windows 7
January 20, 2013 4:07:43 PM

Update your bios to the latest version.
January 20, 2013 5:26:30 PM

This is really sounding more like a motherboard problem...
January 20, 2013 5:49:31 PM

As far as I am aware the bios is completely up to date. I haven't got any other ram to test that either :/ 

If it is sounding like a motherboard issue, can anyone provide links of a replacement? Can't seem to find one.
Doesn't have to be the same board, just one that'll work with everything
January 20, 2013 8:41:12 PM

The Asus P5LD2, MSI 945GCM5-F V2, Gigabyte G41M-ES2L. Or you can just buy the same board you have now.

Please do some research on the boards I mentioned above, just to make sure your Rams and everything else is compatible.

A word of advice, find at least a different Ram module to test before you take the motherboard replacement route.
January 21, 2013 2:24:00 PM

I did a clean boot last night, let the computer on over night with nothing but MS Paint open just so I know if it BSOD during the night at all. Got up and the computer was still on, and paint was still open. Opened up WoW, within an hour it had BSOD. Any program I can run overnight on a clean boot for testing?

Oh and today, other than the BSODs and WoW crashing the display driver has been crashing every now and then.
January 21, 2013 2:34:26 PM

Just for $#!^s and giggles, do you have a spare power supply to test with? Last time I encountered a problem that was this weird with BSODs, the power supply was occasionally dropping the voltage on one of the rails.
January 21, 2013 2:48:12 PM

Well I've got 2 computers, my own personal computer and my girlfriends (broken one). So I could transfer my PSU into hers
January 22, 2013 1:39:56 PM

Put a spare PSU in this morning at 08:30am. Worked fine up till I put the side panels back on, about 20 minutes ago. Since then, computer has frozen and the display driver has crashed.
January 22, 2013 1:58:23 PM

now bsod?????
January 22, 2013 2:02:58 PM

Yep, no BSODs yet
January 22, 2013 4:10:19 PM

Good to hear. At least if there is no BSOD then we know the PC has multiple issues causing both the BSOD and Freezing.

If that ends up being the case, you will have to deal with them as 2 separate issues
January 22, 2013 4:21:11 PM

Well I've removed the side panel again, and since then no freezes, or display drivers crashing

Edit: Still freezing. But still no BSOD. If this continues I'll put this down as solved tomorrow :) 
January 22, 2013 9:44:29 PM

As long as you are happy with the current state and result, its always good to see the OP's issue fixed.

Thanks to "iknowhowtofixit" He does really know how to fix it :) 
January 23, 2013 1:27:49 AM

I'm not perfect, but I've seen some pretty crazy hardware issues with PCs and workstations....
January 23, 2013 8:29:55 AM

Don't jump the gun yet, just got a BSOD :p 

On Wed 23/01/2013 10:28:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012313-21855-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x18C04)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF929A4C04, 0xFFFFFFFF91D4B9F0, 0xFFFFFFFF91D4B5D0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
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 Wed 23/01/2013 10:28:56 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!KeBugCheckEx+0x1E)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFFFFF929A4C04, 0xFFFFFFFF91D4B9F0, 0xFFFFFFFF91D4B5D0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ntkrpamp.exe .
Google query: ntkrpamp.exe SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
January 23, 2013 10:36:17 AM

Do you have a totally different Windows 7 installation CD or even an Evaluation version to try ?

I have a feeling you are using a Windows 7 installation with some infused drivers or something of the sort.

If you are sure the Windows 7 Installation is clean, then I strongly suggest you look at your Ram. You might need a totally different brand. What Brand of Rams do you have on the PC now ?
a b $ Windows 7
January 23, 2013 10:57:22 AM

Ovibag said:
Don't jump the gun yet, just got a BSOD :p 

On Wed 23/01/2013 10:28:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012313-21855-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x18C04)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF929A4C04, 0xFFFFFFFF91D4B9F0, 0xFFFFFFFF91D4B5D0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
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 Wed 23/01/2013 10:28:56 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!KeBugCheckEx+0x1E)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFFFFF929A4C04, 0xFFFFFFFF91D4B9F0, 0xFFFFFFFF91D4B5D0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ntkrpamp.exe .
Google query: ntkrpamp.exe SYSTEM_THREAD_EXCEPTION_NOT_HANDLED


This is started getting me thinking if maybe there is not enough power coming from the rails in the PSU and possibly there is a wire touching something it shouldn't (because of the system not freezing up with the side panel removed and it does with it on).

Where is this unit located exactly in the room its in and what is it sitting on? I know this sounds funky but it's almost like you have an arc happening and making the video card hiccup.
January 23, 2013 11:41:02 AM

Yea "hedwar2011" could be right. Can you post a picture of the Inside of the Case ?
January 23, 2013 12:29:16 PM

Not at home at the minute so picture will have to wait till this evening. Computer is just sat beside the desk, on the floor (carpet). My friends floor where it was before I owned it is wooden.
      • 1 / 2
      • 2
      • Newest
!