Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD after sleep wake-up, random times


  • Please log in to reply
13 replies to this topic

#1 xb9000

xb9000

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:06:02 PM

Posted 12 April 2012 - 11:13 PM

Been getting a BSOD occasionally usually when waking up after sleep. Tried installing new drivers, don't know if I got all of them. Here's the minidump report I could find, not sure I did it right. Just followed guide here http://www.bleepingcomputer.com/forums/topic176011.html best I could. Any help would be great. Anything else needed, just let me know. Thank you much.

BSOD itself had this error: STOP: 0x6 F4 (0x15 3, 0xfffffa8005B7BB30, 0xfffffA8005B7BE10, 0xfffff800479C5F0)


Microsoft ® Windows Debugger Version 6.2.8229.0 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\041212-12589-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`0441d000 PsLoadedModuleList = 0xfffff800`04661650
Debug session time: Thu Apr 12 21:22:05.740 2012 (UTC - 6:00)
System Uptime: 0 days 1:52:47.004
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
.....
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x86\triage\oca.ini, error 2
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x86\winxp\triage.ini, error 2
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa8005b7bb30, fffffa8005b7be10, fffff8000479c5f0}

----- ETW minidump data unavailable-----
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x86\triage\modclass.ini, error 2
Probably caused by : csrss.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: fffffa8005b7bb30, Terminating object
Arg3: fffffa8005b7be10, Process image file name
Arg4: fffff8000479c5f0, Explanatory message (ascii)

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

----- ETW minidump data unavailable-----
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x86\triage\modclass.ini, error 2

PROCESS_OBJECT: fffffa8005b7bb30

IMAGE_NAME: csrss.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: csrss

FAULTING_MODULE: 0000000000000000

PROCESS_NAME: csrss.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: WIN7_DRIVER_FAULT

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`065d5e38 fffff800`048237b2 : 00000000`000000f4 00000000`00000003 fffffa80`05b7bb30 fffffa80`05b7be10 : nt!KeBugCheckEx
fffff880`065d5e40 fffff800`047d0c9b : ffffffff`ffffffff fffffa80`07372660 fffffa80`05b7bb30 fffffa80`05b7bb30 : nt!PspCatchCriticalBreak+0x92
fffff880`065d5e80 fffff800`04750094 : ffffffff`ffffffff 00000000`00000001 fffffa80`05b7bb30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176d6
fffff880`065d5ed0 fffff800`04498fd3 : fffffa80`05b7bb30 fffff800`c0000006 fffffa80`07372660 00000000`00ec0f00 : nt!NtTerminateProcess+0xf4
fffff880`065d5f50 fffff800`04495570 : fffff800`044e4aff fffff880`065d6a38 fffff880`065d6790 fffff880`065d6ae0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`065d60e8 fffff800`044e4aff : fffff880`065d6a38 fffff880`065d6790 fffff880`065d6ae0 00000000`00ec1c10 : nt!KiServiceLinkage
fffff880`065d60f0 fffff800`044993c2 : fffff880`065d6a38 00000000`00012194 fffff880`065d6ae0 00000000`00ec16e8 : nt! ?? ::FNODOBFM::`string'+0x48e24
fffff880`065d6900 fffff800`04497f3a : 00000000`00000000 000007fe`fd21d8b4 00000000`00000001 00000000`00012194 : nt!KiExceptionDispatch+0xc2
fffff880`065d6ae0 00000000`76da9c12 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`00ec1630 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76da9c12


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0xF4_IOERR_IMAGE_csrss.exe

BUCKET_ID: X64_0xF4_IOERR_IMAGE_csrss.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: fffffa8005b7bb30, Terminating object
Arg3: fffffa8005b7be10, Process image file name
Arg4: fffff8000479c5f0, Explanatory message (ascii)

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

----- ETW minidump data unavailable-----
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x86\triage\modclass.ini, error 2

PROCESS_OBJECT: fffffa8005b7bb30

IMAGE_NAME: csrss.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: csrss

FAULTING_MODULE: 0000000000000000

PROCESS_NAME: csrss.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: WIN7_DRIVER_FAULT

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`065d5e38 fffff800`048237b2 : 00000000`000000f4 00000000`00000003 fffffa80`05b7bb30 fffffa80`05b7be10 : nt!KeBugCheckEx
fffff880`065d5e40 fffff800`047d0c9b : ffffffff`ffffffff fffffa80`07372660 fffffa80`05b7bb30 fffffa80`05b7bb30 : nt!PspCatchCriticalBreak+0x92
fffff880`065d5e80 fffff800`04750094 : ffffffff`ffffffff 00000000`00000001 fffffa80`05b7bb30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176d6
fffff880`065d5ed0 fffff800`04498fd3 : fffffa80`05b7bb30 fffff800`c0000006 fffffa80`07372660 00000000`00ec0f00 : nt!NtTerminateProcess+0xf4
fffff880`065d5f50 fffff800`04495570 : fffff800`044e4aff fffff880`065d6a38 fffff880`065d6790 fffff880`065d6ae0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`065d60e8 fffff800`044e4aff : fffff880`065d6a38 fffff880`065d6790 fffff880`065d6ae0 00000000`00ec1c10 : nt!KiServiceLinkage
fffff880`065d60f0 fffff800`044993c2 : fffff880`065d6a38 00000000`00012194 fffff880`065d6ae0 00000000`00ec16e8 : nt! ?? ::FNODOBFM::`string'+0x48e24
fffff880`065d6900 fffff800`04497f3a : 00000000`00000000 000007fe`fd21d8b4 00000000`00000001 00000000`00012194 : nt!KiExceptionDispatch+0xc2
fffff880`065d6ae0 00000000`76da9c12 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`00ec1630 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76da9c12


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0xF4_IOERR_IMAGE_csrss.exe

