Halp! Beginning Dump of Physical Memory

[Fastbreak]

So, I built a new computer.

Chaintech VF4 Mobo

nVidia GeForce 6600

AMD 64 3500+

WD 160 GB HD

Windows XP Pro

1Gb (512x2) Ram

and, everything was working well for a little while then at random times I blue screen and get this message. Then, when I restart I can't get back into windows. The loading screen comes up, then all the lights on my keyboard blink and it sticks at a black screen. No SafeMode, nothing.

The only real message from the Blue Screen is:

*** Stop: 0x000000F4 (0x00000003, 0x865E6DA0, 0x865E6F14, 0x805c7478)

I'm relatively a noob when it comes to major computer issues but any help would be greatly appreciated.

[cluberti]

Stop: 0x000000F4 has a reference value of CRITICAL_OBJECT_TERMINATION. This means that some process or thread critical to OS function terminated unexpectedly (probably a second-chance exception), which in turn caused the operating system to become unstable and bugcheck.

There is a good MSDN article to read that gives more info on that particular bugcheck value that I suggest you read, as it gives you some more insight as to what is actually happening when you get this error:

http://msdn.microsoft.com/library/default....6b95c57.xml.asp

If you could post here the actual output of the bugcheck error message (you can find it in your event viewer if you can't get it from the bluescreen message itself), including the terminating object type (0x3 - process or 0x6 thread), the terminating object itself, the process name, and possibly the ASCII error message at the end, that would be extremely helpful data so I can begin helping you track down the problem code.

[Fastbreak]

Ok, I'm back into Windows for the time being. I just need to know where I can track down all the information you requested and I can get it. Sorry, I've just never had to get really technical with major Windows Issues.

There is something on the blue screen about something being terminated and Windows Shutting down. I just need to know where I can track down all the info.

Thanks for your help

Ok, I checked Event Viewer and WOW. There are TONS! of error messages. The one that seems to be causing the major issue however states:

The Apache Service named reported the following error:

>>>[Tue Nov 22 13:45:56 2005] [notice] Disable use of AcceptEx[]

Winsock2 API

With an event value 3299

Any ideas?

I uploaded my event logs:

Applications: http://www.serinus.us/yummies/Errors2.evt

System: http://www.serinus.us/yummies/Errors.evt

Edited November 22, 2005 by Fastbreak

[Sonic]

I think (very thinking !) about you ram ! there are "noname" ?

[Fastbreak]

It's A-Data DDR 400

[cluberti]

I'm seeing winlogon errors, eventsystem errors, and DCOM errors through the roof. However, the bugcheck isn't registering with the event logging subsystem (due to the aforementions eventsystem errors, apparently), so the next time the box bluescreens PLEASE write down the information onscreen (including the numbers). Otherwise, I won't know what's going on unless you are willing to attach an external kernel debugger to the system via another PC connected to the COM port via a null-modem cable and setting up the machine to run "checked" or with the /debug switch in boot.ini. I'd say it'd be easier just to write the bluescreen info down .

By the way, the DCOM 10016 event references CLSID {BC866CF2-5486-41F7-B46B-9AA49CF3EBB1}. If you look in your registry under HKCR\CLSID\, you should have a key with the above name. Follow the instructions in KB article 899965 (http://support.microsoft.com/?kbid=899965) to fix this issue. However, I doubt this is related to your bugcheck issue, it's just another problem I see on the system.

Edited November 22, 2005 by cluberti

[Fastbreak]

Ok, bluescreened again. The info I listed in the original post is the only technical info in the entire screen.

It just states that an unexpected termination of a program has caused it to shut Windows down.

I'm at a loss from this point

[suryad]

It seems to me at first it is a RAM issue. Have you tried running memtest? Or maybe the memory was not seated in right? I would not rule out a corrupted XP install but that seems less probable than just bad ram. That is why i always go with either Corsair or OCZ no matter how expensive they are.

[cluberti]

OK, so I'm going to need a complete dump of the OS when it bluescreens. To do this, go into the Properties of "My Computer", then click the "Advanced" tab, click the "Settings" tab under the "Startup and Recovery" heading, and then select "Complete memory dump" under the "Write debugging information" heading. You will need to make sure that the page file is at least the same size as the physical memory in the machine +50MB to make sure the dump isn't corrupt.

Once the system bluescreens after making this change, it will create a memory.dmp file in the Windows folder. This file should be the same size as the amount of physical memory in the machine - if you compress this and send it to me or post it here, I can then run it through a debugger and get some "root cause" information.