Software or Hardware issue?

My computer runs like a speed demon for the most part. My only issue is when it comes out of sleep mode in certain cases.

Case #1: I put computer into sleep mode and let it sit for a few seconds, then turn it back on. Everything seems to work great!

Case #2: I put computer into sleep mode for several hours and then turn it back on. In this case the computer will stall for a fraction of a second every 15-20 seconds or so. It drives me bonkers when my mouse or PS brush hangs for even a split second.

I removed my video card and switched over to the integrated Intel graphics and driver. That made the hangups occur to a lesser degree, but they still persist.

I tried shutting down all programs before sleep and it doesn't make a difference, and no processes are doing anything unusual in task manager.

Could this be a hardware problem? I'm thinking maybe the memory has a hard time coming out of sleep mode after being suspended for a longer period of time? I can't imagine any software problem would change due to the amount of time in sleep mode.

Before I try some new memory sticks, any ideas on what is causing this?

I'm using a Dell XPS 8500 with Win 7, 8 gigs ram. I know Dell is notorious for using faulty memory sticks in their hardware, but this computer was given to me for free, so I can't complain too much. On a fresh boot-up this computer is fast and smooth as hell!

Thanks for any suggestions!

After intensive online searching, I have found that Dell does not recommend putting their desktops to sleep mode. Quite silly and probably just an excuse to deny any hardware issue.

I've tried using Hibernate mode instead, and it seems to work just fine!

I'm really starting to think the hardware (whatever bit it is) just can't cope with sleep mode.

I'm still on integrated graphics, but I will try putting the video card back in eventually to see what happens in hibernate mode. I don't do any gaming with my machine or video, so I may just leave it out, as the NEC Spectraview II software calibrates just fine with the Intel integrated graphics hardware and drivers.

What you see there is suspend-to-disk not working right. A BIOS update might help.

Which OS? If you use Linux you have a suspend-to-disk mode that works independently of the BIOS.

I can't help resolve the issue, but my self built PC is put to sleep every evening and is only rebooted every 2-3 weeks, sleep mode has no problems at all.

uOpt wrote in post #16196681
What you see there is suspend-to-disk not working right. A BIOS update might help.

Which OS? If you use Linux you have a suspend-to-disk mode that works independently of the BIOS.

Already stated that the OP has Win 7

It's been my own experience that, since Windows 95, the various 'Sleep,' 'Hibernate' and similar functions are strictly hit-or-miss, even on identical hardware & software configurations, within a Windows environment. It matters not the maker of the hardware.
This remains true all the way up to at least Windows 7.

When it works, it normally works well.
When it has problems, it's usually impossible to resolve.
Of the occurances where it doesn't work as expected/desired, it's best to simply shut down, instead of trying to find a solution which will probably keep you jumping through endless hoops.

SkedAddled wrote in post #16205778
It's been my own experience that, since Windows 95, the various 'Sleep,' 'Hibernate' and similar functions are strictly hit-or-miss, even on identical hardware & software configurations, within a Windows environment. It matters not the maker of the hardware.
This remains true all the way up to at least Windows 7.

When it works, it normally works well.
When it has problems, it's usually impossible to resolve.
Of the occurances where it doesn't work as expected/desired, it's best to simply shut down, instead of trying to find a solution which will probably keep you jumping through endless hoops.

The problem here is that hardware drivers can ruin any kind of suspend mode. Kernel code like drivers actually has to cooperate and implement the hooks for the suspend and resume correct.

And we all know that companies like creative labs are not able to make drivers that actually work for all the things that drivers are supposed to do right.

Thanks for the replies.

There must be a difference in hardware for the cheaper high performance machines Dell makes compared to their more heavy duty machines like the ones we used in the Video Game industry for our work. They seem to weigh about twice as much and all of the hundreds of machines we went through would always work fine for months with sleep mode and never being shut down. Most common issue was hard drive fragmentation due to syncing huge version control depot builds multiple times a day in most cases. Hard drive failure was the most common problem.

Canon_Lover wrote in post #16210617
Thanks for the replies.

There must be a difference in hardware for the cheaper high performance machines Dell makes compared to their more heavy duty machines like the ones we used in the Video Game industry for our work. They seem to weigh about twice as much and all of the hundreds of machines we went through would always work fine for months with sleep mode and never being shut down. Most common issue was hard drive fragmentation due to syncing huge version control depot builds multiple times a day in most cases. Hard drive failure was the most common problem.

What does that have to do with the suspend problems?

uOpt wrote in post #16210684
What does that have to do with the suspend problems?

Cheaper machine = less expected smooth operation. More expensive and heavier duty machine = less problems.

