*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 19, {3, fffff800034557d0, ffffffffffffd, fffff800034557d0}
Probably caused by : Pool_Corruption ( nt!ExFreePool+503 )
Followup: Pool_corruption
Hi,Thanks hope its fixed will
Hi,
did you run the verifier or just remove the driver i outlined?
If the bsod continues then try the verifier.
Any news?Both but can't find any results of the verifier
No bsod yet just some some weird crash on restarting the screen went blue with white lines no text or anything else currently running the memtest86 test with 10 pass will update when doneAny news?
Yeah i'll be surprised if it's the actual memory, personally i feel it's more of a driver issue but still see how your scans go.
there only one running i got the bsod by turning off the only oneThere should only be one csrss.exe process running per logged in user, if there are more then it's probably a malicious process
there only one running i got the most recent bsod by turning off the only one
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck F4, {3, fffffa8008ee2b10, fffffa8008ee2df0, fffff80003589600}
ETW minidump data unavailable
Probably caused by : csrss.exe
Followup: MachineOwner
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 109, {a3a039d89cf9eb03, b3b7465eef76ba29, fffff8000359b900, 1}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt!SeQuerySecurityDescriptorInfo+0 )
Followup: MachineOwner
Hi,This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
or data. See Download Windows Server 2003/2003 R2 Retired Content from Official Microsoft Download Center
2) A developer attempted to set a normal kernel breakpoint using a kernel
debugger that was not attached when the system was booted. Normal breakpoints,
"bp", can only be set if the debugger is attached at boot time. Hardware
breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.