The game runs fine with great FPS anywhere from 5 -15 minutes before my whole computer just reboots itself.

Specs are:

Core 2 Duo 3.4 Ghz
8 Gigs RAM
GTX 260 -> Beta drivers (tried the non beta 270.xx drivers as well)
Dell 30" monitor
HT Claro soundcard

I've tried different resolutions/settings and still have reboot issues.

At first I thought maybe it was a PSU issue but I've played many other games with no issues like this. I then saw other people are having this same exact issue as me which leads me to believe that it isn't a hardware problem.

http://forums.steampowered.com/forums/showthread.php?t=1893879

The game is so great! When it is running I'm loving it, and would love to resolve this issue so I can enjoy the hell out of it.

I'd suggest using memtest86+ (or similar to verify your ram) and double check your CPU/GPU temps as these are the most common hardware issues that produce these results.

Could be some overheating or other hardware problem?

I have similar problem after hours of gameplay, i think it is due to overheating because when i check the temp at BIOS, it is around 75 degree C which i believe is slightly higher in the middle of gaming session.

Hardware is running fine. My temps are all in a reasonable range (Same temps I get when running other games). I also ran memtest and everything checked out.

At first I also though it was hardware related, but after reading other people are having the same issues with different hardware configurations It seems it might have to do with software...Maybe it's a dual-link DVI issue?

I have NVIDIA GTS250 and after installation I had crashes to desktop around every 30-40 min but no rebooting, NVIDIA driver version 266.58.

After I upgraded the driver (tried both beta 275.27 and 270.61) it started crashing and rebooting the computer every 5-10 min.
Try downgrading driver to 266.58, I'm doing it now.

Hmm yeah, I thought about the power source also, since I've seen a single game alone cause reboots while others did not. My power source was slowly dying, and other games started causing reboots also after a while. Although, since you've tested with different settings (which I assume means much lower graphics settings also), it does sound more like some other hardware/driver conflict.

This might seem like a bit of shock for you unless you've already trid this tool. Everytime I belive there's a hardware problem on my w7box, I always boot the system to a linux LIVE session. You download an image either through a CD/DVD or usb and then you boot the system.

If you're not experiencing the same hardware issues, it's mosty windows related.

Best part about the LIVE is that after you remove the media/reboot you're back to windows 7.

Sounds like overheating to me as well, check hwmonitor when you're gaming.

I'm the OP of the Steam thread... this is legit.

Please read through the linked thread from this OP... I've done everything, monitored temps and voltages (HWMonitor, Speedfan, EVGA E-Leet Tuning, RealTemp & Coretemp64), changed drivers (270.61 & 275.25), changed settings (Low-Ultra)... everything. There are no hardware issues. Trust. And there are multiple people with this issue. The linked thread details all of this to a degree.

In my instance, all stock/rated speeds. No overclocks. All other games run fine. All stress tests run fine. A very stable system. But for some odd reason, The Witcher 2 blankly reboots my PC.

Strangely, in my BIOS, I have the "PWROn After PWRFail" option disabled -- which from experience in overclocking on a prior RMA'd EVGA X58 3SLI motherboard, I know works -- so technically if there were some hardware or power failure, my rig should NOT restart itself. It should shut off and stay off.

But after about 10-20 minutes of The Witcher 2, I get a "No Signal!" screen from my TV, then the system goes to post.

I don't mean to sound jaded, but this is a very difficult issue to try and ask for a solution to because everyone seems to point to overheating, underclocking, overclocking, or power; and understandably so; though I very much doubt it is such a general issue when people with all kinds of varying hardware are having the same thing happen in only ONE game.

Suddenly, because of one game, all these people are finding out they have faulty hardware? Or insufficient cooling? Or their GPU/PSU is dying? Why are their computers not showing any signs of this in any other program or game? It's not logical.

I want to say it's some sort of driver issue, because a lot of the people I've seen with this problem have Nvidia GPU solutions, though there have been a few AMDs. I just hope it's resolved somewhat soon. I've submitted a support ticket to CD Projekt RED, if for nothing more than to raise awareness that there are people having this problem with their product, and seemingly their product alone.

Here's hoping, because from the few 20-minute sessions I have played, this game is absolutely amazing.

Have you disabled the "Automatically restart" thing in windows?

http://pcsupport.about.com/od/windows7/ht/automatic-restart-windows-7.htm

This should give you a BSOD instead which is handy for troubleshooting.

Yep. Stated that in the Steam thread as well. No BSOD, it just restarts -- when by BIOS settings it shouldn't, given a hardware failure... all very odd. Only, and I mean ONLY, instance this happens is while running The Witcher 2.

I was lucky enough that I played tonight for maybe 2 hours, before it finally decided to restart. Nothing different in monitoring. Had RealTemp going, had HWMonitor going, and had Windows System Resource Monitoring up and checked every 15-20 minutes.

Same old temps, same old voltages, same memory use. Nothing at all out of the ordinary.

That really is bizarre, it's probably best to wait for the patch as it's obviously an issue with the game itself rather than a fault on your system.

May not be any help, but I get this when I overclock my Video Card too far and the more over clocked it is, the more readily I get the crash.

Just to copypasta some new info from the Steam thread:

--------------------------------------------------------------------------

Kind of a bump...

Played for about 2-3 hours last night without a crash/restart. Same old regular temps, voltages, memory usage as I get with any other program/game.

In fact, it was running colder than before -- given weather conditions. As when it crashed, here's what RealTemp logged:

DATE TIME MHz C0 C1 C2 C3 NV LOAD%
05/21/11 01:31:00 2786.15 48 46 51 45 76 17.5

CPUs in the mid-high 40ºs, as opposed to low-mid 50ºs, and GPU was only at 76º, as opposed to 81º.

Power was at the same. Lowest was 11.96v on the 12V+, and highest was 12.18v. 3.3v and everything else stayed within digits.

Memory use did not skyrocket at any point.

Still, no idea what gives.

-------------------------------------------------------------------------

So, not completely certain as to what this is yet, but it seems that 99% of my crash/reboots happen after I go into the menu. Namely the Journal or Inventory. Almost every time a quest phase is updated, or I get some new item, and I open up the Inventory or Journal screens -- reboot.

Come to think of it, I don't think it's ever done this mid-fight, or in any instance running around town. It's almost always menus. Whether it's checking the Inventory, Journal, or meditating, browsing potions, or applying abilities. I've also had a few instances of the splash movies crashing, and sometimes the main menu.

But it's never -- ever -- been during gameplay.

Again, I can't say for certain, as maybe it's just been in the dice that I've always just opened a menu, but this almost definitely seems like a game code/software-related bug being that it's been timed so crucially to one specific event.

I pushed mine to 266.58 befor the game came out because of issues reported with other games and no problems here...I also use MSI Afterburner for Over Clocking (ASUS GTX 570moderately) and use its fan settings my temps never go over 50C after hours of playing..hope this helps