Replies

Stephen

A quick reply, I may come back. driver_irql_not_less_or_equal, I guess that’s STOP error 0x00..D1, correct? There are, if one want to believe it or not, also many STOP errors that can appear at setup. I have not had that so I have no direct advice. Fore instance, the 0x00..0A error can appear at setup, see MSKB 314063.

I do not know if you have looked at Kelly’s Korner, there is gathered information about troubleshooting Windows XP Setup:
Troubleshooting Setup

Regards,

Stephen

A quick reply, I may come back. driver_irql_not_less_or_equal, I guess that’s STOP error 0x00..D1, correct? There are, if one want to believe it or not, also many STOP errors that can appear at setup. I have not had that so I have no direct advice. Fore instance, the 0x00..0A error can appear at setup, see MSKB 314063.

I do not know if you have looked at Kelly’s Korner, there is gathered information about troubleshooting Windows XP Setup:
Troubleshooting Setup

Regards,

I agree with Steve. If you can open the corrupt file, one way might be to build a new file with copies of the sheets and import macros.

When did it start, any changes made before that? When some old file gets corrupt it almost always turns out that it’s hard to find exactly what is causing, and one will be better of with a new generated file, but without more information it’s hard to tell.

Is it a Excel 97 file, made by Excel 97?

You might want to look at MSKB 142117: Summary of Methods to Recover Data from Corrupted Files, which have some methods of recovering data.

Also, Ole P. Erlandsen has some tools on his site, there is one for damaged workbooks that will not open. I have not used that one, but if that indeed is the case it might work as his files/tools are good.
Erlandsen Data Consulting

Regards,

I agree with Steve. If you can open the corrupt file, one way might be to build a new file with copies of the sheets and import macros.

When did it start, any changes made before that? When some old file gets corrupt it almost always turns out that it’s hard to find exactly what is causing, and one will be better of with a new generated file, but without more information it’s hard to tell.

Is it a Excel 97 file, made by Excel 97?

You might want to look at MSKB 142117: Summary of Methods to Recover Data from Corrupted Files, which have some methods of recovering data.

Also, Ole P. Erlandsen has some tools on his site, there is one for damaged workbooks that will not open. I have not used that one, but if that indeed is the case it might work as his files/tools are good.
Erlandsen Data Consulting

Regards,

As to your latest STOP errors: D1 is common, advice is to look for “unsigned drivers, and be especially suspicious of recently installed or updated antivirus programs, disk utilities, and backup programs, which may install a faulty file-system filter driver.”

Also as mentioned look at Mainboard manual what type/size of mem. the board can handle, but I guess you have already done that. I guess all newer boards handle at least 512 MB /slot, and a total sum of 1024 MB.

0A error, from one MS site (183169):
These errors may be caused by one or more of the following: Hardware failure (memory, processor, or motherboard). Anti-virus software that is running on your computer. Drivers installed by third-party software.
To resolve these behaviors, perform one or more of the following:
Replace the faulty hardware. You may be able to determine the faulty hardware by running diagnostics provided by the manufacturer. Please contact the hardware manufacturer for more information.
Disable any anti-virus software that is running on your computer. If the STOP errors no longer occur, contact the anti-virus software manufacturer about a possible upgrade.
Disable any third-party drivers that may be running. If the STOP errors no longer occur, contact the third-party manufacturer about a possible upgrade.

Regards,

As to your latest STOP errors: D1 is common, advice is to look for “unsigned drivers, and be especially suspicious of recently installed or updated antivirus programs, disk utilities, and backup programs, which may install a faulty file-system filter driver.”

Also as mentioned look at Mainboard manual what type/size of mem. the board can handle, but I guess you have already done that. I guess all newer boards handle at least 512 MB /slot, and a total sum of 1024 MB.

