Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Blue screen issues when loading into Windows XP


  • Please log in to reply

#1
Si_F

Si_F

    New Member

  • Member
  • Pip
  • 7 posts
Hi all

I’ve been having a problem with my PC for the last month or so and wondered if anyone might be able to help me identify what the problem is.

The machine was purchased in February and worked perfectly until a month or so ago. The spec is: Intel Core 2 Duo E8500 3.16GHz Processor, Asrock Wolfdale1333-GLAN Motherboard, Corsair 4GB PC2-6400 CAS5 Memory, Geforce 9800 GT 512MB PCIe, 500GB 7200RPM Hard Disk, Windows XP Home Edition

I’ve been getting blue screens when loading into Windows. It usually happens as the system tray icons are appearing. It will blue screen and reboot 3 or 4 times and then Windows seems to load fine and I can use the machine for the rest of the day without any more problems occurring.

There is usually no message on the blue screen, but there have been: MEMORY_MANAGEMENT, IRQ_NOT_LESS_OR_EQUAL & PAGE_FAULT_IN_NON_PAGED_AREA

I have run memtest over the course of 24 hours and this did not find any errors.

I’ve tried different Nvidia drivers.

I reformatted last weekend and have reinstalled only a few essential things, but it is still happening.

I have looked at the Event Viewer and was going to post some of the error messages, but having gone to look at them now, the Event Viewer now reports that the event log file is corrupt. Is there a way I can fix this and get the events back? I can see in the window behind the error message that there are 1,320 events.

If some kind soul could help me identify the problem here, it would be much appreciated! Please let me know if more detailed information is required.
  • 0

Advertisements


#2
happyrock

happyrock

    Tech Moderator

  • Retired Staff
  • 9,285 posts
since its a new system...try the manufactures support...they will have you run a few tests and if they can't get it working they will have a box shipped to you that you put it in and ship it back to them at no cost to you, and they will repair or replace it...
  • 0

#3
Broni

Broni

    Kraków my love :)

  • Member
  • PipPipPipPipPipPipPipPip
  • 12,300 posts
Looks like bad RAM.
  • 0

#4
Si_F

Si_F

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts

since its a new system...try the manufactures support...they will have you run a few tests and if they can't get it working they will have a box shipped to you that you put it in and ship it back to them at no cost to you, and they will repair or replace it...


Yes, thanks, that is one option. I did just want to check if it was down to a dodgy driver or something before I took that kind of step.

Edited by Si_F, 17 July 2009 - 07:41 AM.

  • 0

#5
Si_F

Si_F

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts

Looks like bad RAM.


I've run memtest over a whole day and it did not find any errors. Are there any other tests I can do to test the RAM? Or can I run memtest in a different way or for longer to show it as being dodgy?
  • 0

#6
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Download Windows Memory Diagnostic
If you have Winrar or another third party compression utility installed it may associate the file to itself and it may look like a Rar or ZIP. Do not unzip or unrar the file as it will not work correctly if you do
There is a really easy to follow WMD Guide here on GTG

If you don't have a burning program that will burn .ISO files then download Burncdcc from my signature below.
Note: Do not put a cd in until Burncdcc opens the tray for you.

1) Start Burncdcc
2) Browse to the saved ISO file on your Desktop...in this case Windiag.iso. Winrar may associate the file to itself and it may look like a Rar or ZIP. Do not unzip or unrar the file as it will not work correctly if you do.
3) Select the Iso file
4) Click on Start

Leave the CD in the drive and reboot the system. Now you will need to change the Boot Sequence in Bios
To change Boot Sequence in your BIOS

• Reboot the system and at the first post screen (where it is counting up memory) watch the screen to find out which KEY button or Combination to click to enter Setup.
• Find the Advanced area and click Enter
• Look for Boot Sequence or Boot Options and highlight that click Enter
• Now highlight the first drive and follow the directions on the bottom of the screen on how to modify it and change it to CDrom or Floppy depending on which way you are running the test.
• Change the second drive to the C or Main Drive
• Once that is done then click F10 to Save and Exit
• You will prompted to enter Y to verify Save and Exit. Click Y and the system will now reboot with the new settings.


When the system boots you will now allow the Windows Memory Diagnostic to run.

