ntoskrnl.exe BSOD Windows XP

Toggle sidebar Toggle sidebar
R

RCSTEAM

Reputable
Jul 19, 2015
3
0
4,510
For a while now I had been getting BSOD's when running Chrome and Steam at the same time. Recently however I started getting BSOD's whenever I try to login. I have managed to pinpoint through BlueScreenView that all the crashes I had experienced were due to ntoskrnl.exe. I have tried replacing that file so I know the file is not corrupt but I still recieve the same error.

I am running (yes it is pretty bad but I am waiting for an upgrade :)):
Windows XP SP2
AMD Athlon II X2 215
HP Narra 6
Nvidia GT 620
Creative Sound Blaster Audigy

Here is the crash reports for the last 5 crashes
==================================================
Dump File : Mini110116-01.dmp
Crash Time : 01/11/2016 10:38:30
Bug Check String : CRITICAL_OBJECT_TERMINATION
Bug Check Code : 0x000000f4
Parameter 1 : 0x00000003
Parameter 2 : 0x8b0e4020
Parameter 3 : 0x8b0e4194
Parameter 4 : 0x805d115e
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+22c4b
File Description : NT Kernel & System
Product Name : Microsoft(R) Windows(R) Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.2622 (xpsp_sp2_gdr.050301-1519)
Processor : 32-bit
Crash Address : ntoskrnl.exe+22c4b
Stack Address 1 : ntoskrnl.exe+f9305
Stack Address 2 : ntoskrnl.exe+fa209
Stack Address 3 : ntoskrnl.exe+6961c
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini110116-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 90,112
Dump File Time : 01/11/2016 10:39:23
==================================================

==================================================
Dump File : Mini103116-08.dmp
Crash Time : 31/10/2016 23:17:06
Bug Check String :
Bug Check Code : 0xc000021a
Parameter 1 : 0xe20009d0
Parameter 2 : 0xc0000005
Parameter 3 : 0x7c9111de
Parameter 4 : 0x0052f96c
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+22c4b
File Description : NT Kernel & System
Product Name : Microsoft(R) Windows(R) Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.2622 (xpsp_sp2_gdr.050301-1519)
Processor : 32-bit
Crash Address : ntoskrnl.exe+22c4b
Stack Address 1 : ntoskrnl.exe+eea4a
Stack Address 2 : ntoskrnl.exe+17e377
Stack Address 3 : ntoskrnl.exe+13b86e
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini103116-08.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 90,112
Dump File Time : 31/10/2016 23:18:26
==================================================

==================================================
Dump File : Mini103116-07.dmp
Crash Time : 31/10/2016 23:06:28
Bug Check String : CRITICAL_OBJECT_TERMINATION
Bug Check Code : 0x000000f4
Parameter 1 : 0x00000003
Parameter 2 : 0x8b268a40
Parameter 3 : 0x8b268bb4
Parameter 4 : 0x805d115e
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+22c4b
File Description : NT Kernel & System
Product Name : Microsoft(R) Windows(R) Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.2622 (xpsp_sp2_gdr.050301-1519)
Processor : 32-bit
Crash Address : ntoskrnl.exe+22c4b
Stack Address 1 : ntoskrnl.exe+f9305
Stack Address 2 : ntoskrnl.exe+fa209
Stack Address 3 : ntoskrnl.exe+6961c
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini103116-07.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 90,112
Dump File Time : 31/10/2016 23:07:58
==================================================

==================================================
Dump File : Mini103116-06.dmp
Crash Time : 31/10/2016 22:43:54
Bug Check String :
Bug Check Code : 0xc000021a
Parameter 1 : 0xe22c3800
Parameter 2 : 0xc0000005
Parameter 3 : 0x7c9106c3
Parameter 4 : 0x00c8f36c
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+22c4b
File Description : NT Kernel & System
Product Name : Microsoft(R) Windows(R) Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.2622 (xpsp_sp2_gdr.050301-1519)
Processor : 32-bit
Crash Address : ntoskrnl.exe+22c4b
Stack Address 1 : ntoskrnl.exe+eea4a
Stack Address 2 : ntoskrnl.exe+17e377
Stack Address 3 : ntoskrnl.exe+13b86e
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini103116-06.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 90,112
Dump File Time : 31/10/2016 22:44:48
==================================================

