BSOD on boot, SYSTEM_SERVICE_EXCEPTION, safe mode works

none

New Member
Messages
2
Dear all,

I am having a recurring SYSTEM_SERVICE_EXCEPTION on boot in Windows 8.1. I have a Lenovo y50 (the one with the SSD). I can boot into safemode.

The only way I can get my computer running is through System Restoring. This problem does not happen on every reboot. It also doesn't happen everytime I switch from using my Linux Boot manager to my Windows one. I have attached my dump files, and will provide anymore information you guys can think of. Is there a way to read the dump files with an installed windows program? I'm curious about what's going on.

It also does not necessarily happen after a Windows update.

Since it makes me system restore to use my computer, I hope the dump files are still relevant to the crashes rather than having been overwritten some how.

Thanks
 

My Computer

System One

  • OS
    Windows 8.1
Do you happen to have an AMD GPU with the latest 14.9 driver version? If so, please try using a different version since that one is known to cause problems.
 

My Computer

System One

  • OS
    Windows 10 Pro x64
    Computer type
    PC/Desktop
    CPU
    INTEL Core i7-2700K 3.5GHz
    Motherboard
    ASROCK Fatal1ty P67 Main Board
    Memory
    HyperX Blu 8GB (2 x 4GB) DDR3 1600
    Graphics Card(s)
    Gigabyte GTX 980 Ti G1 Gaming
    Sound Card
    On-board
    Monitor(s) Displays
    Philips Brilliance BDM4065UC
    Screen Resolution
    3840x2160
    Hard Drives
    SSD: Samsung EVO 250 GB
    Internal HDD: WD Black 1TB
    External: 2x2TB MyBook drives
    1x4TB MyBook
    1x1TB Seagate Freeagent drive
    PSU
    Corsair GS 700W
    Case
    Silverstone Kublai KL04
    Cooling
    Artic Cooling Freezer Pro
    Keyboard
    Logitech G710+
    Mouse
    Razer Mamba Elite 2012
    Internet Speed
    10/0.75
    Browser
    FF 39.0.3, Microsoft Edge, Chrome 44
    Antivirus
    Avast 10.0
I have a nVidia GTX 860m with the newest driver. Anyone have any other ideas? This only happens sometimes on boot and not during games or anything that might queue what the problem is.

Could someone tell me how to read the dump files? If it's relevant, I also dual boot with Arch Linux. I might have messed up the extra partition that Windows sneaks on at some point. But I have the two separate Linux and Windows Boot loaders.
 

My Computer

System One

  • OS
    Windows 8.1
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: 0000000000000000, Address of the instruction which caused the bugcheck
Arg3: ffffd00079d45760, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


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

FAULTING_IP: 
+6381163feae7
00000000`00000000 ??              ???

CONTEXT:  ffffd00079d45760 -- (.cxr 0xffffd00079d45760;r)
rax=ffffe000cf2a0000 rbx=0000000000000000 rcx=ffffc000e1904900
rdx=0000000000000001 rsi=ffffe000d09a5c90 rdi=0000000000000000
rip=0000000000000000 rsp=ffffd00079d46198 rbp=ffffd00079d46260
 r8=ffffd00079d46238  r9=ffffe000d09a5c90 r10=000000000000a230
r11=0000000000000801 r12=ffffc000e1904900 r13=0000000000000001
r14=ffffe000d0f46540 r15=ffffe000cf2ea000
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
00000000`00000000 ??              ???
Last set context:
rax=ffffe000cf2a0000 rbx=0000000000000000 rcx=ffffc000e1904900
rdx=0000000000000001 rsi=ffffe000d09a5c90 rdi=0000000000000000
rip=0000000000000000 rsp=ffffd00079d46198 rbp=ffffd00079d46260
 r8=ffffd00079d46238  r9=ffffe000d09a5c90 r10=000000000000a230
r11=0000000000000801 r12=ffffc000e1904900 r13=0000000000000001
r14=ffffe000d0f46540 r15=ffffe000cf2ea000
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
00000000`00000000 ??              ???
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

LAST_CONTROL_TRANSFER:  from fffff801bb1c944e to 0000000000000000

STACK_TEXT:  
ffffd000`79d46198 fffff801`bb1c944e : ffffd000`75080000 00000000`00000801 00000000`00000000 fffff800`962df908 : 0x0
ffffd000`79d461a0 ffffd000`75080000 : 00000000`00000801 00000000`00000000 fffff800`962df908 ffffc000`e1904900 : RiftEnabler+0x744e
ffffd000`79d461a8 00000000`00000801 : 00000000`00000000 fffff800`962df908 ffffc000`e1904900 00000000`00000001 : 0xffffd000`75080000
ffffd000`79d461b0 00000000`00000000 : fffff800`962df908 ffffc000`e1904900 00000000`00000001 00000000`c0000016 : 0x801


FOLLOWUP_IP: 
RiftEnabler+744e
fffff801`bb1c944e ??              ???

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  RiftEnabler+744e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: RiftEnabler

IMAGE_NAME:  [COLOR=#b22222]RiftEnabler.sys[/COLOR]

DEBUG_FLR_IMAGE_TIMESTAMP:  53f8b74a

STACK_COMMAND:  .cxr 0xffffd00079d45760 ; kb

FAILURE_BUCKET_ID:  0x3B_RiftEnabler+744e

BUCKET_ID:  0x3B_RiftEnabler+744e

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x3b_riftenabler+744e

FAILURE_ID_HASH:  {11c9b631-5030-c063-12a5-32657de52fe2}

Followup: MachineOwner
---------
The cause appears to be the core rift driver. Please follow the instructions posted on this link: https://developer.oculusvr.com/forums/viewtopic.php?f=34&t=12805
Disable switchable graphics in bios.
 

My Computer

System One

  • OS
    Windows 10 Pro x64
    Computer type
    PC/Desktop
    CPU
    INTEL Core i7-2700K 3.5GHz
    Motherboard
    ASROCK Fatal1ty P67 Main Board
    Memory
    HyperX Blu 8GB (2 x 4GB) DDR3 1600
    Graphics Card(s)
    Gigabyte GTX 980 Ti G1 Gaming
    Sound Card
    On-board
    Monitor(s) Displays
    Philips Brilliance BDM4065UC
    Screen Resolution
    3840x2160
    Hard Drives
    SSD: Samsung EVO 250 GB
    Internal HDD: WD Black 1TB
    External: 2x2TB MyBook drives
    1x4TB MyBook
    1x1TB Seagate Freeagent drive
    PSU
    Corsair GS 700W
    Case
    Silverstone Kublai KL04
    Cooling
    Artic Cooling Freezer Pro
    Keyboard
    Logitech G710+
    Mouse
    Razer Mamba Elite 2012
    Internet Speed
    10/0.75
    Browser
    FF 39.0.3, Microsoft Edge, Chrome 44
    Antivirus
    Avast 10.0
Back
Top