0A error, from one MS site (183169):
These errors may be caused by one or more of the following: Hardware failure (memory, processor, or motherboard). Anti-virus software that is running on your computer. Drivers installed by third-party software.
To resolve these behaviors, perform one or more of the following:
Replace the faulty hardware. You may be able to determine the faulty hardware by running diagnostics provided by the manufacturer. Please contact the hardware manufacturer for more information.
Disable any anti-virus software that is running on your computer. If the STOP errors no longer occur, contact the anti-virus software manufacturer about a possible upgrade.
Disable any third-party drivers that may be running. If the STOP errors no longer occur, contact the third-party manufacturer about a possible upgrade.

Regards,

Stephen

First: I hope that the problem is solved or near to be solved!

Second: Re-boots are certainly frustrating and many times it’s hard to find a cause. Some months ago I had really hard times solving it, looked at programs, memory, BIOS, temperature, PSU (Power) etc. Even more frustrating was that sometimes, or often, I got re-boots without BSOD even if I had changed startup/Recovery setting to no reboot at install. Furthermore there was no trace what so ever in Event viewer.

As with everything else in life, in this case re-boots, you will get different suggestions depending on who you ask. Hardware AMD people overclocking/opt. or software forums.

One of the many BSOD I had was: 0x..D1, nv4_mini.sys, not the same STOP error as you, but the same file. And on it went.
Normally if one gets a BSOD, you get a better clue if there is a filename mentioned. One might think that the file is damaged or else has caused the STOP error. Of course that might be the case many times, but, and I quote from the book “Windows XP Inside Out”:

“Don

Stephen

First: I hope that the problem is solved or near to be solved!

Second: Re-boots are certainly frustrating and many times it’s hard to find a cause. Some months ago I had really hard times solving it, looked at programs, memory, BIOS, temperature, PSU (Power) etc. Even more frustrating was that sometimes, or often, I got re-boots without BSOD even if I had changed startup/Recovery setting to no reboot at install. Furthermore there was no trace what so ever in Event viewer.

As with everything else in life, in this case re-boots, you will get different suggestions depending on who you ask. Hardware AMD people overclocking/opt. or software forums.

One of the many BSOD I had was: 0x..D1, nv4_mini.sys, not the same STOP error as you, but the same file. And on it went.
Normally if one gets a BSOD, you get a better clue if there is a filename mentioned. One might think that the file is damaged or else has caused the STOP error. Of course that might be the case many times, but, and I quote from the book “Windows XP Inside Out”:

“Don

There are some different methods when comparing investments. It seems you are after DCF, Discounted Cash Flow, with Present Value method, and Excel functions can handle that for simple CF. If you are going to compare two possible investments and analyze their future cash flow with some sort of discount rate, and not are going to set up a cash flow and discount separate flows etc, use NPV to chose the one with the highest NPV.

Compared to PV, you can add individual values for each period, PV is simple; same payment every period. You will get a negative result from PV if payment is entered as a positive number, negative number is for instance for a saving.

Normally you have an investment I, and some payments in/out (or a net flow of in and out for that period) and you also have to balance what value to discount beyond CF period.

Note: values entered to NPV is End of Period, and that’s fine, but if your first payment, outflow (investment), is at time 0, i.e. in the beginning of first period (today) you have to add the investment to the result.

Ex.
Inv A
Initial payout today 1,000
Discount rate 8 %
Flow: 400, 500, 350, 550
NPV(0.08,400,500,350,550) => 1,481.15 that is present value of the flow. Now add the investment from lets say cell A1 (-1,000). NPV(0.08,400,500,350,550)+A1 => 481.15. OK, at least a positive value.

Inv B
Initial payout today 1,500
Discount rate 8 %
Flow: 650, 700, 500, 725
NPV(0.08,650,700,500,725) => 2,131.80.
Add Investment NPV(0.08,650,700,500,725)+B1 => 631.80.

So compared, even though a greater amount to invest, the discounted flow of investment B gives a greater NPV.

If your initial payout is in the END of the first period you can add it into NPV function as with the following cash flow. NPV(0.08,-1000,400,500,350,550)

As to FV (I have to always remind me with Excel’s use of the terms. To me FV is Future Worth, FV=p*(1+i)^n. Very simple. But Excel’s function FV will give you Future Worth of One, same as my function, or Future Worth of One per Period. Either you calculate the accumulated interest and add it to start value, or you also add a payment (saving) each period.). You can not put different individual payments in FV.

