bzarcher: A Sylveon from Pokemon floating in the air, wearing a pair of wingtip glasses (Default)
[personal profile] bzarcher
Error code 000000d1, parameter1 00000064, parameter2 00000002, parameter3 00000001, parameter4 f71e188e.

This is on the new boot drive.

Date: 2004-03-02 07:43 pm (UTC)
From: [identity profile] alathaniel.livejournal.com
Don't recognize those codes off the top of my head, but wasn't it doing something similar with the old drive?

Date: 2004-03-02 07:46 pm (UTC)
From: [identity profile] bzarcher.livejournal.com
I think so, but I'm not sure if it's the same error code or not.

Date: 2004-03-02 08:04 pm (UTC)
From: [identity profile] runegrey.livejournal.com
Unfortunately, actually getting any information off of these error codes is nearly impossible to get any information directly from Microsoft from them. However, I do have a few references that might help.

From (http://www.eventid.net/display.asp?eventid=1003&eventno=1274) :

Error code 000000d1 = "DRIVER_IRQL_NOT_LESS_OR_EQUAL". A faulty device driver would typically be the cause of that. See also the comments for event id 1001 from "Save Dump".

It would APPEAR to be some sort of device conflict, but I can't say for certain - hopefully this will help you on running down the problem from there.

Date: 2004-03-02 08:06 pm (UTC)
From: [identity profile] runegrey.livejournal.com
Sorry bout that - the website was http://www.eventid.net/display.asp?eventid=1003&eventno=1274

This place has some reference on these sorts of error codes - not sure if you've seen it yet, but it might be of help.

Date: 2004-03-03 03:28 am (UTC)
From: [identity profile] gearhead.livejournal.com
I have a truly evil question.

What's the wattage on the power supply in your case?

Date: 2004-03-03 04:23 am (UTC)
From: [identity profile] bzarcher.livejournal.com
350W.

As far as I can tell, this machine, even at peak, should not need more than 340.

Long shot...

Date: 2004-03-03 04:47 am (UTC)
From: [identity profile] ptika.livejournal.com
I just had a shitload of motherboard failures at work while trying to test a graphics card over the past couple days. Couldn't even do a fresh install of Windows without getting Windows blue screen errors - error code 0x0000001e, and some others. After switching through five mobos, two P4 processors, two hard drives, various IDE cables and three graphics cards, I finally tried swapping the RAM.

Worked like a charm.

Don't suppose you could try that?

Re: Long shot...

Date: 2004-03-03 05:08 am (UTC)
From: [identity profile] bzarcher.livejournal.com
I'd need RAM to swap, first. And I'm getting to where I cannot afford any more parts if I want to have any money for Lisa's visit.

Date: 2004-03-03 08:45 am (UTC)
From: [identity profile] gearhead.livejournal.com
Hmm. I went through a simliar problem to this.. and discovered after replacing nearly everything that it was the power supply the whole time.

Date: 2004-03-03 08:47 am (UTC)
From: [identity profile] bzarcher.livejournal.com
We'll see. My next step is memory, I D/Ld the newest build of memtest to boot from when I get home.

Besides, if it's power, I would have expected this to start when I put the damn thing together, not almost 4 months down the line.

Profile

bzarcher: A Sylveon from Pokemon floating in the air, wearing a pair of wingtip glasses (Default)
bzarcher

December 2018

S M T W T F S
      1
234 5678
9101112131415
16171819202122
23242526272829
3031     

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Feb. 13th, 2026 09:22 pm
Powered by Dreamwidth Studios