[shantd]

GrofLuigi, on 09 June 2011 - 09:26 PM, said:

Another KB...

GL

This deals with system halts that occur upon resuming from standby. My system halts don't occur then. In fact, putting my system on standby actually prevents crashes and buys me some time. It's when I don't put my system on standby that the BSODs occur.

I'll give you an example of when they happen. I start my computer and for 2-3 days straight it will work fine. After say day 3, I leave it on, turn off my monitor and go to sleep. In the morning when I turn my monitor on: I'll have a nice BSOD waiting for me...or the screen will just be frozen and I have to hit the reset key. The system almost never freezes while I'm using a program or am active on it in any way. They only occur when it's left alone for extended periods. Something is kicking in after several hours of inactivity and I'm having a heck of a time finding what it is...

[allen2]

It could be a hard drive problem. Could you check it with the tool from your hdd manufacturer ?
See this page that has almost a link for all brand.

[dencorso]

allen2 is right... you may be getting the BSOD after the HDD spins up or, more probably, on spin down. Since you have ACPI activated, after some time idle the disk will spin down. Try setting, temporarily, your HDD to never spin down, while the machine is on, in the energy saving properties, and let's see if the BSODs stop.

[shantd]

Clever thinking guys, but that's not the issue, as I've been using the "Always on" power scheme, which prevents my hard drives from ever shutting down.

[allen2]

I wasn't thinking about hard drive powering down, i was thinking that the hard drive might have some bad sectors.

[shantd]

I'll check it out. Would bad sectors cause consistently timed shut-downs though? I'll also upload that mini-dump.

[shantd]

OK I Finally uploaded that minidump! Here is the link, guys: http://ul.to/4j4osa4n

Just go to that url and download the minidump, and let me know if you see anything, Thanks again fellas, much appreciated.

[MagicAndre1981]

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 00000003, Process
Arg2: 8ad8a690, Terminating object
Arg3: 8ad8a804, Process image file name
Arg4: 805d2970, Explanatory message (ascii)

PROCESS_NAME:  csrss.exe

EXCEPTION_RECORD:  aca3d9d8 -- (.exr 0xffffffffaca3d9d8)
ExceptionAddress: 75b7b3b9
   ExceptionCode: c0000006 (In-page I/O error)
  ExceptionFlags: 00000000
NumberParameters: 3
   Parameter[0]: 00000008
   Parameter[1]: 75b7b3b9
   Parameter[2]: c000009a
Inpage operation failed at 75b7b3b9, due to I/O error c000009a

EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - Die Anweisung bei "0x%p" verwies auf Speicher bei "0x%p". Die erforderlichen Daten wurden aufgrund eines E/A-Fehlers in "0x%x" nicht an den Arbeitsspeicher  bertragen.

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

ERROR_CODE: (NTSTATUS) 0xc0000006 - Die Anweisung bei "0x%p" verwies auf Speicher bei "0x%p". Die erforderlichen Daten wurden aufgrund eines E/A-Fehlers in "0x%x" nicht an den Arbeitsspeicher  bertragen.

EXCEPTION_PARAMETER1:  00000008

EXCEPTION_PARAMETER2:  75b7b3b9

EXCEPTION_PARAMETER3:  c000009a

IO_ERROR: (NTSTATUS) 0xc000009a - Nicht ausreichend Systemressourcen, um die API abzuschlie en.

EXCEPTION_STR:  0xc0000006_c000009a

FAULTING_IP: 
+0
75b7b3b9 ??              ???

BUGCHECK_STR:  0xF4_IOERR_C000009A

STACK_TEXT:  
aca3d520 805d1ab9 000000f4 00000003 8ad8a690 nt!KeBugCheckEx+0x1b
aca3d544 805d2a1b 805d2970 8ad8a690 8ad8a804 nt!PspCatchCriticalBreak+0x75
aca3d574 8054161c 8ad8a8d8 c0000006 aca3d9b0 nt!NtTerminateProcess+0x7d
aca3d574 80501151 8ad8a8d8 c0000006 aca3d9b0 nt!KiFastCallEntry+0xfc
aca3d5f4 804fe806 ffffffff c0000006 aca3d9f8 nt!ZwTerminateProcess+0x11
aca3d9b0 805028bf aca3d9d8 00000000 aca3dd64 nt!KiDispatchException+0x3a0
aca3dd34 80544ee7 00c8fbe8 00c8fc08 00000000 nt!KiRaiseException+0x175
aca3dd50 8054161c 00c8fbe8 00c8fc08 00000000 nt!NtRaiseException+0x33
aca3dd50 75b7b3b9 00c8fbe8 00c8fc08 00000000 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
00c8fff4 00000000 00000000 00000000 00000000 0x75b7b3b9


STACK_COMMAND:  kb

FOLLOWUP_IP: 
+0
75b7b3b9 ??              ???

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware_disk

FAILURE_BUCKET_ID:  0xF4_IOERR_C000009A_IMAGE_hardware_disk

BUCKET_ID:  0xF4_IOERR_C000009A_IMAGE_hardware_disk

So the data can't be read from disc because the kernel memory reached the limit and so the kernel is out of memory:

EXCEPTION_PARAMETER3: c000009a

//
// MessageId: STATUS_INSUFFICIENT_RESOURCES
//
// MessageText:
//
// Insufficient system resources exist to complete the API.
//
#define STATUS_INSUFFICIENT_RESOURCES    ((NTSTATUS)0xC000009AL) 

Configure your Windows to "Enable pool tagging":

http://support.microsoft.com/kb/177415

and configure your Windows to generate a kernel dump:

http://support.microsoft.com/kb/316450

if you get the next crash, zip the file C:\Windows\Memory.dmp and upload the zip.