m$ BSOD *** STOP errors

Printable View

January 18th, 2005, 04:08 AM
phishphreek

m$ BSOD *** STOP errors

I got a new mobo and processor for my home 2k server and added 1024mb of ram.

(the mobo is actually not new, but used. the person had no problems running 2k server on it)

It is a PCCHIPS m811 mobo with an AMD 1700+ processor.
The video card is the same I used before 64mb nvidia gforce.

I got a new case and everything.

1x dvd drive
1x dvd/cd burner
1x3.5 floppy

1x80gb for OS and misc. don't store much on there
2x120gb data storage
1x160gb data storage

I have a promise ata100 ide controller for the extra two hdds.

I put everything in and boot the OS. It finds new hardware, and I load the drivers from the cd that came with the mobo. I go to windows update and find newer drivers, so I load them.

Shortly after, I start getting the following BSOD errors.
Most of the time it is while using the computer manager to look at disk management.

Quote:

*** STOP: 0x00000076

(0x00000000, 0xff1780c0, 0x00000002, 0x00000000)

Process_has_locked_pages.

Followed tip from
http://www.jsiinc.com/SUBF/Tip2500/rh2566.htm

According to them, I'm supposed to get a new BSOD
"STOP: 0x000000CB (P1,P2,P3,P4) DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS"

But I don't... I get

added registry change and now I get this BSOD

Quote:

*** STOP: 0x000000D9

(0x00000004, 0xff1af5a8, 0xff303228, 0x00000000)

The driver is corrupting the locked pages tracking structures.

I can't find any reference to that error. The 0x000000D9 I've seen always has a different message with it. I've checked it a couple of times now... just to make sure I wrote down the right thing.

I thought it was the promise controller because I haven't used that with this install, so I removed it. But, I still get the same problems.

I've removed all drivers (safe mode) and reloaded them with new versions, but still get the error.

How can I find out exactly which driver is causing the problem?
I've changed IDE cables, changed memory, etc.

BTW: according to windows update, I have all critical updates, sp4 and all driver updates...

EDIT:

I can reproduce the error every time by going into computer management and clicking on disk management. Which it gives the "connecting to logical disk management service" then I get the BSOD.

I can also cause this error by manually starting the logical disk administrative service.

I've now unisntalled EVERY driver from the OS, rebooted and reinstalled every driver from drivers downloaded from the makers websites and it still crashes.
/EDIT:
January 18th, 2005, 09:40 AM
Double//Cut

Im not a hardware guy. But if i was in your position. I'd cut my losses and get a new mobo. Sorry I couldnt be more help
January 18th, 2005, 03:28 PM
morganlefay

sorry if I missed something...

But I have a couple of questions...

Is this a clean install???
NT4..you could just disable\uninstall all devices..change the MB..and then reinstall all devices...

AFAIK..this cannot be done with a 2K OS...

I had on 2k WS that would crash after I changed the power management settings in ths BIOS

according to MS...this is unrecoverable,...and you need to reinstall...repair didnt work....even setting the BIOS back to what it was. This was around SP2...maybe fixed now

Also..do any of those disks have a disk management software or utility on them....may be interfering with the 2k disk management??

Does a new install...or parallel install do this...are you able to try this.

If it crashes with that...ITs hardware.

MLF
January 18th, 2005, 03:36 PM
Tiger Shark

Phish:

It has been our experience here that changing the mobo on a Win2k install often causes significant problems. It is our policy to do a full backup of data and do a fresh install when we change mobo's, drives etc. since we have been bitten by just trying to move a Win2k load across hardware previously.

You might want to consider our "tactic" and redo the install.
January 18th, 2005, 03:42 PM
morganlefay

I think TS and I were posting at the same time...

But he did confirm my hunch....

Quote:

It has been our experience here that changing the mobo on a Win2k install often causes significant problems.

MLF
January 18th, 2005, 03:51 PM
skiddieleet

I'd have to agree on the reinstall. Sound like it should be easy to take stuff off your system drive and put it on your data drives to backup. One thing, I almost got the impression the drivers and everything worked fine before you ran windows update and installed updates they had for them. I'm not sure if it's bad to use old drivers when there are updates, but if they work fine before you update them, you may wanna just use the original drivers from the manufacturers disk. Just my 2 cents :p
January 18th, 2005, 04:27 PM
phishphreek

The reloading of all the original drivers won't work. I've done it several times now and I can't decipher those damn BSODs to determine which driver is causing the probem.

h3r3tic: I'm not sure if it worked before I ran windows update. That was the first thing I did. I like to keep current with everything...