BUCKET_ID: X64_0xF4_IOERR_IMAGE_csrss.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: fffffa8005b7bb30, Terminating object
Arg3: fffffa8005b7be10, Process image file name
Arg4: fffff8000479c5f0, Explanatory message (ascii)

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

----- ETW minidump data unavailable-----
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x86\triage\modclass.ini, error 2

PROCESS_OBJECT: fffffa8005b7bb30

IMAGE_NAME: csrss.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: csrss

FAULTING_MODULE: 0000000000000000

PROCESS_NAME: csrss.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: WIN7_DRIVER_FAULT

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`065d5e38 fffff800`048237b2 : 00000000`000000f4 00000000`00000003 fffffa80`05b7bb30 fffffa80`05b7be10 : nt!KeBugCheckEx
fffff880`065d5e40 fffff800`047d0c9b : ffffffff`ffffffff fffffa80`07372660 fffffa80`05b7bb30 fffffa80`05b7bb30 : nt!PspCatchCriticalBreak+0x92
fffff880`065d5e80 fffff800`04750094 : ffffffff`ffffffff 00000000`00000001 fffffa80`05b7bb30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176d6
fffff880`065d5ed0 fffff800`04498fd3 : fffffa80`05b7bb30 fffff800`c0000006 fffffa80`07372660 00000000`00ec0f00 : nt!NtTerminateProcess+0xf4
fffff880`065d5f50 fffff800`04495570 : fffff800`044e4aff fffff880`065d6a38 fffff880`065d6790 fffff880`065d6ae0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`065d60e8 fffff800`044e4aff : fffff880`065d6a38 fffff880`065d6790 fffff880`065d6ae0 00000000`00ec1c10 : nt!KiServiceLinkage
fffff880`065d60f0 fffff800`044993c2 : fffff880`065d6a38 00000000`00012194 fffff880`065d6ae0 00000000`00ec16e8 : nt! ?? ::FNODOBFM::`string'+0x48e24
fffff880`065d6900 fffff800`04497f3a : 00000000`00000000 000007fe`fd21d8b4 00000000`00000001 00000000`00012194 : nt!KiExceptionDispatch+0xc2
fffff880`065d6ae0 00000000`76da9c12 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`00ec1630 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76da9c12


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0xF4_IOERR_IMAGE_csrss.exe

BUCKET_ID: X64_0xF4_IOERR_IMAGE_csrss.exe

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

BC AdBot (Login to Remove)

 


#2 killerflea

killerflea

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:08:02 PM

Posted 13 April 2012 - 01:07 PM

Do you have a registry editor......and are you comfortable in the registry?

#3 xb9000

xb9000
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:06:02 PM

Posted 13 April 2012 - 04:14 PM

No, and no. I know more about hardware, enough to put together a PC at least, but not much about software. Given instructions, I might be able to figure it out, but that's about it. :/

#4 noknojon

noknojon

  • Banned
  • 10,871 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Local time:11:02 AM

Posted 14 April 2012 - 01:17 AM

Do you have a registry editor......and are you comfortable in the registry?

The use of, and links to any Registry Editor Tools are not sancioned by this forum for many reasons -

Simple mis-use can lead to a badly corrupted registry -

Thank You -

#5 hamluis

hamluis

    Moderator


  • Moderator
  • 56,113 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:08:02 PM

Posted 15 April 2012 - 08:40 AM

Regedit is the Windows registry editor/tool.

Are you employing a solid-state drive?

FWIW: Damaged video drivers are sometimes the cause of problems revolving around sleep/hibernation. You might uninstall the current video drivers...and then reinstall same, available at your system manufacturer's website.

Download/install BlueScreenView, http://www.nirsoft.net/utils/blue_screen_view.html .

Double-click BlueScreenView.exe file.

When autoscan is done (screen comes up), click Edit/Select All...then File/Save Selected Items.

Save the report as BSOD.txt.

Open BSOD.txt, copy all content and paste it into your next reply.

FWIW

Louis

Edited by hamluis, 15 April 2012 - 08:46 AM.


#6 xb9000

xb9000
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:06:02 PM

Posted 16 April 2012 - 08:24 PM

==================================================
Dump File : 041612-5959-01.dmp
Crash Time : 4/16/2012 9:07:26 PM
Bug Check String : CRITICAL_OBJECT_TERMINATION
Bug Check Code : 0x000000f4
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`06e8fb30
Parameter 3 : fffffa80`06e8fe10
Parameter 4 : fffff800`0378d5f0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cd40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17727 (win7sp1_gdr.111118-2330)
Processor : x64
Crash Address : ntoskrnl.exe+7cd40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\041612-5959-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 274,664
==================================================

