Blue screen of death

[xcyper33]

I've gotten a BSOD 2nd time within a week. This has never happened before, here is the code and dmp file.


Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: 1e
BCP1: FFFFFFFFC0000005
BCP2: 0000000000000000
BCP3: 0000000000000008
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1


EDIT: SO YEAH, this forum is not letting me do rar attachments anymore yay.

[rokclimb15]

How are your temps looking? Have you run memtest? I would also run mfr diagnostics on your OS drive. Seagate has Seatools and WD has Datalifeguard Tools. A basic test should be enough.

[xcyper33]

(10-10-2013, 12:57 AM)rokclimb15 Wrote: How are your temps looking? Have you run memtest? I would also run mfr diagnostics on your OS drive. Seagate has Seatools and WD has Datalifeguard Tools. A basic test should be enough.

My tempts are fine at MAX I'm at 66-67C. I have an update: I ran WhoCrashed and the software did a diagnostic on the DMP file that recorded the 2 BSODs that I had while playing Dolphin. Here is what it said:

Crash Dump Analysis


[color=#000000]Crash dump
directory: C:\Windows\Minidump[/color]
[color=#000000][/color]
[color=#000000]Crash dumps are enabled on your
computer.
[/color]
[color=#000000]On
Wed 10/9/2013 2:24:48 PM GMT your computer crashed
crash dump file:
C:\Windows\Minidump\100913-25272-01.dmp
This was probably caused by the
following module: [color=#000000]ntoskrnl.exe[/color] (nt+0x75C00)
Bugcheck code: 0x1E
(0xFFFFFFFFC0000005, 0x0, 0x8, 0x0)
Error: [color=#000000]KMODE_EXCEPTION_NOT_HANDLED[/color]
file path:
C:\Windows\system32\ntoskrnl.exe
product: [color=#000000]Microsoft® Windows® Operating System[/color]
company: [color=#000000]Microsoft Corporation[/color]
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.



[/color]
[color=#000000]On
Wed 10/9/2013 2:24:48 PM GMT your computer crashed
crash dump file:
C:\Windows\memory.dmp
This was probably caused by the following module: [color=#000000]ntkrnlmp.exe[/color] (nt!KeBugCheckEx+0x0)
Bugcheck code:
0x1E (0xFFFFFFFFC0000005, 0x0, 0x8, 0x0)
Error: [color=#000000]KMODE_EXCEPTION_NOT_HANDLED[/color]
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.


[/color]
[color=#000000]On Sat 10/5/2013 10:38:01 PM GMT your computer
crashed
crash dump file: C:\Windows\Minidump\100513-24008-01.dmp
This
was probably caused by the following module: [color=#000000]ntoskrnl.exe[/color] (nt+0x75C00)
Bugcheck code: 0x1E
(0xFFFFFFFFC0000005, 0x0, 0x8, 0x0)
Error: [color=#000000]KMODE_EXCEPTION_NOT_HANDLED[/color]
file path:
C:\Windows\system32\ntoskrnl.exe
product: [color=#000000]Microsoft® Windows® Operating System[/color]
company: [color=#000000]Microsoft Corporation[/color]
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.
[/color]

[rokclimb15]

Check your disk first, then your RAM.

[haddockd]

Are you overclocking? Go back to default settings and timings and see if the crash happens. Code 1E can mean you dont have enough voltage going to the CPU. If you arent overclocking then ignore this