S3 (STR) failing on new shuttle build

tretneo

Member
Aug 4, 2004
70
0
0
I just put together a new rig intended for use as a media center, connected to my TV and Receiver, based the new SG33G5 barebones w/ the following hardware.

E6750 at stock clocks and voltages
OCZ2P800R22GK revision 2 @ 800Mhz 4-4-4-15 @ 2.1v
LG SATA DVD+-/RW
WD SATA Raptor 74GB

No expansion cards or anything else. I am using the Microsoft Wireless Entertainment Keyboard (Bluetooth Dongle) and that is all other than what is built into the shuttle. I am using HDMI out to my Panasonic 42? Plasma and SPDIF onboard out to my Harman Kardon Dolby/DTS receiver.

Now the only real problem I am running into is S3 sleep. I have Hybrid sleep disabled. The system will enter sleep on its own per the power settings or when i manually tell it to sleep but when I go to wake it up via the keyboard or power button I see the post splash screen followed by the windows safe mode prompt alerting me that the system was shut down improperly or unexpectedly. Obviously it just shut down instead of sleep.

If I turn Hybrid sleep back on then the system goes down, wakes up, bios splash screen shows up and then the system recovers but I am pretty sure because the system is posting and the time it takes to recover that it is recovering from the hybernation portion of the hybrid sleep..

Any Ideas? I am using the latest intel GMA and chipset drivers, have tried reinstalling vista and a bunch of different bios options. Anyone know what I can try next?

Thanks,
Rob
 

boxtata

Junior Member
Aug 21, 2007
10
0
0
Hi there, I have a very similar build with G33 Shuttle. Sorry I didn't have much experience with the sleep problem you describe, as I never put my shuttle to sleep :D Always "sharing" files 24/7.

Although I did notice a few times it went to shut down the monitor due to inactivity, and the screen won't come back.

I think the Shuttle bios is far from optimized, so I would probalby flash the bios soon, you probably should do the same.

I mainly wanted to chime in to see how you set your resolution? I have a 50 plasma with native 1366*768, and I couldn't get the Shuttle to do any wide screen resolution that fits the screen. I ended up having it at 1024*768, and the TV scale it to fit the screen. Obviously it's not ideal because it stretches it.

Any idea?

Sorry for half hijacking the thread

 

tretneo

Member
Aug 4, 2004
70
0
0
Hey Boxtata, I have noticed some random strange issues as well, once in a while on a cold boot my system will lock up at the esata detection just after post and just before the OS loads from the internal SATA drive. Also if I disable the bios splash screen, the system will sometimes hang before the quick mem test on a cold boot, but with the splash screen up it never hangs at this point, makes no sense.

I have done plenty of Prime95 and memtest testing and everything is stable. Hopefully future bios updates will handle some of these issues like you said, I am currently running the latest "U" version of the bios.

What I have found to work well with Plasma's is to set the resolution to a standard HDTV resolution, even though your tv runs at 1366x768 (mine is native 1024x768 w/ rectangular pixels) you can set the resolution to 1280x720 (720) or 1920x1080 (1080) and the tv should be able to display them as it would any 720p or 1080i/p HD signal.... I am currently running at 1920x1080 and although the text is too small to read the aspect is correct and mediaportal looks great on it.

GL
 

boxtata

Junior Member
Aug 21, 2007
10
0
0
hey tretneo

yah.. so far with no power down power management and never shutting it down.. i don't have to deal with it much :D

for resolution... i set it to 1280*720.. but somehow it just overscans it by about half the width of the taskbar... which is not really useable....... i dont know why..

1920*1080 underscans it abit..so there's thick black border on the side..plus text gets too small.. so far only 1024*768 fits it perfectly :( sigh... but it's not wide screen aspect

i just want to try to do the native 1366*768 to see what's up :( any idea?