BSoD Windows 8 vid uppstart
Hejsan!
Jag har en relativt ny dator (från i julas) som jag köpte från Inet och som dom byggde ihop åt mig.
Installerade mitt egna Windows 8 på den och i början funkade det som på räls!
Men nu på senare tid så får jag ofta en BSoD då jag startar upp datorn. Your PC has run in to a problem and must restart står det och efter en omstart så går den igång och undrar om jag vill skicka informationen till Microsoft.
Den tidigaste minidump filen av detta är från 2/7 2013.
I dumpcheck står detta och det är alltid samma.
Någon som vet vad detta kan bero på?
Tack på förhand!
/Eric
Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\031213-12921-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9200 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
Machine Name:
Kernel base = 0xfffff803`91c6f000 PsLoadedModuleList = 0xfffff803`91f38a80
Debug session time: Tue Mar 12 12:29:28.109 2013 (UTC + 1:00)
System Uptime: 3 days 0:38:01.357
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
............................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7A, {4, 0, fffffa80178ec410, fffff88009b79000}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+2337e )
Followup: MachineOwner
---------
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_DATA_INPAGE_ERROR (7a)
The requested page of kernel data could not be read in. Typically caused by
a bad block in the paging file or disk controller error. Also see
KERNEL_STACK_INPAGE_ERROR.
If the error status is 0xC000000E, 0xC000009C, 0xC000009D or 0xC0000185,
it means the disk subsystem has experienced a failure.
If the error status is 0xC000009A, then it means the request failed because
a filesystem failed to make forward progress.
Arguments:
Arg1: 0000000000000004, lock type that was held (value 1,2,3, or PTE address)
Arg2: 0000000000000000, error status (normally i/o status code)
Arg3: fffffa80178ec410, current process (virtual address for lock type 3, or PTE)
Arg4: fffff88009b79000, virtual address that could not be in-paged (or PTE contents if arg1 is a PTE address)
Debugging Details:
------------------
ERROR_CODE: (NTSTATUS) 0 - STATUS_SUCCESS
BUGCHECK_STR: 0x7a_0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80391dbe5af to fffff80391ce9040
STACK_TEXT:
fffff880`0375c6e8 fffff803`91dbe5af : 00000000`0000007a 00000000`00000004 00000000`00000000 fffffa80`178ec410 : nt!KeBugCheckEx
fffff880`0375c6f0 fffff803`91cda5e3 : 00000000`00000002 fffff880`0375c850 fffff803`91fbda80 fffff880`0375c840 : nt! ?? ::FNODOBFM::`string'+0x2337e
fffff880`0375c7d0 fffff803`91d243dc : fffffa80`0c6ff900 fffff803`91fbda80 00000000`c0033333 00000001`00000001 : nt!MiIssueHardFault+0x183
fffff880`0375c8a0 fffff803`91cd037e : 00000000`00000001 fffffa80`14171b00 fffff803`91cd1800 fffffa80`14171b02 : nt!MmAccessFault+0x7fc
fffff880`0375c9e0 fffff803`91cd18af : fffff803`91f3fd60 00000000`00000000 00000000`00000000 fffffa80`0d58f500 : nt!MiInPageSingleKernelStack+0x14e
fffff880`0375cbb0 fffff803`91c913d5 : fffffa80`0c6ff900 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeSwapProcessOrStack+0xb3
fffff880`0375cc10 fffff803`91ccf116 : fffff880`0145e180 fffffa80`0c6ff900 fffff880`01469f40 fffffa80`0c7b9040 : nt!PspSystemThreadStartup+0x59
fffff880`0375cc60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+2337e
fffff803`91dbe5af cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+2337e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 50ecec77
BUCKET_ID_FUNC_OFFSET: 2337e
FAILURE_BUCKET_ID: 0x7a_0_nt!_??_::FNODOBFM::_string_
BUCKET_ID: 0x7a_0_nt!_??_::FNODOBFM::_string_
Followup: MachineOwner
---------
