Blue Screen Of Death

[Tym]

Hi folks, trying to work out what is up with my rig, randomly got Blue Screen of Death twice today, although no error code, and I'm trying to work out what is up with my PC, any ideas how I can find out? Been monitoring my GPU and CPU and they've only been hitting 80c under full load.

Any thoughts ?

[oTurtlez]

Hi folks, trying to work out what is up with my rig, randomly got Blue Screen of Death twice today, although no error code, and I'm trying to work out what is up with my PC, any ideas how I can find out? Been monitoring my GPU and CPU and they've only been hitting 80c under full load.

Any thoughts ?

(Attachment Link)

Overclocked?

[kenmai9]

Are you overclocked? If you are, check your Events Manager or whatever, and look for a WHEA 19 Warning/Error. This could be a cause for your BSOD.. but I guess we just need more info to help!

[Tym]

Not overclocked.

[Tym]

Are you overclocked? If you are, check your Events Manager or whatever, and look for a WHEA 19 Warning/Error. This could be a cause for your BSOD.. but I guess we just need more info to help!

Wheres that sorry? Never had to do this before.

[vun]

Use Windbg to check your minidump files?

[naokira]

This can mean a lot of things. are you using an ssd?

[Tym]

This can mean a lot of things. are you using an ssd?

No ssd

[kenmai9]

Are you overclocked? If you are, check your Events Manager or whatever, and look for a WHEA 19 Warning/Error. This could be a cause for your BSOD.. but I guess we just need more info to help!

Wheres that sorry? Never had to do this before.

If you aren't overclocked, what I told you won't matter. But to open the Event Viewer just press Win, then type event.
What processor/GPU do you use? I think 80 for processor is really hot, depending on what you have. Check if its exceeding the temperature limit.

[oTurtlez]

Hmmm... Install anything new recently, hardware or software?

[oTurtlez]

Are you overclocked? If you are, check your Events Manager or whatever, and look for a WHEA 19 Warning/Error. This could be a cause for your BSOD.. but I guess we just need more info to help!

Wheres that sorry? Never had to do this before.

If you aren't overclocked, what I told you won't matter. But to open the Event Viewer just press Win, then type event.
What processor/GPU do you use? I think 80 for processor is really hot, depending on what you have. Check if its exceeding the temperature limit.

Temp limit regardless is 100c. 80 under load is hot but nothing to be too stressed about.

[Tym]

Are you overclocked? If you are, check your Events Manager or whatever, and look for a WHEA 19 Warning/Error. This could be a cause for your BSOD.. but I guess we just need more info to help!

Wheres that sorry? Never had to do this before.

If you aren't overclocked, what I told you won't matter. But to open the Event Viewer just press Win, then type event.
What processor/GPU do you use? I think 80 for processor is really hot, depending on what you have. Check if its exceeding the temperature limit.

i5 2500k, it wasn't getting that hot even, i checked and its still within the safe boundaries.

[Tym]

Hmmm... Install anything new recently, hardware or software?

No new hardware, ill check the software but I don't think it was too much.

[nubbinator]

Run Memory Diagnostic and make sure that it's not your RAM throwing errors.  Also make sure everything is properly seated.

You can also look at the dump files to get a better idea of what happened.

[oTurtlez]

Are you overclocked? If you are, check your Events Manager or whatever, and look for a WHEA 19 Warning/Error. This could be a cause for your BSOD.. but I guess we just need more info to help!

Wheres that sorry? Never had to do this before.

If you aren't overclocked, what I told you won't matter. But to open the Event Viewer just press Win, then type event.
What processor/GPU do you use? I think 80 for processor is really hot, depending on what you have. Check if its exceeding the temperature limit.

i5 2500k, it wasn't getting that hot even, i checked and its still within the safe boundaries.

You must be running a stock cooler on your 2500k in a low ventilated case. I get 65c max temps on my 2500k @ 4.5GHz with a CM Hyper 212+. Check software installs, do an MBAM sweep and see if you've got anything nasty.

[naokira]

How about updating your drivers. BSOD can come from so many things, even just your sata cable.

[wiredPANDA]

Start > Run
Type "eventvwr"
Click on "Windows Logs"
Review the (1) "Application" and (2) "System" logs

Those will probably give you best information if anything was captured before the BSOD.

And like kenmai9, said, more information would help.  What were you doing when the system errored?  At startup?  While running specific application(s)?  After running for "x" amount of time?  Did you just install any new software/hardware/drivers?

Additionally, if you need to test hardware, you can use MemTest86+, Drive Fitness Test, etc...

[jwaz]

Memory test it:
http://www.memtest.org/

[wiredPANDA]

