|
Who crashed Zippy's PC.
|
|
AfterDawn Addict
4 product reviews
|
16. April 2012 @ 20:56 |
Link to this message
|
I can not for the life of me run this one down, this glitch has lasted through 3 full re installs of win 7 and a week long test of an ati video card(still useing the ninvida card a 8800) its the damnest most random of hard lock ups I have ever had.
Anyway heres the who crashed report, will give more info if you tell me where in the hell to get it.
Oh and the crash itself when I am playing a video it will at least once a day start to grind the audio and blank the video. Oh and if you seek on vids it amps the rate at which it may crash.
Quote:
--------------------------------------------------------------------------------
Welcome to WhoCrashed (Professional Edition) v 3.03
--------------------------------------------------------------------------------
This program checks for drivers which have been crashing your computer. If your computer has displayed a blue 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 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. If 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 www.resplendence.com/support
Click here to check if you have the latest version or if an update is available.
Click the Analyze Local button to analyze this computer or the Analyze Remote button for a computer on the network...
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
computer name: ZIPPYHOME64-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD Phenom(tm) II X4 955 Processor AMD586, level: 16
4 logical processors, active mask: 15
RAM: 4294103040 total
VM: 2147352576, free: 1913769984
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 4/17/2012 12:31:39 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041612-90418-01.dmp
uptime: 4 days, 16:02:50
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x1EB54A)
Bugcheck code: 0x117 (0xFFFFFA8003FEA4E0, 0xFFFFF8801144A9C8, 0x0, 0x0)
Error: VIDEO_TDR_TIMEOUT_DETECTED
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 285.62
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 285.62
Bug check description: This indicates that the display driver failed to respond in a timely fashion.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 285.62 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation VIDEO_TDR_TIMEOUT_DETECTED
On Wed 1/4/2012 1:49:28 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\010312-66534-01.dmp
uptime: 21:50:17
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF8000307E231, 0xFFFFF8800682BFF0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 which cannot be identified at this time.
On Tue 12/27/2011 3:36:27 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\122711-47112-01.dmp
uptime: 00:00:12
This was probably caused by the following module: ntoskrnl.exe (nt+0x4B16CC)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8004E148F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
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 which cannot be identified at this time.
On Mon 11/14/2011 5:09:12 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111311-57065-01.dmp
uptime: 07:30:36
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x4A (0x74DC2E09, 0x2, 0x0, 0xFFFFF88005C43CA0)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
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 thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sat 10/29/2011 3:33:42 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\102811-49046-01.dmp
uptime: 01:07:17
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x4A (0x75282E09, 0x2, 0x0, 0xFFFFF88008788CA0)
Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
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 thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Wed 10/12/2011 12:37:49 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\101111-51729-01.dmp
uptime: 00:00:10
This was probably caused by the following module: ntoskrnl.exe (nt+0x4B16CC)
Bugcheck code: 0x124 (0x0, 0xFFFFFA80051F0748, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
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 which cannot be identified at this time.
On Sat 9/24/2011 1:03:54 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\092411-29312-01.dmp
uptime: 4 days, 12:07:13
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x69D9E1)
Bugcheck code: 0x3B (0xC0000094, 0xFFFFF880121459E1, 0xFFFFF8800CD44770, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 285.62
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 285.62
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 285.62 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation SYSTEM_SERVICE_EXCEPTION
On Sat 9/10/2011 8:00:38 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\091011-25131-01.dmp
uptime: 00:00:12
This was probably caused by the following module: ntoskrnl.exe (nt+0x4B16CC)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8004F202F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
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 which cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
8 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:
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 285.62 , NVIDIA Corporation)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
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.
Copyright infringement is nothing more than civil disobedience to a bad set of laws. Lets renegotiate them.
This message has been edited since posting. Last time this message was edited on 16. April 2012 @ 22:15
|
|
Advertisement
|
|
|
|
|
ddp
Moderator
|
16. April 2012 @ 21:56 |
Link to this message
|
i did not crash your computer as i'm innocent!! moved to correct forum. what video card are you using? is the driver off the cd or from ati site?
|
AfterDawn Addict
4 product reviews
|
16. April 2012 @ 21:58 |
Link to this message
|
Originally posted by ddp:
i did not crash your computer as i'm innocent!! moved to correct forum. what video card are you using? is the driver off the cd or from ati site?
Ah sorry was not sure which forum to post under.
Currently using a ninvida card(8800), the ati was a temp card.
And I am running the newest nivida drivers updated them 2 or 3 times and it still dose it.
Copyright infringement is nothing more than civil disobedience to a bad set of laws. Lets renegotiate them.
|
AfterDawn Addict
4 product reviews
|
18. April 2012 @ 19:20 |
Link to this message
|
|
Newish bug noticed is sometimes when playing audio it will lag a bit but not crash.
Copyright infringement is nothing more than civil disobedience to a bad set of laws. Lets renegotiate them.
|
|
JST1946
Senior Member
|
18. April 2012 @ 21:29 |
Link to this message
|
|
From what I have been reading sometimes a hardware change or updating the drivers will sometimes cause this in Windows 7 and Vista.
|
AfterDawn Addict
4 product reviews
|
18. April 2012 @ 21:34 |
Link to this message
|
Originally posted by JST1946:
From what I have been reading sometimes a hardware change or updating the drivers will sometimes cause this in Windows 7 and Vista.
Funny thing is it happened before I changed hardware 0-o
Copyright infringement is nothing more than civil disobedience to a bad set of laws. Lets renegotiate them.
|
|
JST1946
Senior Member
|
18. April 2012 @ 21:38 |
Link to this message
|
I had a similar problem and it was because of my NVIDIA driver.
|
AfterDawn Addict
4 product reviews
|
18. April 2012 @ 21:39 |
Link to this message
|
Originally posted by JST1946:
I had a similar problem and it was because of my NVIDIA driver.
I kinda figured it was the NVIDIA driver(s) but I can not believe its stuck past 3+ new version installs. 0-o
Copyright infringement is nothing more than civil disobedience to a bad set of laws. Lets renegotiate them.
This message has been edited since posting. Last time this message was edited on 18. April 2012 @ 21:39
|
|
JST1946
Senior Member
|
18. April 2012 @ 21:45 |
Link to this message
|
Sorry for the double post. Microsoft was the one who recommended the driver when I did an update.I went to NVIDIA's wesite and downloaded it from there and haven't had any problems since.Who knows maybe I have a ghost in my house.
|
|
ddp
Moderator
|
18. April 2012 @ 21:57 |
Link to this message
|
|
double deleted
|
|
scorpNZ
AfterDawn Addict
4 product reviews
|
19. April 2012 @ 02:31 |
Link to this message
|
|
Once you've discounted all other causes,what evers left no matter how improbable must be the cause,does that help :p
|
AfterDawn Addict
4 product reviews
|
19. April 2012 @ 02:32 |
Link to this message
|
Originally posted by scorpNZ:
Once you've discounted all other causes,what evers left no matter how improbable must be the cause,does that help :p
That pretty much means this build was buggered from the start. :P
Copyright infringement is nothing more than civil disobedience to a bad set of laws. Lets renegotiate them.
|
Senior Member
|
19. April 2012 @ 03:13 |
Link to this message
|
try a program called 'D7' it's more helpful with the dumps or the 'beta ERD disc' from microsoft seems you're not getting quite enough info from whocrashed
i7 3770 12GB ram terrabyte sata drive 1 750Gb sata drive 285GTX graphics Sony dvdwriter same NZXT Nemesis case
Still playing Black Hawk Down why did I upgrade?
|
AfterDawn Addict
4 product reviews
|
19. April 2012 @ 03:27 |
Link to this message
|
Originally posted by pcrepair:
try a program called 'D7' it's more helpful with the dumps or the 'beta ERD disc' from microsoft seems you're not getting quite enough info from whocrashed
So is the ntoskrnl.exe thats bad?
Quote:
==================================================
Dump File : 041612-90418-01.dmp
Crash Time : 4/16/2012 7:31:39 PM
Bug Check String :
Bug Check Code : 0x00000117
Parameter 1 : fffffa80`03fea4e0
Parameter 2 : fffff880`1144a9c8
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+1f8a0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : watchdog.sys+a577
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\041612-90418-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 475,039
==================================================
==================================================
Dump File : 010312-66534-01.dmp
Crash Time : 1/3/2012 8:53:59 PM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c000001d
Parameter 2 : fffff800`0307e231
Parameter 3 : fffff880`0682bff0
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17790 (win7sp1_gdr.120305-1505)
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\010312-66534-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 296,512
==================================================
==================================================
Dump File : 122711-47112-01.dmp
Crash Time : 12/27/2011 10:36:58 AM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`04e148f8
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : hal.dll
Caused By Address : hal.dll+f7f0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+4b16cc
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\122711-47112-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================
==================================================
Dump File : 111311-57065-01.dmp
Crash Time : 11/14/2011 12:12:32 AM
Bug Check String : IRQL_GT_ZERO_AT_SYSTEM_SERVICE
Bug Check Code : 0x0000004a
Parameter 1 : 00000000`74dc2e09
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff880`05c43ca0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17790 (win7sp1_gdr.120305-1505)
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\111311-57065-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 296,512
==================================================
==================================================
Dump File : 102811-49046-01.dmp
Crash Time : 10/28/2011 10:36:19 PM
Bug Check String : IRQL_GT_ZERO_AT_SYSTEM_SERVICE
Bug Check Code : 0x0000004a
Parameter 1 : 00000000`75282e09
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff880`08788ca0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cc40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17790 (win7sp1_gdr.120305-1505)
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\102811-49046-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 292,176
==================================================
==================================================
Dump File : 101111-51729-01.dmp
Crash Time : 10/11/2011 7:38:28 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`051f0748
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4b16cc
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17790 (win7sp1_gdr.120305-1505)
Processor : x64
Crash Address : ntoskrnl.exe+4b16cc
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\101111-51729-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================
==================================================
Dump File : 092411-29312-01.dmp
Crash Time : 9/24/2011 8:10:19 AM
Bug Check String : SYSTEM_SERVICE_EXCEPTION
Bug Check Code : 0x0000003b
Parameter 1 : 00000000`c0000094
Parameter 2 : fffff880`121459e1
Parameter 3 : fffff880`0cd44770
Parameter 4 : 00000000`00000000
Caused By Driver : nvlddmkm.sys
Caused By Address : nvlddmkm.sys+69d9e1
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7cc40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\092411-29312-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 292,248
==================================================
==================================================
Dump File : 091011-25131-01.dmp
Crash Time : 9/10/2011 3:00:47 PM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : fffffa80`04f202f8
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+4b16cc
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17790 (win7sp1_gdr.120305-1505)
Processor : x64
Crash Address : ntoskrnl.exe+4b16cc
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\091011-25131-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================
Copyright infringement is nothing more than civil disobedience to a bad set of laws. Lets renegotiate them.
|
AfterDawn Addict
4 product reviews
|
19. April 2012 @ 04:01 |
Link to this message
|
|
did some research might be a timing/voltage issue on the ramm.
Copyright infringement is nothing more than civil disobedience to a bad set of laws. Lets renegotiate them.
|
|
ps355528
Senior Member
|
19. April 2012 @ 10:15 |
Link to this message
|
You may be right.. thing is away from windoze world we are quite aware that the latest nvidia driver is a bit flakey. I'm only running an old FX5200 but even the "legacy" latest is crap. How hot is the thing getting?.. mine was trying to be a space heater.
Try rolling back say 2 versions and see if that improves matters, it did for me until xorg1.11 went and messed up the boot runtime for the nvidia legacy blob.
|
AfterDawn Addict
4 product reviews
|
19. April 2012 @ 12:29 |
Link to this message
|
Originally posted by ps355528:
You may be right.. thing is away from windoze world we are quite aware that the latest nvidia driver is a bit flakey. I'm only running an old FX5200 but even the "legacy" latest is crap. How hot is the thing getting?.. mine was trying to be a space heater.
Try rolling back say 2 versions and see if that improves matters, it did for me until xorg1.11 went and messed up the boot runtime for the nvidia legacy blob.
Ya I kinda figured it was that but the strange thing is now that I got a few mini dumps to look at the ninvida driver dose not seem to be crashing 0-o. And I do vaguely recall that it started after I put in 8GB of ramm.
Copyright infringement is nothing more than civil disobedience to a bad set of laws. Lets renegotiate them.
|
|
ddp
Moderator
|
19. April 2012 @ 15:13 |
Link to this message
|
Zippy, does the new ram have a label on it that shows the voltage & if so then does the bios show what the ram voltage is at & are they the same or different? check with motherboard maker to see what the latest bios version there is & see if it is same or newer then yours.
|
AfterDawn Addict
4 product reviews
|
20. April 2012 @ 21:46 |
Link to this message
|
|
f2-8500cl5d-4gbpk, it wants 2.1 for 533 mode so I am running it with that and the clocks set to auto....seems stable I will know in a few days if it is or not LOL
Copyright infringement is nothing more than civil disobedience to a bad set of laws. Lets renegotiate them.
|
|
pmshah
Member
|
23. April 2012 @ 02:31 |
Link to this message
|
In most likelihood the problem lies with your ram and or the slot holding it. It can lead to random memory access problems leading to the PC freezing on you. In most cases jiggling it or cleaning the ram and the socket with isopropanol does the trick.
I would also suggest you get the latest copy of freeware MemTest86+ and run it on your PC for a thorough check of the ram. You will have to boot from a floppy/CD.
If you have a single dimm and multiple sockets switch the slot used. Alternately test individual dimms in different sockets, one at a time using MemTest85+.
|
|
Advertisement
|
|
|
AfterDawn Addict
4 product reviews
|
23. April 2012 @ 05:22 |
Link to this message
|
Originally posted by pmshah:
In most likelihood the problem lies with your ram and or the slot holding it. It can lead to random memory access problems leading to the PC freezing on you. In most cases jiggling it or cleaning the ram and the socket with isopropanol does the trick.
I would also suggest you get the latest copy of freeware MemTest86+ and run it on your PC for a thorough check of the ram. You will have to boot from a floppy/CD.
If you have a single dimm and multiple sockets switch the slot used. Alternately test individual dimms in different sockets, one at a time using MemTest85+.
Did memtest over night and it gave no errors, its a power and or timeing issue which I think I have solved by upping the voltage to the ramm.
Copyright infringement is nothing more than civil disobedience to a bad set of laws. Lets renegotiate them.
|
