Overclockers Australia Forums

OCAU News - Wiki - QuickLinks - Pix - Sponsors  

Go Back   Overclockers Australia Forums > General Topics > Newbie Lounge

Notices


Sign up for a free OCAU account and this ad will go away!
Search our forums with Google:
Reply
 
Thread Tools
Old 25th July 2001, 9:39 PM   #1
CRusty_KID Thread Starter
(Banned or Deleted)
 
CRusty_KID's Avatar
 
Join Date: Jul 2001
Location: Southport, QLD
Posts: 82
Unhappy My Comp Won't Shut-down

ok. everytime i tried to shutdown/restart etc... my computer doesn't do it..

like.. i shut it down.. it goes to that blue 'windows is shutting down' screen.. then one of those blue error screens comes up. heres what it says

Windows
An exception error has occured at 0028:00000001 in VxD ---. This was called from 0028:C002F97D in VxD NTKERN(01) + 0000E23D. It may be possible to continue normally.
  • Press any key to attempt to continue
  • Press CTRL + ALT + DEL to restart your computer. You will lose any unsaved infomation in all applications

Press any key to continue


when i push any key.. it comes up again. And when i press CTRL ALT DEL.. it doesn't do anything.
I have to turn off the computer by holding the on button for a few seconds. Then when i start up the next time i have to wait for that scan disk thing

Thanks
CRusty_KID is offline   Reply With Quote

Join OCAU to remove this ad!
Old 25th July 2001, 10:54 PM   #2
Deus_Horribilus
Member
 
Join Date: Jun 2001
Location: Melbourne, Australia
Posts: 348
Default

Is your processor overclocked by any chance?
Deus_Horribilus is offline   Reply With Quote
Old 25th July 2001, 11:28 PM   #3
MoNk{LAH}
Member
 
MoNk{LAH}'s Avatar
 
Join Date: Jun 2001
Location: Melbourne
Posts: 17,277
Default

What version of windows are you running????

Make sure you get all the windows updates from microsoft, to iron out any bugs

That's the same message i got when using Win ME, and i never found a way to fix it, so i went to Win2k instead
__________________
Trading List
PS3 profile
GT5 Garage
My Avatar continually changes, to represent the game i'm playing on PS3
MoNk{LAH} is offline   Reply With Quote
Old 26th July 2001, 1:03 AM   #4
KinSlayer
Member
 
Join Date: Jun 2001
Location: Brisbane
Posts: 253
Default

This seems to be a common problem found with win98SE when you install the via's. Ive found the only way to reliably get round this is to clean install of windoze. Also go to the run command line and type msconfig. In that app that comes up look through the tabs till you find one called "Enable fast shutdown" make sure it is NOT ticked. if it is most likely your system will not shut down.

The other thing that could be doing it is that windows 98se has a problem with cpu's operating faster then 933mhz , apparantly there are issues with data corruption. I read some stuff somewhere that recommended allowing the computer to sit idle for a few seconds after you finish what you are doing before going for the shutdown.

Though if your getting blue screens of death a reinstall of windows cant hurt
KinSlayer is offline   Reply With Quote
Old 26th July 2001, 4:04 PM   #5
samos
Member
 
Join Date: Jun 2001
Location: Melbourne
Posts: 7,658
Default

Hmm dunno bout that, know a fair few people running 1000 mhz + in win 98 and don't get that prob...


hmmm weird, yeah i would re-install windows, use ME, if it continues to do so, if it keeps doing it latest drivers for everything etc, if it keeps doing it, oh well
samos is offline   Reply With Quote
Old 26th July 2001, 4:52 PM   #6
CRusty_KID Thread Starter
(Banned or Deleted)
 
CRusty_KID's Avatar
 
Join Date: Jul 2001
Location: Southport, QLD
Posts: 82
Default

thanks for the replies..
i have windows 98SE, I couldn't see any 'fast shutdown' thing anywhere in the msconfig.
and i don't overclock my computer either.. lol its only 355MHZ or somethinlike that
well i can't really reinstall windows.. because i don't have a CD writer to put all my files onto cd.
or does windows keep the files when i re-install?
CRusty_KID is offline   Reply With Quote
Old 26th July 2001, 6:26 PM   #7
Deus_Horribilus
Member
 
Join Date: Jun 2001
Location: Melbourne, Australia
Posts: 348
Default

This sounds similar, but not exactly like a problem widespread in Win98SE releases, in which the OS will not shut down. Microsoft has a patch for it on their site. No reinstall required if it works. If not, consider going up to Win2k, it is much better, if your computer can handle it (my K6-2 500@550 runs it v. smoothly). 128MB of RAM is a good idea though.
Deus_Horribilus is offline   Reply With Quote
Old 27th July 2001, 4:39 PM   #8
ashdaw
(Banned or Deleted)
 
Join Date: Jul 2001
Posts: 45
Default

Have you tried the VXD fix?? cause that May help also.. WIN98 had this trouble and it is sometimes cause of the MASSIVE VMM32.vxd which is made when the OS is installed..

WIN98 VXD BUG


