black screen and reboot

[kuki]

Glad to hear someone has solved this problem. Unfortunately, I still experience problems while returning from sleep. It happens when the sleep is longer. There is no BSOD, just black screen and reboot.

Can I use this thread to continue solving my problem? If yes and if someone is willing to help, please tell me which commands should I apply to full memory dump in Windbg to clarify things? There is no way I will upload 3,7 GB.

Minidump attached.

 

[kuki]

anyone?

 

[wish]

Follow this instruction to collect more files.
Blue Screen of Death (BSOD) Posting Instructions

 

[kuki]

done.
System spec:

Acer TimelineX 5820TG
core i5 450, 4GB ram, Intel GMA/Radeon HD5650 (switchable in BIOS set to on), PQI S535 128GB SSD
Windows 7 Ultimate 64bit ENG full retail, previously preinstalled Windows 7 HE 64bit from Acer.

Problems started to appear after replacing oryginal HDD with PQI SSD drive and installing a new system. That is why I am not sure whether that is HW or SW issue.

 

[mgorman87]

All your crashes are the same
STOP 0x000000F4: CRITICAL_OBJECT_TERMINATION


Run a system file check - http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Hard drive scan usings SeaTools - SeaTools for Windows | Seagate - Both long and short tests


BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Thu May 19 12:00:49.760 2011 (UTC - 4:00)
System Uptime: 0 days 0:15:42.196
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
BUGCHECK_STR:  0xF4_IOERR
FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_csrss.exe
BiosReleaseDate = 11/01/2010
SystemManufacturer = Acer
SystemProductName = Aspire 5820TG
CPUID:        "Intel(R) Core(TM) i5 CPU       M 450  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 2394
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Mon May 16 08:06:35.984 2011 (UTC - 4:00)
System Uptime: 0 days 2:22:04.420
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
BUGCHECK_STR:  0xF4_C0000005
FAILURE_BUCKET_ID:  X64_0xF4_C0000005_IMAGE_csrss.exe
BiosReleaseDate = 11/01/2010
SystemManufacturer = Acer
SystemProductName = Aspire 5820TG
CPUID:        "Intel(R) Core(TM) i5 CPU       M 450  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 2394
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Fri May 13 12:10:40.924 2011 (UTC - 4:00)
System Uptime: 0 days 3:07:53.376
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
BUGCHECK_STR:  0xF4_IOERR
FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_csrss.exe
BiosReleaseDate = 11/01/2010
SystemManufacturer = Acer
SystemProductName = Aspire 5820TG
CPUID:        "Intel(R) Core(TM) i5 CPU       M 450  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 2394
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Fri May 13 09:02:31.838 2011 (UTC - 4:00)
System Uptime: 0 days 0:42:56.290
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
BUGCHECK_STR:  0xF4_IOERR
FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_csrss.exe
BiosReleaseDate = 11/01/2010
SystemManufacturer = Acer
SystemProductName = Aspire 5820TG
CPUID:        "Intel(R) Core(TM) i5 CPU       M 450  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 2394
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Fri May 13 08:19:18.922 2011 (UTC - 4:00)
System Uptime: 0 days 1:58:04.374
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
BUGCHECK_STR:  0xF4_IOERR
FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_csrss.exe
BiosReleaseDate = 11/01/2010
SystemManufacturer = Acer
SystemProductName = Aspire 5820TG
CPUID:        "Intel(R) Core(TM) i5 CPU       M 450  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 2394
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Thu May 12 06:47:16.373 2011 (UTC - 4:00)
System Uptime: 0 days 0:15:57.434
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
BUGCHECK_STR:  0xF4_IOERR
FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_csrss.exe
BiosReleaseDate = 11/01/2010
SystemManufacturer = Acer
SystemProductName = Aspire 5820TG
CPUID:        "Intel(R) Core(TM) i5 CPU       M 450  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 2394
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Wed May 11 07:28:48.577 2011 (UTC - 4:00)
System Uptime: 0 days 1:32:16.013
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
BUGCHECK_STR:  0xF4_C0000005
FAILURE_BUCKET_ID:  X64_0xF4_C0000005_IMAGE_csrss.exe
BiosReleaseDate = 11/01/2010
SystemManufacturer = Acer
SystemProductName = Aspire 5820TG
CPUID:        "Intel(R) Core(TM) i5 CPU       M 450  @ 2.40GHz"
MaxSpeed:     2400
CurrentSpeed: 2394
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/font]

 

[kuki]

thank you for your fast reply. the system rebooted on wake up and just after it gone black I saw system information stating a newdll.dll library file failed to load.

seatools work for SSD drives?

C:\Windows\system32>sfc /VERIFYONLY

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\Windows\system32>

 

[mgorman87]

