Sign in with
Sign up | Sign in
Your question

Application cannot open after 2 hrs ; Slow Shutdown

Last response: in Overclocking
Share
December 22, 2006 11:25:22 PM

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!!!!
December 23, 2006 12:02:42 AM

Sorry forgot to memtion: 48-50oC LOADED
December 23, 2006 12:16:40 AM

tried, backoff to 3.0GHz, experiencing the same thing
but never try default 2.4Ghz tho, cus that ain't OC at all. :cry: 
Related resources
December 24, 2006 4:15:35 AM

Can anyone give me any hints?
Thanks again~~
December 24, 2006 8:29:07 AM

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
December 24, 2006 10:12:38 AM

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
December 24, 2006 5:36:15 PM

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:
December 24, 2006 5:37:05 PM

Quote:
:idea:

Download this ZIP file:

http://darkpeace.cust.internode.on.net/hash/FSUM_WINDOW...

Extract it to C:\WINDOWS\

Run FSUM_WINDOWS.CMD

It'll check over files in your C:\WINDOWS\ folder, and sub-folders, for any that *might* be corrupt (from overclocking too far, or other causes).

8) Tabris:D arkPeace


So, how am I gonna fix the corrupted files??
Reformat??
Thx!
December 24, 2006 7:33:45 PM

Quote:
:idea:

Download this ZIP file:

http://darkpeace.cust.internode.on.net/hash/FSUM_WINDOW...

Extract it to C:\WINDOWS\

Run FSUM_WINDOWS.CMD

It'll check over files in your C:\WINDOWS\ folder, and sub-folders, for any that *might* be corrupt (from overclocking too far, or other causes).

8) Tabris:D arkPeace


There are 5861 errors~~~
WHAT CAN I DO??? :cry:  :cry:  :cry: 
December 25, 2006 5:31:24 PM

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 ?

December 25, 2006 5:52:34 PM

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!
December 25, 2006 5:56:59 PM

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: 
December 25, 2006 6:08:19 PM

Getting back the the making of the .LOG file:
FSUM -c -w -jf WINDOWS_XP_PRO.HASH > C:\OUTPUT.HASH.LOG
from C:\WINDOWS>)
Which ones are failing ?

Have you run Windows Update ?

Have you run OneCare Live! ?
December 27, 2006 1:47:11 AM

Quote:
Getting back the the making of the .LOG file:
FSUM -c -w -jf WINDOWS_XP_PRO.HASH > C:\OUTPUT.HASH.LOG
from C:\WINDOWS>)
Which ones are failing ?

Have you run Windows Update ?

Have you run OneCare Live! ?


Here is the LOG file: http://files.filefront.com/OUTPUTHASHLOG/;6425962;;/fileinfo.html

I ran both Windows Update and the OneCare Live.
Thanks a lot!!
December 29, 2006 1:15:52 AM

Thanks to everyone's effort.
I finally made everything worked out. (except the creative issue)
RMA the Board, and BAMB!!!!
3.6GHz!!!!

Thanks again!!
January 2, 2007 7:57:24 PM

How is this different from SFC ? (Windows internal file checker)
!