And you should be able to find the minidump files here:  C:\Windows\Minidump

[Tym]

dump file

http://www.mediafire.com/download/k33uskz62jw5phc/072313-17097-01.dmp

[SpAmRaY]

Do you have any spare parts to test with? for example, swap video card, remove some ram, try different (inset part name here) etc.

[oTurtlez]

Code: [Select]

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 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Machine Name:
Kernel base = 0xfffff800`02c58000 PsLoadedModuleList = 0xfffff800`02e9b670
Debug session time: Tue Jul 23 14:46:30.809 2013 (UTC - 4:00)
System Uptime: 0 days 3:28:57.011
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002c5f1d4, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 000007ffffff0000, Parameter 1 of the exception

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:
nt! ?? ::FNODOBFM::`string'+c071
fffff800`02c5f1d4 8a01            mov     al,byte ptr [rcx]

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  000007ffffff0000

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f05100
GetUlongFromAddress: unable to read from fffff80002f051c0
 000007ffffff0000 Nonpaged pool

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

BUGCHECK_STR:  0x1e_c0000005

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  withSIX-Play.e

CURRENT_IRQL:  1

TRAP_FRAME:  fffff88005951d40 -- (.trap 0xfffff88005951d40)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000007ffffff0000 rbx=0000000000000000 rcx=000007ffffff0000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c5f1d4 rsp=fffff88005951ed0 rbp=000000007549ae60
 r8=0000000000000000  r9=00000000754d3528 r10=fffff88005952a68
r11=0000000075480000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt! ?? ::FNODOBFM::`string'+0xc071:
fffff800`02c5f1d4 8a01            mov     al,byte ptr [rcx] ds:000007ff`ffff0000=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002d18728 to fffff80002ccdc00

CONTEXT:  000464d5840fff3a -- (.cxr 0x464d5840fff3a)
Unable to read context, Win32 error 0n30

STACK_TEXT: 
fffff880`059514b8 fffff800`02d18728 : 00000000`0000001e ffffffff`c0000005 fffff800`02c5f1d4 00000000`00000000 : nt!KeBugCheckEx
fffff880`059514c0 fffff800`02ccd282 : fffff880`05951c98 fffff880`05951ff0 fffff880`05951d40 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x487ed
fffff880`05951b60 fffff800`02ccbdfa : 00000000`00000000 000007ff`ffff0000 fffff880`05951d00 fffff880`05951ff0 : nt!KiExceptionDispatch+0xc2
fffff880`05951d40 fffff800`02c5f1d4 : 00000000`00004204 00000000`00210206 fffff880`05951ef0 00000000`00000018 : nt!KiPageFault+0x23a
fffff880`05951ed0 fffff800`02fc04bd : fffff880`00000000 00000000`75480000 fffff880`00000000 fffff880`00000000 : nt! ?? ::FNODOBFM::`string'+0xc071
fffff880`05951f60 fffff800`02cbf141 : 00000000`00000000 fffff880`059ecd30 13850a0a`00000003 fffff880`05953000 : nt!PspGetSetContextInternal+0x265
fffff880`05952500 fffff800`02cc0617 : 00000000`00000000 00000000`00000000 17090808`005a0a09 00100005`08000095 : nt!PspGetSetContextSpecialApc+0xa1
fffff880`05952610 fffff800`02cc381d : fffffa80`0770b060 00000000`00000000 00000000`00000000 fffffa80`0770b060 : nt!KiDeliverApc+0x1c7
fffff880`05952690 fffff800`02cd498f : fffffa80`0770b168 fffff800`02cc3612 00000000`00000000 fffffa80`0770b060 : nt!KiCommitThreadWait+0x3dd
fffff880`05952720 fffff800`02cbf9d4 : fffff880`05952700 fffff800`00000005 fffff880`05952900 00000000`00000000 : nt!KeWaitForSingleObject+0x19f
fffff880`059527c0 fffff800`02cc0651 : fffffa80`0770b060 fffffa80`0770b0b0 00000000`00000001 fffff800`00000000 : nt!KiSuspendThread+0x54
fffff880`05952800 fffff800`02cc08c7 : 00000000`00000000 00000000`00000000 fffff800`02cbf980 00000000`00000000 : nt!KiDeliverApc+0x201
fffff880`05952880 fffff880`03fcd749 : 00000000`00001794 00000000`75472450 00000000`00000000 00000000`75472450 : nt!KiApcInterrupt+0xd7
fffff880`05952a10 00000000`00001794 : 00000000`75472450 00000000`00000000 00000000`75472450 00000000`7549b1c8 : SbieDrv+0xe749
fffff880`05952a18 00000000`75472450 : 00000000`00000000 00000000`75472450 00000000`7549b1c8 00000000`00000020 : 0x1794
fffff880`05952a20 00000000`00000000 : 00000000`75472450 00000000`7549b1c8 00000000`00000020 00000000`00000000 : 0x75472450


FOLLOWUP_IP:
SbieDrv+e749
fffff880`03fcd749 ??              ???

