BCCode: 100000d1 error

[R_H] · Post by **[R_H]** » 2008-03-21 02:42pm

I've been having a problem that requires a restart, and upon logging into XP the following is displayed : "Windows has recovered from a serious error etc". Under details, the following error code is displayed: BCCode:100000d1 BCP1:F6734758 BCP2:00000002 BCP3:00000000 BCP4:F66E1920 OSVER:5_1_2600 SP:2_0 Product:256_1 (BCP2 and 4 change)

According to the MS site that comes up after the error report is sent, the problem is due to a device driver, and that there's no solution (going from memory here, will try to confirm this). What I'm doing when this happens doesn't seem to be causing this problem. I've had it occur when idle (only background processes running), while browsing, while watching video, while listening to music, while torrenting. The problem is intermittent, today I've had it occur 3 or 4 times, but it hasn't occurred the rest of the week. I've turned off automatic restart, but right after I did so, the same thing happened (monitor displays nothing, no signal) as usual and there wasn't a BSOD screen.

Any help would be greatly appreciated

Thanks

General Zod · Post by **General Zod** » 2008-03-21 02:54pm

Sounds like hardware failure. Either the motherboard, or most likely the RAM.

[R_H] · Post by **[R_H]** » 2008-03-21 03:02pm

General Zod wrote:Sounds like hardware failure. Either the motherboard, or most likely the RAM.

Thanks for your reply, General Zod. I googled this problem, and faulty RAM comes up a lot as a possible cause. Strangely enough, I don't have any problems when booted into Ubuntu. I'll run MemTest and see what it turns up.

[R_H] · Post by **[R_H]** » 2008-03-22 08:03am

I ran 7 passes of MemTest last night, and it didn't turn up any errors. Was 7 passes enough, or should I have it scan more?

Thanks

General Zod · Post by **General Zod** » 2008-03-22 05:13pm

Not terribly familiar with memtest. Do you have any spare ram chips that you can swap it out with to see if it does the same thing? Otherwise it's possible that it could be the hard disk or the motherboard if the ram is showing a green light.

[R_H] · Post by **[R_H]** » 2008-03-30 02:33pm

Just got a BSOD

The Stop code was 0x0000000D1 (0xF67F9758, 0x00000002, 0x00000000, 0xF67A6920)

Below the Stop code was an error code that had something to do with wtg211T13.sys which is probably my WLAN card driver, I'll try reinstalling it and see if the problem persists.

What diagnostic tools are there that I can use to see if my HDD is failing (other than S.M.A.R.T. which I'm pretty sure I have enabled)?

Thanks.

Resinence · Post by **Resinence** » 2008-03-30 11:52pm

[R_H] wrote:Just got a BSOD

The Stop code was 0x0000000D1 (0xF67F9758, 0x00000002, 0x00000000, 0xF67A6920)

Below the Stop code was an error code that had something to do with wtg211T13.sys which is probably my WLAN card driver, I'll try reinstalling it and see if the problem persists.

What diagnostic tools are there that I can use to see if my HDD is failing (other than S.M.A.R.T. which I'm pretty sure I have enabled)?

Thanks.

I'm pretty sure window's doesn't come with a S.M.A.R.T monitor process, for some insane reason (seriously wtf). You can use HDD Health from http://www.panterasoft.com/download.html to check your HDD's S.M.A.R.T status. Also right click the drive and go to properties, and run a disk check with "Check for disk errors" or "bad sectors" enabled, it will take a decent amount of time though. But if smart says it's failing trust that first, since modern hard drives self correct a certain amount of dead sectors before the OS starts picking them up.

Just a note, I was getting flaky bullshit like this in windows when my PSU was dieing on me, eventually the faults the PSU was causing led to corrupted data being written to disk which can throw you off into thinking it's the HD unless you do a bad sector test, so add another component to the list. I just love how in this day and age PC's have fuck all self-tests so you have to mix and match and independently test components.

[R_H] · Post by **[R_H]** » 2008-03-31 10:28am

Resinence wrote: I'm pretty sure window's doesn't come with a S.M.A.R.T monitor process, for some insane reason (seriously wtf). You can use HDD Health from http://www.panterasoft.com/download.html to check your HDD's S.M.A.R.T status. Also right click the drive and go to properties, and run a disk check with "Check for disk errors" or "bad sectors" enabled, it will take a decent amount of time though. But if smart says it's failing trust that first, since modern hard drives self correct a certain amount of dead sectors before the OS starts picking them up.

I thought if S.M.A.R.T was enabled in the BIOS it would display a warning during boot-up if anything was wrong. I downloaded HDD Health, and it says that the HDD where my XP partition is located on is at 84% health. What should I look for in the S.M.A.R.T attributes to determine if the HDD is failing or not?

Resinence wrote: Just a note, I was getting flaky bullshit like this in windows when my PSU was dieing on me, eventually the faults the PSU was causing led to corrupted data being written to disk which can throw you off into thinking it's the HD unless you do a bad sector test, so add another component to the list. I just love how in this day and age PC's have fuck all self-tests so you have to mix and match and independently test components.

The PSU is a 350W Antec which came with my Antec Mid-Tower, and I don't have any other PSU to swap it out for.

Thanks

[R_H] · Post by **[R_H]** » 2008-04-06 07:36am

Between Monday and yesterday morning I didn't have any more BSODs. Yesterday afternoon and also in the evening the computer BSODed four or five times, all with the same "Stop: 0x000000D1..." error code. My Ubuntu install was also being flakey, I could boot into it, but I couldn't run any programs (I could only move the cursor around on the desktop) etc. I had to do a hard shutdown, as I couldn't shut down normally while booted into Ubuntu.

Any ideas as to what is going on?

Thanks.

[R_H] · Post by **[R_H]** » 2008-04-06 08:34am

Less than ten minutes after posting the above, my computer BSODed yet again. I then reinstalled the driver for my wireless networking card, as the address the stop code was throwing up was for wireless card's driver. Hopefully that will put an end to the BSODing.

[R_H] · Post by **[R_H]** » 2008-04-12 06:06pm

An update: My computer has started BSODing again. I didn't have any BSODs anymore after reinstalling the wireless networking card drivers until today. This evening I've had five BSODs within a 3 to 4 hour timespan. I have no idea what else to do, any help/suggestions would be great.

Thanks