Crazy BSOD Windows 8

I've experienced a crazy issue recently. Out of nowhere on my Yoga 13, I got BSOD CRITICAL_PROCESS_DIED. Then, upon the first reboot after that, I received another BSOD "SYSTEM_THREAD_EXCEPTION_NOT_HANDLED" and my system did not want to wake. I was offered a chance to system restore, but I cancelled, upon which my Lenovo just hung at the BOOT menu doing nothing.

I hard reset, and now I'm in he system fine, as if nothing happened.

Any ideas what this could be related to? I ran CHKDSK and it says no bad sectors. I'm stumped!

 

So I have recently done a clean install of W 8.1, and while it worked fine for a week, lately it has started crashing all the time. It is always the same error, as above, and always loops BSOD until I do a hard shutdown.

I can't remember what I did last time to fix it, but it is honestly the worst. Here are 2 log files.

srttail.txt

Code:

Startup Repair diagnosis and repair log
---------------------------
Last successful boot time: ‎12/‎8/‎2013 5:13:02 PM (GMT)
Number of repair attempts: 1

Session details
---------------------------
System Disk = \Device\Harddisk0
Windows directory = C:\WINDOWS
AutoChk Run = 0
Number of root causes = 1

Test Performed:
---------------------------
Name: Check for updates
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: System disk test
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Disk failure diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 15 ms

Test Performed:
---------------------------
Name: Disk metadata test
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Target OS test
Result: Completed successfully. Error code =  0x0
Time taken = 63 ms

Test Performed:
---------------------------
Name: Volume content check
Result: Completed successfully. Error code =  0x0
Time taken = 62 ms

Test Performed:
---------------------------
Name: Boot manager diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: System boot log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Event log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 31 ms

Test Performed:
---------------------------
Name: Internal state check
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Boot status test
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Setup state check
Result: Completed successfully. Error code =  0x0
Time taken = 79 ms

Test Performed:
---------------------------
Name: Registry hives test
Result: Completed successfully. Error code =  0x0
Time taken = 609 ms

Test Performed:
---------------------------
Name: Windows boot log diagnosis
Result: Completed successfully. Error code =  0x0
Time taken = 0 ms

Test Performed:
---------------------------
Name: Bugcheck analysis
Result: Completed successfully. Error code =  0x0
Time taken = 141 ms

Root cause found:
---------------------------
Unknown Bugcheck: Bugcheck 7e. Parameters = 0xffffffffc0000005, 0xfffff8000231d312, 0xffffd00021431528, 0xffffd00021430d30.

Repair action: System Restore
Result: Cancelled

---------------------------
---------------------------

bcdinfo.txt

Code:

Firmware Boot Manager
---------------------
identifier              {fwbootmgr}
displayorder            {bootmgr}
                        {55afe48e-5ae9-11e3-a1b0-d389cc63afae}
                        {55afe48f-5ae9-11e3-a1b0-d389cc63afae}
                        {55afe490-5ae9-11e3-a1b0-d389cc63afae}
timeout                 0

Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=\Device\HarddiskVolume2
path                    \EFI\Microsoft\Boot\bootmgfw.efi
description             Windows Boot Manager
locale                  en-US
inherit                 {globalsettings}
integrityservices       Enable
default                 {default}
resumeobject            {55afe497-5ae9-11e3-a1b0-d389cc63afae}
displayorder            {default}
toolsdisplayorder       {memdiag}
timeout                 30

Firmware Application (101fffff)
-------------------------------
identifier              {55afe48e-5ae9-11e3-a1b0-d389cc63afae}
description             EFI USB Device

Firmware Application (101fffff)
-------------------------------
identifier              {55afe48f-5ae9-11e3-a1b0-d389cc63afae}
description             EFI DVD/CDROM

Firmware Application (101fffff)
-------------------------------
identifier              {55afe490-5ae9-11e3-a1b0-d389cc63afae}
description             EFI Network

Windows Boot Loader
-------------------
identifier              {55afe494-5ae9-11e3-a1b0-d389cc63afae}
device                  ramdisk=[D:]\Recovery\WindowsRE\Winre.wim,{55afe495-5ae9-11e3-a1b0-d389cc63afae}
path                    \windows\system32\winload.efi
description             Windows Recovery Environment
locale                  en-US
inherit                 {bootloadersettings}
displaymessage          Recovery
displaymessageoverride  Recovery
osdevice                ramdisk=[D:]\Recovery\WindowsRE\Winre.wim,{55afe495-5ae9-11e3-a1b0-d389cc63afae}
systemroot              \windows
nx                      OptIn
bootmenupolicy          Standard
winpe                   Yes

Windows Boot Loader
-------------------
identifier              {default}
device                  partition=C:
path                    \WINDOWS\system32\winload.efi
description             Windows 8.1
locale                  en-US
inherit                 {bootloadersettings}
recoverysequence        {current}
integrityservices       Enable
recoveryenabled         Yes
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \WINDOWS
resumeobject            {55afe497-5ae9-11e3-a1b0-d389cc63afae}
nx                      OptIn
bootmenupolicy          Standard

