ZippyDSMlee Posted November 17, 2013 Share Posted November 17, 2013 (edited) *strangles comp*... ahem.... After a hard crash random stuff dose not wont to work.Fallout NV works but FOMM will not work unless you change its folder name I have no idea what sort of bug this is this is a new one for me. Foobar and media player classic refuse to work as dose GECK so I am guessing some DLL's are bad but I do not even know where to begin... well I guess with a general DLL checker... *sigh* Anyone know of anything that would help this narrow down? Thanks for any help >< Edited November 17, 2013 by ZippyDSMlee Link to comment Share on other sites More sharing options...
Werne Posted November 20, 2013 Share Posted November 20, 2013 Define hard crash. Post full hardware specifications. How old is the hardware (mostly interested in HDDs, Windows boot drive to be specific)? When was the OS installed (how long ago)? Have you tried running Malwarebytes sweep? And if the CPU is overclocked through BCLK, post the BCLK, HT Link and NB frequency values. Way I see it, there are three possibilities for what you're describing - hardware (dying storage drive, dying Southbridge, dying RAM, HT frequency issue, etc), file system block failure (NTFS went bonkers), and malware-induced operating system failure (picked up a virus somewhere). All three can have the same symptoms you described, it's just a matter of finding the right one. Link to comment Share on other sites More sharing options...
ZippyDSMlee Posted November 20, 2013 Author Share Posted November 20, 2013 Define hard crash. Post full hardware specifications. How old is the hardware (mostly interested in HDDs, Windows boot drive to be specific)? When was the OS installed (how long ago)? Have you tried running Malwarebytes sweep? And if the CPU is overclocked through BCLK, post the BCLK, HT Link and NB frequency values. Way I see it, there are three possibilities for what you're describing - hardware (dying storage drive, dying Southbridge, dying RAM, HT frequency issue, etc), file system block failure (NTFS went bonkers), and malware-induced operating system failure (picked up a virus somewhere). All three can have the same symptoms you described, it's just a matter of finding the right one.A hard crash AFAIK is when the hardware stops and reboots with or without a blue screen, I got a blue screen, ran whocrashed it said a driver messed up er PFN_LIST_CORRUPT, it happens every now and then I have come to think the ramm and mobo hate each other but the mobo is probly going with my luck. No matter the ram setting I put in it will still crash after a day or so. After a couple reboots and redoing K lite codec pack and .net frame work stuff is working again once more, the only thing that is not working if I change the name of the FOMM folder back to GEMM it wont work change it to GEMM2 it works fine. 0-o Planning to get new mobo/cpu/ramm in the next 2-3 months. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now