Computer falls into BSOD

[Meomix]

My computer has BSOD'd for the 3'rd time in the past week, i can't view the error logs because i don't have the tools to open them, what do i need to open .DMP and .XML files?

[Lupin]

The important info you should look for is the Bug Check Code (BCCode). Googling this code (0x7a) gives me this link: http://msdn.microsoft.com/en-us/library/ff559211%28v=vs.85%29.aspx

[Meomix]

Installing backlogged updates to see whether it will fix the problem.

[Lupin]

You should also test your RAM using Memtest86 or something similar

[rostheferret]

You should also test your RAM using Memtest86 or something similar

In a similar manner, if you're only using half the DIMM slots, try changing them to the other two. Sometimes its the connection on the side of the mobo rather than the RAM itself.

If I remember correctly, XML is the format for Excel, or I'm certain one of the other MSOffice programs. If the above idea's don't help, run a system restore. Perhaps there's some sort of driver issue. Check the BIOS to make sure nothing's overclocked, make sure there's adequate heat flow, etc, etc. The problem with this kind of thing is that it could be anything, so it's just a matter of trial and error until you find the source of the problem. It's usually RAM related mind...

[Freedom Kira]

Nope, XML = Extensible Markup Language. You're probably thinking of XLS, which would be Excel. Can't say for sure if any MS Office programs can open XML files, but chances are at least one of them can.

XML can be opened with a number of tools, but personally I'm only familiar with Visual Web Developer for that. In the worst case you should be able to open it in Notepad.

[kureshii]

XML files can be opened in a text editor. The DMP file is probably binary dump and not meant for user viewing; if it opens as garbled symbols in Notepad, ignore it.

In any case, as Lupin said, it seems to be a hardware rather than software problem, likely RAM-related.

[kitamesume]

if you know that the BSOD isnt caused by hardware then try reinstalling windows, should solve the BSOD. if it does get solved by reinstalling then it might have been a virus or a bad driver fucking up your system.

ah and be sure your OS Drive isnt failing =P

Edit: did you, by any chance, overclock your ram?

[Lupin]

0xC000000E (BCP2) means STATUS_NO_SUCH_DEVI CE

I'd check the following:
1. RAM integrity
2. Drive health
3. PSU - just a wild guess but maybe your PSU is barely supplying enough or the contact between your drives and the power connector aren't tight enough

[Meomix]

Ugh the updates slowed down my computers boot speed to a crawl, stupid system restore points are failing yet again.

Edit: Phew even doe the system restores failed my computer seems to have returned back to it's normal boot speed, cleaning out the restore points permanently now.

[x5ga]

well, usually it's the system disk drive having a few errors. chkdsk should fix it.

another less frequent cause is corrupted system files. "sfc /scannow" should help with that.

if you're unlucky, it's the RAM. If you're moderately lucky, removing the RAM, blowing the dust, and reinserting the RAM back (or maybe even changing the sockets in which you insert them) should fix it.

3. PSU - just a wild guess but maybe your PSU is barely supplying enough or the contact between your drives and the power connector aren't tight enough

this is also a less frequently cause, but it's worth checking. PSUs not having enough power to run all components, or faulty cabling/connectors can result in very annoying and non-specific errors.

[kitamesume]

i`ll go with faulty cable connections if its the PSU, usually the first thing to fail on a faulty PSU is the power sensitive ones like GPU and CPU, although they do have power backups that lasts a couple of milliseconds to filter spikes and/or hiccups, i think they call it power phase? well i`m not betting my ass on this info.

luckily when i get BSODs its usually the OS thats acting up, havent witnessed a failing system due to age and other natural faults. though i have witnessed a failing system caused by getting wet, dust build-up and causing a short circuit(dust+high humidity is bad) and similar to that.

one thing to try, take apart the whole rig piece by piece(take the ram out, unplug the PSU from the motherboard, take the HDD out, everything) and replug it back, this time tightly, ohh and clean up the parts while you're at it. loose/rusted connections causes similar problems imho, specially on years-old PCs.

[Big Teeth]

Download the free 'WhoCrashed' tool from http://www.resplendence.com/
Maybe it shows a little more details on the problem.

My most recent crash (PC rebooted automatically and resumed without issues):

On Thu 07-07-2011 03:55:45 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini070711-01.dmp
This was probably caused by the following module: tcpip6.sys (tcpip6+0x19EE7)
Bugcheck code: 0x100000D1 (0x15, 0x2, 0x0, 0xFFFFFFFFB7E28EE7)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\tcpip6.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: IPv6 driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect.
Possibly this problem is caused by another driver on your system which cannot be identified at this time.