skip to main content

Blue screen of death?

18 years ago

What is this? I sometimes get a blue screen says "fatal exception has occured", more info, and finally, "press any key to continue".

Is this something I should be concerned with? I seem to be going downhill here, even after taking maintenance precautions.

Using Windows98, and OE6.

Thanks for any info, you people are so patient with me!

Sort by:Oldest

Comments (7)

Chemocurl zn5b/6a Indiana
18 years ago
Yikes!

Did you maybe do a search on BSOD here? Below is a link to the results...until someone else comes along.

I have been plagued by it in the past. When it persists, the only fix I have found is to completely empty out the computer and reload everything (reformatting I'm told that is called) with Dell's help. It is certainly nothing I could do on my own.

I have been told that sometimes the BSOD itself holds a clue as to what the problem might be....but who wants to copy down all that stuff, and I have yet to learn how to copy the screen.

Best of luck to you.

Sue

Here is a link that might be useful: BSOD search results.
zep516
18 years ago
Here is a link from Microsoft, I get the error once in a while on my old 98se machine, In xp BLUE SCREEN OF DEATH means windows has simply stopped working and can relate to almost anything, hardware, ram, driver,& software ect--In 98 and I have never read the link closely but maybe a memory issue(Ram). I have always been able to recover by a reboot on mine, next time you get the error I would write it down because if it is hardware related, re-installing would be a waste of time, as I said I did not read the link so perhaps it also could be software related, a software related error as in xp would most likely indicate a 3ed party program something that was downloaded. Google these key words 'copy screen in 98' Or print screen key.

Here is a link that might be useful: FATAL ERROR
Related Discussions
Question about XP Re-Install
Q
Comments (2)
To start with, you can't just switch drives from one computer to another and expect it to boot to windows, unless the computers are the exact same make and model. You can put your C drive into the new computer and if you have a windows xp disc, do a repair install. If it asks for a product key, look on the case of the new computer for the sticker. If the new computer came with a HD and works, I'd just start transferring important data to it either with dvd or flash drives and eventually get it setup the way you like. The people that do a clean install are erasing the whole drive. Yes, a re-install will erase your entire C: drive, a repair install would leave your documents intact. You're going to need a windows xp disc to get started, also software needs to be installed to work, not just a simple transfer folders thing. You may be able to put your old C drive in the new computer, boot from the xp disc, go to the recovery console and fixboot or fixmbr and she may boot up. Don't know what windows genuine advantage or activation will do noticing your C drive has a different motherboard, video and ram.
...See More
Firefox won't display web graphics (just text) - then BSOD
Q
Comments (11)
Hi Zep, Here's the information from the Whocrashed report. System Information (local) -------------------------------------------------------------------------------- computer name: LYNNDELL windows version: Windows XP Service Pack 3, 5.1, build: 2600 windows dir: C:\WINDOWS Hardware: Inspiron 530, Dell Inc., 0FM586 CPU: GenuineIntel Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz Intel586, level: 6 4 logical processors, active mask: 15 RAM: 2950799360 total VM: 2147352576, free: 2022486016 -------------------------------------------------------------------------------- Crash Dump Analysis -------------------------------------------------------------------------------- Crash dump directory: C:\WINDOWS\Minidump Crash dumps are enabled on your computer. On Tue 6/10/2014 9:46:41 PM GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\Mini061014-01.dmp This was probably caused by the following module: win32k.sys (win32k+0x5FC9E) Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFBF85FC9E, 0xFFFFFFFFADB9BAE4, 0x0) Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M file path: C:\WINDOWS\system32\win32k.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Multi-User Win32 Driver Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. -------------------------------------------------------------------------------- Conclusion -------------------------------------------------------------------------------- One crash dump has been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you. Read the topic general suggestions for troubleshooting system crashes for more information. Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further. ------------------------------------------------------------ I'll try reinstalling Firefox, but I'm doubtful because during the course of today - after my initial Firefox difficulties, I did update from Firefox 29 to Firefox 29.0.1. So I can re-install 29.0.1, but installing it this afternoon did not fix the problem. I'll check back later. And now I'll reinstall. Thank you. Lynn.
...See More
BSOD - can't take the few steps rec. in prior posts
Q
Comments (10)
Hi, Zep, I had not run the whocrashed program bc. sysnative has it's own two programs it recommends. I used those - the diagnostic one contained 18 files filled with information I would not have been able to decipher - including 2 containing the dump file info that were roughly 3 and 11 MB (roughly). But your post reminded me to download whocrashed for the future. I went ahead and ran it for curiousity's sake. The results are below. It does seem they are suggesting a bad drive - and in at least one place they point to Avast. The larger diagnostic files generated for sysnative showed all the crashes were tied to an Avast driver. I uninstalled and it's been running fine. I might want to reinstall Avast since I run it on all our home desktops and laptops. I'm familiar with it and it hasn't posed a problem elsewhere. The folks at sysnative suggest waiting a little longer and using microsoft security essentials for now. Whocrashed: On Sun 8/4/2013 10:18:38 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\080413-21091-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80002CD2D6C) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Sun 8/4/2013 10:18:38 PM GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: aswsp.sys (aswSP+0x4133E) Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80002CD2D6C) Error: IRQL_NOT_LESS_OR_EQUAL Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: aswsp.sys . Google query: aswsp.sys IRQL_NOT_LESS_OR_EQUAL On Sun 8/4/2013 9:33:50 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\080413-21340-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80002C9CD6C) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Sun 8/4/2013 8:58:12 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\080413-21418-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80002CDCD6C) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Sun 8/4/2013 6:30:46 PM GMT your computer crashed crash dump file: C:\Windows\Minidump\080413-22152-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80002CE6D6C) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. ----------------------------- This report is in somewhat more plain English - but seems to contain less specific diagnostics than the tests for sysnative. thanks. Lynn. -------------------------------------------------------------------------------- Conclusion -------------------------------------------------------------------------------- 5 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers: aswsp.sys If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems. Read the topic general suggestions for troubleshooting system crashes for more information. Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
...See More
Microsoft has pulled one of the Tuesday updates!
Q
Comments (1)
Thanks for the update. Thankfully I stopped having my Windows 7 automatically update just last month. It would reboot without warning and was making me crazy.
...See More
zep516
18 years ago
I continue to see folks using these operating systems here windows 98SE and ME, 98SE probably one of the better written softwares from Microsoft, ME was the start of 2000/ xp and in fact has some features that xp has like system restore. But these systems are at risk on the Internet now, there is a certain group that target these systems because they can get at them eaisly...Never do any banking, E-bay, or any financial things on these systems. I think we all know this just wanted to get it out there.
DA_Mccoy
18 years ago
#1 cause of BSOD is RAM overload. Trying to do too much with too little RAM available.

DA
zep516
18 years ago
That's right, but they don't have a true BSOD, They have a fatal exception error as in windows 98, 95, so to look into this error you would need to examine "Fatal Exception Errors", BSOD errors are unique to xp, 2000, & vista where they give an error code like - 0c00000xe 000000a1 0000000ff, it is these errors that define the most probable cause and problem.
DA_Mccoy
18 years ago
I never argue a point I am not informed on, but I do have to report my old WIN98OE would BSOD when I tried to create a blivey sp? (Dutch for 10 lbs of **** in a five pound bag) on it. The screen would present the Fatal Exception Error alert with error code. I never did look it up as I knew what I was doing at the time was pushing the old codger to its limits.

DA
zep516
18 years ago
I stand corrected after looking around here is what I found my point was it is a different type of error, but your right still called a blue screen:

The blue screen of death frequently occurs in Microsoft's home desktop operating systems Windows 95, 98, and Me. Here it is usually less serious, but much more common. In these operating systems, the BSOD is the main way for virtual device drivers to report errors to the user. It is internally referred to by the name of "_VWIN32_FaultPopup". A Windows 9x/Me BSOD gives the user the option either to restart or continue. However, VxDs do not display BSODs frivolously Â they usually indicate a problem which cannot be fixed without restarting the computer, and hence after a BSOD is displayed the system is usually unstable or unresponsive.

Two of the most common reasons for BSODs are:

Problems that occur with incompatible versions of DLLs. This cause is sometimes referred to as DLL hell. Windows loads these DLLs into memory when they are needed by application programs; if versions are changed, the next time an application loads the DLL it may be different from what the application expects. These incompatibilities increase over time as more new software is installed, and is one of the main reasons why a freshly-installed copy of Windows is more stable than an "old" one.
Faulty or poorly written device drivers, hardware incompatibilities, or damaged hardware may also cause a BSOD. If you have just installed a new piece of hardware, updated a driver, or installed an Operating System update shortly before you see the BSOD, be sure to investigate these causes also.
In Windows 95 and 98, a BSOD occurred when the system attempted to access the file "c:\con\con" on the hard drive. This was often inserted on websites to crash users' machines. Microsoft has released a patch for this.[4]

The BSOD can appear if a user ejects a removable medium while it is being read on 9x/ME. This is particularly common while using Microsoft Office: if a user simply wants to view a document, he might eject a floppy disk before exiting the program. Since Microsoft Office always creates a temporary file in the same directory, it will trigger a BSOD upon exiting because it will attempt to delete the file on the disk that is no longer in the drive.

This type of blue screen is no longer seen in Windows NT, 2000, and XP. In the case of these less serious software errors, the program may still crash, but it will not take down the entire operating system with it due to better memory management and decreased legacy support. In these systems, the "true" BSOD is seen only in cases where the entire operating system crashes.

Related Stories

EXTERIORS The Joyful Exterior: How to Give Your Home Just the Right Touch of Blue

By Jennifer Ott Design

Here are ways to add blue to the outside of your house — and 8 palettes to try

GARDENING GUIDES Grow Your Own Privacy: How to Screen With Plants and Trees

By Jocelyn H. Chilvers

Use living walls to lower your home and garden's exposure while boosting natural beauty in your landscape

GARDENING AND LANDSCAPING Renovation Detail: The Blue Porch Ceiling

By Rachel Grace

Ghostly legends spurred the Haint Blue porch ceiling trend in the South, but you can pick this color just because it's pretty

BEDROOMS Dreaming in Color: 10 Beautiful Blue Bedrooms

By Jennifer Ott Design

Whether soft and sleepy or bold and splashy, see why blue can be the perfect hue in your bedroom

COLOR 10 Reasons to Use Sky Blue

By Laura Gaskill

This versatile color can look fresh or timeless, beachy or polished. Check out ways to use sky blue indoors and out

FRONT DOOR COLORS Front and Center Color: When to Paint Your Door Blue

By Jennifer Ott Design

Who knew having the blues could be so fun? These 8 exterior color palettes celebrate sunny-day skies to electric nights

COLOR Relax and Reflect in a Blue Landscape

Find sanctuary by introducing this well-loved hue outside

GARDENING GUIDES Great Design Plant: Try Blue Bells for Blooms in Dry Soil

By Noelle Johnson Landscape Consulting

This shrub’s violet-blue flowers and silvery foliage brighten low-water gardens all year long

COLOR Room of the Day: Deep Blue Proves a Hot Hue

By Mary Jo Bowling

Navy takes a New Jersey living room from dull to dashing in the flick of a paintbrush

COLOR PALETTES Summer Color Combo: Blue and Green

By Becky Harris

Consider 10 fresh approaches to the tried-and-true pairing

Sponsored

More Discussions

Tired of MS Office 365 Monthly Fees?

1