BSOD - many times in recent months

Hey guys, I was also having the same problem just today. I was watching youtube, fell asleep on my bed, wake up 20 minutes later and my computer was put to sleep. Not sure if the computer got hot during sleep time but it ended up with a blue screen of death.

An attempt was made to write to read only memory blue screen.

I've had bsod's a lot during these past few months and it just happened so suddenly. I don't know how to fix it Happens quite often, it's either a BSOD or my computer COMPLETELY freezes, I don't hear any sound AND I can't even move my mouse, make any keyboard gestures etc. It's just completely frozen, so I don't know what's wrong with my computer I've uninstalled recent programs, basically only have games installed as well as the normal microsoft programs and necessities. Help!

I've been using Ccleaner to remove my registry and clean my computer, so I don't know where the other dumps are, but the BSOD happened again and so I thought of looking it up and asking someone who knows what's going on so hopefully someone can help! Any help would be appreciated!

The computer has rebooted from a bugcheck. The bugcheck was: 0x000000be (0xfffff96000323ad8, 0x8f400001c8ebf021, 0xfffff88009d92610, 0x000000000000000b). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 020214-15490-01.

Hi Simonpoo.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If it does not show any error, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.
_________________________________________________________________________________________

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck BE, {fffff96000323ad8, 8f400001c8ebf021, fffff88009d92610, b}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : win32k.sys ( win32k+18c55d )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory.  The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff96000323ad8, Virtual address for the attempted write.
Arg2: 8f400001c8ebf021, PTE contents.
Arg3: fffff88009d92610, (reserved)
Arg4: 000000000000000b, (reserved)

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xBE

PROCESS_NAME:  Skype.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

TRAP_FRAME:  fffff88009d92610 -- (.trap 0xfffff88009d92610)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff9008a028170 rbx=0000000000000000 rcx=fffff96000323a78
rdx=fffffa800bb176f0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030c3f96 rsp=fffff88009d927a0 rbp=fffffa800bb176f0
 r8=0000000000000000  r9=fffff96000323a78 r10=0000000000003f3c
r11=fffff88009d929f0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di pl zr na po nc
nt!ExpReleaseResourceForThreadLite+0x46:
fffff800`030c3f96 f0480fba696000  lock bts qword ptr [rcx+60h],0 ds:fffff960`00323ad8=0000000000000029
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000314c7c6 to fffff800030cebc0

STACK_TEXT:  
fffff880`09d924a8 fffff800`0314c7c6 : 00000000`000000be fffff960`00323ad8 8f400001`c8ebf021 fffff880`09d92610 : nt!KeBugCheckEx
fffff880`09d924b0 fffff800`030cccee : 00000000`00000001 fffff960`00323ad8 00000000`00000000 fffff960`00323a78 : nt! ?? ::FNODOBFM::`string'+0x44cde
fffff880`09d92610 fffff800`030c3f96 : 00000000`00000001 00000000`00000000 00000000`00003f3c 00000000`00001514 : nt!KiPageFault+0x16e
fffff880`09d927a0 fffff800`030d7d42 : 00000000`00001514 00000000`00000000 00000000`00000bbc 00000000`62051514 : nt!ExpReleaseResourceForThreadLite+0x46
fffff880`09d92800 fffff960`001fc55d : 00000000`00000000 fffffa80`0ad13d80 00000000`00000001 fffff800`030d7a8b : nt!ExReleaseResourceAndLeaveCriticalRegion+0x12
fffff880`09d92830 00000000`00000000 : fffffa80`0ad13d80 00000000`00000001 fffff800`030d7a8b 00000000`000de8b0 : win32k+0x18c55d


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k+18c55d
fffff960`001fc55d ??              ???

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  win32k+18c55d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0xBE_win32k+18c55d

BUCKET_ID:  X64_0xBE_win32k+18c55d

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xbe_win32k+18c55d

FAILURE_ID_HASH:  {84ecbf15-5a22-e55f-80de-ed301cea741a}

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

I'll do this tonight! I'll hopefully get back to you soon, thank you for your reply Arc!


Update:

I've completed the memtest and didn't get an error which is a good sign I assume. I will now try the Driver Verifier! Once I've done this, what does it mean if nothing happens? Is there something wrong with my programs or hardware or something?

Let the Driver Verifier go ... then we will decide the further courses of action seeing the results.

The Driver Verifier makes the system slow and laggy on purpose. And "A device driver attempting to corrupt the system has even caught." --- that is what we need.

Upload the crash dump. Statements will not help you.