System.ini

[TheCardMan]

Starting up normal causes a BSOD when windows kicks in. I went to safe mode and got into MSCONFIG, I used selective startup to identify where the problem is stemming from. I found that I can boot with everything check but the system.ini. If I have it load the system.ini I get BSOD. How can I narrow this down further? I have a feeling it has to do with corrupt drivers.

[shamus]

Run sysedit and see if anything looks questionable in the system.ini file. It may take some trial and error, but rem out items in [drivers] one at a time the same way you narrowed it down with msconfig.
If it is a corrupt file, you could run SFC and let Windows check and see if it finds anything.

[craigmodius]

Also make sure the TTFontDimenCache entry looks like this...

[TTFontDimenCache]
0 4=2 4
0 5=3 5
0 6=4 6
0 7=4 7
0 8=5 8
0 9=5 9
0 10=6 10
0 11=7 11
0 12=7 12
0 13=8 13
0 14=8 14
0 15=9 15
0 16=10 16
0 18=11 18
0 20=12 20
0 22=13 22

If you have several duplicate entries of the 4= thru 22= lines then it's bad news. However this usually shows up with a not enough memory to run windows error as noted

here (http://support.microsoft.com/?kbid=311367)

[Orangeman]

You could also uncheck every item in the system.ini (about 17 items) and reboot like you normally do, until you find the baddy.

When you find it you can either uncheck it, or highlight it and click EDIT, then place a semicolon in front of the line that is causing you problems. Click OK, and restart.

Like he said, its probably a bad or stuck driver that didn't uninstall.

:D

[TheCardMan]

Thanks everyone! I isolated the problem with the help of all of you. Going one by one throughout the system.ini, I narrowed it down to the [boot] section, when checked one at a time I found that the follow line gave me the BSOD: system.drv=atmsys.drv, which relates to adobe type manager. I removed that line along with atm.system.drv=system.drv, and all is working well.

Appreciate all the responses!!

-Joe