BSOD coming back from sleep

mycelo · 04 Mar 2011

Would you guys help me with this one?

I suspect it has something to do with Bluetooth, it seems to happen when my cellphone was connected before entering sleep state.

I hope I provided all necessary details inside this ZIP file.

Also, another seemingly unrelated issue, my laptop very rarely doesn't find a boot device. I even switched my pretty new HDD for a SSD but the problem remains. I understand that it leads to problems with my SATA interface or something, but maybe you guys have something else to say about that.

DeanP · 04 Mar 2011

Dump blames 0x7F - see this thread: STOP 0x7F (UNEXPECTED_KERNEL_MODE_TRAP)

Code:

Event[831]:
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2011-03-02T16:29:25.000
  Event ID: 1001
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: mycelo-lg
  Description: 
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000007f (0x00000008, 0x90303750, 0x00000000, 0x00000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: .

Please upload Memory.DMP from C:\Windows to a third-party site (such as Mediafire, Uppit).

Regards...
Dean

mycelo · 05 Mar 2011

Link to MEMORY.DMP

I've also attached another BSOD report because I had another one yesterday and I guess this dump is related to the last one. But the STOP error was the same and the circumstances were the same.

mycelo · 10 Mar 2011

I guess I'll have to just live with that?

Thank you for your time anyway.

wish · 10 Mar 2011

Hi,
The crash look like caused by your Wireless LAN driver, so it's better to update it.
→ Realtek Wireless LAN 802.11n PCI-E

And also you must increase your Windows page file size. I recommend you to use default settings for page file.

LOG

Code:

Windows 7 Kernel Version 7600 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0x83008000 PsLoadedModuleList = 0x83150810
Debug session time: Fri Mar  4 12:32:23.131 2011 (GMT-8)
System Uptime: 0 days 0:22:10.738
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols

Loading unloaded module list
...............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 801df000, 0, 0}

*** ERROR: Module load completed but symbols could not be loaded for rtl8192se.sys
Probably caused by : rtl8192se.sys ( rtl8192se+187e0 )

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

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

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: 801df000
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR:  0x7f_8

TSS:  00000028 -- (.tss 0x28)
eax=83131d20 ebx=8313363c ecx=8313363c edx=0000342e esi=83131d20 edi=00000000
eip=83076cd4 esp=a54c4ff4 ebp=a54c501c iopl=0         nv up ei ng nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010282
nt!KiSearchForNewThread+0xb:
83076cd4 53              push    ebx
Resetting default scope

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 8307699f to 83076cd4