Windows Boot Loader
-------------------
identifier              {current}
device                  ramdisk=[D:]\Recovery\WindowsRE\Winre.wim,{55afe49a-5ae9-11e3-a1b0-d389cc63afae}
path                    \windows\system32\winload.efi
description             Windows Recovery Environment
locale                  en-US
inherit                 {bootloadersettings}
displaymessage          Recovery
osdevice                ramdisk=[D:]\Recovery\WindowsRE\Winre.wim,{55afe49a-5ae9-11e3-a1b0-d389cc63afae}
systemroot              \windows
nx                      OptIn
bootmenupolicy          Standard
winpe                   Yes

Resume from Hibernate
---------------------
identifier              {55afe492-5ae9-11e3-a1b0-d389cc63afae}
device                  partition=C:
path                    \Windows\system32\winresume.efi
description             Windows Resume Application
locale                  en-US
inherit                 {resumeloadersettings}
recoverysequence        {55afe494-5ae9-11e3-a1b0-d389cc63afae}
recoveryenabled         Yes
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
filedevice              partition=C:
filepath                \hiberfil.sys
bootmenupolicy          Standard
debugoptionenabled      No

Resume from Hibernate
---------------------
identifier              {55afe497-5ae9-11e3-a1b0-d389cc63afae}
device                  partition=C:
path                    \WINDOWS\system32\winresume.efi
description             Windows Resume Application
locale                  en-US
inherit                 {resumeloadersettings}
recoverysequence        {current}
recoveryenabled         Yes
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
filedevice              partition=C:
filepath                \hiberfil.sys
bootmenupolicy          Standard
debugoptionenabled      No

Windows Memory Tester
---------------------
identifier              {memdiag}
device                  partition=\Device\HarddiskVolume2
path                    \EFI\Microsoft\Boot\memtest.efi
description             Windows Memory Diagnostic
locale                  en-US
inherit                 {globalsettings}
badmemoryaccess         Yes

EMS Settings
------------
identifier              {emssettings}
bootems                 No

Debugger Settings
-----------------
identifier              {dbgsettings}
debugtype               Serial
debugport               1
baudrate                115200

RAM Defects
-----------
identifier              {badmemory}

Global Settings
---------------
identifier              {globalsettings}
inherit                 {dbgsettings}
                        {emssettings}
                        {badmemory}

Boot Loader Settings
--------------------
identifier              {bootloadersettings}
inherit                 {globalsettings}
                        {hypervisorsettings}

Hypervisor Settings
-------------------
identifier              {hypervisorsettings}
hypervisordebugtype     Serial
hypervisordebugport     1
hypervisorbaudrate      115200

Resume Loader Settings
----------------------
identifier              {resumeloadersettings}
inherit                 {globalsettings}

Device options
--------------
identifier              {55afe495-5ae9-11e3-a1b0-d389cc63afae}
description             Windows Recovery
ramdisksdidevice        partition=D:
ramdisksdipath          \Recovery\WindowsRE\boot.sdi

Device options
--------------
identifier              {55afe496-5ae9-11e3-a1b0-d389cc63afae}
description             Windows Setup
ramdisksdidevice        partition=C:
ramdisksdipath          \$WINDOWS.~BT\Sources\SafeOS\boot.sdi

Device options
--------------
identifier              {55afe49a-5ae9-11e3-a1b0-d389cc63afae}
description             Windows Recovery
ramdisksdidevice        partition=D:
ramdisksdipath          \Recovery\WindowsRE\boot.sdi

 

Just ran a basic windows memory test (2 runs) and it came back clean. Will run an extended test overnight.

 

I have included two minidump files -- I have downloaded the dump reader utility, but now it is complaining about symbols...and as there are like 8 possible choices to choose from, I'm giving up at this point.

Any help finding the culprit would be appreciated -- it almost always happens during wake from sleep.

UploadMB.com
UploadMB.com

Thanks!

 

Looks to be my wireless (Realtek driver issue), due to "Rtwlanu" issues:

Code:

Instant Online Crash Analysis, brought to you by OSR Open Systems Resources, Inc.

