|
Post by warlock on May 15, 2014 0:28:55 GMT
Well Irv since all is working now. One of those problem cannot be duplicated scenarios. I would lean toward a hardware issue, may never know. No, I'm sure it will come back. Someday though the actual failure will be a hard one and then I'll know. Electrical and s/w problems don't fix themselves. My last problem was caused by the keyboard. Tough to find.
|
|
|
Post by Admin_Vistamike on May 15, 2014 13:16:00 GMT
I don't personally run WIN 8 but have had very similar problems in WIN 7. Laptops don't seem to suffer this so I always point to hardware changes. The towers I have worked on it always seems to point to the graphics card. Depending on the BIOS, perhaps there is a way to configure the memory from the default parameters? Experimentation I know is pain, but with builds this might be just part of the play!
My new and nearly completed new build is win 7. I might upgrade to WIN 8.1 later.
I have to share the results with clients so they fully understand
|
|
|
Post by irvsp on May 15, 2014 14:32:56 GMT
I don't personally run WIN 8 but have had very similar problems in WIN 7. Laptops don't seem to suffer this so I always point to hardware changes. The towers I have worked on it always seems to point to the graphics card. Depending on the BIOS, perhaps there is a way to configure the memory from the default parameters? Experimentation I know is pain, but with builds this might be just part of the play! My new and nearly completed new build is win 7. I might upgrade to WIN 8.1 later. I have to share the results with clients so they fully understand Mike, I agree with a custom build. One could always do something wrong, BIOS setting, h/w compatibility, even some s/w compatibility. No so for one delivered from a manufacturer, much less one that worked fine for 4+ years with NO h/w additions done recently. Even no s/w probably. A true incompatibility one would think would pop up immediately and be consistent, not random or for a stretch of time and then go away and come back again. This new Dell is driving me nuts. Unlike many 'users' I tend to want a clean slim system. So I again can get myself into problems. One thing I do immediately is check out the computer. Run diagnostics and performance bench marks. Measure the disk access to make sure they are running at the correct speed (SATA III in this case). Next it look at the EVENT VIEWER. Yeah, a lot of stuff in there and some are errors, even a critical here or there. First thing I try to do is decrease them, like the warnings. Errors usually can be normal, some task reporting it didn't run or didn't have too. Try to stop those. Next I look at the Services. Like the REMOTE stuff, isn't always needed. BlueTooth is a pain on this Dell. The wireless card has it as part of it. Initially I connected wirelessly, but stopping that service stopped the wireless, sigh. I decided to use my BT headphones. No sound? Huh? Old computer had Logitech wireless keyboard and mouse and on there that receiver also worked for headphones. Since I can't use it now that I'm wired to the router I killed BT totally as well as the wireless. I could always disable the devices, but services had to be made disabled too to totally remove them and the error reports that they could not run.... Next screw up, the Virtual Disk service. I had no desire to use that, or so I thought. Next boot Symantec System Restore was broken and complaining. It needed that service if it should move a back-up to a virtual drive. You'd think the program would just not allow that option, but no, it was 'broken', could not even find anything. Log showed this: ========= Error EC8F1780: Cannot successfully reconcile changes since last session. Error EC8F1771: Cannot enumerate the current drives on this system ========= It basically did not work at all until I started the service... poor programming or real problem? If you search for that error you'd find a lot of ways to fix it, of course NONE mention needing the service. Only reason I suspected it was because I turned it off yesterday and almost immediately I got the error, but was fooled because it did see everything and 'assumed' it was the flashdrive I put in. SSR's page showed me it didn't know what to do with the drive, so I assumed it was the problem, until I booted this morning and it found NOTHING. BTW, I started using WinPatrol. Had it before but only used it for looking at processes. Now I use it to monitor startups and other stuff added recently to the program. Very powerful and you can even 'watch' registry hives if you want. I have the Pro license, not sure if the free version covers most of the same.
|
|