SYMBOL_STACK_INDEX:  d

SYMBOL_NAME:  SbieDrv+e749

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: SbieDrv

IMAGE_NAME:  SbieDrv.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c305969

STACK_COMMAND:  .cxr 0x464d5840fff3a ; kb

FAILURE_BUCKET_ID:  X64_0x1e_c0000005_SbieDrv+e749

BUCKET_ID:  X64_0x1e_c0000005_SbieDrv+e749

Followup: MachineOwner
---------
There's the analyzed dump.

[Tym]

Don't have any spare parts unfortunately, trying to live on a budget.

[Yzeets]

it looks like a memory or driver error, if it's happened more than once just try 1 stick of memory at a time if you have multiple, I've seen this be driver error more than anything. You're sure you haven't installed any new drivers? or windows auto update?
Were you watching a video or anything or just random? Looks like it might be a problem with Sandboxie, see if you have a old version

[Leslieann]

Look up Bluescreen View or Whocrashed.
Either will analyze the log files and tell you in English what files caused the crash. From there you can look up what the file belongs to and figure out the crash.

[Michael]

[Photoelectric]

BlueScreenView can be not specific enough, sadly.  Still a good first step.  But I'd definitely try to bring everything to stock, think about any recent changes, make sure your drivers are all up to date, then go with the minimum of components and test every one (MemTest86 in DOS or better MemTest in Windows (different program), Prime95 stress tests, disk diagnostic (ATTO Benchmark for SSDs and HD Tune free for HDDs), making sure everything is plugged in correctly).

When does the computer crash?  Are you playing a game?  Doing something specific both times?

[rowdy]

Show Image

And I'm quite pleased about it!

[Leslieann]

BlueScreenView can be not specific enough, sadly. 

Depends, between Whocrashed and Bluescreenview, I get results about 90% of the time.

[smknjoe]

1. BIOS stock as possible.
2. Hardware - Test RAM and HD (Ultimate Boot CD) and Power supply (including juice from the wall if you still have problems)
3. Boot in Safe mode (with networking.) If it runs okay in safe mode then it's likely a software issue.

[Tym]

Thank you very much for everyone's help so far, I have set up windows driver verify'er. So hopefully I should find out the direct problem soon. I have deleted alot of ****, but can't find any software which correlates to the problem starting. Anyhow, thank you all!

[smknjoe]

Whenever troubleshooting always do the hardware tests first. It only takes about 15 minutes and then you can move on to troubleshooting software which can take much longer.

[Tym]

According to the 2 tools leslieann suggested it is not a hardware problem, they both agreed it was a software driver issue.

[smknjoe]

Missed that. Good show, carry on...

I will add that it's ideal to run HW diagnostics from a CD or Flash drive and not from the OS in order to get the most accurate results, but anything is better than nothing. I use UBCD, but there are many others out there that are just as good.

[Photoelectric]

I don't think you mentioned what the computer was doing when it crashed(?)  That could be relevant.

When does the computer crash?  Are you playing a game?  Doing something specific both times?

[SidusNare]

I am jsut repeating what others have said, but definitely test the memory. This is the best program to do it with: http://www.memtest.org/ just write it to a floppy or CD.
It is not based on Windows, DOS, or Linux, it is its own lightweight assembler program that loads directly.

In my long experience with desktop troubleshooting, random BSOD has most often been memory, followed closely by corrupt OS files (typically caused by bad HDD and / or bad RAM).

[Photoelectric]

This is as more stressful memory- and overall stability test compared to the standard MemTest86.
http://hcidesign.com/memtest/

This MemTest runs within Windows on all available memory.  It needs to run for many hours, but it's a great test and is preferred by people who overclock their memory by tweaking timings in small increments.

[smknjoe]

...but you really shouldn't run diagnostics from Windows. If there is a problem with the HD or the file system it could give inaccurate results.

http://www.ultimatebootcd.com/


and see below. SidusNare is correct. Memtest is the standard anyway. Check out the link I provided. It has all of the basic tools you need including Memtest.

[SidusNare]

This MemTest runs within Windows on all available memory.

If it runs within windows, it cant test the memory windows itself is using...
This http://www.memtest86.com/#algo talks about the algorithm used by MemTest86.

[Tym]

I don't think you mentioned what the computer was doing when it crashed(?)  That could be relevant.

