2016/07/04 16:48:02
Sushihunter
I bought a new Video Card a little over a year ago.   I bought an EVGA NVIDIA GT620 2GB video card.
Card lasted about 6 months when something popped and the card died suddenly. EVGA did a warranty replacement and sent me a dead card. EVGA replaced that one with one that semi-worked, but painted a large stripe through the screen. EVGA replaced that one with a new one. This one seems to work.
 
However...  
 
In spite of doing regular clean installs of every new driver that has come out (about a half dozen), I keep getting regular Driver Crashes.
Screens will go black and come back after 15 - 30 seconds Often I get an error message indicating Video Driver Crash. Screens will freeze then come back after 1 - 2 minutes of disk activity. Screens will freeze and not come back without reset or reboot. Will get sudden BSoD with short countdown and automatic reboot. Issue seems to come up more when watching videos on YouTube or Facebook. Computer will crash a dozen times a day - more or less. Computer will spontaneously reboot without warning. Computer will crash within minutes of a reset or reboot.
I had been on a system disk for about 3 years and replaced it with a new HD and system install recently to try and get rid of this problem. It seems to be worse than before after only a month on the fresh system install!
 
Someone suggested that this may be a hardware problem with the Power Supply.
I am now considering replacing the PSU to see if this fixes the problem.
Is there any way I can load test the PSU?
 
Should I be looking at any other hardware?
 
Which PSU's should I be looking at buying - I'm on a budget, but I would like to get a high quality unit.
 
Thanks in advance for your comments!
 
System:
Asus P5K Premium
Intel Core 2 Quad Q6600
Windows 7 Ultimate SP1 with all updates.
Antec Truepower Trio 650 Watt PSU
4 GB OCZ DDR2 RAM
EVGA NVIDIA GeForce GT 620 - 2 GB RAM *
DELL 2407WFPHC Monitor on NVIDIA GeForce GT 620 Primary Monitor
Samsung SyncMaster 750S - 2nd Monitor (CRT)
Seagate 500 GB HD X2
Lots of other HD's
MediaSonic HD Bay with 4X SATA HD's on USB 3 port
LG BD Burner SATA
LG DVD Burner SATA
Generic USB 3.0 card
Note: RAM was tested with MemTest when first installed in 2007 - contiuous testing for 2 weeks with no errors detected. RAM was tested last week with MemTest and about a dozen passes were done with no sign of error.
 
Sushihunter
Vancouver, BC Canada
 
Happy 4th of July!
2016/07/04 19:13:51
Sajin
Definitely replace the psu first and let us know if you continue to have issues. Great replacement psu... http://www.evga.com/Produ...aspx?pn=220-G2-0650-Y1
2016/07/04 20:04:55
Sushihunter
Sajin
Definitely replace the psu first and let us know if you continue to have issues. Great replacement psu... 


Thanks for the reply.
 
Not sure if this will help, but here is the error code I get on most of the crashes - This is crash #34
 
 
Problem signature:  
Problem Event Name: BlueScreen   OS Version: 6.1.7601.2.1.0.256.1  
Locale ID: 4105
 
Additional information about the problem:   BCCode: 124  
BCP1: 00000000  
BCP2: 86F8801C  
BCP3: B2000040  
BCP4: 00000800  
OS Version: 6_1_7601  
Service Pack: 1_0  
Product: 256_1
 
Files that help describe the problem:  
C:\Windows\Minidump\062916-50778-01.dmp   C:\Users\Jim\AppData\Local\Temp\WER-94131-0.sysdata.xml
Read our privacy statement online:  
If the online privacy statement is not available, please read our privacy statement offline:   C:\Windows\system32\en-US\erofflps.txt
2016/07/04 20:06:38
Sajin
124 usually points to the cpu not getting enough power when overclocking. Is your cpu overclocked?
2016/07/04 20:28:50
Sushihunter
Sajin
124 usually points to the cpu not getting enough power when overclocking. Is your cpu overclocked?


No. No over-clocking.
 
I checked voltage with a meter - 12V is 12.26V  and 5V is 5.03V
Don't have a 3.3V reading available.
I just pulled and reseated the RAM
In addition to adding another 4 GBs of RAM for a total of 8 GBs
 
My first thought is the GT620 Video Card - mainly due to the problems I've had in the past with dead cards.
Second thought is the PSU starting to crap out and not providing enough power under load.
 
I'm on a pretty tight budget and really don't need any unplanned purchases, but I can't afford to be without a computer either.
 
Thanks!
Sushihunter
 