STACK_TEXT:  
a54c501c 8307699f 00000000 86718d48 00000000 nt!KiSearchForNewThread+0xb
a54c5058 83075423 86718e08 86718d48 a54c511c nt!KiSwapThread+0xe0
a54c5080 8306f2cf 86718d48 86718e08 00000000 nt!KiCommitThreadWait+0x1df
a54c50fc 8e474ef5 a54c511c 00000000 00000000 nt!KeWaitForSingleObject+0x393
a54c5144 940747e0 000186a0 890f5000 a54c5164 ndis!NdisMSleep+0x55
WARNING: Stack unwind information not available. Following frames may be wrong.
a54c5154 940a219a 000186a0 890f5000 a54c51b0 rtl8192se+0x187e0
a54c5164 940a2442 00000002 00000001 890f5001 rtl8192se+0x4619a
a54c51b0 940a21c4 00000002 00000001 890f5001 rtl8192se+0x46442
a54c51f0 940a2442 00000002 00000001 890f5001 rtl8192se+0x461c4
a54c523c 940a21c4 00000002 00000001 890f5001 rtl8192se+0x46442
a54c527c 940a2442 00000002 00000001 890f5001 rtl8192se+0x461c4
a54c52c8 940a21c4 00000002 00000001 890f5001 rtl8192se+0x46442
a54c5308 940a2442 00000002 00000001 890f5001 rtl8192se+0x461c4
a54c5354 940a21c4 00000002 00000001 890f5001 rtl8192se+0x46442
a54c5394 940a2442 00000002 00000001 890f5001 rtl8192se+0x461c4
a54c53e0 940a21c4 00000002 00000001 890f5001 rtl8192se+0x46442
a54c5420 940a2442 00000002 00000001 890f5001 rtl8192se+0x461c4
a54c546c 940a21c4 00000002 00000001 890f5001 rtl8192se+0x46442
a54c54ac 940a2442 00000002 00000001 890f5001 rtl8192se+0x461c4
a54c54f8 940a21c4 00000002 00000001 890f5001 rtl8192se+0x46442
a54c5538 940a2442 00000002 00000001 890f5001 rtl8192se+0x461c4
a54c5584 940a21c4 00000002 00000001 890f5001 rtl8192se+0x46442
a54c55c4 940a2442 00000002 00000001 890f5001 rtl8192se+0x461c4
a54c5610 940a21c4 00000002 00000001 890f5001 rtl8192se+0x46442
a54c5650 940a2442 00000002 00000001 890f5001 rtl8192se+0x461c4
a54c569c 940a21c4 00000002 00000001 890f5001 rtl8192se+0x46442
a54c56dc 940a2442 00000002 00000001 890f5001 rtl8192se+0x461c4
a54c5728 940a21c4 00000002 00000001 890f5001 rtl8192se+0x46442
a54c5768 940a2442 00000002 00000001 890f5001 rtl8192se+0x461c4
a54c57b4 940a21c4 00000002 00000001 890f5001 rtl8192se+0x46442
a54c57f4 940a2442 00000002 00000001 890f5001 rtl8192se+0x461c4
a54c5840 940a21c4 00000002 00000001 890f5001 rtl8192se+0x46442
a54c5880 940a2442 00000002 00000001 890f5001 rtl8192se+0x461c4
a54c58cc 940a21c4 00000002 00000001 890f5001 rtl8192se+0x46442
a54c590c 940a2442 00000002 00000001 890f5001 rtl8192se+0x461c4
a54c5958 940a21c4 00000002 00000001 890f5001 rtl8192se+0x46442
a54c5998 940a2442 00000002 00000001 890f5001 rtl8192se+0x461c4
a54c59e4 940a21c4 00000002 00000001 890f5001 rtl8192se+0x46442
a54c5a24 940a2442 00000002 00000001 890f5001 rtl8192se+0x461c4
a54c5a70 940a21c4 00000002 00000001 890f5001 rtl8192se+0x46442
a54c5ab0 940a2442 00000002 00000001 890f5001 rtl8192se+0x461c4
a54c5afc 940a21c4 00000002 00000001 890f5001 rtl8192se+0x46442
a54c5b3c 940a2442 00000002 00000001 890f5001 rtl8192se+0x461c4
a54c5b88 940a21c4 00000002 00000001 890f5001 rtl8192se+0x46442
a54c5bc8 940a2442 00000002 00000001 890f5001 rtl8192se+0x461c4
a54c5c14 940a21c4 00000002 00000001 890f5001 rtl8192se+0x46442
a54c5c54 940a2442 00000002 00000001 890f5001 rtl8192se+0x461c4
a54c5ca0 940a21c4 00000002 00000001 890f5001 rtl8192se+0x46442
a54c5ce0 940a2442 00000002 00000001 890f5001 rtl8192se+0x461c4
a54c5d2c 940a21c4 00000002 00000001 890f5001 rtl8192se+0x46442
a54c5d6c 940a2442 00000002 00000001 890f5001 rtl8192se+0x461c4
a54c5db8 940a21c4 00000002 00000001 890f5001 rtl8192se+0x46442
a54c5df8 940a2442 00000002 00000001 890f5001 rtl8192se+0x461c4
a54c5e44 940a21c4 00000002 00000001 890f5001 rtl8192se+0x46442
a54c5e84 940a2442 00000002 00000001 890f5001 rtl8192se+0x461c4
a54c5ed0 940a21c4 00000002 00000001 890f5001 rtl8192se+0x46442
a54c5f10 940a2442 00000002 00000001 890f5001 rtl8192se+0x461c4
a54c5f5c 940a21c4 00000002 00000001 890f5001 rtl8192se+0x46442
a54c5f9c 940a2442 00000002 00000001 890f5001 rtl8192se+0x461c4
a54c5fe8 940a21c4 00000002 00000001 890f5001 rtl8192se+0x46442
a54c6028 940a2442 00000002 00000001 890f5001 rtl8192se+0x461c4
a54c6074 940a21c4 00000002 00000001 890f5001 rtl8192se+0x46442
a54c60b4 940a2442 00000002 00000001 890f5001 rtl8192se+0x461c4
a54c6100 940a21c4 00000002 00000001 890f5001 rtl8192se+0x46442
a54c6140 940a2442 00000002 00000001 890f5001 rtl8192se+0x461c4
a54c618c 940a21c4 00000002 00000001 890f5001 rtl8192se+0x46442
a54c61cc 940a2442 00000002 00000001 890f5001 rtl8192se+0x461c4
a54c6218 940a21c4 00000002 00000001 890f5001 rtl8192se+0x46442
a54c6258 940a2442 00000002 00000001 890f5001 rtl8192se+0x461c4
a54c62a4 940a21c4 00000002 00000001 890f5001 rtl8192se+0x46442
a54c62e4 940a2442 00000002 00000001 890f5001 rtl8192se+0x461c4
a54c6330 940a21c4 00000002 00000001 890f5001 rtl8192se+0x46442
a54c6370 940a2442 00000002 00000001 890f5001 rtl8192se+0x461c4
a54c63bc 940a21c4 00000002 00000001 890f5001 rtl8192se+0x46442
a54c63fc 940a2442 00000002 00000001 890f5001 rtl8192se+0x461c4