==================================================
Dump File : 041612-5428-01.dmp
Crash Time : 4/16/2012 6:36:10 PM
Bug Check String : KERNEL_DATA_INPAGE_ERROR
Bug Check Code : 0x0000007a
Parameter 1 : fffff6fc`400309d0
Parameter 2 : ffffffff`c000009d
Parameter 3 : 00000000`95167860
Parameter 4 : fffff880`0613a568
Caused By Driver : RTKVHD64.sys
Caused By Address : RTKVHD64.sys+268568
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7cd40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\041612-5428-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 282,080
==================================================

==================================================
Dump File : 041212-12589-01.dmp
Crash Time : 4/12/2012 9:25:49 PM
Bug Check String : CRITICAL_OBJECT_TERMINATION
Bug Check Code : 0x000000f4
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`05b7bb30
Parameter 3 : fffffa80`05b7be10
Parameter 4 : fffff800`0479c5f0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cd40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17727 (win7sp1_gdr.111118-2330)
Processor : x64
Crash Address : ntoskrnl.exe+7cd40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\041212-12589-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 274,368
==================================================

==================================================
Dump File : 041212-11575-01.dmp
Crash Time : 4/12/2012 7:21:47 PM
Bug Check String : KERNEL_DATA_INPAGE_ERROR
Bug Check Code : 0x0000007a
Parameter 1 : fffff6fc`4000b778
Parameter 2 : ffffffff`c000000e
Parameter 3 : 00000000`ba70e860
Parameter 4 : fffff880`016eff44
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+eff44
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7cd40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\041212-11575-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 282,080
==================================================

==================================================
Dump File : 041112-10904-01.dmp
Crash Time : 4/11/2012 4:57:11 PM
Bug Check String : CRITICAL_OBJECT_TERMINATION
Bug Check Code : 0x000000f4
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`07248b30
Parameter 3 : fffffa80`07248e10
Parameter 4 : fffff800`047875f0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cd40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17727 (win7sp1_gdr.111118-2330)
Processor : x64
Crash Address : ntoskrnl.exe+7cd40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\041112-10904-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 274,312
==================================================

Edited by xb9000, 16 April 2012 - 10:30 PM.


#7 xb9000

xb9000
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:06:02 PM

Posted 16 April 2012 - 10:28 PM

Yes, I am using an SSD as the system drive. And I did update the video card drivers and the BIOS.

#8 hamluis

hamluis

    Moderator


  • Moderator
  • 56,113 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:08:02 PM

Posted 17 April 2012 - 10:08 AM

You might try updating your SSD firmware.

Why did you update the BIOS?

Louis

#9 xb9000

xb9000
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:06:02 PM

Posted 20 April 2012 - 06:38 AM

SSD firmware update didn't help. Updated the BIOS cuz two of the SATA ports stopped working, thought it might help, and it did. But still getting the BSOD... Is it more likely to be a hardware or software issue?

#10 hamluis

hamluis

    Moderator


  • Moderator
  • 56,113 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:08:02 PM

Posted 20 April 2012 - 12:06 PM

If you are having problems with motherboard ports...I'd say that's a hardware situation...but I've been wrong before :).

Let's hang on here for other inputs.

Louis

#11 rotor123

rotor123

  • Moderator
  • 8,093 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:09:02 PM

