[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference decwet::windows-nt

Title:Windows NT
Notice:See note 15.0 for HCL location
Moderator:TARKIN::LIN.com::FOLEY
Created:Thu Oct 31 1991
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6086
Total number of notes:31449

5847.0. "Size of Registry causes Bluescreens" by SAPEC3::BACHOFER () Wed Mar 26 1997 08:38

Hello,

I have a problem around the size of the registry.

The machine is a 4CPU (300MHz) AS4100 with 2GB of memory
running NT40 with SP2 and the Hotfix for Alpha.
AlphaBios is 5.28.
(I only tested this on an AS4100 yet)

A colleage also has this problem. He uses an AS4000 with 
1CPU (400MHz) and 512 KB memory.

To reproduce the problem add some dummy keys and values
into the registry.
As a result I got the filesizes:

system   ~ 2,70 MB   (before adding the dummies it was 0,7 MB)
software ~ 0,58 MB
security ~ 0,02 MB
sam      ~ 0,02 MB

for the registry files.

Up to now the system works properly.
The problem occurs when rebooting the machine.

The error which appears when rebooting the system is a bluescreen:

STOP: 0x0000001E (0xC000001D,0x807C0A84,0x00000000,0x00000000)
KMODE_EXCEPTION_NOT_HANDLED
MS WIN NT 0xf000565
Machine State at Call to Bug Check PC : 800BB10C PSR : 00000002

Callee-Sp Return-Ra  Dll Base - Name
EX889530  800BB10C : 80080000 - ntoskrnl.exe
EX889820  800BF384 : 80080000 - ntoskrnl.exe
EX8898C0  800BF324 : 80080000 - ntoskrnl.exe
EX889AC0  807C0A88 : 80080000 - ntoskrnl.exe
EX889AC0  80729A80 : 00000000 - 
EX889AC0  80729A80 : 00000000 - 
EX889AC0  80729A80 : 00000000 - 
EX889AC0  80729A80 : 00000000 - 

IRQL : 7, DPC Active : FALSE


The value for the current registry size is 3 MB.
And the registry size limit is 44 MB.
(I also increase the RSL up to 100MB without any success.)



Any ideas are welcome

Thanks & Ciao

HJ Bachofer
DEC/SAP Engineering Walldorf/Germany

T.RTitleUserPersonal
Name
DateLines
5847.1same failure on as1000a. reported to Microsoft.CSCMA::HODGEWed Apr 23 1997 12:3718
    more information:
    
    The customer encountered this problem when adding shares and printers
    to the system, not by putting junk in the registry.
    
    The same type of crash occurs on an AS1000A 5/400, but was not
    duplicated on an AS1000 4/200.
    
    A AS2100 5/250 will crash after doubling the size of the system hive
    from around 2MB to 4MB, but fails with a STOP 67.  
    stop 0x00000067 (0,0,0,0)
    config_initilization_failed
    Subsequent boots on the AS2100 are ok.
    
    The problem has been reported to Microsoft.  
    I will update this note as soon as it is resolved.
    
    Frannie