Originally Posted by the_real_spongebob

hi jephree,

The software "WhoCrashed" need to be purchased. Can the free version do the job too?

Take a look here: Resplendence Software - Free Downloads

Jim

Hi there,

just one question. Do you have overheating problems? i had the same issue yesterday where each time i booted up (a total of 26 times.. yeah i counted!) i got the BSoD. i finally solved it by fixing the CPU fan aftresh. try that.. maybe it will help...

Cheers,

ReB

PS: to check for CPU temp look at the screen as soon as you boot up.... I use WinXP Pro... average boot up temp should not be more than the ambient temp of the room ur in... i.e if its 50F in the room the comp should not register more than 60F on booting up... Mod's feel free to correct this..

I have tried Diagnostic Startup and Selective Startup and still getting BSoDs. I haven't tried memtest yet as i don't have a burner to create a disc. I tried "WhoCrashed" utility and below are some of the common crashes detected:

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.


Too many crashes have been detected. Only the latest 40 crashes will be displayed.

On Mon 05/10/2009 07:24:41 your computer crashed
This was likely caused by the following module: hardware
Bugcheck code: 0x10000050 (0xEF9E004B, 0x1, 0x80573B08, 0x0)
Error: Unknown
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on hardware





On Mon 05/10/2009 05:57:06 your computer crashed
This was likely caused by the following module: hardware
Bugcheck code: 0x10000050 (0xEDE0004B, 0x1, 0x80573B08, 0x0)
Error: Unknown
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on hardware





