cpc2004 (or anybody else who wants to help), you helped me a while back in a 17 or 18-page thread...which you've asked not be continued, so I'm starting a new one.

I bought new RAM, which it looked like I needed because of my memtest86+ run, and failures in a number of different programs on memory write operations. The new RAM now passes memtest86+, and for 2 or 3 days the computer ran fine. Then, last night, I had a BSOD with a win32.sys error.

I've attached my 1001 in a text file, and the minidump in a zip file.

Any help on what next steps I should try? I'm really tempted to reformat my HD and start over, since I feel like I've got a general system slowdown, but if it's a hardware issue, that wouldn't really help.

Thanks,

-Tom

Attached Files

	new1001.txt (281 Bytes, 7 views)
	1minidump.zip (21.3 KB, 2 views)

The symptom is hardware related. Maybe overheat or faulty motherboard. How many times do you get BSOD after you replace the RAM? As you know minidump is the snapshot when Windows crashes, I want more minidumps to find out the culprit.

BugCheck 1000008E, {c0000005, bf837815, f33c7a68, 0}
Probably caused by : win32k.sys ( win32k!WNDOBJ_bEnum+e17 )

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f33c7adc bf82399a f33c7b08 bf823e98 bc63c868 win32k!WNDOBJ_bEnum+0xe17
f33c7ae4 bf823e98 bc63c868 f33c7afc 0000000a win32k!EngMulDiv+0x4acf
f33c7b08 bf823ded bc6736c8 0000000a 00000037 win32k!EngMulDiv+0x4fcd
f33c7b40 bf823eaa bc6306e8 0000000a 00000037 win32k!EngMulDiv+0x4f22
f33c7b70 bf824fb8 bc6306e8 0000000a 00000037 win32k!EngMulDiv+0x4fdf
f33c7c94 bf801f05 00000200 f33c7d14 bc652f30 win32k!EngSetLastError+0xeb8
f33c7ce8 bf80372a f33c7d14 000025ff 00000000 win32k+0x1f05
f33c7d48 804de7ec 0012f4c4 001a019e 00000000 win32k+0x372a
f33c7d48 7c90eb94 0012f4c4 001a019e 00000000 nt!KiFastCallEntry+0xf8
0012f444 00000000 00000000 00000000 00000000 0x7c90eb94

FOLLOWUP_IP:
win32k!WNDOBJ_bEnum+e17
bf837815 8a5109 mov dl,[ecx+0x9]

SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: win32k!WNDOBJ_bEnum+e17
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 422511a2
STACK_COMMAND: .trap fffffffff33c7a68 ; kb
FAILURE_BUCKET_ID: 0x8E_win32k!WNDOBJ_bEnum+e17
BUCKET_ID: 0x8E_win32k!WNDOBJ_bEnum+e17

This is the only BSOD since I replaced the RAM.

I'll post new ones as I get them.

Ok, I finally had a 2nd BSOD. I wasn't there when it happened, my wife was getting our cable internet installed. This is much better than before the new RAM, so it's helped, but I'm still BSODing. Below is the text of the 1001, and attached is my minidump (zipped).

Any advice for checking to see if I'm overheating? I'm not overclocking anything or anything else different.

Thanks,

-Tom
---------------

The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0x8056b356, 0xebd86904, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini081205-01.dmp.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Attached Files

0812minidump.zip (15.4 KB, 1 views)

What is frequency of your RAM. Maybe the new RAM is not fully compatible with your motherboard. Downclock the RAM.

The old original RAM is PC2100, the new RAM is PC2700. I was told it was backwards compatible...is this an issue with the 266 MHz PC2100 and 333 MHz PC2700?

How do I check? Is this in my BIOS?

-Tom

Aargh...just tried to post, and Mozilla crashed when I attached my minidump.

Anyways, I had a weird BSOD earlier today, which only gave me a 1 or 2 line notice...I didn't write it down, thinking I'd be able to reference the 1001 or minidump. Unfortunately, neither was generated.

However, when I rebooted, Windows Explorer immediately crashed, I shutdown, which hung up, so I had to manually power off and back on my computer. When it rebooted the second time, as soon as I logged into Windows, I got another BSOD.

Below is the 1001, and zipped and attached is the minidump.

Thanks again,

-Tom

------------------

The computer has rebooted from a bugcheck. The bugcheck was: 0x1000000a (0x760c7d3b, 0x00000002, 0x00000000, 0x804eb3eb). A dump was saved in: C:\WINDOWS\Minidump\Mini081305-01.dmp.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Attached Files

0813minidump.zip (17.2 KB, 1 views)

Again this is hardware problem. I am not a hardware expert. Repost your problem at hardware forum.
Mini081305-01.dmp 0A (760c7d3b, 00000002, 00000000, 804eb3eb) nt!MiDeleteVirtualAddresses+18f

Hi theberle,

Do you have any update of the problem?

CPC,

I haven't figured the problem out fully yet...nobody responded in the hardware forum, when I asked for help there. However, I did look into the temperature of my CPU, and found it was up around 70 deg C, which is WAY too high, and probably caused most of the problems. I have my case off, with an external fan, for now, and I'm not getting any BSOD's any more (along with the new RAM I bought as a first guess).

Long term, I guess I should try to replace the CPU fan (or at least the thermal epoxy bonding it to the CPU). Do you know any way to diagnose my CPU/Motherboard to see if there's any permanent damage from the overheated state? I used memtest86+ for my RAM, and found my old RAM had a bad address. Any way to do that for a CPU?

Also, I'm still getting software crashes, and my computer boots VERY slowly, so I'm thinking of reformatting the hard drive sometime.

Thanks for all your help.

-Tom

Hi theberle,

Re-install windows fix the most performance issue unless your PC has only 256MB.