if you have a volt or multimeter you can check the terminal voltage on the battery. If it is less than 3V then it is a good indicator that it's expired
if you have a volt or multimeter you can check the terminal voltage on the battery. If it is less than 3V then it is a good indicator that it's expired
As you seem to have tried the obvious
is there any problem with the electrical supply / cables / earthing...
is any other device failing or locking up?
I had an intermittently faulty fridge - freezer which caused similar...
what voltage is shown in the bios for the ram
and what is the recommended voltage on the sticks themselves
i had similar crashing issues, and it was the voltage that was set wrong, even in auto
I have changed the SATA port from using 1 to 4 to see if that makes a difference. Guess i will find out in a weeks time or so.... fingers crossed!
Thanks to all for the help and ideas so far!
Cheers
Can not believe it but i think i have sorted it now as PC has been fine after removing Samsung PC Studio Software which had a non compatible driver. Of all the things... FFS! i don't know... but my rig is all good again so happy days...
Thanks for all your time and help all!
Dam!
I am back.... just when i thought i had sorted it as PC has been running fine for a month it has come back again where PC just freezes. The good new though is that i got a BSOD for a change after rebooting so i did what i was advised to do and use Crash Analyser and it came up with the following.
Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
Also seeing this alot in Event viewer?
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000c9 (0x0000000000000226, 0xfffff88001861870, 0xfffff9801cbccee0, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 050210-36660-01.
\SystemRoot\SysWow64\Drivers\StarOpen.SYS has been blocked from loading due to incompatibility with this system. Please contact your software vendor for a compatible version of the driver.
On Sun 02/05/2010 07:44:15 AM your computer crashed
This was likely caused by the following module: rapportpg64.sys
Bugcheck code: 0xC9 (0x226, 0xFFFFF88001861870, 0xFFFFF9801CBCCEE0, 0x0)
Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION
Dump file: C:\Windows\Minidump\050210-36660-01.dmp
file path: \??\C:\Program Files (x86)\Trusteer\Rapport\bin\RapportPG64.sys
On Sun 02/05/2010 02:04:44 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x19 (0x3, 0xFFFFFA8003E84B00, 0x0, 0xFFFFFA8003E84B00)
Error: BAD_POOL_HEADER
Dump file: C:\Windows\Minidump\050210-34039-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
Can any one help? All i can tell its not happy with a driver but i have updated all i think!
Also when the PC rebooted into windows it told me that it had recovery from a serious error and when i said Yes said to MS the PC went to a BSOD again for about 5 seconds and rebooted.
I guess at least my PC is giving me a bit more to go on now?
Cheers
Also seeing this alot in Event viewer?
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000c9 (0x0000000000000226, 0xfffff88001861870, 0xfffff9801cbccee0, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 050210-36660-01.
\SystemRoot\SysWow64\Drivers\StarOpen.SYS has been blocked from loading due to incompatibility with this system. Please contact your software vendor for a compatible version of the driver.
This is not a problem, the system did NOT load the driver and is letting you know in case you get a problem using an application.
The clue is in the path to the driver (SysWow64) - it's a 32-bit driver on a 64-bit version of Windows - it is impossible to load that driver.
staropen.sys looks like it might be part of Rocket Division's StarBurn software.
Chronologically, your first crash was a pool memory corruption (STOP 0x19) - most likley a kernel mode driver, an outside chance it is RAM (depends how consistent the crashes are):The problem with bugchecks caused by memory corruption is that even the dump cannot be relied on - the crash occurs because we hit the corruption, not when the memory was corrupted.
The next crash a few hours later is being pinned on the Trusteer driver rapportpg64.sys:Some chaps over here seem to be reporting a stability issue with this driver on Windows 7 x64 quite recently, and Trusteer Support claim a later version is stable.
Also, the bugcheck implies that Driver Verifier was enabled, at least for this driver, which caught its bad behaviour (hence the much quicker bugcheck).
This is a much more reliable piece of information, so I would start by taking this piece of (Trusteer) software out of the equation, or at the very least updating to the latest stable version if it's not already on it.
~ I have CDO. It's like OCD except the letters are in alphabetical order, as they should be. ~
PC: Win10 x64 | Asus Maximus VIII | Core i7-6700K | 16GB DDR3 | 2x250GB SSD | 500GB SSD | 2TB SATA-300 | GeForce GTX1080
Camera: Canon 60D | Sigma 10-20/4.0-5.6 | Canon 100/2.8 | Tamron 18-270/3.5-6.3
malice19 (05-05-2010)
Will update the Trusteer software and see how it goes.... tried windows update and it did install drivers for my Nvidia Geforce 260, but i only recently updated it from the main Nvidia site not long ago. Not sure but i have always thought its better to use drivers from Nvidia site than from Windows update?
Cheers for your time.
~ I have CDO. It's like OCD except the letters are in alphabetical order, as they should be. ~
PC: Win10 x64 | Asus Maximus VIII | Core i7-6700K | 16GB DDR3 | 2x250GB SSD | 500GB SSD | 2TB SATA-300 | GeForce GTX1080
Camera: Canon 60D | Sigma 10-20/4.0-5.6 | Canon 100/2.8 | Tamron 18-270/3.5-6.3
And just to add an anecdote - I recently updated a computer's nvidia drivers via windows update and it resulted in lots of stability problems in fallout 3 (this was a 8800GT). Rolling back to older drivers (a process possibly made easier by going through the windows update route) sorted the stability problems out. Now with nVidia drivers I always apply the 'if it ain't broke'.. adage..
Enjoy it looks like it was the RAM at fault, not that it is faulty but that my MOBO does like it... Went back to my old 4 GB RAM sticks which are slower but has now worked fine for 2 months.
Next time i will research a bit more before buying ram to make sure that one im getting does not have any known issues with my MOBO next time.
Cheers for all the posts peeps!
There are currently 1 users browsing this thread. (0 members and 1 guests)