When does the computer crash?  Are you playing a game?  Doing something specific both times?

Doing nothing particuly both times, just general internet surfing, i remember precisely I was about to (but hadn't yet) loaded up a game, the 2nd time and the first time wasn't doing anything really.

[SpAmRaY]

I don't think you mentioned what the computer was doing when it crashed(?)  That could be relevant.

When does the computer crash?  Are you playing a game?  Doing something specific both times?

Doing nothing particuly both times, just general internet surfing, i remember precisely I was about to (but hadn't yet) loaded up a game, the 2nd time and the first time wasn't doing anything really.

He was looking at pics and his graphics driver couldn't handle the load!

Driver issues are the worst!

[Yzeets]

Have you uninstalled Sandboxie? This happens a lot when you install something with Sandboxie and Windows is trying to open a file within the sandbox and you have process isolation or just a faulty version of Sandboxie, It's the whole reason I stopped using it. Also make sure you don't install the newest windows platform update because it's terrible and causes BSOD.

[Tym]

Have you uninstalled Sandboxie? This happens a lot when you install something with Sandboxie and Windows is trying to open a file within the sandbox and you have process isolation or just a faulty version of Sandboxie, It's the whole reason I stopped using it. Also make sure you don't install the newest windows platform update because it's terrible and causes BSOD.

Sandboxie has since gone, wasn't using it anyhow. What do you mean by this ?

Also make sure you don't install the newest windows platform update because it's terrible and causes BSOD.

[Yzeets]

Windows came out with a platform update not to long ago that has caused nothing but problems for people, mostly BSOD I don't recommend anyone installs it

Platform Update for Windows 7 x64-Edition (KB2670838)

[Leslieann]

According to the 2 tools leslieann suggested it is not a hardware problem, they both agreed it was a software driver issue.

What files did it say were the problem?

Just a guess based on experience, but 99.9% of the time I see things like this, it's either Flash or a sound card driver. Occasionally it will be a USB device. Usually, I ask if it was a one time thing, or if it's a common occurrence, if it's a one time thing, I tell them to ignore it. It's not worth the fight to fix it for something that happens only twice a year.

Flash is a poor excuse of a media system, it's a battery hogging, virus infested, poorly coded pile of cr@p, which is why Apple doesn't like it on their systems. Sound cards, often have poorly coded drivers, often which try to directly interface with hardware. Part of Windows XP's whole point was to make the hardware go through a software level to protect against the hardware/software conflicts that caused Win 9X and prior to constantly crash. Sound card makers often bypass this (not sure why they have to when video cards do not, but they do), and often, they do it poorly. When the sound driver crashes, if it's directly connected, it can take down the whole system in a heartbeat.

By interfacing direct, it bypasses Windows IRQ system and sometimes even the motherboards IRQ system. Creative was NOTORIOUS for this years ago, creating all sorts of trouble, the original Live cards were known for it (they still suck in regards to drivers!). Creative used to hard code the IRQ into their cards. A buddy only got his sorted after buying a Creative video card and holding them to their warranty (they blamed his non Creative video card for the problem), which resulted in several, hours long, three way calls with them and Microsoft software engineers to get the issue fixed. Only guy I knew who not only had the direct number to MS software engineers, but was also on a first name basis with several of them.

[Tym]

On Tue 23/07/2013 18:46:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072313-17097-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002C5F1D4, 0x0, 0x7FFFFFF0000)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

[TheQsanity]

Omg. You too! Windows!!!!

[Tym]

Omg. You too! Windows!!!!

Yeah I saw yours too Why windows? Why?

[dorkvader]

hmm, if your stop ox1e (kmode exception not handled) is caused by the ntoskrnl, I would run some memory tests (memtest comes with most linux distributions) and HDD tests (whatever the gnu project renamed palimpsest can run smart self tests if your hdd supports them. otherwise, try to find a decent read/verify test.

at work, I see BSOD's caused by faulty ram, bad processors, corrupted system files, (windows does recommend replacing the faulty driver an the article here: http://support.microsoft.com/kb/275678) bad hdd's, and bad motherboards. It's much easier to figure out what is gone wrong if you have some known good parts available. I'd give you some, if you were willing to pay shipping, but it'd be at least $7 for a trip across the atlantic

[Yzeets]

The worst part is when it says ntoskrnl.exe is causing the BSOD, it's not actually that driver causing the problem(rarely have I seen it ever), When it can't find a driver to pin the crash on it shows ntoskrnl.exe as default, so it could really be anything, Did you try the single sticks of memory yet? and Did you see if you installed the updated I mentioned above?

The dump log shows
withSIX-Play.e and Sandboxie in the stacktext