|
此文章由 bulaohu 原创或转贴,不代表本站立场和观点,版权归 oursteps.com.au 和作者 bulaohu 所有!转贴必须注明作者、出处和本声明,并保持内容完整
原帖由 助理 于 2008-8-14 15:53 发表 
纯技术探讨哈,如果这个运行在XP系统下的开幕式软件,经过了充分的调试,什么情况下会出这个蓝屏呢?
XP has been out there for about 8 years. It's now rock solid. I frankly don't think there is any other client OS that is better than XP right now. Bear this in mind, I'd say it's most likely caused by hardware malfunctioning, however I have no clue of the software that runs on this computer, so it could be software as well.
If a software tries to perform operations like divide by zero or trying to access memory that it's not supposed to access, it triggers the kernel to halt the system immediately and start doing a memory dump if configured so. At the same time, it displays a white on blue screen with useful debugging information. That's the (in)famous BSOD. The STOP 0X*********(p1, p2, p3, p4) is the most important piece of information you should try to write down. They'll normally give you a clue about what happened.
If that's not enough and you did have a memory dump, windbg will help you further by pinpointing exactly which driver or executable caused the kernel halt. That's getting a bit too deep and I won't want to discuss here. Hope what I wrote is useful to you.
[ 本帖最后由 bulaohu 于 2008-8-14 16:01 编辑 ] |
|