Search
Sign in with
Sign up | Sign in

Application cannot open after 2 hrs ; Slow Shutdown

Last response: in Overclocking
Share

I am completely new of the OCing world.
Built 2 systems, and one is having a problem:

E6600 + DS3 + 2GB RAM + X-Fi ExtremeMusic
@3.4GHz(48-50oC loaded), 4-4-4-12, vCore: 1.4V, vMCH: +0.1V, vFSB: +0.2V, vDIMM: +0.3V

everything runs perfect, had dual Prime95 ran over 18 hrs with no warning and errors.
HOWEVER, after a few hrs of running (e.g. 2hrs+); some application will not run and need to restart. Did I fry something?? or its the MB??
Also, I am experiencing a really slow shutdown (~2mins), tried UHPClean from microsoft, but no luck. I think that's the problem of the X-Fi driver.

Reformatted it twice, still experiencing the same thing above.

Anyone has any idea??

Thanks for the help!!!!

More about : application open hrs slow shutdown

Register or log in to remove
Related ressources
Ask the community

Hey mate,
Ive had some problems with slow shutdowns, after i installed a creative audigy 2 zs soundcard, it was a problem with the driver, if i uninstalled the soundcard and deleted the driver it would shut down properly, but with the drivers installed it took 2~3 minutes to shutdown.
try uninstalling the sound card and deleting the drivers, see if that fixes the problem. then smash your creative soundcard, as it is devil spawn ;p

I had the exact same problem. In fact afte several reformats I gave up and RMA'd mobo and RAM, bad choice. My original RAM could OC real nice, i cant get crap out of the repalcement set, and the replacment mobo had a bad flash ROM i think! neway. It's definatly the Creative driver! i had it happen to me again recently right after i updated my X-fi's drivers, it was one of the very few things i didnt bother to trouble shoot. I fixed it after uninstalling and reinstalling the driver a few times.

EDIT: if u have G. skill 4-4-4-12 DDR2 800 RAM, ur system is identicle to mine, lol

so, u have the slow shutdown problem or the application issue?
I will try to uninstall and reinstall the driver later tonight.
Hope it will solve the slow shutdown thing.
Thanks a lot for everyone's reply~~~ :D 

AND~~~~~~~~Merry Christmas~~~~~ :wink:

EDIT: and I have the Corsair RAM... :wink:

Are the errors for 'missing' files (not a big deal), or 'non-idential' files ?

And if for 'non-idential' files, which ones ? (eg: If all the .log files are different, well that is to be expected, if core DLL and EXE files differ, well that could be a cause for concern).

EDIT: 'Checksum Failed' = Different

Try running just CMD.EXE

Then from C:\> enter the following:

CD\WINDOWS [Enter]
FSUM [Enter] (Will display a help screen).

Commands of use are:

FSUM -c -w -jf WINDOWS_XP_PRO.HASH
- The line above displays errors only on screen, any line that would give an 'OK' is not displayed (So expect lots of disk reads, and not much console output).

and

FSUM -c -w -jf WINDOWS_XP_PRO.HASH > C:\OUTPUT.HASH.LOG
- The line above captures all the output to C:\OUTPUT.HASH.LOG instead of displaying it on screen as the above one does. This is useful for posting the (partial + parsed) contents of the file, or é-mailing it, sharing it, etc

:?: What voltage do you run your RAM at ?

:?: Are you running Windows XP Pro, or Home, or Pro x64 Edition ?

Quote:
Are the errors for 'missing' files (not a big deal), or 'non-idential' files ?

And if for 'non-idential' files, which ones ? (eg: If all the .log files are different, well that is to be expected, if core DLL and EXE files differ, well that could be a cause for concern).

EDIT: 'Checksum Failed' = Different

Try running just CMD.EXE

Then from C:\> enter the following:

CD\WINDOWS [Enter]
FSUM [Enter] (Will display a help screen).

Commands of use are:

FSUM -c -w -jf WINDOWS_XP_PRO.HASH
- The line above displays errors only on screen, any line that would give an 'OK' is not displayed (So expect lots of disk reads, and not much console output).

and

FSUM -c -w -jf WINDOWS_XP_PRO.HASH > C:\OUTPUT.HASH.LOG
- The line above captures all the output to C:\OUTPUT.HASH.LOG instead of displaying it on screen as the above one does. This is useful for posting the (partial + parsed) contents of the file, or é-mailing it, sharing it, etc

:?: What voltage do you run your RAM at ?

:?: Are you running Windows XP Pro, or Home, or Pro x64 Edition ?



vDIMM: 1.8V + 0.3V = 2.1V
and I am running XP Pro
Thanks!

Quote:
Are the errors for 'missing' files (not a big deal), or 'non-idential' files ?

And if for 'non-idential' files, which ones ? (eg: If all the .log files are different, well that is to be expected, if core DLL and EXE files differ, well that could be a cause for concern).

EDIT: 'Checksum Failed' = Different

Try running just CMD.EXE

Then from C:\> enter the following:

CD\WINDOWS [Enter]
FSUM [Enter] (Will display a help screen).

Commands of use are:

FSUM -c -w -jf WINDOWS_XP_PRO.HASH
- The line above displays errors only on screen, any line that would give an 'OK' is not displayed (So expect lots of disk reads, and not much console output).

and

FSUM -c -w -jf WINDOWS_XP_PRO.HASH > C:\OUTPUT.HASH.LOG
- The line above captures all the output to C:\OUTPUT.HASH.LOG instead of displaying it on screen as the above one does. This is useful for posting the (partial + parsed) contents of the file, or é-mailing it, sharing it, etc

:?: What voltage do you run your RAM at ?

:?: Are you running Windows XP Pro, or Home, or Pro x64 Edition ?



There are 3076 checksums failed...... :cry:  :cry:  :cry: 
Register or log in to remove
 
Ask the community
Read discussions in other Overclocking categories
!