Show DivPrimary Analysis

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.16384.amd64fre.winblue_rtm.130821-1623
Machine Name:
Kernel base = 0xfffff803`62a00000 PsLoadedModuleList = 0xfffff803`62cc79b0
Debug session time: Mon Dec  9 19:20:14.861 2013 (UTC - 5:00)
System Uptime: 0 days 1:31:49.744
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002890e94, The address that the exception occurred at
Arg3: ffffd00020d94738, Exception Record Address
Arg4: ffffd00020d93f40, Context Record Address

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

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:
rtwlanu+22e94
fffff800`02890e94 80bbc908000000  cmp     byte ptr [rbx+8C9h],0

EXCEPTION_RECORD:  ffffd00020d94738 -- (.exr 0xffffd00020d94738)
ExceptionAddress: fffff80002890e94 (rtwlanu+0x0000000000022e94)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 00000000000008c9
Attempt to read from address 00000000000008c9

CONTEXT:  ffffd00020d93f40 -- (.cxr 0xffffd00020d93f40)
rax=ffffe000016f1550 rbx=0000000000000000 rcx=ffffe00001a00000
rdx=000000000000076e rsi=0000000000000028 rdi=000000000000076e
rip=fffff80002890e94 rsp=ffffd00020d94970 rbp=ffffd00020d94a50
 r8=0000000000000004  r9=00000000000fffff r10=0000000000000005
r11=ffffd00020d94998 r12=0000000000000009 r13=0000000000000000
r14=0000000000000000 r15=0000000000000001
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
rtwlanu+0x22e94:
fffff800`02890e94 80bbc908000000  cmp     byte ptr [rbx+8C9h],0 ds:002b:00000000`000008c9=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  00000000000008c9

READ_ADDRESS: fffff80362cb5360: Unable to get special pool info
fffff80362cb5360: Unable to get special pool info
GetUlongFromAddress: unable to read from fffff80362d50208
 00000000000008c9

FOLLOWUP_IP:
rtwlanu+22e94
fffff800`02890e94 80bbc908000000  cmp     byte ptr [rbx+8C9h],0

BUGCHECK_STR:  AV

LAST_CONTROL_TRANSFER:  from fffff80002a51d40 to fffff80002890e94

STACK_TEXT: 
ffffd000`20d94970 fffff800`02a51d40 : ffffd000`20d94a50 00000000`00000028 ffffe000`05000000 ffffe000`05400000 : rtwlanu+0x22e94
ffffd000`20d94978 ffffd000`20d94a50 : 00000000`00000028 ffffe000`05000000 ffffe000`05400000 fffff800`02991cae : rtwlanu+0x1e3d40
ffffd000`20d94980 00000000`00000028 : ffffe000`05000000 ffffe000`05400000 fffff800`02991cae 00000000`00008401 : 0xffffd000`20d94a50
ffffd000`20d94988 ffffe000`05000000 : ffffe000`05400000 fffff800`02991cae 00000000`00008401 fffff800`02a51d40 : 0x28
ffffd000`20d94990 ffffe000`05400000 : fffff800`02991cae 00000000`00008401 fffff800`02a51d40 00000000`00000004 : 0xffffe000`05000000
ffffd000`20d94998 fffff800`02991cae : 00000000`00008401 fffff800`02a51d40 00000000`00000004 00000000`00000000 : 0xffffe000`05400000
ffffd000`20d949a0 00000000`00008401 : fffff800`02a51d40 00000000`00000004 00000000`00000000 ffffe000`05000000 : rtwlanu+0x123cae
ffffd000`20d949a8 fffff800`02a51d40 : 00000000`00000004 00000000`00000000 ffffe000`05000000 fffff800`02942e6a : 0x8401
ffffd000`20d949b0 00000000`00000004 : 00000000`00000000 ffffe000`05000000 fffff800`02942e6a ffffe000`05000000 : rtwlanu+0x1e3d40
ffffd000`20d949b8 00000000`00000000 : ffffe000`05000000 fffff800`02942e6a ffffe000`05000000 00000000`00000000 : 0x4


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  rtwlanu+22e94

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: rtwlanu

IMAGE_NAME:  rtwlanu.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .cxr 0xffffd00020d93f40 ; kb

FAILURE_BUCKET_ID:  X64_AV_rtwlanu+22e94

BUCKET_ID:  X64_AV_rtwlanu+22e94

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


This free analysis is provided by OSR Open Systems Resources, Inc.
Want a deeper understanding of crash dump analysis? Check out our Windows Kernel Debugging and Crash Dump Analysis Seminar (opens in new tab/window)
Show DivCrash Code Links

Show DivLoaded Module List

Show DivRaw Stack Contents

Show DivDump Header Information

Show DivStrings

Gonna roll back to windows default drivers and see! Wish me luck.

 

Hey Rykoshet,

Just so you're not having a conversation with yourself: Good Luck!!!

I hate it when that happens, but sometimes end up self-resolving.

Rolling back is a good start, system restore too. Backup stuff just in case.

Fingers crossed.

 

Thanks. Sorry about the walls of text, just want to document it in case it happens to anyone else.

What actually ended up solving the issue for me was checking out the C:/Windows/Minidump files online at Instant Online Crash Analysis

They converted it to readable text and offered a basic blurb (ie, your computer is crashing). However, near the bottom of the document I found:

MODULE_NAME: rtwlanu

Someone else had similar issues (BSOD after wake from sleep) and after analyzing their dump file, they found the faulty module (it was driver issue with an XBOX controller). In this case, rtwlanu is Realtek WLan, so I assumed the wireless drivers needed changing -- in either rollback or update direction.

I started with rollback 2 days ago, and numerous wakes from sleep later, nothing! So I'm pretty confident that solved it.

Hope it will be of use to someone else. Cheers.