BSOD (once every couple of weeks) while idle 0x00000050 - ntoskrnl.exe

[Heero Yuy]

Hi there

I've been experiencing BSOD issues on my computer quite recently. The issue started to occur when I noticed I had some trojans on my computer via a scan using symantec end point. I tried to remove the trojans which were unsuccessful, in the end I deleted the infected files manually hoping this would solve the issue. This action seemed to corrupt the symantec end point protection program. The IT guys uninstalled and then re installed symantec which then resulted in very frequent BSOD errors. It seemed as if symantec was installing as corrupt. In the end the IT guys installed a newer, version of symantec end point, this seem to have done the trick. I came in on Monday to find that I had a BSOD error over the weekend. At this point I ran CHKDISK, Memtest, repair system file checks, you name it. At this point I believed the error was cleared a week went by and I was living the BSOD free life. Today I came in to my computer being off, checked the logs and another BSOD!

I think I've isolated the problem to ntoskrnl.exe address in stack :ntoskrnl.exe+f25b3

However I have no idea what is triggering the problem, the fact the my BSOD are happening out of work hours, when the computer is IDLE is very perplexing. I have attached my dump files.

I have had no recent hardware upgrades within the past 3 months either!

Any light shed would be a great help Gurus.

 

[Thedoctor44]

I might not be able to help that much because I'm on my phone so I can't look at the dump files but the bugcheck in the title indicates a page fault in a non paged area, meaning requested data is located in an area of memory that can't be paged out to disk. Anti virus programs, bad memory and corrupted NTFS partitions are the main causes. You said you ran memtest and found no errors so memory is ruled out. I would try replacing the anti virus with a different one, if that fails you try repairing windows.
Edit: I forgot to add that ntoskrnl.exe is the kernel so that isn't the actual cause, it's just that windows can't identify the driver causing the problem so it points it to the kernel.

 

[Thedoctor44]

Right, you have multiple 0x50 bugchecks that are generally caused by failing RAM. Please run memtest86 by following these instructions. You should run memtest for at least 8 passes.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

[COLOR="Red"]PAGE_FAULT_IN_NONPAGED_AREA (50)[/COLOR]
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff948c423eea0, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff960001adcc3, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000005, (reserved)

You also seem to have an issue with your HDD. Please run a disk check by following these instructions.

http://www.sevenforums.com/tutorials/433-disk-check.html

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff8800319a5b8, fffff88003199e10, fffff80002c8ca15}

[COLOR="red"]Probably caused by : Ntfs.sys[/COLOR] ( Ntfs!NtfsDeleteScb+108 )

When you have ran a disk check please follow these instructions carefully on how to test for a failing HDD.

http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html

 

[Heero Yuy]

Hi Thedoctor44

Thank you very much for taking the time out to have a look into my issue.

I ran a chkdsk scan on my main hard drive, this took around 1hr and 30 minutes to complete. This has led me to the conclusion that there is definitely an issue with the hard drive.

When I originally ran memtest I did receive no errors originally. I think I will try and fix the hard drive issues using seatools and if the issue continues I'll try the memory again.

Thanks again for the invaluable help.