Have you ever got a "VxD error" message while starting Windows 98 or 98 SE?
It's pretty much "fatal", and automatically returns you to the DOS prompt.
Especially if you upgraded to Win98 from Win95 or OSR2, since some old 32-bit protected virtual drivers might have "survived" the upgrade.
The MS Windows 98 Resource Kit Help file (Win98rk.hlp, found in the \Tools\Reskit\Help folder on the Win98 Setup cd-rom) states that:
"If a virtual device driver (VxD) is missing or damaged, Windows 98 displays an error message that indicates which VxD is involved. If the VxD is critical to the operation of Windows 98, then Windows 98 does not start and the screen displays the command prompt. You might need to run Windows 98 Setup and select Verify or Safe Recovery to replace the missing VxD."

But there is an easier solution to this problem.
The generic driver Vmm32.vxd (located in C:\Windows\System) was built when you first installed Win98 on your computer. Depending on your hardware specs, it may contain some or all of the following VXDs (Virtual eXtended Drivers): biosxlat.vxd, configmg.vxd, dynapage.vxd, ebios.vxd, enable.vxd, ifsmgr.vxd, int13.vxd, ios.vxd, parity.vxd, reboot.vxd, vcache.vxd, vcd.vxd, vcomm.vxd, vcond.vxd, vdd.vxd, vdef.vxd, vfat.vxd, vfbackup.vxd, vflatd.vxd, vkd.vxd, vmcpd.vxd, vmouse.vxd, vmpoll.vxd, vpd.vxd, vsd.vxd, vtdapi.vxd, vwin32.vxd, vxdldr.vxd. Vmm32.vxd is not only slow to load (because of its huge size), but if you have added/changed your hardware devices after installing Win98, this old driver might not match your system specs anymore.
Certain system errors, like random lockups, error messages at startup, VMM errors, erratic and/or slow mouse movement etc, might be resolved by selectively overriding a VXD included within Vmm32.vxd.
Start by manually extracting one or more of these individual drivers from the .CAB files found in the \Win98 folder on your Win98 Setup cd-rom, and then copying them to your C:\Windows\System\Vmm32 folder (change the Windows folder name if different on your machine). Use this command line (example):

EXTRACT /Y /A D:\WIN98\BASE4.CAB VCOMM.VXD

to extract VCOMM.VXD to the current directory. Typing in the first .CAB file name in a given folder (in this case BASE4.CAB), forces EXTRACT.EXE to search all CABs in the same directory for the file you specify.
Change the cd-rom drive letter if different on your system.
Now move VCOMM.VXD to C:\Windows\System\Vmm32, and reboot.
From now on Win98 will use the individual VXD instead of the one contained in Vmm32.vxd, because if the same VXD loads twice, the second instance (in this case the one in C:\Windows\System\Vmm32) intercepts all the calls to that particular VXD.
Alternatively you can edit System.ini (located in your Windows folder) using Notepad, and add an entry for the VXD you know creates "problems", under the [386enh] section. Example:

device=vcomm.vxd

VXDs known to generate error messages more frequently are: configmg.vxd, ntkern.vxd, vcomm.vxd, vdd.vxd, vdmad.vxd, vflatd.vxd and vmouse.vxd.
You can also check which VXDs are used in Vmm32.vxd on your Win98 computer by running Control Panel -> System -> Device Manager tab -> Your device name -> Driver tab -> Driver File Details button, and look for all drivers that have VMM32 in parenthesis after their filenames. Example:

C:\WINDOWS\SYSTEM\VCOMM.VXD (VMM32)

Check all items on your Device Manager list for similar drivers and write down their names. Extract them to C:\Windows\System\Vmm32 and then reboot.
Now go back into Device Manager, and check again for the same drivers. You'll notice that all (VMM32) instances after the driver filenames are gone.

WARNING: If you exceed the maximum number of VXDs allowed by Windows 9x at startup (80), the GUI may fail to load or display a Blue Screen Of Death (BSOD)!

FYI:


Run VXD_FIX.BAT [23 KB, free] to copy all necessary VXD files from your Win98/98 SE(U) Setup cd-rom to the C:\Windows\System\Vmm32 folder.
See this guide for recreating VMM32.VXD.
Search MSKB for (keyword) VMM32.VXD.
ashdaw is offline   Reply With Quote
Old 28th July 2001, 12:08 PM   #9
CRusty_KID Thread Starter
(Banned or Deleted)
 
CRusty_KID's Avatar
 
Join Date: Jul 2001
Location: Southport, QLD
Posts: 82
Default

ok thanks for that. i have already fixed up all my VxD files by doing what is said in this thing.. http://www.hogens.com/review/info/wi...kup/index4.htm
CRusty_KID is offline   Reply With Quote
Reply

Bookmarks

Sign up for a free OCAU account and this ad will go away!

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +10. The time now is 11:33 PM.


Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2013, Jelsoft Enterprises Ltd. -
OCAU is not responsible for the content of individual messages posted by others.
Other content copyright Overclockers Australia.
OCAU is hosted by Internode!