Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Computer locking up, no BSOD but screen turns a solid color


  • Please log in to reply
14 replies to this topic

#1 Alyj

Alyj

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:01:55 AM

Posted 28 June 2013 - 02:16 AM

Hello. I have an issue that started about a 3 and a half weeks ago, and I have so far not been able to fix it or figure out what is causing it..I've posted on another forum and have received no help so I found this place and hope you guys can help me!

 

My computers specs are:

case: rosewill ranger-m dual fans mini tower
Windows 7 64-bit
Intel i5-2400
Nvidia geforce gtx 550 Ti
ASRock H77 Pro4-M
16GB DDR3 ram (g.skill ripjaws series)
Corsair 700-watt power supply
Western Digital HD (WD1002FAEX)

also:
razor naga epic
razor anansi
western digital my book external HD
sennheiser wireless headphones

 

I sort of have a dual monitor set-up; I have an Acer monitor as well as a Cintiq that is always on. The issue I am having is that my computer will randomly freeze up and each screen will turn a solid color, such as white, brown, gray, black, purple, pink, etc (if it matters, neither screen is the same color when this happens) - now, my computer doesn't actually freeze - everything is perfectly fine until the screens blank out. There is no sluggish mouse movement, lag, or anything like that. The reset button on the computer works instantly to restart it and it boots up fine with no errors. (UPDATE: Tonight, the reset button no longer responds. I have to hard shut-down the computer.)

 

When I first updated the graphics card drivers, I thought I had fixed the problem, I went over a week without it doing it again - now, tonight, it's done it 3 times. Each time it has happened, as far as I can recall, I have had world of warcraft open. (UPDATE: Tonight it has happened one time shortly after another crash, this time with nothing open. Every other crash had been with warcraft open, except this one.)

 

I have so far:
~Done windows updates
~Updated graphics card drivers
~Updated anti-virus
~Scanned for malware
~Monitored temps, they all seem fine
~Cleaned out computer (dust)
~Reset graphics card
~Made sure all fans are running
~I've checked the event log, and all that is there around the time of the crashes is event ID 41, which appears to just be a generic unexpected shutdown. There are things under the error logs, but nothing that jumps out

~Ran memtest86 for over 8 hours, no errors were reported

~Ran Prime95 stress test - the first time I started this on "Blend", my computer crashed in the same manner in less than a minute, however I had WoW open in the background. The second time I ran it, on Blend once again, it has been doing fine - it is currently running - for about 30 minutes now. I don't have WoW open.

 

 

I looked in my "important messages" for Windows and I saw this:
"Problem: Video Hardware Error"

 

Here is the information whocrashed gave me:

On Tue 6/26/2012 8:17:10 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFFA800E5D6028) 
Bugcheck code: 0x124 (0x0, 0xFFFFFA800E5D6028, 0xB2000000, 0x81000402)
Error: WHEA_UNCORRECTABLE_ERROR
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). 
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue. 
A third party driver was identified as the probable root cause of this system error. 
Google query: WHEA_UNCORRECTABLE_ERROR

 

As far as temperatures go, my graphics card is about 60C when idle and reaches about 73C when I have Warcraft open. From what I read, these are normal temps for my card.

My processor is around 40c. The highest is is reaching under stress testing is 79C. 

I have monitored these extensively and the few times I've looked right before a crash, they were all low/normal, so I do not think it is a heating issue. This DID seem to start very shortly after a forced windows update.

 

I tried to upload the memory.dmp file I have, but it is over the limit (zipped).

 

 

 



BC AdBot (Login to Remove)

 


#2 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,470 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:11:55 PM

Posted 28 June 2013 - 07:21 AM

Did you uninstall the old Nvidia drivers before updating the drivers?

 

It is also important to uninstall the graphics driver last!


Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#3 Alyj

Alyj
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:01:55 AM

Posted 11 July 2013 - 01:55 AM

Hi, I am still having issues and they seem to be accelerating... 

 

