re: New machine keeps bombing
Monday, December 13, 2004 at 7:30 pm
Windows 2000 Annoyances Discussion Forum
Posted by DEX
(11847 messages posted)
Bojanglez
Errors 1001 and 1026.txt
see below
http://techsupt.winbatch.com/TS/T000002026F35.html
-----------------------------------------------------
OR it may be kernel space available
This problem occurs because there is a limited amount of kernel space available for
kernel drivers. If the operating system runs out of kernel space, then the computer
displays a blue screen error message.
Modify the registry by adding the KStackMinFree value
Windows 2000 running NTFS
Windows 2000 running NTFS examines the available kernel stack before processing an
I/O request. If NTFS determines that there is insufficient stack space, then an exception
error results. If there is not enough stack space for processing the exception, then
a stack overflow occurs and the system double-faults, resulting in a blue screen
with a STOP message
Windows 2000 kernel space
The limit is 12 KB for kernel drivers.
Required minimum available kernel memory
recommends a range between 8.0 KB and 8.5 KB (Hex 2000-2200), though each environment
is different and it may take some experimenting to find the right value. Other possible
values are defined in the following chart.
HEX Value
5.0 KB 0x1400
5.5 KB 0x1600
6.0 KB 0x1800
6.5 KB 0x1a00
7.0 KB 0x1c00
7.5 KB 0x1e00
8.0 KB 0x2000
8.5 KB (recommended) 0x2200
9.0 KB 0x2400
Notes:
* If the value is set too low, then a stack overflow can occur and the system
will stop responding.
* If the value is set too high, then file scans will be skipped unnecessarily.
* If the registry value is not present, set to 0, or greater than 0x2400, then
file system real-time protection behaves normally.
Note: On Windows NT/2000/XP systems, you must have Administrator access to do this.
How to start the 32 bit Registry Editor
The 32 bit Registry Editor, RegEdt32.exe, is available only in Windows NT, Windows
2000, and Windows XP.
1. Exit all open programs.
2. Click Start, and then click Run. The Run dialog box appears.
3. Type regedt32 and then click OK. The Registry Editor window appears.
How to add a value
1. Open the registry list to the folder where you want to add the new value.
2. Right-click where you want to add the new value.
3. Point to New, and then click the type of value you want to add: String Value,
Binary Value, or DWORD Value.
The new value appears with a temporary name.
4. Type a name for the new value, and then press ENTER.
How to change a value
1. Double-click the value you want to change.
2. In the Edit dialog box, change the Value Data by entering a new value.
3. Click OK to save the changes.
How to exit the Registry Editor
1. Click Registry and click Exit to save the changes and close the Registry Editor.
2. Restart the computer.
On Monday, December 13, 2004 at 5:59 pm, Bojanglez wrote:
>i put together a new machine at the weekend (p4 3.2 (ht), 2gb pc3200 RAM, 120gb
HDD,
>Nvidia 6800 graphics card) but it's been very unstable - the machine works beautifully
>for a while, then reboots itself, mostly without any warning or explanation on the
>screen - it can be installing something, updating from the web, or launching an
app
>(it doesn't seem to do it while Idle).
>
>I checked my system log and saw 11 x Event 1001, Source:Save Dump that have varied
>entries - all referencing 'a bugcheck' - I'm presuming the issue is RAM, but i would
>really appreciate ANY help anyone can give, it's very frustrating not being able
>to indentify the source of the issue - thanks in advance for ANY help anyone can
>offer on this -
>
>the Dumps, from newest to oldest, are:
>
>Event Type: Information
>Event Source: Save Dump
>Event Category: None
>Event ID: 1001
>Date: 12/13/2004
>Time: 6:45:32 PM
>User: N/A
>Computer: Home
>Description:
>The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xc6d34f42,
>0x00000001, 0x01010043, 0x00000000). Microsoft Windows 2000 [v15.2195]. A dump was
>saved in: C:\WINNT\Minidump\Mini121304-05.dmp.
>
>Event Type: Information
>Event Source: Save Dump
>Event Category: None
>Event ID: 1001
>Date: 12/13/2004
>Time: 1:22:24 PM
>User: N/A
>Computer: Home
>Description:
>The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0xb49e8d10,
>0x00000002, 0x00000000, 0x8042d781). Microsoft Windows 2000 [v15.2195]. A dump was
>saved in: C:\WINNT\Minidump\Mini121304-04.dmp.
>
>Event Type: Information
>Event Source: Save Dump
>Event Category: None
>Event ID: 1001
>Date: 12/13/2004
>Time: 12:55:49 AM
>User: N/A
>Computer: Home
>Description:
>The computer has rebooted from a bugcheck. The bugcheck was: 0x000000be (0xa001d21f,
>0x0cdca121, 0xbc003f70, 0x0000000b). Microsoft Windows 2000 [v15.2195]. A dump was
>saved in: C:\WINNT\Minidump\Mini121304-03.dmp.
>
>Event Type: Information
>Event Source: Save Dump
>Event Category: None
>Event ID: 1001
>Date: 12/13/2004
>Time: 12:41:32 AM
>User: N/A
>Computer: Home
>Description:
>The computer has rebooted from a bugcheck. The bugcheck was: 0x000000be (0xa001d21f,
>0x0cdc9121, 0xbbf01600, 0x0000000b). Microsoft Windows 2000 [v15.2195]. A dump was
>saved in: C:\WINNT\Minidump\Mini121304-02.dmp.
>
>Event Type: Information
>Event Source: Save Dump
>Event Category: None
>Event ID: 1001
>Date: 12/13/2004
>Time: 12:38:28 AM
>User: N/A
>Computer: Home
>Description:
>The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x4020006f,
>0x000000ff, 0x00000000, 0x80401807). Microsoft Windows 2000 [v15.2195]. A dump was
>saved in: C:\WINNT\Minidump\Mini121304-01.dmp.
>
>Event Type: Information
>Event Source: Save Dump
>Event Category: None
>Event ID: 1001
>Date: 12/12/2004
>Time: 11:43:41 PM
>User: N/A
>Computer: Home
>Description:
>The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0x4028dc99,
>0x00000002, 0x00000000, 0x8043ef01). Microsoft Windows 2000 [v15.2195]. A dump was
>saved in: C:\WINNT\Minidump\Mini121204-06.dmp.
>
>Event Type: Information
>Event Source: Save Dump
>Event Category: None
>Event ID: 1001
>Date: 12/12/2004
>Time: 11:42:28 PM
>User: N/A
>Computer: Home
>Description:
>The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0xc0000005,
>0xa00cf806, 0x00000000, 0x00000168). Microsoft Windows 2000 [v15.2195]. A dump was
>saved in: C:\WINNT\Minidump\Mini121204-05.dmp.
>
>Event Type: Information
>Event Source: Save Dump
>Event Category: None
>Event ID: 1001
>Date: 12/12/2004
>Time: 11:39:59 PM
>User: N/A
>Computer: Home
>Description:
>The computer has rebooted from a bugcheck. The bugcheck was: 0x000000c5 (0x0000003d,
>0x000000ff, 0x00000000, 0x80467004). Microsoft Windows 2000 [v15.2195]. A dump was
>saved in: C:\WINNT\Minidump\Mini121204-04.dmp.
>
>Event Type: Information
>Event Source: Save Dump
>Event Category: None
>Event ID: 1001
>Date: 12/12/2004
>Time: 10:58:11 PM
>User: N/A
>Computer: Home
>Description:
>The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0xc000001d,
>0x88ba84b9, 0xbff89d73, 0x88fef030). Microsoft Windows 2000 [v15.2195]. A dump was
>saved in: C:\WINNT\Minidump\Mini121204-03.dmp.
>
>Event Type: Information
>Event Source: Save Dump
>Event Category: None
>Event ID: 1001
>Date: 12/12/2004
>Time: 10:54:56 PM
>User: N/A
>Computer: Home
>Description:
>The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0xc0000005,
>0xa000be42, 0x00000000, 0x00000002). Microsoft Windows 2000 [v15.2195]. A dump was
>saved in: C:\WINNT\Minidump\Mini121204-02.dmp.
>
>Event Type: Information
>Event Source: Save Dump
>Event Category: None
>Event ID: 1001
>Date: 12/12/2004
>Time: 10:44:56 PM
>User: N/A
>Computer: Home
>Description:
>The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0xc000001d,
>0xbfbe8506, 0xfff79b90, 0xffffffff). Microsoft Windows 2000 [v15.2195]. A dump was
>saved in: C:\WINNT\Minidump\Mini121204-01.dmp.
- Written in response to:
- New machine keeps bombing (Bojanglez: Monday, December 13, 2004 at 5:59 pm)
Responses to this message:
|
|
All messages in this thread [show all]
 |  | re: New machine keeps bombing (DEX: Mon, Dec 13, 2004, 7:30 pm) |
|
