BSOD Many Errors. One of them: 0x0000001E. While Playing Rune.Priv.Ser

[moonglare]

This has happened to me while playing BF3 also. I don't know why. Here are the files.

 

[moonglare]

Pleassse help this problem persists and is really aggravating!

 

[writhziden]

[list=1]
[*]
Loading Dump File [C:\Users\Mike\Documents\Kingston\BSODDmpFiles\moonglare\021512-20560-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0320f000 PsLoadedModuleList = 0xfffff800`03454670
Debug session time: Wed Feb 15 16:36:56.243 2012 (GMT-7)
System Uptime: 0 days 0:14:23.772
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff800032aad08, 0, ffffffffffffffff}

Probably caused by : memory_corruption ( nt!MiCompleteProtoPteFault+188 )

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

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffff800032aad08, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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


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

FAULTING_IP: 
nt!MiCompleteProtoPteFault+188
fffff800`032aad08 8b5004          mov     edx,dword ptr [rax+4]

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034be100
 ffffffffffffffff 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  javaw.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800032d7588 to fffff8000328bc40

STACK_TEXT:  
fffff880`0c403de8 fffff800`032d7588 : 00000000`0000001e ffffffff`c0000005 fffff800`032aad08 00000000`00000000 : nt!KeBugCheckEx
fffff880`0c403df0 fffff800`0328b2c2 : fffff880`0c4045c8 00000000`00000000 fffff880`0c404670 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4977d
fffff880`0c404490 fffff800`03289bca : fffff880`0c404a0c fffff880`06d7e1ef 00000000`00000000 00000000`00000001 : nt!KiExceptionDispatch+0xc2
fffff880`0c404670 fffff800`032aad08 : 00000000`00000003 fffff880`06a2e333 fffffa80`095bc000 fffff880`0c404918 : nt!KiGeneralProtectionFault+0x10a
fffff880`0c404800 fffff800`032bcfaf : 80000001`65595820 80000001`65595121 fffffa80`04300bf0 fffffa80`06beeec8 : nt!MiCompleteProtoPteFault+0x188
fffff880`0c404890 fffff800`032aa695 : 00000000`00000000 80000001`65595820 fffff880`0c4043d0 fffffa80`06beeec8 : nt!MiResolveTransitionFault+0x32f
fffff880`0c404920 fffff800`032a9053 : 00000000`0019023d 000007fe`ee032f2c fffff683`ff770190 fffffa80`06beeec8 : nt!MiResolveProtoPteFault+0x325
fffff880`0c4049b0 fffff800`03298f19 : 00000000`00000000 000007fe`ee032f2c 00000000`00000000 00000000`00000000 : nt!MiDispatchFault+0x1c3
fffff880`0c404ac0 fffff800`03289d6e : 00000000`00000000 000007fe`ee032f2c fffff880`0c404b01 00000000`00005b29 : nt!MmAccessFault+0x359
fffff880`0c404c20 00000000`77a29c12 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0d54e040 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77a29c12


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiCompleteProtoPteFault+188
fffff800`032aad08 8b5004          mov     edx,dword ptr [rax+4]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!MiCompleteProtoPteFault+188

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x1E_nt!MiCompleteProtoPteFault+188

BUCKET_ID:  X64_0x1E_nt!MiCompleteProtoPteFault+188

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

[/list]

1. Possible causes are Memory problems... Viruses... Corrupted hard disk file system... Corrupted System Files... Lack of Windows updates... Drivers...
   Thanks to JMH for helping with my understanding of this crash.
2. Possible causes are Memory problems... Corrupted hard disk file system... Drivers... corrupted SCSI or IDE Drivers...

Thanks to Dave76 for help understanding possible causes.



We will start with the common problems first (see bold possible causes). Do the following steps and test after each to see if stability increases (the memory tests you can run concurrently as they will not increase stability unless you are forced to move modules around). Post back your results after each step, and if you get a blue screen crash, upload the files again and await further instructions after we are able to analyze the crash.

• If you are overclocking any hardware, please stop.
  
  
  
• Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html
  
  
  
• Please remove Gigabyte Easy Saver as one of the drivers is outdated and the program is known to cause crashes on some systems. Also, remove EasyTune6 as it also can cause crashes.
  
  
  
• Please remove Daemon Tools, as it uses a driver called dtsoftbus01.sys that is known to cause BSODs.
  
  I prefer TotalMounter as my CD/DVD virtualization software as it allows me to burn images to a virtual CD/DVD if I just want an ISO file instead of a disc, and it is free.
  
  Many use MagicISO - Convert BIN to ISO, Create, Edit, Burn, Extract ISO file, ISO/BIN converter/extractor/editor as well, which is also free.
  
  
  
• Re-install your java software.
  
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  If you swap any memory components, follow these steps for ESD safety:
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
  Once these steps have been followed, it is safe to remove and replace components within your computer.

Also, please follow the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html so we have more information about your system to provide better troubleshooting steps.