• Allow the program to run for at at least Two Complete passes
• There are Six Tests that the program will run on each Pass
• This will take some time but allow it to run
• If at anytime there appears a Failed Message at the bottom of the screen, then you can Exit the program by clicking the X
• If After it has run the required passes and there are no error messages then just click the X to exit the program and reboot.
• When the system reboots then please go back into the bios and reset the Boot Sequence so that the HDD0 is the first boot device.
• Make the CD Rom the Second boot device.
• Click F10 to Save and Exit and then Y to verify the Save and Exit


The system will now boot up again. Once these are complete then reply back with the results of the test.
  • 0

#7
happyrock

happyrock

    Tech Moderator

  • Retired Staff
  • 9,285 posts

I have run memtest over the course of 24 hours and this did not find any errors.

its not ram...try reinstalling your chipset drivers

Edited by happyrock, 17 July 2009 - 10:29 AM.

  • 0

#8
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
I agree Happyrock, it doesn't look like a ram problem.
I offered a second option for memory testing only because it was requested.
Your suggestion on MOBO is right on. :)
  • 0

#9
Si_F

Si_F

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts
Hi all. Sorry for the delay in responding.

Ok, I downloaded Windows Memory Diagnostic and let it run for an afternoon, about 100 passes and it did not find any errors. So this backs up the suggestion that it is not the RAM.

The Event Viewer seems to have sorted itself out, so I can now report some of the errors I have been getting. To add to "Memory_Management", "Irql_not_Less_or_Equal" and "Page_Fault_in_Non_Paged_area" - I am now also getting "BAD_POOL_HEADER" and on one day I had quite a few "PFN_LIST_CORRUPT".

This is what I have had this morning:


The computer has rebooted from a bugcheck. The bugcheck was: 0x100000be (0xabf19a2e, 0x38de4121, 0xadbc587c, 0x0000000b). A dump was saved in: C:\WINDOWS\Minidump\Mini072709-03.dmp.

The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0x805db7e7, 0xb78f7920, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini072709-03.dmp.

Error code 00000019, parameter1 00000020, parameter2 e1e8edf8, parameter3 e1e8edf8, parameter4 1c000101.

Error code 00000019, parameter1 00000020, parameter2 e1f7e938, parameter3 e1f7ead8, parameter4 0c340039.

Error code 0000001a, parameter1 00041284, parameter2 77e90001, parameter3 00000000, parameter4 c0503000.

Error code 1000008e, parameter1 c0000005, parameter2 805db7e7, parameter3 b78f7920, parameter4 00000000.


Can anyone see if these point to a specific problem?

Also, it was suggested that the problem might be the motherboard. Are there any diagnostic tests you can download to check it?

Many thanks.

Edit: I did also download the latest chipset drivers from the Asrock site and the problems remain.

Edited by Si_F, 27 July 2009 - 05:55 AM.

  • 0

#10
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
PFN_LIST_CORRUPT

This seems to be driver related. let's try the next step to run this down.

Download WhoCrashed from the link in my signature below
This program checks for any drivers which may have been causing your computer to crash....

Click on the file you just downloaded and run it.
Put a tick in Accept then click on Next
Put a tick in the Don't create a start menu folder then click Next
Put a tick in Create a Desktop Icon then click on Install and make sure there is a tick in Launch Whocrashed before clicking Finish
Click Analyze
It will want to download the Debugger and install it Say Yes

WhoCrashed will create report but you have to scroll down to see it
Copy and paste it into your next reply
  • 0

#11
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
BAD_POOL_HEADER

This could be caused by Indexing or something in Msconfig
I'm looking at the latter, so let's do this.

Lets see what you have in your startup

Please click on
Start and then to Run
Type in msconfig and press Enter
Now click on Startups
Then uncheck everything and restart.
If system boots correctly and is running smoothly and faster then we have a startup problem
Try going back into msconfig and check one item and reboot
Keep doing that till you have found the problem or all are finally checked.
Post back with the results

If the above doesn't find anything then go to the next set of instructions.


Lets see what you have in your startup services area

Please click on
Start and then to Run
Type in msconfig and press Enter
Now click on Services
Click on the Hide All Microsoft Services
Then uncheck everything and restart.
If system boots correctly and is running smoothly and faster then we have a startup problem
Try going back into msconfig and check one item and reboot
Keep doing that till you have found the problem or all are finally checked.
Post back with the results
  • 0