OK, this was a short explanation of NPV, I put my CF’s together with the formulas and do not use Excel functions. I maybe have to come back to add something, since it’s really late here

Regards,

Yes, I would be very surprised if the battery was going already. OK , the error has not reappeared, first reboot since last night I went into BIOS Setup and changed to 133/133/33, (FSB), so I would get my 1533 Hz, saved and rebooted. Works fine, and today the boot also went OK. I have seen so many different error messages when in rebooting tango, and known that the actual cause is not always what is reported, so I am not all that surprised over this checksum error. Anyway Mark and Cowboy thanks for your quick replies and information.

Yes, I would be very surprised if the battery was going already. OK , the error has not reappeared, first reboot since last night I went into BIOS Setup and changed to 133/133/33, (FSB), so I would get my 1533 Hz, saved and rebooted. Works fine, and today the boot also went OK. I have seen so many different error messages when in rebooting tango, and known that the actual cause is not always what is reported, so I am not all that surprised over this checksum error. Anyway Mark and Cowboy thanks for your quick replies and information.

Mark: Hmmm, OK, this is a 14 month old machine, I don’t know how long these batteries last. If I remember correct from last time I looked at the mainboard; yes it seems to be a “button type” battery. I have another, ten year old, machine and have not changed battery on that one yet, maybe the old ones lasted longer?

Cowboy: OK, well I have not cleared CMOS, and not changed any settings in BIOS before the error. That is, I did some changes 50 days ago when I reinstalled XP. Small changes, disable onboard modem etc. and then some days later, changed CPU Core Volt from Default to 1.75 V (wich it should be for my Palomino) cause the MB undervolt slightly (Default gives 1.69 V). That’s all I can think of for the moment.

The checksum error came after some reboots yesterday, and I certainly do not know what went wrong this time.

I did flash the BIOS in April this year, and made a back up of old one. Everything worked well untill September when rebooting started.

Regards,

Mark: Hmmm, OK, this is a 14 month old machine, I don’t know how long these batteries last. If I remember correct from last time I looked at the mainboard; yes it seems to be a “button type” battery. I have another, ten year old, machine and have not changed battery on that one yet, maybe the old ones lasted longer?

Cowboy: OK, well I have not cleared CMOS, and not changed any settings in BIOS before the error. That is, I did some changes 50 days ago when I reinstalled XP. Small changes, disable onboard modem etc. and then some days later, changed CPU Core Volt from Default to 1.75 V (wich it should be for my Palomino) cause the MB undervolt slightly (Default gives 1.69 V). That’s all I can think of for the moment.

The checksum error came after some reboots yesterday, and I certainly do not know what went wrong this time.

I did flash the BIOS in April this year, and made a back up of old one. Everything worked well untill September when rebooting started.

Regards,

If you have cables for LPT ports, which should be faster than serial, you could try that first before USB.

If you only want to establish connection and not create a network, i.e. you can manage files and folders on the other computer, then I think there might be small programs that will work on both machines directly after you have connected them. I did this between a old win95 and a WinXP over serial DCC. For the moment I do not know if my specific program will work over LPT.

On the other hand if you want to use Windows networking etc. you might find the pages here usefull:
Direct-Cable Connection Introduction

I have used their information successfully when connecting win95 and winXP some year ago, I can not recall the different steps etc. but I know that you can choose OS etc. in their FAQ and get information.

Regards,
Argus

If you have cables for LPT ports, which should be faster than serial, you could try that first before USB.

If you only want to establish connection and not create a network, i.e. you can manage files and folders on the other computer, then I think there might be small programs that will work on both machines directly after you have connected them. I did this between a old win95 and a WinXP over serial DCC. For the moment I do not know if my specific program will work over LPT.

On the other hand if you want to use Windows networking etc. you might find the pages here usefull:
Direct-Cable Connection Introduction

I have used their information successfully when connecting win95 and winXP some year ago, I can not recall the different steps etc. but I know that you can choose OS etc. in their FAQ and get information.

Regards,
Argus