BSOD - Immediately after waking computer from sleep

[somethingsimple]

Hello,

The BSOD occurs after/while waking the computer from sleep.

I like to fall asleep to a movie or show, so I have a program called sleep# which will immediately put the computer to sleep once the media player has stopped playing.

Sleep#: Save Power. No More Noise! | Free Audio & Video software downloads at SourceForge.net

I have had the program for sometime and it has operated without issue for several months, at least.

Thank you for your time and effort.
If you need more information, please don't hesitate to ask.

 

[koolkat77]

Please test RAM.

Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Usra\Downloads\SF_15-04-2014\032614-12386-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`0341c000 PsLoadedModuleList = 0xfffff800`0365f6d0
Debug session time: Thu Mar 27 02:57:13.748 2014 (UTC + 6:00)
System Uptime: 4 days 15:50:19.684
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41201, fffff68000137360, fedc0058fe37ffd7, fffffa8012340a90}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13702 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041201, The subtype of the bugcheck.
Arg2: fffff68000137360
Arg3: fedc0058fe37ffd7
Arg4: fffffa8012340a90

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


BUGCHECK_STR:  0x1a_41201

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  CCC.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800034ed9fe to fffff80003491bc0

STACK_TEXT:  
fffff880`081f18f8 fffff800`034ed9fe : 00000000`0000001a 00000000`00041201 fffff680`00137360 fedc0058`fe37ffd7 : nt!KeBugCheckEx
fffff880`081f1900 fffff800`034ab6c4 : 00000000`00000080 fffff680`00137378 00000000`26e6c000 00000000`00000080 : nt! ?? ::FNODOBFM::`string'+0x13702
fffff880`081f1940 fffff800`0378a28a : fffff880`00000000 00000000`00000000 fffffa80`0fe8c060 00000000`00000004 : nt!MiCommitExistingVad+0x2c4
fffff880`081f19e0 fffff800`03490e53 : ffffffff`ffffffff fffffa80`116f8630 fffff8a0`00000000 fffff880`081f1da8 : nt!NtAllocateVirtualMemory+0x134a
fffff880`081f1b80 fffff800`0348d410 : fffff800`0377f484 00000000`00000000 00000000`01180080 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
fffff880`081f1d88 fffff800`0377f484 : 00000000`00000000 00000000`01180080 00000000`00000000 fffffa80`0ca0b908 : nt!KiServiceLinkage
fffff880`081f1d90 fffff800`0377d619 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00001000 : nt!RtlCreateUserStack+0x1a4
fffff880`081f1e80 fffff800`0377d24a : fffffa80`0fe8c060 00000000`00000000 fffffa80`0ca0bb01 fffff880`081f28d0 : nt!PspAllocateThread+0x299
fffff880`081f20a0 fffff800`03781569 : fffff880`081f2b60 00000000`00000000 00000000`00000001 fffff880`081f28d0 : nt!PspCreateThread+0x1d2
fffff880`081f2320 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtCreateThreadEx+0x25d


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+13702
fffff800`034ed9fe cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+13702

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  521ea035

FAILURE_BUCKET_ID:  X64_0x1a_41201_nt!_??_::FNODOBFM::_string_+13702

BUCKET_ID:  X64_0x1a_41201_nt!_??_::FNODOBFM::_string_+13702

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

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• RAM - Test with Memtest86+

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
​

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
​

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
​

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
​

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
​

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

   Information

Errors are sometimes found after 8 passes.

   Tip

Do this test overnight, before going to bed.

 

[somethingsimple]

So far I have tested both sticks together for 16 passes with no errors.
Should I continue to the individual sticks?
The total time for both sticks was 42 hrs and 44 mins.

 

[koolkat77]

So far I have tested both sticks together for 16 passes with no errors.
Should I continue to the individual sticks?
The total time for both sticks was 42 hrs and 44 mins.

I think that's fine.

Any new BSOD? Please upload the dumps if so.

 

[somethingsimple]

No new BSOD.
Will update when it occurs.