PErfomrance issue

I have one win2k box with sp4 , yesterday i had recived a ticket of high cpu utilization , when i tried logging on the server via rdp i can only see the grey screen cannot see the ctrl alt del screen . finally server was hard booted and everything was fine .
i saw two dump files was created after openinging the dmp file in windbg could seee
BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP

LAST_CONTROL_TRANSFER:  from 00000000 to bff64f70

STACK_TEXT:  
f2eccf2c 00000000 00000000 00000000 00000000 RDPDD!DrvStrokePath+0x3dc


FOLLOWUP_IP:
RDPDD!DrvStrokePath+3dc
bff64f70 ??               ???

SYMBOL_STACK_INDEX:  0

FOLLOWUP_NAME:  MachineOwner

SYMBOL_NAME:  RDPDD!DrvStrokePath+3dc

MODULE_NAME:  RDPDD

IMAGE_NAME:  RDPDD.dll


role of the server is SQL server

can any one  give his suggestion on this  I had alsos configured the perfom mon logs also on the server
vijyantAsked:
Who is Participating?
 
jalilthe1Connect With a Mentor Commented:
Your windows crashes with 5 different bugcheck code. All the bugcheck codes are related to memory. 3 minidumps are crashed with pool corruption and 1 minidump is crashed with memory corruption. The stack trace of several minidumps have the footprint of f-prot.

Conclusion
1. Upgrade F-prot
2. Diagnostic your Ram
    You can run memtest to stress the ram. If memtest reports the ram is faulty, ram is bad. However Memtest is not a perfect tool to test the memory as some faulty ram can pass memtest.

    - Check the temperature of the CPU and make sure that it is not overheat (ie temperature < 60C)
       Make sure that the CPU fan works properly
    -  Reseat the memory stick to another memory slot
    -  Downclock the ram
    - Clean the dust inside the computer case
    -  Make sure that the ram is compatible to the motherboard
    - Check the bios setting about memory timing and make sure that it is on
    If it still crashes, diagnostic which memory stick is faulty
    - Take out one memory stick. If windows does not crash, the removed memory stick is faulty.
    -  If you have only one memory stick, replace the ram

Debug reports
Mini091205-01.dmp BugCheck 50, {9c20f870, 1, 8088c1d3, 0}
Mini091205-01.dmp DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP
Mini091205-01.dmp Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+1cd )

Mini092105-01.dmp BugCheck 50, {ff00240e, 0, 809807d2, 0}
Mini092105-01.dmp DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP
Mini092105-01.dmp Probably caused by : FSTOPW.SYS ( FSTOPW+535 )

Mini092305-01.dmp BugCheck 19, {20, 856f21c8, 856f22a0, a1bfffe}
Mini092305-01.dmp DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP
Mini092305-01.dmp Probably caused by : ntkrnlpa.exe ( nt!ExFreePoolWithTag+436 )

Mini092805-01.dmp BugCheck 1000007E, {c0000005, 80863733, f789ec7c, f789e978}
Mini092805-01.dmp DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP
Mini092805-01.dmp Probably caused by : memory_corruption ( nt!MiMapPagesToZeroInHyperSpace+a1 )

Mini100505-01.dmp BugCheck C5, {cfcfcfd3, 2, 1, 8088d35b}
Mini100505-01.dmp DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP
Mini100505-01.dmp Probably caused by : FSTOPW.SYS ( FSTOPW+de3 )

Mini100805-01.dmp BugCheck A, {4, 2, 0, 8080f232}
Mini100805-01.dmp DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP
Mini100805-01.dmp Probably caused by : ntkrnlpa.exe ( nt!CcFlushCache+6c )

Mini101305-01.dmp BugCheck D0, {8, 2, 0, 8088a122}
Mini101305-01.dmp DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP
Mini101305-01.dmp Probably caused by : fltMgr.sys ( fltMgr!FltpDispatch+6f )

Mini101405-01.dmp BugCheck 1000008E, {c0000005, 8092fc29, b94ddc94, 0}
Mini101405-01.dmp DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP
Mini101405-01.dmp Probably caused by : ntkrnlpa.exe ( nt!NtWaitForSingleObject+7b )

Mini101705-01.dmp BugCheck 1000008E, {c0000005, 8088c5be, b8e2e7d4, 0}
Mini101705-01.dmp DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP
Mini101705-01.dmp Probably caused by : Pool_Corruption ( nt!ExFreePool+f )

Mini101905-01.dmp BugCheck 1000008E, {c0000005, 8088c5be, ba9ac7d4, 0}
Mini101905-01.dmp DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP
Mini101905-01.dmp Probably caused by : Pool_Corruption ( nt!ExFreePool+f )

Mini102005-01.dmp BugCheck A, {615461, 2, 0, 8082f613}
Mini102005-01.dmp DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP
Mini102005-01.dmp Probably caused by : ptilink.sys ( ptilink+409f )

0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.