STACK_COMMAND:  .tss 0x28 ; kb

FOLLOWUP_IP: 
rtl8192se+187e0
940747e0 eb1a            jmp     rtl8192se+0x187fc (940747fc)

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  rtl8192se+187e0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: rtl8192se

IMAGE_NAME:  rtl8192se.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4bb45e85

FAILURE_BUCKET_ID:  0x7f_8_rtl8192se+187e0

BUCKET_ID:  0x7f_8_rtl8192se+187e0

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

0: kd> lmvm rtl8192se
start    end        module name
9405c000 9416f000   rtl8192se   (no symbols)           
    Loaded symbol image file: rtl8192se.sys
    Image path: \SystemRoot\system32\DRIVERS\rtl8192se.sys
    Image name: rtl8192se.sys
    Timestamp:        Thu Apr 01 01:51:17 2010 (4BB45E85)
    CheckSum:         000F8248
    ImageSize:        00113000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

mycelo · 10 Mar 2011

wish said:

Hi,
The crash look like caused by your Wireless LAN driver, so it's better to update it.
→ Realtek Wireless LAN 802.11n PCI-E

Okay, thank you. I suspect that I already have the latest one, but now at least I have the issue nailed down.

wish said:

And also you must increase your Windows page file size. I recommend you to use default settings for page file.

May I ask why? I mean, I ran my laptop several months without a pagefile at all, and I didn't seem to have any issues due to that. Then I read somewhere that the BSODs wouldn't be able to dump the error details if I didn't have some pagefile space, this is why I have such small one.

I researched quite a bit about the real need to have a pagefile (which will certainly contribute to wear my SSD) and couldn't find a good reason. Maybe do you guys could come up with a good argument?

wish · 10 Mar 2011

Here's an article about SSD → Support and Q&A for Solid-State Drives - Engineering Windows 7 - Site Home - MSDN Blogs

Should the pagefile be placed on SSDs?
Yes. Most pagefile operations are small random reads or larger sequential writes, both of which are types of operations that SSDs handle well.
In looking at telemetry data from thousands of traces and focusing on pagefile reads and writes, we find that

Pagefile.sys reads outnumber pagefile.sys writes by about 40 to 1,
Pagefile.sys read sizes are typically quite small, with 67% less than or equal to 4 KB, and 88% less than 16 KB.
Pagefile.sys writes are relatively large, with 62% greater than or equal to 128 KB and 45% being exactly 1 MB in size.

In fact, given typical pagefile reference patterns and the favorable performance characteristics SSDs have on those patterns, there are few files better than the pagefile to place on an SSD.

If you never had problems without pagefile, it's mean your RAM is good enough for your OS and applications and they didn't consume much memory resources.
So swapping file to drive is no longer necessary.

You're the owner so I bet you have more knowledge about your system.
Just go on with your best decision.

mycelo · 11 Mar 2011

You guys are amazing, I can't thank you enough.

Also, I did find a newer version of my problematic driver and I'm getting no BSODs anymore!