I did uninstall old drivers first.

 

New problems:

For the past 3 nights now, the crashing has become a lot more alarming! Now, when I experience this crash, I can shut the computer down with the power button held but then it will not boot back up for several minutes. I push the power button, and the fans come on(all fans except the CPU fan come on), the lights (the light on the power supply, and the lights on my fans), however, nothing else comes on. After that, if I hold the power button, it will no longer shut off - I must flip the switch on the power supply, or unplug the power. This will go on for several minutes, before it finally does boot up. 

 

Now, suddenly, my computer is no longer reading all of my ram. It is only reading 8 out of the 16 gigs. The ram doesn't seem to be bad... if I go into my bios, and go to the system browser, it shows me a map of the mobo and everything installed on it; here, it shows that all 4 banks have ram in them, and it shows their size and name, so it IS SEEING IT still. However, in the start up information and under my computer, it only shows 8gigs. Trying to resolve this issue, I discovered that it seemed some wires were not acting properly in the case.

 

Tonight, while trying to fix the ram, I started out by removing all but 1 stick. When I tried to boot it up this way, there were 3 beeps, and it would not start. I put all the sticks back in, and then it would boot up, but still only reading 8 gigs. After that, I tried booting with only 2, and this is when my computer would no longer boot at all and we spent a good 2 hours trying to get it to boot up trying different configurations for the ram slots. Again, the lights and fans would power up, but nothing else. Eventually, the light on the power supply started blinking, and we noticed when we moved the wires it would stop or start the blinking again (when left alone, it just kept blinking, over 12 times before we flipped the switch). We moved all the wiring around after this and we also changed the PCI cable that goes to the graphics card, and after this the computer booted right back up again. Still, however, it is only reading 8 gigs. 



#4 th3fall3n777

th3fall3n777

  • Members
  • 364 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Wisconsin
  • Local time:12:55 AM

Posted 11 July 2013 - 02:15 AM

I'm not sure if you have tried this or not, but have you ever used Blue Screen View?  It's an awesome freeware utility that will locate the mini-dumps and full dumps on the PC and put together an intelligible report for you to browse.  http://www.nirsoft.net/utils/blue_screen_view.html

 

It might point in the right direction.



#5 Alyj

Alyj
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:01:55 AM

Posted 11 July 2013 - 02:21 AM

Hi th3fall3n, I did install that program as well but it seems to do the exact same thing WhoCrashed does? So it is giving me the same information. But, I do want to note now that I've looked at this again, is that there doesn't seem to be any crash reports after 6/26/13, despite having many crashes since then.

 

This is the last WhoCrashed report, on 6/26:

On Tue 6/26/2012 8:17:10 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFFA800E5D6028) 
Bugcheck code: 0x124 (0x0, 0xFFFFFA800E5D6028, 0xB2000000, 0x81000402)
Error: WHEA_UNCORRECTABLE_ERROR
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). 
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue. 
A third party driver was identified as the probable root cause of this system error. 
Google query: WHEA_UNCORRECTABLE_ERROR



#6 th3fall3n777

th3fall3n777

  • Members
  • 364 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Wisconsin
  • Local time:12:55 AM

Posted 11 July 2013 - 02:33 AM

The WHEA_UNCORRECTABLE_ERROR usually means you have hardware failing I'm afraid, BUT, if it were my computer I would do a Start -> Run (or type in "Search Programs and files" for Windows 7) chkdsk /r /f and then restart - that will give you your best chance of success on fixing any software side problems.  You could also run a System File Checker - again with the Start -> Run, but instead do sfc /scannow which will check your Windows system files and repair them along the way.  Note for the SFC check, I have seen Windows request your Windows OS disk to complete the process, so I would start with the chkdsk

 

I see you already ran a memory test.... Microsoft seems to think it is a Memory related issue based on the codes you are getting from your dumps though. 

 

