Random BSOD's again, this time instantly when I started Skyrim.

ePeen said:

Don't know. They provide a USB key installer that does everything for you, so there shouldn't be an issue.

It thinks I have Linux.

Ok, I just got another BSOD. Dump attached, can you please check it out?

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\Jmvars\041412-26130-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 Personal
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Machine Name:
Kernel base = 0xfffff800`03007000 PsLoadedModuleList = 0xfffff800`0324b650
Debug session time: Sat Apr 14 08:52:04.975 2012 (UTC - 6:00)
System Uptime: 0 days 0:52:06.598
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 34, {50853, fffff88007ea5488, fffff88007ea4ce0, fffff800030ee7ea}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2a12a )

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

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

CACHE_MANAGER (34)
    See the comment for FAT_FILE_SYSTEM (0x23)
Arguments:
Arg1: 0000000000050853
Arg2: fffff88007ea5488
Arg3: fffff88007ea4ce0
Arg4: fffff800030ee7ea

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


EXCEPTION_RECORD:  fffff88007ea5488 -- (.exr 0xfffff88007ea5488)
ExceptionAddress: fffff800030ee7ea (nt! ?? ::FNODOBFM::`string'+0x000000000002a12a)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 00007a8006eddf90
Attempt to read from address 00007a8006eddf90

CONTEXT:  fffff88007ea4ce0 -- (.cxr 0xfffff88007ea4ce0)
rax=0000000000000010 rbx=0000000000000070 rcx=0000000000000002
rdx=000000001f44d000 rsi=fffff8a00c2fa270 rdi=000000000000000e
rip=fffff800030ee7ea rsp=fffff88007ea56c0 rbp=fffff88007ea5970
 r8=0000000000000000  r9=fffffa800415e230 r10=000000000000000f
r11=2b9000010a898921 r12=fffffa80045bdcc0 r13=00007a8006eddf90
r14=0000000fffffffff r15=fffffa8006eddf10
iopl=0         nv up ei pl nz ac po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010216
nt! ?? ::FNODOBFM::`string'+0x2a12a:
fffff800`030ee7ea 4d8b7d00        mov     r15,qword ptr [r13] ds:002b:00007a80`06eddf90=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

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

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

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  00007a8006eddf90

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032b5100
 00007a8006eddf90 

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+2a12a
fffff800`030ee7ea 4d8b7d00        mov     r15,qword ptr [r13]

FAULTING_IP: 
nt! ?? ::FNODOBFM::`string'+2a12a
fffff800`030ee7ea 4d8b7d00        mov     r15,qword ptr [r13]

BUGCHECK_STR:  0x34

LAST_CONTROL_TRANSFER:  from fffff80003099500 to fffff800030ee7ea

STACK_TEXT:  
fffff880`07ea56c0 fffff800`03099500 : fffff6fc`c0142880 00000000`00000001 fffffa80`00000010 fffffa80`0118e750 : nt! ?? ::FNODOBFM::`string'+0x2a12a
fffff880`07ea5830 fffff800`03071fde : fffff980`28500000 00000000`00010000 fffffa80`00000000 fffffa80`045bdc01 : nt!MmCheckCachedPageStates+0x3c0
fffff880`07ea59e0 fffff800`032e759d : 00000000`00000000 00000000`c00000d8 fffffa80`045bdcc0 fffffa80`05e95410 : nt!CcFetchDataForRead+0x10e
fffff880`07ea5a40 fffff800`0303065c : fffffa80`045bdcc0 00000000`1f440000 00000000`00040000 fffffa80`0415e230 : nt!CcMapAndCopyFromCache+0xc5
fffff880`07ea5ad0 fffff800`030c8cce : fffffa80`045bdcc0 00000000`00000000 fffffa80`00000005 00000000`00000701 : nt!CcPerformReadAhead+0x3b8
fffff880`07ea5c00 fffff800`0308d361 : fffffa80`03b58620 fffff800`03223201 fffff800`032848b0 fffffa80`00000005 : nt!CcWorkerThread+0x21e
fffff880`07ea5cb0 fffff800`0331dfda : 00000000`f4d8d710 fffffa80`0415e230 00000000`00000080 fffffa80`03b4d040 : nt!ExpWorkerThread+0x111
fffff880`07ea5d40 fffff800`030749c6 : fffff880`02f63180 fffffa80`0415e230 fffffa80`03b5d680 00000038`48378000 : nt!PspSystemThreadStartup+0x5a
fffff880`07ea5d80 00000000`00000000 : fffff880`07ea6000 fffff880`07ea0000 fffff880`07ea56e0 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+2a12a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4f558b55

STACK_COMMAND:  .cxr 0xfffff88007ea4ce0 ; kb

FAILURE_BUCKET_ID:  X64_0x34_nt!_??_::FNODOBFM::_string_+2a12a

BUCKET_ID:  X64_0x34_nt!_??_::FNODOBFM::_string_+2a12a

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

Still pointing to memory problems. Either you do not have enough RAM (doubtful with 4 GB; that should be plenty), or your memory has errors.

Were you ever able to get Memtest86+ to run? Boot Windows 7 System Repair Disc from USB Using Grub4Dos may help if you cannot get the Memtest86+ USB maker to work.

writhziden said:

Were you ever able to get Memtest86+ to run? Boot Windows 7 System Repair Disc from USB Using Grub4Dos may help if you cannot get the Memtest86+ USB maker to work.

Thanks, but cba now because im sick.

That's alright, but I am sorry you are sick.

I'll be subscribed when you are able to get to it. Feel better!

writhziden said:

That's alright, but I am sorry you are sick.

I'll be subscribed when you are able to get to it. Feel better!

Thanks! :)

writhziden said:

Still pointing to memory problems. Either you do not have enough RAM (doubtful with 4 GB; that should be plenty), or your memory has errors.

Were you ever able to get Memtest86+ to run? Boot Windows 7 System Repair Disc from USB Using Grub4Dos may help if you cannot get the Memtest86+ USB maker to work.

Feeling better now :) But what does this do?

I still have the Windows CD if it matters.

Sorry, I was not clear about what you were supposed to do with the information in that link. The steps in Boot Windows 7 System Repair Disc from USB Using Grub4Dos can be used for getting an ISO on a USB drive. I was suggesting that you use only the steps for getting the Grub4Dos and then putting your Memtest86+ ISO on the USB using the Grub4Dos program.

OK, so. I found out why it didn't install. There is this switch on the USB key, it makes the key read-only. I knew about this switch but didn't think about it until now.

I have installed the Memtest onto the key and will try it when I go to sleep. It takes very long, amirite?

You are correct. Post back the results of the test. Best of luck!