Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Crash Analysis and Debugging › Random Bluescreen: Caused by ntoskrnl.exe
New Posts  All Forums:Forum Nav:

Random Bluescreen: Caused by ntoskrnl.exe

post #1 of 7
Thread Starter 
Hey,

Just today my computer suffered a random blue screen while I was away from my computer. After some digging in event logger, and bluescreen view, I've figured out that it was a SYSTEM_SERVICE_EXCEPTION ntoskrnl.exe that caused the BSOD. Can anyone provide me with anymore possible causes, and solutions please?

Event Viewer: The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff880014a9938, 0xfffff8800ccbb600, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 030213-54069-01.




I can provide additional information if you need it to figure out my problem, such as the .dmp file.


Thanks

-Frodo.
Edited by Frodo baggins - 3/2/13 at 1:39am
post #2 of 7
3B... Need some more information, is this PC overclocked?
post #3 of 7
im getting a related problem and would also like to know a solution. i made another post about it earlier. Try running memtest from a usb on your ram. check and make sure all new stuff installed is correct and maybe even use system restore? how long and frequently have you gotten them?
post #4 of 7
any newly installed hardware

I think I've had the same BSOD thrown in the past year and it was comming from a WIFI card.... happened on 3 different rigs with the same card.

Please post your Hardware and how long you've been running this setup with out error...are you Overclocked? and please zip and post the minidmp file here for us to view (and when I say "US" I mean someone smarter than me I've still N00b when it comes to reading dumps, but I try)
LIttle Giant
(14 items)
 
 
Old HP upgraded
(13 items)
 
CPUMotherboardGraphicsGraphics
3570k Asus P8Z77-I Deluxe  AMD Radeon HD Myst 7870 Tahiti Accelero Twin Turbo II 
RAMHard DriveHard DriveMonitor
16GB Corsair 1600  Samsung 840pro Samsung 500 GB 2.5" 7200 HDD Asus VG236h 120hz  
KeyboardPowerCaseMouse
Corsair K90 Corsair 500w Bitfenix Prodigy  Logitech G9x 
Mouse PadAudio
Rocketfish Hard dual sided Creative 2.1 speakers/Razer Megalodon/Charasis  
CPUMotherboardGraphicsRAM
I5 2500k Asus P8Z68-lx XFX 685X Pny 
Hard DriveHard DriveHard DriveOptical Drive
Wd caviar black FAALS Wd caviar blue  Ocz agility 2 Ssd Asus dvd burner 
CoolingOSMonitorKeyboard
Frio Win 7 home premium Hp 2207 Logitech G11 (rev 1) 
PowerCaseMouseMouse Pad
Pc power and colling 775w Antech 900 Logitech G9x Rocketfish 
Audio
Razer megalodon 
CPUMotherboardGraphicsHard Drive
Athlon X2 4800+ ESC Nettle2 Asus 5770 wd Black 
Hard DriveOSMonitorKeyboard
SSD OCZ agility II Win 7 home Premium  Hp w2207 Logitech G11 
PowerCaseMouseMouse Pad
750w PC power and cooling Antec 900 Logitech G9 Rocket fish 
Audio
Razer Megelodon  
  hide details  
Reply
LIttle Giant
(14 items)
 
 
Old HP upgraded
(13 items)
 
CPUMotherboardGraphicsGraphics
3570k Asus P8Z77-I Deluxe  AMD Radeon HD Myst 7870 Tahiti Accelero Twin Turbo II 
RAMHard DriveHard DriveMonitor
16GB Corsair 1600  Samsung 840pro Samsung 500 GB 2.5" 7200 HDD Asus VG236h 120hz  
KeyboardPowerCaseMouse
Corsair K90 Corsair 500w Bitfenix Prodigy  Logitech G9x 
Mouse PadAudio
Rocketfish Hard dual sided Creative 2.1 speakers/Razer Megalodon/Charasis  
CPUMotherboardGraphicsRAM
I5 2500k Asus P8Z68-lx XFX 685X Pny 
Hard DriveHard DriveHard DriveOptical Drive
Wd caviar black FAALS Wd caviar blue  Ocz agility 2 Ssd Asus dvd burner 
CoolingOSMonitorKeyboard
Frio Win 7 home premium Hp 2207 Logitech G11 (rev 1) 
PowerCaseMouseMouse Pad
Pc power and colling 775w Antech 900 Logitech G9x Rocketfish 
Audio
Razer megalodon 
CPUMotherboardGraphicsHard Drive
Athlon X2 4800+ ESC Nettle2 Asus 5770 wd Black 
Hard DriveOSMonitorKeyboard
SSD OCZ agility II Win 7 home Premium  Hp w2207 Logitech G11 
PowerCaseMouseMouse Pad
750w PC power and cooling Antec 900 Logitech G9 Rocket fish 
Audio
Razer Megelodon  
  hide details  
Reply
post #5 of 7
Thread Starter 
Hey

Thanks for the replies. No, I have not applied any overclocks to my hardware, but I used to be overclocked a while back. I undid it though. I havn't installed any new hardware either, so it can't be that.

Specs:
Core i5 3.3 GHz
GTS 450 SuperClocked (Factory overclock)
16gb ram
520w PSU.

I have attacked my dmp file

Thanks

-Frodo. 030213-54069-01.zip 38k .zip file
post #6 of 7
Hi.