The last thing I would say, if you haven't done so already (I may have missed it) is try using Driver Verifier - it has gotten me to the crux of issues before coming up with a bad driver - http://support.microsoft.com/kb/244617

 

 



#7 Alyj

Alyj
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:01:55 AM

Posted 11 July 2013 - 06:15 AM

I just finished running chkdsk which took nearly 3 hours. There didn't seem to be any problems, 0 bad sectors, it did say windows changed some files. Computer is still only seeing 8 out of 16gigs of my ram. Because the crashing is so random, it hasn't happened again yet, but I've spent most of the time running chkdsk / in the bios etc. I have a feeling it will crash again, but it could be days before it does so if it keeps up what it's been doing. It seems that everytime I update a driver, or drastically change a setting, it appears fixed for a few days before it starts this again.

I forgot to mention, the last thing that I tried doing was uninstalling windows updates. Shortly before all of this started, my computer forced a windows update when I was not around to stop it, and I uninstalled those 2 weeks ago. It seemed to fix the crashing issue for nearly two weeks, but now it is back and worse than it's been,

I do not /mind/ if it's a hardware issue... I just want to figure out WHICH piece it is already!  :(


Edited by Alyj, 11 July 2013 - 06:17 AM.


#8 Anshad Edavana

Anshad Edavana

  • Members
  • 2,805 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:India
  • Local time:12:25 PM

Posted 11 July 2013 - 06:28 AM

Hi

 

STOP 0x124 generally indicates a hardware issue but in some cases bad drivers can cause CPU to be unresponsive and lead to this error.

 

Please follow the below steps one by one to identify the culprit.

 

:step1: Stop overclocking.

 

If you by any chance overclocked either your CPU or graphic card, please revert them to stock values immediately.

 

:step2: Update the system BIOS to the latest.

 

      http://www.asrock.com/mb/Intel/H77%20Pro4-M/?cat=Download&os=BIOS

 

:step3: Check whether there is a VGA BIOS update available for the graphic card. If you are unsure, post the exact full model number of the card.

 

:step4: Identify the root cause of the memory issue. Please note that Windows 7 Home Basic only supports 8 GB of RAM. 

 

     http://msdn.microsoft.com/en-us/library/aa366778.aspx

 

If you are running Home Basic, you need to upgrade to a higher version.



#9 Alyj

Alyj
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:01:55 AM

Posted 11 July 2013 - 06:44 AM

Hi Anshad, to respond to some of those suggestions,

 

I am running home premium 64 bit and I have had the 16gbs of ram showing up just fine for over a year.

 

I have never overclocked anything. when my ram started not showing up correctly, I did go into the bios and look at the dram voltages. I noticed the mobo set the voltage to 1.586v, when the default recommendation for this ram is 1.5v, so I did set the voltage to 1.5v. It didn't correct the issue though. I have a feeling that whatever is causing my computer to crash has made windows unable to read the memory, even though the mobo can see that it is there..

 

I am unsure of how to check for a bios update for VGA.. this is my exact card

EVGA 01G-P3-1556-KR GeForce GTX 550 Ti (Fermi) FPB 1GB 192-bit GDDR5 PCI Express 2.0 x16 HDCP Ready SLI Support Video Card http://www.newegg.com/Product/Product.aspx?Item=N82E16814130625

 

I have a question: 

If my power connections were messed up somehow, as seemed to be by my earlier post with the blinking power supply lights, would this be something that could cause all of my issues? Could that have been causing my graphics card to not get enough power, crashing my computer during gaming, and also possibly damaged something that related to my memory?

 

When I look at the bios, it is reading the memory in slots a1 and b1, but not a2 and b2, but it does not matter what sticks I have in those banks, it is the banks that appear to not be reading. Here is just a photo of what the bios system browswer displays; see that in here at least, it does see the memory sticks?

http://imgur.com/6dI45U4

 

Also, if helpful, this is the exact memory I bought.

http://www.newegg.com/Product/Product.aspx?Item=N82E16820231309


Edited by Alyj, 11 July 2013 - 07:06 AM.