2016/07/04 20:45:50
Sajin
124 is power related. Idle voltage readings don't really tell us much.
2016/07/04 21:57:36
Sushihunter
Sajin
124 is power related. Idle voltage readings don't really tell us much.


True.
 
Is there any way to load test the PSU?  Would a computer shop likely have the proper test equipment to do that?
 
Also,
 
As I am likely to be replacing my PSU soon, I'd like to go to a 750 Watt unit.
 
Two that I am looking at are the 750 SuperNOVA G2 and the 750 SuperNOVA P2.
 
While a little, (lot) more expensive than I would like to spend at the moment, I'm sort of planning on upgrading with a new motherboard, CPU and RAM in the future.
 
I figure it would be better to spend a little extra now on something I can use to power the new system, rather than come up short now and have to replace it with one of these two units say next year.
 
Thanks again,
 
Sushihunter
 
 
2016/07/04 22:08:12
Sushihunter
Maybe this will help:
 
Welcome to WhoCrashed (HOME EDITION) v 5.51

This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.
Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue screen unless they are configured for this. Instead these systems suddenly reboot without any notice.
This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.
To obtain technical support visit

Just click the Analyze button for a comprehensible report ...


Home Edition Notice

This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.


System Information (local)

Computer name: JIM-PC Windows version: Windows 7 Service Pack 1, 6.1, build: 7601 Windows dir: C:\Windows Hardware: P5K Premium, , ASUSTeK Computer INC. CPU: GenuineIntel Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz Intel586, level: 6 4 logical processors, active mask: 15 RAM: 3488735232 bytes total


Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Mon 04/07/2016 12:35:17 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\070416-48126-01.dmp This was probably caused by the following module: (hal+0xEFCD) Bugcheck code: 0x124 (0x0, 0xFFFFFFFF8697001C, 0xFFFFFFFFF2000040, 0x800) 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. It is suggested you look for an update for the following driver: hal.sys . Google query:
On Mon 04/07/2016 12:35:17 PM GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: (hal!HalBugCheckSystem+0xAB) Bugcheck code: 0x124 (0x0, 0xFFFFFFFF8697001C, 0xFFFFFFFFF2000040, 0x800) 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. It is suggested you look for an update for the following driver: hal.sys . Google query:
On Mon 04/07/2016 11:00:25 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\070416-48750-01.dmp This was probably caused by the following module: (hal+0xEFCD) Bugcheck code: 0x124 (0x0, 0xFFFFFFFF86F1801C, 0xFFFFFFFFF2000040, 0x800) 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. It is suggested you look for an update for the following driver: hal.sys . Google query:
On Mon 04/07/2016 7:53:16 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\070416-48812-01.dmp This was probably caused by the following module: (hal+0xEFCD) Bugcheck code: 0x124 (0x0, 0xFFFFFFFF86D6401C, 0xFFFFFFFFB2000040, 0x800) 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. It is suggested you look for an update for the following driver: hal.sys . Google query:
On Mon 04/07/2016 7:41:44 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\070416-44787-01.dmp This was probably caused by the following module: (hal+0xEFCD) Bugcheck code: 0x124 (0x0, 0xFFFFFFFF86DBC01C, 0xFFFFFFFFB2000040, 0x800) 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. It is suggested you look for an update for the following driver: hal.sys . Google query:
On Mon 04/07/2016 4:15:04 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\070316-32136-01.dmp This was probably caused by the following module: (hal+0xEFCD) Bugcheck code: 0x124 (0x0, 0xFFFFFFFF86B7901C, 0xFFFFFFFFF2000040, 0x800) 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. It is suggested you look for an update for the following driver: hal.sys . Google query:
On Sun 03/07/2016 8:00:35 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\070316-48953-01.dmp This was probably caused by the following module: (hal+0xEFCD) Bugcheck code: 0x124 (0x0, 0xFFFFFFFF86F7501C, 0xFFFFFFFFF2000040, 0x800) 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. It is suggested you look for an update for the following driver: hal.sys . Google query:
On Sat 02/07/2016 4:23:31 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\070216-40903-01.dmp This was probably caused by the following module: (nt+0x32D9E7) Bugcheck code: 0x124 (0x0, 0xFFFFFFFF870048FC, 0x0, 0x0) Error: file path: C:\Windows\system32\ntoskrnl.exe product: company: description: NT Kernel & System 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.
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 02/07/2016 1:47:07 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\070216-46285-01.dmp This was probably caused by the following module: (hal+0xEFCD) Bugcheck code: 0x124 (0x0, 0xFFFFFFFF85BA001C, 0xFFFFFFFFB2000040, 0x800) 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. It is suggested you look for an update for the following driver: hal.sys . Google query:
On Sat 02/07/2016 10:47:16 AM GMT your computer crashed crash dump file: C:\Windows\Minidump\070216-44881-01.dmp This was probably caused by the following module: (nt+0x32D9E7) Bugcheck code: 0x124 (0x0, 0xFFFFFFFF86FFB024, 0x0, 0x0) Error: file path: C:\Windows\system32\ntoskrnl.exe product: company: description: NT Kernel & System 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



