- Joined
- Nov 27, 2009
- Messages
- 24 (0.00/day)
Processor | Intel Dual Core E5300 |
---|---|
Motherboard | MSI G31TM-P21 |
Cooling | Stock everything :P |
Memory | 3GB DDR2 @800Mhz |
Video Card(s) | Sapphire HD5670 1GB |
Storage | 2xWD Caviar Blue 320GB |
Display(s) | Dell ST2220l |
Power Supply | FSP SAGAII 400 watts |
Software | Windows 7 Ultimate |
Hi all...
i've been having random crashes resuming from sleep or hibernation. sometimes a crash dump would be generated and a bsod displayed, at other times it just restarts while resuming and throws up a message windows wasn't properly shut down
yesterday i got a crash dump as well with just a restart (without a bsod) while i was trying to bring up the issue again by putting the comp to sleep and wake again.
the dump was generated from a resume from hibernation, the first try at the resume was unsuccessful with a message appearing saying the same thing and asking whether i should try again to resume the system or restart afresh, i chose to resume, the desktop appeared for like 5 seconds and then the bsod.
here is the analysis from that dump.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_STACK_INPAGE_ERROR (77)
The requested page of kernel data could not be read in. Caused by
bad block in paging file or disk controller error.
In the case when the first arguments is 0 or 1, the stack signature
in the kernel stack was not found. Again, bad hardware.
An I/O status of c000009c (STATUS_DEVICE_DATA_ERROR) or
C000016AL (STATUS_DISK_OPERATION_FAILED) normally indicates
the data could not be read from the disk due to a bad
block. Upon reboot autocheck will run and attempt to map out the bad
sector. If the status is C0000185 (STATUS_IO_DEVICE_ERROR) and the paging
file is on a SCSI disk device, then the cabling and termination should be
checked. See the knowledge base article on SCSI termination.
Arguments:
Arg1: 00000001, (page was retrieved from disk)
Arg2: 00000006, value found in stack where signature should be
Arg3: 00000000, 0
Arg4: 8cf0fb60, address of signature on kernel stack
Debugging Details:
------------------
ERROR_CODE: (NTSTATUS) 0x1 - STATUS_WAIT_1
BUGCHECK_STR: 0x77_1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 830792f5 to 83121e3c
STACK_TEXT:
8d54fc7c 830792f5 00000077 00000001 00000006 nt!KeBugCheckEx+0x1e
8d54fd10 83078f4a 87623030 8d54fd30 00000000 nt!MiInPageSingleKernelStack+0x29b
8d54fd44 830d112b 876230a4 8d54fd90 832539df nt!KiInSwapKernelStacks+0x41
8d54fd50 832539df 00000000 a0a33583 00000000 nt!KeSwapProcessOrStack+0x78
8d54fd90 83105219 830d10b3 00000000 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiInPageSingleKernelStack+29b
830792f5 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!MiInPageSingleKernelStack+29b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4d9fd915
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0x77_1_nt!MiInPageSingleKernelStack+29b
BUCKET_ID: 0x77_1_nt!MiInPageSingleKernelStack+29b
Followup: MachineOwner
i have carried out diskchecks and memory checks with the windows memory diagnostics running in extended mode with no errors being thrown up...
i have been introduced to all such system crashes ever since i upgraded my graphics card to ati (i know this time the disk/memory seem at fault). i have worked on my xp system for several years on integrated graphics without ever even a single bsod....i would then be just left wondering why people bitch about bsod's n what not...lol .
thanks for taking the time for going through my post...some help please..
i've been having random crashes resuming from sleep or hibernation. sometimes a crash dump would be generated and a bsod displayed, at other times it just restarts while resuming and throws up a message windows wasn't properly shut down
yesterday i got a crash dump as well with just a restart (without a bsod) while i was trying to bring up the issue again by putting the comp to sleep and wake again.
the dump was generated from a resume from hibernation, the first try at the resume was unsuccessful with a message appearing saying the same thing and asking whether i should try again to resume the system or restart afresh, i chose to resume, the desktop appeared for like 5 seconds and then the bsod.
here is the analysis from that dump.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_STACK_INPAGE_ERROR (77)
The requested page of kernel data could not be read in. Caused by
bad block in paging file or disk controller error.
In the case when the first arguments is 0 or 1, the stack signature
in the kernel stack was not found. Again, bad hardware.
An I/O status of c000009c (STATUS_DEVICE_DATA_ERROR) or
C000016AL (STATUS_DISK_OPERATION_FAILED) normally indicates
the data could not be read from the disk due to a bad
block. Upon reboot autocheck will run and attempt to map out the bad
sector. If the status is C0000185 (STATUS_IO_DEVICE_ERROR) and the paging
file is on a SCSI disk device, then the cabling and termination should be
checked. See the knowledge base article on SCSI termination.
Arguments:
Arg1: 00000001, (page was retrieved from disk)
Arg2: 00000006, value found in stack where signature should be
Arg3: 00000000, 0
Arg4: 8cf0fb60, address of signature on kernel stack
Debugging Details:
------------------
ERROR_CODE: (NTSTATUS) 0x1 - STATUS_WAIT_1
BUGCHECK_STR: 0x77_1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 830792f5 to 83121e3c
STACK_TEXT:
8d54fc7c 830792f5 00000077 00000001 00000006 nt!KeBugCheckEx+0x1e
8d54fd10 83078f4a 87623030 8d54fd30 00000000 nt!MiInPageSingleKernelStack+0x29b
8d54fd44 830d112b 876230a4 8d54fd90 832539df nt!KiInSwapKernelStacks+0x41
8d54fd50 832539df 00000000 a0a33583 00000000 nt!KeSwapProcessOrStack+0x78
8d54fd90 83105219 830d10b3 00000000 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!MiInPageSingleKernelStack+29b
830792f5 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!MiInPageSingleKernelStack+29b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4d9fd915
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: 0x77_1_nt!MiInPageSingleKernelStack+29b
BUCKET_ID: 0x77_1_nt!MiInPageSingleKernelStack+29b
Followup: MachineOwner
i have carried out diskchecks and memory checks with the windows memory diagnostics running in extended mode with no errors being thrown up...
i have been introduced to all such system crashes ever since i upgraded my graphics card to ati (i know this time the disk/memory seem at fault). i have worked on my xp system for several years on integrated graphics without ever even a single bsod....i would then be just left wondering why people bitch about bsod's n what not...lol .
thanks for taking the time for going through my post...some help please..