#10 Anshad Edavana

Anshad Edavana

  • Members
  • 2,805 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:India
  • Local time:12:25 PM

Posted 11 July 2013 - 07:12 AM

Hi

 

Our first step should be is to solve the memory issue as there is a clear problem. Follow the below steps.

 

:step1: Clear the BIOS using  CMOS clearing jumper. 

 

If you are in doubt refer the official manual which includes detailed instructions.

 

http://download.asrock.com/manual/H77%20Pro4-M.pdf

 

After clearing the BIOS, load the default values and let the motherboard to choose what is best voltage and frequency settings for the RAM and CPU.

 

:step2: Upgrade to the latest BIOS as instructed in the previous post.

 

 

If the above steps didn't helps to solve the RAM issue, either the motherboard slots or it's control circuits might be faulty. 



#11 th3fall3n777

th3fall3n777

  • Members
  • 364 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Wisconsin
  • Local time:12:55 AM

Posted 11 July 2013 - 11:21 AM

I'd have to say I would follow through with Anshad's recommendations.  If you are having a power supply issue, and you have made custom settings for managing the voltage on your RAM, then it could certainly be misfiring and crashing your system.  It could also be damaging your RAM.  

 

I would revert all your overclock settings back to stock values - at least until you get this figured out yeah?

 

Just my two cents worth! 

 

Did the sfc /scannow pick up anything?



#12 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,470 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:11:55 PM

Posted 11 July 2013 - 12:57 PM

 

I would revert all your overclock settings back to stock values - at least until you get this figured out yeah?

 

In post #9 Alyj posted

I have never overclocked anything.

Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#13 th3fall3n777

th3fall3n777

  • Members
  • 364 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Wisconsin
  • Local time:12:55 AM

Posted 11 July 2013 - 05:39 PM

My apologies Alyj - I misunderstood what you were saying when I read you had made a manual modification to the voltage on the RAM in Post #9:

 

I noticed the mobo set the voltage to 1.586v, when the default recommendation for this ram is 1.5v, so I did set the voltage to 1.5v

.

Have you tried running chkdsk using the switches separately?  For instance, just use the /f switch or, chkdsk /r (I'm only asking because you indicated that the chkdsk took 3 hours, which is quite a long time for chkdsk!) I'm curious if you tried running the sfc /scannow as well, and what the results of that were.  Or even Driver Verifier?  Actually if these three things aren't resolving the problem, short of running a Windows repair, I'm not sure that anything else you could do software side would fix this?  (of course if others have other ideas that I'm not thinking of...)  

 

After searching for the information you provided I do keep finding various posts and topics indicating that replacing the motherboard resolves the problem (or RAM) - I'm sure you've read these too though... if it were my computer, the only other thing I could think of, and probably what would be my next stop is running a stress test, like with Prime95, but for that you would have to create an Ubuntu Live disk.  If you're interested:

 

Create an Ubuntu Live CD, and boot up selecting "Try Ubuntu with no changes to my computer". When booted, open up FireFox, and download Prime95.  If you ran the three tests available and wanted to post the results it may help.  

 

Ubuntu Download: http://www.ubuntu.com/download/desktop

Prime95: http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html


Edited by th3fall3n777, 11 July 2013 - 05:39 PM.


#14 Splatwacker

Splatwacker

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:06:55 AM

Posted 21 July 2014 - 12:49 AM

I am having the same problems as op upon installing the same Geforce Gtx 550ti. It seems an ongoing issue with little solves for many nvidia cards. I see thread is old and op has likely abandoned the issue but perhaps my two cents will help in some way.

#15 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,470 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:11:55 PM

Posted 21 July 2014 - 12:19 PM

I am having the same problems as op upon installing the same Geforce Gtx 550ti. It seems an ongoing issue with little solves for many nvidia cards. I see thread is old and op has likely abandoned the issue but perhaps my two cents will help in some way.

You need to open your own topic.


Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users