I read a lot of people with random suspend problems on the Dell XPS 8500 series, but from my own experience of using Dells at work and going through hundreds of various models, there has never been a suspend issue with those. Those professional workstation Dell models are far more reliable in my own experience.

I am just going to leave it be and use hibernate or shut down instead of sleep on my cheaper machine. My computer is just as fast as what we had at work, but there's obviously going to be shortcuts on a cheaper build, right?

Do you have hibernate enabled? If so then disable it and see if it cures the problem. I've never heard of any significant issues with sleep mode, but I'd avoid hibernate which is known to be probelmatic on some systems. Hibernate also saves a file to the C-drive that is close in size to the amount of RAM you have installed, so if you use an SSD as your boot drive it's a huge waste of space.

Canon_Lover wrote in post #16211125
I am just going to leave it be and use hibernate or shut down instead of sleep on my cheaper machine. My computer is just as fast as what we had at work, but there's obviously going to be shortcuts on a cheaper build, right?

My experience is opposite as far as the base computer is concerned. Various forms of sleeping have a better chance to work with simpler mainboards, presumably because there are less devices to screw up and they are sold more often so there is more problem data coming back.

When it comes to add-on devices, yes cheap brands tend to screw up the drivers they provide more and that can and will prevent suspend or make it crash on or after wakeup. However, as opposed to screwing up the mainboard BIOS that doesn't affect me because one of the biggest advantages of Linux and FreeBSD is that you have drivers written by operating system professionals, not lowest bidders hired guns that make a drivers work until the soundcard makes beep and then not caring how much damage to the overall OS they do.

And creative lab products aren't cheap either and have the worst driver problems.

Canon_Lover wrote in post #16210617
Thanks for the replies.

There must be a difference in hardware for the cheaper high performance machines Dell makes compared to their more heavy duty machines like the ones we used in the Video Game industry for our work. They seem to weigh about twice as much and all of the hundreds of machines we went through would always work fine for months with sleep mode and never being shut down. Most common issue was hard drive fragmentation due to syncing huge version control depot builds multiple times a day in most cases. Hard drive failure was the most common problem.

As a Dell certified tech, I see this a good bit. In most cases it has do do with corruption due to a hardware 'tick'. Hardware ticks are classified as intermittent and usually do not require replacement unless a customer specifically requests it (and it's under replacement warranty). Most OEM's will actually change certain hardware and even chipsets at different times during a products life, which can be problematic when the original image may still be used. That can cause odd things to happen, but it won't rise to the level of replacement or re-imaging. Re-imaging is a big deal and OEMs will avoid it like the plague if they can get away with it. If it costs less to tell a customer to reinstall then they will do that instead.

Long story short, reinstall from scratch. That has about a 80% success rate, depending on model. And, do not use a system images, use a real Dell OEM install disk. If this doesn't solve the problem culprit is usually (in this order) - motherboard, video, hard drive, a faulty USB device, or network device that keeps sending 'wake' commands.

MaxxuM wrote in post #16214265
As a Dell certified tech, I see this a good bit. In most cases it has do do with corruption due to a hardware 'tick'. Hardware ticks are classified as intermittent and usually do not require replacement unless a customer specifically requests it (and it's under replacement warranty). Most OEM's will actually change certain hardware and even chipsets at different times during a products life, which can be problematic when the original image may still be used. That can cause odd things to happen, but it won't rise to the level of replacement or re-imaging. Re-imaging is a big deal and OEMs will avoid it like the plague if they can get away with it. If it costs less to tell a customer to reinstall then they will do that instead.

Long story short, reinstall from scratch. That has about a 80% success rate, depending on model. And, do not use a system images, use a real Dell OEM install disk. If this doesn't solve the problem culprit is usually (in this order) - motherboard, video, hard drive, a faulty USB device, or network device that keeps sending 'wake' commands.

Well, there's about as a definitive answer as I could ever wish! I might send in my machine to get it fixed just out of principle and to make sure it works fine with the video card which was causing some issues (I'm on integrated graphics now). Of course after a try at a fresh system install, which wouldn't be a problem seeing as how my fast computer is only used for photo editing and has exactly two programs installed on it.

I assume Dell will send me install disks for free if the HD image instal does not work in resolving the issue?

Thanks!

Canon_Lover wrote in post #16214618
I assume Dell will send me install disks for free if the HD image instal does not work in resolving the issue?

Thanks!

You have to request them and usually at a small price, depending on your model, warranty and the originally packaged disks. Something most people don't know, but Dell computers will accept install dvd's from other Dells as long as it's in the same [model] family. It's hit or miss once you get outside a certain date. A good way to tell what family your install comes from is from the color of the dvd.