Posted 20 April 2012 - 03:40 PM

Hi,

I don't like hearing that two of the SATA ports stopped working that makes me suspicious of the Motherboard as was mentioned before.
It is also possible that the drives attached to them are problematic.

However certain models of SSDs with the Sandforce 2xxx can also cause a BSOD when waking up.
Another possible cause is the controller on the SATA port you are hooked up too.
What controller are you using, Marvel, Nvidia, Intel etc.
Are you using the ports you said had stopped working before the BIOS update?
Do you have a USB Flash Drives plugged in?
Have you visited the SSD makers website to see if they have any diagnostics to run against the SSD? Intel and Samsung for example have a toolbox.

Windows will crash if a non-removable drive drops out.

What make and Model SSD, Motherboard, Video card.

And of course the lazy mans approach to this problem, If it gives problems don't use it :whistle:

Good Luck
Roger

Edited by rotor123, 20 April 2012 - 03:41 PM.

Fortune Cookie says: Fortune not Found: Abort, Retry, Ignore?

Sent from my All-In-One Desktop. Perfect for Internet, Not for heavy usage or gaming however.

How Does a computer get Infected? http://www.bleepingcomputer.com/forums/t/2520/how-did-i-get-infected/
Forum Rules,    The BC Welcome Guide

167 @ June 2015


#12 xb9000

xb9000
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:06:02 PM

Posted 20 April 2012 - 07:11 PM

Here's my system:
Intel i5-2300 2.80GHz
AsRock H61M/U3S3 BIOS v. 1.40
Intel Cougar Point 6 port SATA AHCI Controller
SSD: Mushkin Enhanced Chronos Deluxe 60GB MKNSSDCR60GB-DX
HDD: Western Digital Caviar Blue 320GB WDC WD3200AAKX-001CA0
PowerColor Radeon 6790 1GB
Corsair XMS 4GB (2x2GB) DDR1333 CMX4GX3M2A1333C8
Windows 7 64bit Home Premium
Rosewill Green 530W PSU

SSD and HDD each plugged into 6GB/s port with ASMedia ASM1061 controller, which are the ones that hadn't been working. I'll try switching em out
No USB drives plugged in, just a USB mouse and PS/2 keyboard.

Thanks for the tips, I really appreciate it.

#13 xb9000

xb9000
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:06:02 PM

Posted 20 April 2012 - 07:14 PM

BTW, here's the latest BSOD error. Don't know if it helps at all.
==================================================
Dump File : 042012-5694-01.dmp
Crash Time : 4/20/2012 5:29:54 AM
Bug Check String : CRITICAL_OBJECT_TERMINATION
Bug Check Code : 0x000000f4
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`060a4b30
Parameter 3 : fffffa80`060a4e10
Parameter 4 : fffff800`037d35f0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7cd40
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17727 (win7sp1_gdr.111118-2330)
Processor : x64
Crash Address : ntoskrnl.exe+7cd40
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\042012-5694-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 274,664
==================================================

#14 rotor123

rotor123

  • Moderator
  • 8,093 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:09:02 PM

Posted 21 April 2012 - 10:04 AM

Hello

That sounds like a good Idea. I think I'd try using a Intel SATA port and Test. I would also try a Intel SATA II port as part of the testing, Motherboard ports and not add on card of course.

One possibility is that the controller isn't waking up and causing the Blue Screens.

Another possibility from the customer reviews here
http://www.newegg.com/Product/Product.aspx?Item=N82E16820226246&Tpk=MKNSSDCR60GB-DX

Example

Cons: Randomly gave me the BSOD, and then hid in the bios and the only way to show the drive again, was to unplug the whole computer and then plug back in


This controller has been problematic with regards to certain hardware causing BSODs, so maybe....
It has been getting better with later firmwares however.

Controller
SandForce SF-2281


So lets see how it works on a Intel SATA port.

Also set the controller top AHCI for SSDs, And do not fell up a SSD. It needs some free room for wear leveling and garbage collection (Trim).

With wear leveling the more free room the longer the SSD life as it has more room to spread the wear around in.

I'm at 49Gb used on this computer out of 111Gb for example.

Good Luck
Roger

Edited by rotor123, 21 April 2012 - 10:09 AM.

Fortune Cookie says: Fortune not Found: Abort, Retry, Ignore?

Sent from my All-In-One Desktop. Perfect for Internet, Not for heavy usage or gaming however.

How Does a computer get Infected? http://www.bleepingcomputer.com/forums/t/2520/how-did-i-get-infected/
Forum Rules,    The BC Welcome Guide

167 @ June 2015





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users