The last BSOD was caused by Symantec, please remove it using its removal tool from here: http://kb.eset.com/esetkb/index?page=content&id=SOLN146

Make sure Windows Defender and Windows Firewall are enabled.
http://windows.microsoft.com/en-us/windows-8/windows-defender#1TC=t1

Dump output:
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff880014a9938, fffff8800ccbb600, 0}

*** WARNING: Unable to verify timestamp for SYMDS64.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMDS64.SYS
Probably caused by : SYMDS64.SYS ( SYMDS64+5938 )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffff880014a9938, Address of the instruction which caused the bugcheck
Arg3: fffff8800ccbb600, 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: 
SYMDS64+5938
fffff880`014a9938 f6402804        test    byte ptr [rax+28h],4

CONTEXT:  fffff8800ccbb600 -- (.cxr 0xfffff8800ccbb600)
rax=0008000000000000 rbx=fffff8a00382d018 rcx=fffff8a03e1845f8
rdx=00000000ffffffff rsi=fffff8a03e7f6bf0 rdi=0000000000000000
rip=fffff880014a9938 rsp=fffff8800ccbc008 rbp=0000000000000002
 r8=fffff8a00382d130  r9=fffff780000003b0 r10=fffff78000000008
r11=fffff8a00382d130 r12=0000000000000000 r13=0000000000000001
r14=fffff8a00382c788 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
SYMDS64+0x5938:
fffff880`014a9938 f6402804        test    byte ptr [rax+28h],4 ds:002b:00080000`00000028=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  ccsvchst.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff880014a9bb2 to fffff880014a9938

STACK_TEXT:  
fffff880`0ccbc008 fffff880`014a9bb2 : fffff8a0`0382d018 00000000`00000001 fffff8a0`3e7f6be8 00000000`00000053 : SYMDS64+0x5938
fffff880`0ccbc010 fffff8a0`0382d018 : 00000000`00000001 fffff8a0`3e7f6be8 00000000`00000053 00000000`00000001 : SYMDS64+0x5bb2
fffff880`0ccbc018 00000000`00000001 : fffff8a0`3e7f6be8 00000000`00000053 00000000`00000001 fffff880`014adfbf : 0xfffff8a0`0382d018
fffff880`0ccbc020 fffff8a0`3e7f6be8 : 00000000`00000053 00000000`00000001 fffff880`014adfbf fffff8a0`3561c2a8 : 0x1
fffff880`0ccbc028 00000000`00000053 : 00000000`00000001 fffff880`014adfbf fffff8a0`3561c2a8 00000000`00000000 : 0xfffff8a0`3e7f6be8
fffff880`0ccbc030 00000000`00000001 : fffff880`014adfbf fffff8a0`3561c2a8 00000000`00000000 00000000`0000001c : 0x53
fffff880`0ccbc038 fffff880`014adfbf : fffff8a0`3561c2a8 00000000`00000000 00000000`0000001c 00000000`00000008 : 0x1
fffff880`0ccbc040 fffff8a0`3561c2a8 : 00000000`00000000 00000000`0000001c 00000000`00000008 fffff8a0`3e7f6b38 : SYMDS64+0x9fbf
fffff880`0ccbc048 00000000`00000000 : 00000000`0000001c 00000000`00000008 fffff8a0`3e7f6b38 fffff880`014b528f : 0xfffff8a0`3561c2a8


FOLLOWUP_IP: 
SYMDS64+5938
fffff880`014a9938 f6402804        test    byte ptr [rax+28h],4

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  SYMDS64+5938

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: SYMDS64

IMAGE_NAME:  SYMDS64.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  50f75a5d

STACK_COMMAND:  .cxr 0xfffff8800ccbb600 ; kb

FAILURE_BUCKET_ID:  0x3B_SYMDS64+5938

BUCKET_ID:  0x3B_SYMDS64+5938

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

1: kd> lmvm SYMDS64
start             end                 module name
fffff880`014a4000 fffff880`01522000   SYMDS64  T (no symbols)           
    Loaded symbol image file: SYMDS64.SYS
    Image path: \SystemRoot\system32\drivers\NISx64\1403000.024\SYMDS64.SYS
    Image name: SYMDS64.SYS
    Timestamp:        Thu Jan 17 07:56:45 2013 (50F75A5D)
    CheckSum:         0008361A
    ImageSize:        0007E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Edited by koolkat77 - 3/14/13 at 7:05am
post #7 of 7
Quote:
Originally Posted by Frodo baggins View Post

Hey

Thanks for the replies. No, I have not applied any overclocks to my hardware, but I used to be overclocked a while back. I undid it though. I havn't installed any new hardware either, so it can't be that.

Specs:
Core i5 3.3 GHz
GTS 450 SuperClocked (Factory overclock)
16gb ram
520w PSU.

I have attacked my dmp file

Thanks

-Frodo. 030213-54069-01.zip 38k .zip file

Yeah I would put my money on failing memory, run a memtest or if you're on Windows 7 click on start and type MEM in the search and you'll see Windows Memory Diagnostic. Or just run %windir%\system32\MdSched.exe See if it throws any errors.

Then again.. this only happened once right? So, I wouldn't be too worried about it.
Edited by freakb18c1 - 3/14/13 at 10:10am
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Crash Analysis and Debugging
Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Crash Analysis and Debugging › Random Bluescreen: Caused by ntoskrnl.exe