Computer Restarts by itself...
<div class="IPBDescription">Help?</div>Alright, so here's the low-down:
I bought Bioshock, installed and played for sometime. Around 6 hours straight, I have no life. Anyway, after a while I quit and my computer BSODs while browsing the web and restarts itself.
Upon the restart, XP doesn't boot and I'm left with a message saying "Remove all media; Insert Boot Disc." I go into my BIOS and it turns out that my secondary hard drive has first priority. "A-ha!" I think because I don't have an OS on my second HD just random storage files. I switch priority and bam, XP booted and everything was fine.
Upon loading Bioshock up again I play for another good chunk of time, the computer restarts itself again(Without the BSOD). I check the BIOS and the priority was switched again. I switch it back.
Now Bioshock didn't load, so I reinstalled it (Haven't checked if it works) and about the same amount of time later the computer restarted itself again.
Windows did that error report thing every time I restarted, and told me it's <a href="http://wer.microsoft.com/responses/Response.aspx/10/en-us/5.1.2600.2.00010100.2.0?SGD=91f4a87a-af5f-4afc-86d8-9b30d675714d" target="_blank">Driver Problems</a>. "What drivers?" I though. I recently got an external DVD drive, but I don't think it those drivers caused it. I'm leaning more towards Bioshocks' Securom crap. Because I updated my NVidia drivers after the first restart since I thought it was my older drivers.
PS: Bad-ass forum skin.
I bought Bioshock, installed and played for sometime. Around 6 hours straight, I have no life. Anyway, after a while I quit and my computer BSODs while browsing the web and restarts itself.
Upon the restart, XP doesn't boot and I'm left with a message saying "Remove all media; Insert Boot Disc." I go into my BIOS and it turns out that my secondary hard drive has first priority. "A-ha!" I think because I don't have an OS on my second HD just random storage files. I switch priority and bam, XP booted and everything was fine.
Upon loading Bioshock up again I play for another good chunk of time, the computer restarts itself again(Without the BSOD). I check the BIOS and the priority was switched again. I switch it back.
Now Bioshock didn't load, so I reinstalled it (Haven't checked if it works) and about the same amount of time later the computer restarted itself again.
Windows did that error report thing every time I restarted, and told me it's <a href="http://wer.microsoft.com/responses/Response.aspx/10/en-us/5.1.2600.2.00010100.2.0?SGD=91f4a87a-af5f-4afc-86d8-9b30d675714d" target="_blank">Driver Problems</a>. "What drivers?" I though. I recently got an external DVD drive, but I don't think it those drivers caused it. I'm leaning more towards Bioshocks' Securom crap. Because I updated my NVidia drivers after the first restart since I thought it was my older drivers.
PS: Bad-ass forum skin.
Comments
The next time you see the BSOD write down that long error message, exactly as you see it. Then post it here. Any credible support personel would ask for the same thing (you may or may not have it dumped where the file can be retrieved and analyzed).
That was here.
<a href="http://www.nsmod.org/forums/index.php?showtopic=8624" target="_blank">http://www.nsmod.org/forums/index.php?showtopic=8624</a>
New Problem!
Every type of video file I attempt to play leaves all of my media players just pitch-black. Nothing comes through. I tried reinstalling CCCP to no avail.
DAMN YOU TECHNOLOGY!
<edit>A simple restart fixed the video problem, woop!</edit>
Can a Windows crash mess with the BIOS somehow?
Those dmp files can be loaded using a kernel mode debugger to get some information about where things went wrong (typically which driver crashed). You don't really need to be a programmer or anything like that to work the debugger, it's quite simple. Just download the <a href="http://www.microsoft.com/whdc/devtools/debugging/default.mspx" target="_blank">Microsoft debugging tools</a>, run WinDbg and load up the latest dmp file. You'll see a line that says "probably caused by..." or something like that, or type "!analyze -v" and look for the image name. Then just type that file name into Google to find out what it is.
I got this from the "!analyze -v" command:
<div class='codetop'>CODE</div><div class='codemain' style='height:200px;white-space:pre;overflow:auto'>
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000004, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: ba6345fb, address which referenced memory</div>
The file is "nvata.sys," an NVidia driver. I can't seem to find any real solution outside of updating my Mobo-drivers, and that just seem like a precaution.
Thanks for the help by the way guys.
Good advice from Max, but let me add that Googling BSOD STOP messages can / will result in major headaches. I spent countless hours researching mine, and unless you're very knowledgeable (which the average PC use isn't) about this stuff, prepare to be perplexed.
The PSU is often overlooked when a PC is having restart / BSOD issues, but more than likely it will be a driver issue.
<a href="http://www.nsmod.org/forums/index.php?showtopic=8624" target="_blank">http://www.nsmod.org/forums/index.php?showtopic=8624</a><!--QuoteEnd--></div><!--QuoteEEnd-->
Thanks for the plug, but it was on these forums <a href="http://www.unknownworlds.com/forums/index.php?&showtopic=101071" target="_blank">here</a> - Liku may or may not find info here to help.
nvata.sys sounds like the nvidia hdd controller driver.
not a after a brief Google search it reveals that you are likely using a nforce main board. that numerous users have reported teh issue and that it appears to be a result of bad drivers for the board. additionally using the windows driver appears to result in choppy performance and ultimately shut downs.
Some users report that uninstalling the driver works.
I would check to see if there is a newer version of your main board drivers out and update if possible, if not try the windows driver.
Performance has been a tad choppy, how would I go about uninstalling the windows drivers?
other wise the old uninstall from the device manager might be worth a try.
whee