Conclusion

51 crash dumps have been found and analyzed. Only 10 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.
Read the topic for more information.
Note that it's not always possible to state with certainty whether a reported driver is 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.


2016/07/05 09:38:52
Sajin
You can load test the psu yourself. Just run prime95 (small fft) & heaven 4.0 (max settings) at the same time and check the voltage on your psu while the programs are running. Let me know what the voltages are. I'd highly suggest getting a new psu anyway as it looks like your psu is 9 to 10 years old.
2016/07/28 16:26:23
Sushihunter
UPDATE - July 28, 2016
 
Yesterday I bit the bullet and went out and bought a shiny new PSU - eVGA 750 Watt G2
Installed it last night and things were looking good - no crashes for several hours.
However, it was not to be...
I started getting BSoD crashes and freezes after watching several YouTube videos.
Ironically, it crashed just as I opened up this page a few minutes ago...
 
New Crash Report:
 
System Information (local)

Computer name: JIM-PC Windows version: Windows 7 Service Pack 1, 6.1, build: 7601 Windows dir: C:\Windows Hardware: P5K Premium, , ASUSTeK Computer INC. CPU: GenuineIntel Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz Intel586, level: 6 4 logical processors, active mask: 15 RAM: 3488735232 bytes total


Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Thu 28/07/2016 10:25:13 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\072816-56331-01.dmp This was probably caused by the following module: (hal+0xEFCD) Bugcheck code: 0x124 (0x0, 0xFFFFFFFF86D7301C, 0xFFFFFFFFB2000040, 0x800) 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 also be caused because of overheating (thermal issue). 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: hal.sys . Google query:
On Thu 28/07/2016 10:25:13 PM GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: (hal!HalBugCheckSystem+0xAB) Bugcheck code: 0x124 (0x0, 0xFFFFFFFF86D7301C, 0xFFFFFFFFB2000040, 0x800) 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 also be caused because of overheating (thermal issue). 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: hal.sys . Google query:


Conclusion

2 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.
Read the topic for more information.
Note that it's not always possible to state with certainty whether a reported driver is 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.


-----------------------------------------------------------------------------------------
 
Strangely, the crashes take several forms.
 
Most common is a simple screen freeze where the mouse pointer freezes and the computer will not take any input - including a Cntl-Alt-Del attempt at reset.
Sometimes I can wait it out and after a couple of minutes it begins working again. Most times I have to hit the Reset Button on the computer and reboot.
 
Another one is a quick freeze, then a BSoD with a countdown and automatic reboot.
I generally leave my computer powered up all the time. Sometimes I come back to find the computer has rebooted itself and I get a message like this:
 
 --------------------------------
Problem signature:   Problem Event Name: BlueScreen   OS Version: 6.1.7601.2.1.0.256.1   Locale ID: 4105
 
Additional information about the problem:   BCCode: 124   BCP1: 00000000   BCP2: 8688C01C   BCP3: B2000040   BCP4: 00000800   OS Version: 6_1_7601   Service Pack: 1_0   Product: 256_1
Files that help describe the problem:   C:\Windows\Minidump\072816-42463-01.dmp   C:\Users\Jim\AppData\Local\Temp\WER-157280-0.sysdata.xml
Read our privacy statement online:  
If the online privacy statement is not available, please read our privacy statement offline:   C:\Windows\system32\en-US\erofflps.txt
------------------------------
Very often, I get a Video Driver Crash which will last for anywhere from a few seconds to a couple of minutes while the screen images come back from black or white. Sometimes it won't come back and I have to reboot.
 
Prior to installing the new PSU, I removed all my extra hard drives to lower the power consumption to see if that had an effect - it didn't. Now, with the new PSU, I have to conclude that the old PSU was not the problem.
 
So, the question is: Is it the eVGA GT620 video card?  Or is it something else?
 
At this point, I'm really tempted to send the video card back to eVGA for replacement with some other model.
 
Thanks in advance for all your help!
 
Sushihunter
 

Use My Existing Forum Account

Use My Social Media Account