thank you for your fast reply. the system rebooted now during waking up and just after it went black I have seen system information stating a newdll.dll library file failed to load.

seatools work for SSD drives?

No. Probably not. See if you can find a SSD drive test

 

[kuki]

my SSD seems to be fine - ATTO and CrystalDiskInfo benchmarks are just below the average values I have found on google (but they were benchmarked on intel ICH10, which definately outstand the one installed in my laptop), so the disk seems to be fine.

either I am currently missing some driver/software from the oryginal Acer Windows system or SSD are badly supported by my motherboard

 

[mgorman87]

my SSD seems to be fine - ATTO and CrystalDiskInfo benchmarks are just below the average values I have found on google (but they were benchmarked on intel ICH10, which definately outstand the one installed in my laptop), so the disk seems to be fine.

either I am currently missing some driver/software from the oryginal Acer Windows system or SSD are badly supported by my motherboard

Have you tried updating the firmware on the SSD?

Been seeing a lot of problems with SSDs lately and reading reviews on line there seem to be a lot of issues with SSDs dieing very fast.

The stop error you're having usually means that the hard drive has been "lost". Like the I/O cable was unplugged while the computer was running.

 

[kuki]

If that was an Intel drive, maybe firmware upgrade would be possible. I bought PQI drive and as far as I am concerned they do not give any tools for FW upgrade for the public.

It seems that TRIM is working for me, it should reduce the wear-off. I have read somewhere on that forum, that there was a guy with SSD and BSODs on wake up. He unchecked in the drivepolicy "write cacheing" and it solved his problem. It does not work for me - no matter if I have cacheing enabled/disabled or even buffer flushing - I do experience reboots/BSODs on wake up.

Yesterday I have experienced another black screen and it seems (at the first glance) to be a little bit different:

Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02c02000 PsLoadedModuleList = 0xfffff800`02e47650
Debug session time: Wed May 25 16:22:26.966 2011 (UTC + 2:00)
System Uptime: 0 days 5:26:44.402
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa80064b2b30, fffffa80064b2e10, fffff80002f84f40}

Probably caused by : wininit.exe

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: 0000000000000003, Process
Arg2: fffffa80064b2b30, Terminating object
Arg3: fffffa80064b2e10, Process image file name
Arg4: fffff80002f84f40, Explanatory message (ascii)

Debugging Details:
------------------


PROCESS_OBJECT: fffffa80064b2b30

IMAGE_NAME:  wininit.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: wininit

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  wininit.exe

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.

BUGCHECK_STR:  0xF4_IOERR

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`0838a0e8 fffff800`030097d2 : 00000000`000000f4 00000000`00000003 fffffa80`064b2b30 fffffa80`064b2e10 : nt!KeBugCheckEx
fffff880`0838a0f0 fffff800`02fb7bdb : ffffffff`ffffffff fffffa80`07142b60 fffffa80`064b2b30 fffffa80`064b2b30 : nt!PspCatchCriticalBreak+0x92
fffff880`0838a130 fffff800`02f3a838 : ffffffff`ffffffff 00000000`00000001 fffffa80`064b2b30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x179e6
fffff880`0838a180 fffff800`02c80f93 : fffffa80`064b2b30 fffff800`c0000006 fffffa80`07142b60 00000000`00d00bc0 : nt!NtTerminateProcess+0xf4
fffff880`0838a200 fffff800`02c7d530 : fffff800`02ccd6cf fffff880`0838ab78 fffff880`0838a8d0 fffff880`0838ac20 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0838a398 fffff800`02ccd6cf : fffff880`0838ab78 fffff880`0838a8d0 fffff880`0838ac20 00000000`ffdeb4d8 : nt!KiServiceLinkage
fffff880`0838a3a0 fffff800`02c81382 : fffff880`0838ab78 00000000`00d80000 fffff880`0838ac20 00000000`ffdefb88 : nt! ?? ::FNODOBFM::`string'+0x49974
fffff880`0838aa40 fffff800`02c7fefa : 00000000`00000000 00000000`ffde3900 00000000`00000001 00000000`00d80000 : nt!KiExceptionDispatch+0xc2
fffff880`0838ac20 00000000`77438f55 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`00d01180 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77438f55


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_wininit.exe

BUCKET_ID:  X64_0xF4_IOERR_IMAGE_wininit.exe

Followup: MachineOwner
---------

Minidump is attached.

I have also updated AHCI Intel driver to the newest version - no effect.

 

[mgorman87]

That error means that your SSD stopped communicating with the motherboard and it blue screened. I really don't know much about SSDs since they are so new so I can't really help you. Try googling and seeing if there is a fix out there.

It could also be because your motherboard is older and it might not support SSDs properly. Try finding a BIOS update.