On Mon 05/10/2009 05:16:56 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000008E (0xC0000005, 0x804EF79A, 0xF6826BF0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Mon 05/10/2009 0419 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000008E (0xC0000005, 0x80579266, 0xF6E5BCA0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sun 04/10/2009 05:39:36 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000008E (0xC0000005, 0x80579266, 0xED067CA0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sat 03/10/2009 08:10:12 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000008E (0xC0000005, 0x80579266, 0xF7965CA0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sat 03/10/2009 08:04:45 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000008E (0xC0000005, 0x804EF79A, 0xB260DBEC, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.

.
.
.

On Fri 02/10/2009 2238 your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x24 (0x1902FE, 0xB2A25B9C, 0xB2A25898, 0x0)
Error: NTFS_FILE_SYSTEM
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.


.
.
.

On Fri 02/10/2009 06:24:43 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x1000008E (0xC0000005, 0x805512B6, 0xF7663750, 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
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.

.
.
.

On Wed 30/09/2009 15:05:17 your computer crashed
This was likely caused by the following module: ndis.sys
Bugcheck code: 0x1000008E (0xC0000005, 0x80579266, 0xB9C68CA0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\ndis.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NDIS 5.1 wrapper driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



Could someone help analyse above and tell me what to do next pls..

hi rebellion,

i don't understand how cpu could get overheated so soon after rebooted. besides i have the aircon and fan running. what do u mean by "to check for CPU temp look at the screen as soon as you boot up". Is there something on screen showing cpu temp?

The first thing that needs to be done is check that windows system files are OK

You do that by using System File Checker (SFC) you will need your XP installation disc for this.

Instructions on how to use SFC found here: scannow sfc - LEARN how to use SFC.EXE (system file checker)

You will also need to run chkdsk
Instructions found here:

How to Understand and Use Chkdsk in Windows XP

You also need to do the memory test



None of this is worth doing until you know your memory is OK
How much ram do you have.
If you right click My Computer and select properties you can see how much ram you have in your PC there.
If you have I.00 GB of ram or more then you will most likely have 2 sticks of 521MB of ram.
You could try removing one stick and see if you get the BSOD
If you do put in the other and see if you get the BSOD
In this way you could check to see if one your memory modules is faulty.

Windows will run OK on 512MB of ram

As an additional thought you said "I haven't tried memtest yet as i don't have a burner to create a disc".
All PC's today come with a DVD/CD burner is your PC an old system or is your DVD/CD faulty?
Second question If the DVD/CD is faulty is the DVD/CD burner still fitted in the PC?

Jim

Originally Posted by pjmcginley

when i turn on my pc it gets to the welcome to windows xp, click on user name then i get the blue screen sometimes i get the small dialogue box that says task manager has been diabled by administrator.

You really should start a new post on this. Its considered impolite to try to take over
someone else's problem.

If you want help you really should create a fresh post. Giving details of BSOD.
with the complete error message.


NOTE: Threads mentioned above have been moved to the XP Forum under Computer won't boot.
Dan Penny

I have tried typing "chkdsk /f" under Start>Run and my pc restarted and my hard disk was scanned
before windows was loaded. The result showed my hard disk ok.

I have something to say about the RAM. My pc is able to work only after I shut it down for hours. I
am using the same pc to type this here. But every time after using my pc for like 30 minutes to an
hour or so, windows would either hang up and stop responding, or BSoDs would appear, most often
with stop error code 0x0000008E. What can I do?? The only thing I could do there is to reboot my pc
with its on-off button. Well that's not the end of it. No matter how times I reboot my pc, BSoDs
keep appearing at the point when windows begins to load or when windows has loaded halfway. The
error codes here are ususally 0x0000007E, 0x0000007F, 0x0000008E, 0x00000024, 0x00000050. It is
only after I shut down my pc for hours then I could get it to work again but only, like I mentioned
above, for 30 minutes to an hour or so and the entire problem cycle kicks in again. *sigh* Any
clues here you could find to help fix the BSoD problem? Anything you coud uderstand out of these
error codes? Come to think of the fact that my pc could work initially for the first 30 minutes to
an hour or so, I reckon that my RAM shouldn't be faulty but rather the BSoD problem could be caused
by something else, maybe drivers? What do you think? Please correct me if I am wrong.

I was wondering if running System File Checker would help. You see, my Windows has been updated
many times through Windows Update and if I run SFC, won't I get many system file errors as these
files definitely have changed from they were initially. Therefore no point using SFC, right?

How can I determine which drivers need to be updated? Is there a free program out there I could use
to scan my pc for necessary driver updates?

Hey thank you all.

P.S.: While typing this, Windows hung up again and I rebooted my pc but couldn't get Windows to
load as BSoS kept appearing each time I rebooted. I finally got it to work after shutting down my
pc for a few hours. Wondering how I type this, well, I saved it on notepad continued the next successful boot.

You have a hardware problem, most likely caused by overheating. Check all fans, especially the fan in the power supply and on the video card if there is a fan on it.

Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M

I'm reading that memory needs to be testing when a system gives you this error so need to do whatever it takes to test it to rule this out as a problem or confirm that it is and that would be with memtest like previously suggested. The alternative is to replace the ram but it might not be your ram.

Also it could be a driver problem so you could get it to boot without a BSOD I would do so in safe mode to make sure that minimal drivers are used. Leave it running like that for a few hours. An alternative to rule out windows or your drivers is to run your computer off of a linux live distribution. I like Knoppix. You will download it as an ISO & you will have to burn it to a disk (read how). If you don't have the resources to perform these tests then you could take it to a technician. I see no way for you to get much further than you are now without obtaining a cd burner and a keyboard or taking it to a tech. If you can't depend upon using your computer long enough to download & burn either linux or memtest then you might need to borrow another computer to do so.

To rule out heat you either need to be able to get into your bios & hope that it has a temperature display in it or, if you can get windows going, install & run a temperature monitoring program such as speedfan. You can set speedfan to log your temperatures.

You should also check the memory dump file (read how). You will need to download & install the windows debugging tools & the symbols package for you computer (download). If you borrow another computer that can be done from that computer but you will have to get the dump files from your computer. That could give you a clue as to whether it is a driver (and perhaps which one) or if it is your memory.

Did you run SFC like Jim suggested?

Originally Posted by Ztruker

You have a hardware problem, most likely caused by overheating. Check all fans, especially the fan in the power supply and on the video card if there is a fan on it.

I would with Ztruker agree that heat could be the part of the problem but all the BSOD's
suggest other problems and all townsbg's comments point you in the right direction to
trouble shoot your problems.
If cannot obtain a CD/DVD burner then perhaps you could enlist the help of a friend and download and burn the tools you need to test your PC

Running your PC on a Linux live CD would help to rule out OS errors because if you still get
errors in Linux then clearly the problem points to hardware.

For information on your Windows BSOD's see below

If yo got to Troubleshooting Windows STOP Messages

you can look up all your BSOD errors for instance BSOD 0x00000024

aumha.org advises this : -

0x00000024: NTFS_FILE_SYSTEM
(Click to consult the online MSDN article.)
A problem occurred within NTFS.SYS, the driver file that allows the system to read and write to NTFS file system drives. There may be a physical problem with the disk, or an Interrupt Request Packet (IRP) may be corrupted. Other common causes include heavy hard drive fragmentation, heavy file I/O, problems with some types of drive-mirroring software, or some antivirus software. I suggest running ChkDsk or ScanDisk as a first step; then disable all file system filters such as virus scanners, firewall software, or backup utilities. Check the file properties of NTFS.SYS to ensure it matches the current OS or SP version. Update all disk, tape backup, CD-ROM, or removable device drivers to the most current versions.

0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
(Click to consult the online MSDN article.)
Requested data was not in memory. An invalid system memory address was referenced. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause this Stop message, as may other hardware problems (e.g., incorrect SCSI termination or a flawed PCI card).