I've tried updating the BIOS, but the BIOS I downloaded from the manufacturer's site doesn't work. Says that I'm trying to load the wrong image for my system... but its the only freaking download available.

I only have the OS and some misc. programs on that my OS drive. I don't really keep any data on there... I do have an extra drive that I can install to and see if I get the same problem.

I was hoping that the reinstall would be last choice. But, at this point... I've got nothing to loose.

thanks

Oh yeah.. one more thing.

Is it ok to use a ata-133 harddrive on a promise ata-100 controller?

I can hook it up and it'll recognize, but to be safe... I put my CDROMs on that controller and kept all four harddrives on the onboard controllers.
January 18th, 2005, 04:34 PM
cacosapo

my experience as a MS "cloner" is that you cant (most of the times) transfer an O.S. for a machine that has a so different MotherBoard. It simply too hard to "clean" the previous O.S. from old MoBo drivers. Even if you install all new drivers, the damn windows continue to have some "hidden" parameters and programs and it simply goes crazy.

Its same thing when you have a IDE boot disk and try to move the O.S. to a SATA disks. its just easier to go on TS idea: backup and fresh install. :)
January 19th, 2005, 04:10 AM
phishphreek

Just a quick update. You all were right. Format and reload worked fine.

Too bad I didn't backup the server settings... just the data. I never think to backup my home stuff... only work. :( Ah well... should be easy enough to recreate. :)

I still have some hardware to install... so if it starts acting up again. I'll at least know which component. Thanks again everyone.

Son of a b***h! No sooner did I hit reply, the fecking thing BSOD'd on me again!
I'm gonna pully my hair out... I swear!
January 19th, 2005, 11:48 AM
Tiger Shark

Then you have bad hardware that is intermittent there Phish old chap. Did it "pop" on ZDisk management again or just randomly? Is the Mobo on the HCL?
January 19th, 2005, 03:47 PM
phishphreek

This time it didn't BSOD on the disk manager. It actually was running smooth.

Then I tried to update all the drivers (windows update) and it crapped out on a driver install. I beleive that it crapped out when trying to update the driver for the onboard lan. I just disabled that since I have other NIC that I put in there.

It only BSOD'd on me the one time since a fresh install... and not since I disabled the onboard lan.

Hopefully that was the problem. I've been reconfiguring it and its been running smoothly.

I have some diagnostics software (PC Doctor) that I'm going to bring home and run on it tonight.

Can anyone recommend any other diagnositcs software that may be helpful in this situation?
January 19th, 2005, 03:55 PM
Tiger Shark

Ah... I have had several problems with Win2K server when you update the NIC drivers to the latest and greatest the manufacturer has to offer..... I don't do them any more unless the current version is causing a problem. Get rid of the new driver, put the old one back and see what happens.
January 19th, 2005, 05:54 PM
cacosapo

phis, you got a really crap Mobo. PCChips uses to be the worst mobo in the world. But, for your usage (a server) maybe we can fix it :)

1) PCCHIPS m811 - do you have the lastest bios? If you have a m811lu, your bios version should be 3.1. Here is a link for d/l. http://www.pcchipsusa.com/download-mainframe.asp I hope that you know how to upgrade a BIOS safely. On that site, there is lan driver dated 2004/10/14 -- you have mencioned that BSOD is related to onboard lan

2) This board uses a kt266a chip and you are using a nvidia graphic card. There is some issues about that combination, that may cause a problem named "infinite loop" and random reboots. But since you are using for a server (not a graphic intensive process) i dont think that you will get this problem.

3) run a memtest on your machine to see if you have any RAM problem.

4) Run e superpi and some performance comparision software to see if you have other problems

5) i couldnt find some screen shots of bios, but are you sure that your bios parameters are compatible with your hardware (as memory/cpu clock, cas/ras parms, dma, etc)
January 19th, 2005, 06:10 PM
phishphreek

Quote:

you got a really crap Mobo

I know... :( But I get what I pay for. $0

I tried updating the BIOS, but it tells me that the image does not match my hardware.
They only have one file availble for download. Its the m811811.bin file. It simply won't load it.

Quote:

This board uses a kt266a chip and you are using a nvidia graphic card. There is some issues about that combination, that may cause a problem named "infinite loop" and random reboots. But since you are using for a server (not a graphic intensive process) i dont think that you will get this problem.

I have an 64mb ATI card I can throw in there just in case.

Quote:

run a memtest on your machine to see if you have any RAM problem.

Done with memtest86, no errors.

Quote:

Run e superpi and some performance comparision software to see if you have other problems

Will do!