#12
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
After doing the above steps then Do the next steps in order and let me know the results when Finished.

Go to
Start and then to Run
Type in Chkdsk /r Note the space between k and /
Click Enter ...It will probably ask if you want to do this on the next reboot...click Y

If the window doesn't shutdown on its own then reboot the system manually. On reboot the system will start the chkdsk operation
This one will take longer then chkdsk /f

Note... there are 5 stages...
It may appear to hang at a certain percent for a hour or more or even back up and go over the same area...this is normal...
DO NOT SHUT YOUR COMPUTER DOWN WHILE CHKDSK IS RUNNING OR YOU CAN HAVE SEVERE PROBLEMS
This can take several hours to complete.
When completed it will boot the system back into windows.

Let me know if this fixes the problem
  • 0

#13
Si_F

Si_F

    New Member

  • Topic Starter
  • Member
  • Pip
  • 7 posts
WhoCrashed results:

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

On Mon 27/07/2009 12:31:08 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41284, 0x1A90001, 0x0, 0xC0503000)
Error: MEMORY_MANAGEMENT
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 27/07/2009 12:26:18 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000008E (0xC0000005, 0x805DB7E7, 0xB7987BD4, 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 27/07/2009 12:21:11 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000008E (0xC0000005, 0x805DB73B, 0xAC299928, 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 27/07/2009 12:16:53 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x1000008E (0xC0000005, 0xBF80EA1C, 0xAAE81AFC, 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 Mon 27/07/2009 11:30:49 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000008E (0xC0000005, 0x805DB7E7, 0xB78F7920, 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 27/07/2009 11:16:59 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41284, 0x77E90001, 0x0, 0xC0503000)
Error: MEMORY_MANAGEMENT
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 27/07/2009 11:12:25 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0xC0040240, 0x2, 0x0, 0x80500351)
Error: Unknown
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 26/07/2009 09:45:04 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x19 (0x20, 0xE1F7E938, 0xE1F7EAD8, 0xC340039)
Error: BAD_POOL_HEADER
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 Sun 26/07/2009 09:36:40 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x19 (0x20, 0xE1E8EDF8, 0xE1E8EDF8, 0x1C000101)
Error: BAD_POOL_HEADER
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 26/07/2009 09:29:12 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x1000008E (0xC0000005, 0x804E7D30, 0xB4882CCC, 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 Sun 26/07/2009 09:28:02 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x19 (0x20, 0xE2A55218, 0xE2A55248, 0xC060201)
Error: BAD_POOL_HEADER
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 26/07/2009 09:27:09 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x1000008E (0xC0000005, 0x8055196D, 0xB4912B98, 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 Sun 26/07/2009 09:23:23 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x1000007F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP_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 Sun 26/07/2009 09:22:05 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000008E (0xC0000005, 0x8056ED7B, 0xB44FE970, 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 26/07/2009 09:16:12 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xC09E2F1C, 0x0, 0x804E8DA4, 0x2)
Error: Unknown
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 26/07/2009 09:15:13 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41284, 0x75290001, 0x0, 0xC0503000)
Error: MEMORY_MANAGEMENT
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 26/07/2009 09:14:25 your computer crashed
This was likely caused by the following module: nv4_disp.dll
Bugcheck code: 0x1000008E (0xC0000005, 0xBD01C0B0, 0xB486C8D4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\nv4_disp.dll
product: NVIDIA Compatible Windows 2000 Display driver, Version 178.24
company: NVIDIA Corporation
description: NVIDIA Compatible Windows 2000 Display driver, Version 178.24



On Sun 26/07/2009 09:06:16 your computer crashed
This was likely caused by the following module: avgldx86.sys
Bugcheck code: 0x1000008E (0xC0000005, 0xB50D0D37, 0xB42307A0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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 avgldx86.sys





On Sun 26/07/2009 00:39:23 your computer crashed
This was likely caused by the following module: kmixer.sys
Bugcheck code: 0x10000050 (0xC3E600A4, 0x1, 0xB3528249, 0x0)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\kmixer.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Audio Mixer
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sat 25/07/2009 07:28:47 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x19 (0x20, 0x8A022241, 0x8A022691, 0x688A07E5)
Error: BAD_POOL_HEADER
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 24/07/2009 18:20:39 your computer crashed
This was likely caused by the following module: memory_corruption
Bugcheck code: 0x4E (0x99, 0x0, 0x1, 0x0)
Error: PFN_LIST_CORRUPT
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 memory_corruption





On Fri 24/07/2009 18:16:55 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x19 (0x20, 0xE1218218, 0xE1218258, 0xC080808)
Error: BAD_POOL_HEADER
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 Thu 23/07/2009 17:41:41 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xB429D000, 0x1, 0x8058AB4D, 0x0)
Error: Unknown
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 Thu 23/07/2009 17:38:18 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x19 (0x20, 0xE325E000, 0xE325EA48, 0xD490600)
Error: BAD_POOL_HEADER
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 Thu 23/07/2009 17:35:20 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x19 (0x20, 0xE232C208, 0xE232C240, 0xC070401)
Error: BAD_POOL_HEADER
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 Wed 22/07/2009 17:28:56 your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x24 (0x1902FE, 0xB5267478, 0xB5267174, 0x805519E9)
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 Wed 22/07/2009 06:10:36 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x1000008E (0xC0000005, 0xB878FDA2, 0xB878FA64, 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 Tue 21/07/2009 17:57:54 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x4128B, 0xA694201, 0x0, 0xC0503000)
Error: MEMORY_MANAGEMENT
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 Tue 21/07/2009 07:21:39 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xE25EB412, 0x0, 0x8055199C, 0x1)
Error: Unknown
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 20/07/2009 07:15:54 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x1000008E (0xC0000005, 0x80551AE2, 0xB40EEAA8, 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 Sun 19/07/2009 10:23:54 your computer crashed
This was likely caused by the following module: csrss.exe
Bugcheck code: 0xF4 (0x3, 0x8A04A9E0, 0x8A04AB54, 0x8060566E)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\WINDOWS\system32\csrss.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Client Server Runtime Process
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sun 19/07/2009 10:22:42 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xC0BA231C, 0x0, 0x804E8DA4, 0x2)
Error: Unknown
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 18/07/2009 09:41:25 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000008E (0xC0000005, 0x80551AE2, 0xB455ED6C, 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 18/07/2009 09:37:48 your computer crashed
This was likely caused by the following module: avgldx86.sys
Bugcheck code: 0x10000050 (0xC346959C, 0x0, 0xB5028D37, 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 avgldx86.sys





On Thu 16/07/2009 18:29:34 your computer crashed
This was likely caused by the following module: vsdatant.sys
Bugcheck code: 0x1000008E (0xC0000005, 0x80551AE2, 0xB49F32A8, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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 vsdatant.sys





On Thu 16/07/2009 18:25:49 your computer crashed
This was likely caused by the following module: vsdatant.sys
Bugcheck code: 0x10000050 (0xAB888A37, 0x1, 0x805515A1, 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 vsdatant.sys





On Thu 16/07/2009 07:14:04 your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x1000000A (0xE60, 0x2, 0x1, 0x80701A16)
Error: Unknown
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 Wed 15/07/2009 18:11:47 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x1000008E (0xC0000005, 0x80551AE2, 0xB408F614, 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 15/07/2009 18:10:53 your computer crashed
This was likely caused by the following module: vsdatant.sys
Bugcheck code: 0x1000008E (0xC0000005, 0x80551AE2, 0xB434BA70, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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 vsdatant.sys





On Wed 15/07/2009 07:19:29 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000008E (0xC0000005, 0x80551AE2, 0xB3FF4AA0, 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.
  • 0

#14
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Hmm interesting. It seems the majority of your crashes are due to the OS itself.
I also saw a crash for
Nvidia
AVG
vsdatant.sys which seems to belong to ZoneAlarm
kmixer.sys which is the audio

Do you have the original Windows XP disk?
You may want to consider a SFC /SCANNOW or a Repair Installation
  • 0

#15
happyrock

happyrock

    Tech Moderator

  • Retired Staff
  • 9,285 posts

Hmm interesting. It seems the majority of your crashes are due to the OS itself.
I also saw a crash for
Nvidia
AVG
vsdatant.sys which seems to belong to ZoneAlarm
kmixer.sys which is the audio

Do you have the original Windows XP disk?
You may want to consider a SFC /SCANNOW or a Repair Installation

yep.. :)... run the chkdsk /r first to fix any possible hard drive errors and then the SFC or repair like rshaffer61 advised
you may have to reinstall a few drivers or programs after your done though
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP