dave_m Posted June 14, 2009 Share Posted June 14, 2009 Hi all, I'm running a show on a roadhog tonight, software version 3.0.1, and as the title suggests, the pesky thing keeps on dropping to a blue screen ... 3 times so far and the event's only been running for about an hour! It's not running anything special, 24 desk channels, 30 generic LED's, 4 CP alpha spot 300's and 2 pro 400s. All distributed across 3 universes. It doesn't seem to have a "preferred" time to crash, it's crashed when it's been doing nothing, and while I've been doing things with it. I keep forgetting to note down the BSOD reason as well, but next time (sods law says it'll be fine now) I'll make sure I get it. Looking forward to hearing the collective brain-pickings you might have on this topic Link to comment Share on other sites More sharing options...
niclights Posted June 14, 2009 Share Posted June 14, 2009 I can't be specific about the console, but I would open it up and check everything's seated and connected properly first. Link to comment Share on other sites More sharing options...
dave_m Posted June 14, 2009 Author Share Posted June 14, 2009 I can't be specific about the console, but I would open it up and check everything's seated and connected properly first. Much as I wish I could ... it's not my console (being a FL, and annoyingly not booked to bring my desk today) and I need the console to keep running certain things! Link to comment Share on other sites More sharing options...
niclights Posted June 14, 2009 Share Posted June 14, 2009 If it's crashing then what harm can be done by opening it up? I would have no hesitation doing this with a hire console if it wasn't working. Or call the hire company. And if it's venue I'd ask them, no? In my experience of XP embedded, the only thing that is likely to cause BSOD is a driver problem. But it's quite possible is something much more simple, like a loose connector internally. Link to comment Share on other sites More sharing options...
mac.calder Posted June 14, 2009 Share Posted June 14, 2009 Poorly seated RAM is almost sure to be the issue (past experiance with Hogs has taught me that one...) Link to comment Share on other sites More sharing options...
Modge Posted June 14, 2009 Share Posted June 14, 2009 Poorly seated RAM is almost sure to be the issue (past experiance with Hogs has taught me that one...)I thought RAM there it has to be said (poorly seated or just dying, possibly through over heating) but that comes from IT experience, not experience of the console in question. Link to comment Share on other sites More sharing options...
Tomo Posted June 15, 2009 Share Posted June 15, 2009 Once running, XP Embedded will basically only BSOD due to a hardware issue. - BSOD during boot can be caused by corrupted hard disk that is often recoverable by re-imaging, unless the hard disk is physically dying. The error in this case says that it couldn't find some particular file or it's "log or alternate". I'd pop the lid and check everything is properly connected, unless it's particularly hard to open the console. Link to comment Share on other sites More sharing options...
z.peletz Posted June 30, 2009 Share Posted June 30, 2009 Hi Dave, The best thing would be the check all connections, as stated previously. If you could also write down the hexadecimal code that might clue us in to what is going on. Snapping a clear picture would also work. The front panel will easily come off with the four hex screws located in each corner of the metal bezel. This will lift off both the metal face plate and the front panel PCB. Feel free to respond here or email me at zach.peletz@barco.com Thanks. -Zach PeletzBarco/HES Product Support Link to comment Share on other sites More sharing options...
mutley Posted July 3, 2009 Share Posted July 3, 2009 Does the BSOD stay on the screen long enough to read what it says, or does it just flash up for a split-second and restart? Is it the same error code every time? If you can read it, and it mentions a partitcular file or 'module', then it would suggest a software or driver issue. If it shows a stack dump (columns of hexadecimal numbers), then it's more likely to be a hardware issue. In this case, there is no other option than to open it up and take a look. 1) Firstly, check the CPU cooler fan is spinning properly, and that it isn't cloged up with dust. This is the primary cause of BSODs in computers of more than 18 months old, in my experience.2) Reseat the RAM, cleaning the gold contacts on the DIMM and blowing the slot out, before refitting it.3) Listen for the hard drive making rythmical noises and the system running slowly. This would suggest a damaged HDD surface. The fact it takes an hour or so before it happens, would suggest to me that the CPU fan is clogged up with dust and isn't cooling the CPU enough, causing it to overheat and become unstable. You could try running as normal (not in a live show), and if/when it BSODs, open the desk up (having unscrew it ready) and feel how hot the CPU cooler is. If it's too hot to touch for over a second, it's overheating. Semiconductor silicon (used to manufacture CPUs) starts to become unreliable at temperatures above about 70'C. Link to comment Share on other sites More sharing options...
Joe Bleasdale Posted July 3, 2009 Share Posted July 3, 2009 If it shows a stack dump (columns of hexadecimal numbers), then it's more likely to be a hardware issue. In this case, there is no other option than to open it up and take a look. The actual owner of this desk came on the High End Systems Support forums (http://forums.highend.com) just a week or so after this post was posted here. The Support staff at HES advised him on what to do, and the owner said he will be arranging for the desk to go for a service due to the fact there has been on-going problems. You can read the threads here.. http://forums.highend.com/showthread.php?t=8004 and here.. http://forums.highend.com/showthread.php?t=8005 Best Regards, Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.