Code:
BugCheck F4, {3, fffffa8007ef69e0, fffffa8007ef6cc0, fffff8000317e350}
----- ETW minidump data unavailable-----
Probably caused by : csrss.exe
Code:
2: kd> !process fffffa8007ef69e0 3
GetPointerFromAddress: unable to read from fffff800030af000
PROCESS fffffa8007ef69e0
SessionId: none Cid: 023c Peb: 7fffffd9000 ParentCid: 0228
DirBase: 1e9290000 ObjectTable: fffff8a005108b20 HandleCount: <Data Not Accessible>
Image: csrss.exe
VadRoot fffffa8011f00830 Vads 155 Clone 0 Private 1690. Modified 7812. Locked 1032.
DeviceMap fffff8a000006090
Token fffff8a0051b9060
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
fffff78000000000: Unable to get shared data
ElapsedTime 00:00:00.000
UserTime 00:00:00.000
KernelTime 00:00:00.000
QuotaPoolUsage[PagedPool] 483232
QuotaPoolUsage[NonPagedPool] 28688
Working Set Sizes (now,min,max) (4221, 50, 345) (16884KB, 200KB, 1380KB)
PeakWorkingSetSize 6853
VirtualSize 211 Mb
PeakVirtualSize 220 Mb
PageFaultCount 16965
MemoryPriority BACKGROUND
BasePriority 13
CommitCharge 2981
Code:
EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.
Code:
2: kd> k
Child-SP RetAddr Call Site
fffff880`02783e38 fffff800`03205d22 nt!KeBugCheckEx
fffff880`02783e40 fffff800`031b208b nt!PspCatchCriticalBreak+0x92
fffff880`02783e80 fffff800`03132144 nt! ?? ::NNGAKEGL::`string'+0x17486
fffff880`02783ed0 fffff800`02e76e93 nt!NtTerminateProcess+0xf4
fffff880`02783f50 fffff800`02e73450 nt!KiSystemServiceCopyEnd+0x13
fffff880`027840e8 fffff800`02ec281f nt!KiServiceLinkage
fffff880`027840f0 fffff800`02e77282 nt! ?? ::FNODOBFM::`string'+0x488e4
fffff880`02784900 fffff800`02e75dfa nt!KiExceptionDispatch+0xc2
fffff880`02784ae0 00000000`76da9c12 nt!KiPageFault+0x23a
00000000`00c41170 00000000`00000000 0x76da9c12
The problem seems to have resulted, due to a page fault which wasn't handled, the working set has already exceeded it's maximum value, I'm wondering the page fault couldn't be handled because there wasn't enough physical memory, and for some reason working set trimming wasn't carried out. However, because Stop 0xF4's are usually related to storage difficulties, then a driver may have referenced and accessed a page which wasn't in physical memory, and therefore had to paged from the disk, but it couldn't due to I/O problems.
--------------------------------------------------------------------------
Reduce the number of programs at startup, to avoid any driver or program conflicts:
Run some hard-drive diagnostics and follow these steps:
Find your hard-drive manufacturer and run their tests.
Additional Tests:
Post a screenshot of
Crystal Disk Info summary:
writhziden said:
If you have an SSD, make sure the following are up to date:
- SSD firmware
- BIOS Version
- Chipset Drivers
- Hard disk controller drivers/SATA drivers
- If you have a Marvell IDE ATA/ATAPI device, make sure the drivers are up to date from the Intel site or Marvell site and not from your motherboard/vendor support site.
Check for any file system errors and bad sectors using
Option #2 of:
Use this command with
Disk Check:
Remove:
Code:
Start Menu\Programs\ASUS Utility\SmartLogon
Start Menu\Programs\ASUS Utility\ASUS Live Update
Start Menu\Programs\ASUS Utility
These programs are simply bloatware which can slow down and corrupt your system, please remove these programs completely with
Revo Uninstaller Pro - Uninstall Software, Remove Programs easily, Forced Uninstall, Leftovers Uninstaller