==================================================
Dump File : Mini103116-05.dmp
Crash Time : 31/10/2016 22:41:32
Bug Check String :
Bug Check Code : 0xc000021a
Parameter 1 : 0xe2f77d78
Parameter 2 : 0xc0000005
Parameter 3 : 0x7c9106c3
Parameter 4 : 0x0100ed04
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+22c4b
File Description : NT Kernel & System
Product Name : Microsoft(R) Windows(R) Operating System
Company : Microsoft Corporation
File Version : 5.1.2600.2622 (xpsp_sp2_gdr.050301-1519)
Processor : 32-bit
Crash Address : ntoskrnl.exe+22c4b
Stack Address 1 : ntoskrnl.exe+eea4a
Stack Address 2 : ntoskrnl.exe+17e377
Stack Address 3 : ntoskrnl.exe+13b86e
Computer Name :
Full Path : C:\WINDOWS\Minidump\Mini103116-05.dmp
Processors Count : 2
Major Version : 15
Minor Version : 2600
Dump File Size : 106,496
Dump File Time : 31/10/2016 22:43:35
==================================================

Thanks
 
Solution
ChaoticWolf
It's kind of hard to distinguish the exact problem in a case like this
Critical Object Termination somewhat sounds like a process that windows needs enabled in the background being terminated, but I dont know for sure

You should try a few things, maybe install the latest updates to your system, for example upgrade to Windows XP SP3, and install any updates that you haven't downloaded and installed yet, atleast the ones that are still left to download until Windows XP was discontinued by Microsoft

Also, maybe you should check your memory,The ntoskrnl.exe BSOD is usually related to memory so you might need to simply replace your RAM. Take out each stick of RAM one by one and try to boot your system, this may help you find the faulty...
Sort by date Sort by votes
ChaoticWolf

ChaoticWolf

Honorable
Feb 2, 2016
639
1
11,365
It's kind of hard to distinguish the exact problem in a case like this
Critical Object Termination somewhat sounds like a process that windows needs enabled in the background being terminated, but I dont know for sure

You should try a few things, maybe install the latest updates to your system, for example upgrade to Windows XP SP3, and install any updates that you haven't downloaded and installed yet, atleast the ones that are still left to download until Windows XP was discontinued by Microsoft

Also, maybe you should check your memory,The ntoskrnl.exe BSOD is usually related to memory so you might need to simply replace your RAM. Take out each stick of RAM one by one and try to boot your system, this may help you find the faulty memory but the lot might need replacing.

Update any drivers for any of your devices that may be outdated

Maybe restore your system using System Restore to a point in time where the issues wouldn't happen at all if you have any or if you want to

A few more things you should try are clearing the CMOS in the bios of your system
Disconnect all power to the PC, disconnect the cord to the system, flip the switch at the back in the psu if there is any switches, which some dont include, hold the power button for 8 seconds or so to discharge any power left remaining in the system, open up the system, and look for a small calculator looking battery attached to the motherboard, pull it out carefully and see if it comes out, on some motherboards it wont come out at all, so if it doesnt at all, dont force it at all, and look for the bios jumper, the bios jumper will look something like this: http://pad2.whstatic.com/images/thumb/7/71/Reset-Your-BIOS-Step-8.jpg/aid40069-728px-Reset-Your-BIOS-Step-8.jpg
There are 3 pins on the jumper. It should be on pin 1 and 2. Remove the jumper from pin 1 and 2, put it onto Pin 2 and 3, the last two pins and wait 5-10 seconds and put it back on Pin 1 and 2 like it normally was
plug the pc back in and configure the bios if you have to, some will configure automatically, see if it works normally now
Your last resort would to be either upgrade your PC or operating system, or reinstall Windows, back up anything you can and reinstall and see if that will help
Another thing to try is doing a disk cleanup or registry repair with programs like CCleaner and disk defragment

I don't exactly know why this is happening to you, but try any of this and it could work possibly, if not then oh well I apologize, I tried my best
 
Upvote 0 Downvote
Solution
R

RCSTEAM

Reputable
Jul 19, 2015
3
0
4,510
Thank you for all your help but I may have fixed it after trying all of these things I just gave up and installed a fresh copy of windows.

Thanks for the help
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom