Solved BSOD looks to be related to sleep settings, please help.

[davefon]

Hey Guys,
I'm getting a BSOD from my recently built desktop gaming rig. It correlates strongly with when the computer sleeps. In fact I've never seen it happen while I'm using the PC, only when I come to it after it's been unused for a while. I'd like to continue using the sleep functionality to save on electricity costs and (hopefully) increase the longevity of the PS'c components.

I've done some searching but I can't really interpret the dump files very well other than the problem seems to be related to the ntoskrnl.exe program.

I have followed the instructions on uploading the dump files and I've attached the file.

Thanks in advance,
Dave

 

[essenbe]

Hello, davefon and welcome to Seven Forums. I will try to help you with this, if I can. You only have 2 dump files and they give very differing information.

If you are overclocking, please set everything back to defaults. That is for your CPU and GPU both. As you can tell, I am not opposed to overclocking, but it just makes everything unreliable when you are not stable.

Please go into BIS and look at your SATA controller and see what it is set to (IDE< AHCI or Raid) Also, make sure your ram is set to Manufacturer's specs for frequency, timings and Voltage. Set your BIOS to optimized defaults, then make sure your SATA controller is set to what it is right now, set your ram frequency, timings and Voltage to manufacturer's specs, set your boot order as it is right now, save and exit.

Your Dump files listed

dump_asahci64
start             end                 module name
fffff880`05b72000 fffff880`05b81000   dump_asahci64 T (no symbols)           
    Loaded symbol image file: dump_asahci64.sys
    Image path: \SystemRoot\System32\Drivers\dump_asahci64.sys
    Image name: dump_asahci64.sys
    Timestamp:        Wed Jan 04 23:08:19 2012 (4F053043)
    CheckSum:         000104B8
    ImageSize:        0000F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

That is a file reserving part of the disk for creating crash dumps.

volsnap
start             end                 module name
fffff880`01000000 fffff880`0104c000   volsnap    (pdb symbols)          c:\symcache\volsnap.pdb\6C762AD2B37146AA848E4A16BD846B852\volsnap.pdb
    Loaded symbol image file: volsnap.sys
    Mapped memory image file: c:\symcache\volsnap.sys\4CE792C84c000\volsnap.sys
    Image path: \SystemRoot\system32\drivers\volsnap.sys
    Image name: volsnap.sys
    Timestamp:        Sat Nov 20 03:20:08 2010 (4CE792C8)
    CheckSum:         000527ED
    ImageSize:        0004C000
    File version:     6.1.7601.17514
    Product version:  6.1.7601.17514
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation

That is the Volume Shadow copy service used for making backup images.

The one most concerning is this one

KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in.  Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: fffff6fb41fffea8, lock type that was held (value 1,2,3, or PTE address)
Arg2: ffffffffc000000e, error status (normally i/o status code)
Arg3: 00000003a9198884, current process (virtual address for lock type 3, or PTE)
Arg4: fffff683fffd5000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
Debugging Details:
 
ERROR_CODE: (NTSTATUS) 0xc000000e -[COLOR=red] A device which does not exist was specified[/COLOR].
[COLOR=red]DISK_HARDWARE_ERROR: There was error with disk hardware[/COLOR]
BUGCHECK_STR:  0x7a_c000000e
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

The one thing all those errors have in common is the hard drive. I would check with your Intel Toolbox for any problems with the SSD. Also run the manufacturer's diagnostic tests on your Mechanical hard drives. Make sure your SSD is connected to port 0 or 1 on your motherboard and check both ends of the cables to make sure they are firmly attached.

I would also run check disk on the Mechanical Hard Drives. http://www.sevenforums.com/tutorials/433-disk-check.html

Toshiba does not list a diagnostic test for Toshiba drives they only list them for Fujitsu drives (http://storage.toshiba.com/storage-services-support/warranty-support/software-utilities#diagnostic )

Otherwise I would use the Seagate test Seatools, http://www.seagate.com/support/inte...-electronics/ld25-series/seatools-dos-master/

 

[davefon]

Thanks, essenbe,
I've been fighting with this issue for a while but I only have the two dump files because one of th emost recent things I tried was to finally reinstall Windows. Prior to that I had about 7 instances of this error, always with the same 2 issues.

I'm not OC'd and I'll check my BIOS again to make sure I'm at your suggested settings.

Prior to posting here, I tried Intel's SSD software and the drive checks out fine but the errors kept happening. I don't remember if I did anything with the HDD yet, I'll work on that tonight. A few weeks ago I ran Memtest for overnight and saw zero errors.

It's a very intermittent issue and only occurs when the computer power saving settings are allowed to turn it off so it's difficult to reproduce...but I sure hope it's not a mechanical issue with the SSD. Can we tell which drive is causing it?

Thanks,
Dave

 

[essenbe]

Do you use wireless? If not, disable it in BIOS. One thing I do with my systems is disable everything in BIOS that I do not use.

Almost every chipset released recently has had problems with waking from sleep, it seems. I know the Intel chipsets do. I don't seem to, but I don't use it, so.... what external devices are connected to your computer other than keyboard and mouse? What, other than those 2 things, are connected to USB ports?

When you do wake from sleep without any problems, have you noticed anything that takes longer than usual to be recognized? Some devices don't wake up as fast as others. I know many of the mechanical hard drives have an automatic sleep mode if not being used. When waking up, they have to spin up to speed before they are recognized by the computer. I was just thinking it could be that when the error code said 'there was a device that does not exist which was identified' it could be something that does not wake up or does not wake up in time. I know your graphics divers were identified in one dump and the closest I can come to what the device was is a WAN Miniport Network adapter. I'm not sure about that but I have tried to find it and that was a close as I could get.

Aside from something not waking up in time, I am just wondering if there is some service enabled in BIOS that you do not have installed that the motherboard or OS is trying to find.

I do realize, some of these things I am grasping at straws, but sometimes things like this happen. Also, sometimes the power saving features cause problems. For example, in the advanced power plan settings is a setting to save power by allowing the OS to turn off USB ports when not in use. That setting has caused a lot of people, including me, problems in the past. I have that disabled. It may not suit your purposes to disable it, buy it may be worth a try, depending on what you have connected by USB. For my purposes, I don't use sleep or Hibernate and disable them and most other power saving features. With an SSD, for my purposes, if I'm going to be away from the computer for a while, I shut it off. An SSD has a quick enough startup that I don't use sleep. I know others do and others have a specific need for it, and that's fine. I only mention these things for you to think about. The USB power saving and disabling things not use in bios is a good idea. I have wireless and Bluetooth on this board, but don't use them, so they are disabled in BIOS. If I want to use them in the future, I can enable them and install the drivers.

When you ran Memtest, did you use the one from Memtest.org and how many passes did you run? Each pass tests a different part of the ram and each of the 9 or 10 tests in each pass tests something different. To fully test the ram it takes a minimum of 8 complete passes at a minimum, more is better. That's why I ask.

 

[davefon]

Unfortunately, I do use the wireless.

I just ran the check disk that comes with Win 7 and it went quickly and without errors.

I used MemTest 4.1 from HCI Design. I ran 4 simultaneous windows for 3 hours with zero errors.

I'm going to go into the bios and go over it looking for the things you said, I was busy with a car problem last night so I couldn't even touch the PC until that was done.

The three things connected to the usb ports are:
1. HP Printer
2. Keyboard/ mouse wireless reciver
3. wireless adapter

Since you saw an issue with the WAN Miniport Network Adapter I can unplug that and see what happens.

 

[essenbe]

I may suggest you update the drivers for the wireless, and if that does not work, then try to use the computer with it uninstalled. Also, I realize what a pain it is, as I've had to do it more times than I care to count, but the best most reliable memory test there is, is memtest.org. It just takes it quite a long time to run it. It has to be run for 8 passes all at one time, which will take 20+ hours with 16 GB of memory. but it is worth it. There is no test I have ever heard of that runs under Windows that is reliable.

Please Run Memtest86+

   Information

Please download from this site only http://www.memtest.org/ in the middle of the page are the Download links, you can download the ISO.zip or the Auto USB Flash Drive installer.zip

Extract the Zip file. If you chose the ISO image, burn it to a CD using Windows Disk Image Burner or any Image burner you may have. If you downloaded the Auto USB installer, extract it, insert your USB 2.0 Flash Drive and take note of the drive letter. Run the installer, select the Flash Drive Letter, check the format box and press next. It will install memtest86+ to a flash drive. You can use either V4.20 or V5.01. Boot from your selected media. If you use V5.01 it will tell you to press certain buttons at the start, please press no buttons. The test will begin on it's own and continue to run until you stop it. It needs to run for 8 complete passes or until you receive an error. If you receive an error, stop the test. Even 1 error is a fail. Each pass tests a different part of the ram and each of the 10 tests in each pass tests something different. It takes a minimum of 8 passes to completely test the ram, more passes are better. It is quite a long test and will take several hours depending on how much ram you have. Due to the time length it is best to run overnight. If you have any questions, please do not hesitate to ask​

 

[davefon]

Essenbe, I was absent for a while for testing but it's been 5 full days since the last BSOD and all I did was follow your suggestion:
"Make sure your SSD is connected to port 0 or 1 on your motherboard and check both ends of the cables to make sure they are firmly attached"

My SSD was connected to a navy blue SATA plug which was number SATA6G_E1. I have since plugged it into a grey SATA plug number SATA6G_1 and it's been fine.

Thanks for your help!

Dave

 

[essenbe]

You're very welcome. Some of the add on ports have issues with SSDs, which is what yours was plugged into. Besides the native sata ports give better performance. I'm glad it was an easy fix for you. Whenever you feel it's solved, please mark this thread as solved. I would appreciate it.

 

[davefon]

Yeah, I'm calling this "resolved."

Thanks again.

 

[essenbe]

Glad to hear it. Great job. Glad you have it running right.