Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Blue screen dump


  • Please log in to reply
7 replies to this topic

#1 Kimito

Kimito

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:10:53 AM

Posted 20 January 2014 - 03:39 PM

Hello!

 

I've been trying to work out what is wrong with my computer. It is quite new, but I've been having trouble since I bought it. A lot of memory dumps and it gets worse for every Win 8 update. I also ran the memory test in windows 8 and it claimed I had a memory problem.

 

This is all my bugchecks (from last to first) after I reinstalled Windows 8 the last time.

 

Is there anything I could do or do I need to send it in for repairs on the guarantee?

 

1.

 

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041284, A PTE or the working set list is corrupt.
Arg2: fffff9010592c001
Arg3: 00000000000019e8
Arg4: fffff90000452000

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


BUGCHECK_STR:  0x1a_41284

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  consent.exe

CURRENT_IRQL:  0

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

LAST_CONTROL_TRANSFER:  from fffff800fa40c59a to fffff800fa464440

STACK_TEXT:  
fffff880`185e9db8 fffff800`fa40c59a : 00000000`0000001a 00000000`00041284 fffff901`0592c001 00000000`000019e8 : nt!KeBugCheckEx
fffff880`185e9dc0 fffff800`fa4daefa : 9e800001`5eef6863 fffff6fc`8082c960 00000000`00000000 fffff880`185e9f00 : nt! ?? ::FNODOBFM::`string'+0x1ea45
fffff880`185e9e00 fffff800`fa4d8d99 : fffff901`05800000 ffff3a93`140c5560 fffff901`05800000 fffff960`00154e20 : nt!MiDeleteSystemPagableVm+0x19a
fffff880`185e9fc0 fffff800`fa67bc9a : fffff880`04fe2000 fffff880`185ea179 00000000`00000021 fffffa80`092d2b00 : nt!MiFreePagedPoolPages+0x179
fffff880`185ea100 fffff960`00155328 : fffff901`05800000 00000000`00000000 00000000`00000001 fffff901`35316847 : nt!ExFreePoolWithTag+0xb3a
fffff880`185ea1e0 fffff960`0012a6fe : fffffa80`092d2aa0 fffff901`0020ac68 00000000`00000000 00000000`0000072f : win32k!SURFMEM::~SURFMEM+0x437
fffff880`185ea2d0 fffff960`00155ebe : fffff880`185ea6e0 00000000`00000000 00000000`00000000 fffff901`00000730 : win32k!EngAlphaBlend+0x38e
fffff880`185ea5f0 fffff800`fa463453 : 00000000`0185000f fffff901`01b369b0 00000000`00000000 fffff901`000b6010 : win32k!NtGdiAlphaBlend+0xb5e
fffff880`185eaa90 000007fd`bcb210fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000080`c1d7f628 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fd`bcb210fa


STACK_COMMAND:  kb

FOLLOWUP_IP:
win32k!SURFMEM::~SURFMEM+437
fffff960`00155328 ebbe            jmp     win32k!SURFMEM::~SURFMEM+0x3f8 (fffff960`001552e8)

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  win32k!SURFMEM::~SURFMEM+437

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  527ace4b

IMAGE_VERSION:  6.2.9200.16758

BUCKET_ID_FUNC_OFFSET:  437

FAILURE_BUCKET_ID:  0x1a_41284_win32k!SURFMEM::_SURFMEM

BUCKET_ID:  0x1a_41284_win32k!SURFMEM::_SURFMEM

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x1a_41284_win32k!surfmem::_surfmem

FAILURE_ID_HASH:  {c3a4d76b-b89c-88eb-bb1b-59d8038d2c3c}

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

2.

 

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041792, A corrupt PTE has been detected. Parameter 2 contains the address of
    the PTE. Parameters 3/4 contain the low/high parts of the PTE.
Arg2: fffff6800002c080
Arg3: 00000000000c0000
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41792

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  mscorsvw.exe

CURRENT_IRQL:  0

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

LAST_CONTROL_TRANSFER:  from fffff801c6da7a71 to fffff801c6cd2440

STACK_TEXT:  
fffff880`053bf798 fffff801`c6da7a71 : 00000000`0000001a 00000000`00041792 fffff680`0002c080 00000000`000c0000 : nt!KeBugCheckEx
fffff880`053bf7a0 fffff801`c6d130b4 : fffff880`053b0001 fffffa80`00000000 fffffa80`00000002 fffff880`00000000 : nt! ?? ::FNODOBFM::`string'+0x36d1b
fffff880`053bf930 fffff801`c6d2351e : 00000000`00000000 fffffa80`07633210 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xe4
fffff880`053bf9a0 fffff801`c70a5159 : fffffa80`07633210 00000000`054f0000 00000000`00000000 00000000`00000000 : nt!MiUnmapVad+0x6e
fffff880`053bfa00 fffff801`c70c0c2b : fffff6fb`40000100 fffff680`00000008 00000000`054f0000 00000000`0015ed01 : nt!MiUnmapViewOfSection+0xc9
fffff880`053bfab0 fffff801`c6cd1453 : fffffa80`06af15c0 00000000`00000000 fffff880`053bfb01 fffffa80`06b1d940 : nt!NtUnmapViewOfSectionEx+0x83
fffff880`053bfb00 000007fa`a56c2e4a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0015e468 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fa`a56c2e4a


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+36d1b
fffff801`c6da7a71 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+36d1b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5165e551

IMAGE_VERSION:  6.2.9200.16581

BUCKET_ID_FUNC_OFFSET:  36d1b

FAILURE_BUCKET_ID:  0x1a_41792_nt!_??_::FNODOBFM::_string_

BUCKET_ID:  0x1a_41792_nt!_??_::FNODOBFM::_string_

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x1a_41792_nt!_??_::fnodobfm::_string_

FAILURE_ID_HASH:  {e00e25fc-1d2f-6e67-bb24-ba96083192fa}

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

3.

PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc).  If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 000000000016400d, page frame number
Arg3: 0000000000000003, current page state
Arg4: 0000000000000000, 0

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


BUGCHECK_STR:  0x4E_99

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  MsMpEng.exe

CURRENT_IRQL:  2

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

LAST_CONTROL_TRANSFER:  from fffff8020b98992b to fffff8020b87c040

STACK_TEXT:  
fffff880`16566d48 fffff802`0b98992b : 00000000`0000004e 00000000`00000099 00000000`0016400d 00000000`00000003 : nt!KeBugCheckEx
fffff880`16566d50 fffff802`0b8535dc : 00000000`00000000 fffffa80`0428ae40 00000000`00000000 00000000`00000000 : nt!MiBadShareCount+0x4b
fffff880`16566d90 fffff802`0b850cd9 : fffffa80`09744940 fffff680`559f1100 00000000`00004ea7 00000000`00000002 : nt!MiDeletePfnList+0x5b1
fffff880`16566e70 fffff802`0b8595dd : fffffa80`09744940 fffff8a0`00000a0b 00000000`0000002e fffff802`00004382 : nt!MiDeleteAddressesInWorkingSet+0x39a
fffff880`16567740 fffff802`0bc24644 : fffff8a0`01e81060 fffff880`16567988 fffffa80`0972a080 00000000`00000000 : nt!MiBeginProcessClean+0xbd
fffff880`16567780 fffff802`0bc2be68 : fffff8a0`01e81060 fffff880`16567988 00000000`00000001 00000000`00000001 : nt!MmCleanProcessAddressSpace+0x4c
fffff880`165677f0 fffff802`0bc25f80 : fffffa80`000000ff 00000000`00000001 000007f6`1a3da000 000000ab`78457350 : nt!PspExitThread+0x668
fffff880`16567910 fffff802`0b8de001 : 00000000`00000002 fffff802`0b8e367e 00000000`00000000 fffff880`165679e8 : nt!PsExitSpecialApc+0x1d
fffff880`16567940 fffff802`0b8de330 : 000000ab`3a4e76e0 fffff880`165679c0 fffff802`0bc259f0 00000000`00000001 : nt!KiDeliverApc+0x2cf
fffff880`165679c0 fffff802`0b87b0fa : 00000000`000000d0 000000ab`3a4e7360 00000000`00000010 000000ab`3aadf730 : nt!KiInitiateUserApc+0x70
fffff880`16567b00 000007fc`4fc8466b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9f
000000ab`3aadf6d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fc`4fc8466b


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt!MiBadShareCount+4b
fffff802`0b98992b cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!MiBadShareCount+4b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  5010ac4b

IMAGE_VERSION:  6.2.9200.16384

IMAGE_NAME:  memory_corruption

BUCKET_ID_FUNC_OFFSET:  4b

FAILURE_BUCKET_ID:  0x4E_99_nt!MiBadShareCount

BUCKET_ID:  0x4E_99_nt!MiBadShareCount

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x4e_99_nt!mibadsharecount

FAILURE_ID_HASH:  {60e553e9-e4c5-ed08-9be6-c353e0011003}

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

4.

 

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure.  The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: fffff8801671e0a0, Address of the trap frame for the exception that caused the bugcheck
Arg3: fffff8801671dff8, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved

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


TRAP_FRAME:  fffff8801671e0a0 -- (.trap 0xfffff8801671e0a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a007c7be60 rbx=0000000000000000 rcx=0000000000000003
rdx=000000000017e748 rsi=0000000000000000 rdi=0000000000000000
rip=fffff802d0a4f067 rsp=fffff8801671e230 rbp=0000000000000003
 r8=0000000000000030  r9=fffff8a00652e8c8 r10=0000000000000000
r11=fffff98000020654 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po cy
nt! ?? ::NNGAKEGL::`string'+0x88bf:
fffff802`d0a4f067 cd29            int     29h
Resetting default scope

EXCEPTION_RECORD:  fffff8801671dff8 -- (.exr 0xfffff8801671dff8)
ExceptionAddress: fffff802d0a4f067 (nt! ?? ::NNGAKEGL::`string'+0x00000000000088bf)
   ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
  ExceptionFlags: 00000001
NumberParameters: 1
   Parameter[0]: 0000000000000003

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  LIST_ENTRY_CORRUPT

BUGCHECK_STR:  0x139

PROCESS_NAME:  TiWorker.exe

CURRENT_IRQL:  1

ERROR_CODE: (NTSTATUS) 0xc0000409 - Det ble oppdaget en overflyt i en stakkbasert buffer i programmet. Overflyten kan f re til at ondsinnede brukere tar kontroll over programmet.

EXCEPTION_CODE: (NTSTATUS) 0xc0000409 - Det ble oppdaget en overflyt i en stakkbasert buffer i programmet. Overflyten kan f re til at ondsinnede brukere tar kontroll over programmet.

EXCEPTION_PARAMETER1:  0000000000000003

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

LAST_CONTROL_TRANSFER:  from fffff802d04f0369 to fffff802d04f1040

STACK_TEXT:  
fffff880`1671dd78 fffff802`d04f0369 : 00000000`00000139 00000000`00000003 fffff880`1671e0a0 fffff880`1671dff8 : nt!KeBugCheckEx
fffff880`1671dd80 fffff802`d04f0690 : 28386cf4`00000000 fffff8a0`ac7eafea ffff4688`44ce0bff fffff880`1671e448 : nt!KiBugCheckDispatch+0x69
fffff880`1671dec0 fffff802`d04ef8f4 : 00000000`00000014 fffff8a0`0652e7f8 00000000`dece44c6 00000000`0000000e : nt!KiFastFailDispatch+0xd0
fffff880`1671e0a0 fffff802`d0a4f067 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff802`d084c253 : nt!KiRaiseSecurityCheckFailure+0xf4
fffff880`1671e230 fffff802`d084bb8d : 00000000`f8de16d0 00000000`0017e748 fffff8a0`04305024 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x88bf
fffff880`1671e260 fffff802`d084ea3f : fffff8a0`00217010 fffff880`0017e748 fffff8a0`039ab74c fffff8a0`066326f8 : nt!CmpCreateKeyControlBlock+0xdd
fffff880`1671e2f0 fffff802`d08af348 : fffff880`1671e490 fffff8a0`0017e748 fffff8a0`06d61930 fffff880`1671e430 : nt!CmpAddInfoAfterParseFailure+0x27f
fffff880`1671e380 fffff802`d08bdc5d : fffff802`d0476000 fffff802`d0476000 00000000`00000148 00000052`d1b14930 : nt!CmpParseKey+0x1059
fffff880`1671e710 fffff802`d08c32b8 : 00000000`00000000 fffff880`1671e8b8 fffff802`00000040 fffffa80`066da840 : nt!ObpLookupObjectName+0x7a1
fffff880`1671e840 fffff802`d08b3f01 : 00000000`00000000 00000052`d241d040 fffffa80`09a5e201 00000000`00000000 : nt!ObOpenObjectByName+0x258
fffff880`1671e910 fffff802`d0872837 : 000007fe`00000006 ffff4688`44ce3fff 000007fe`996a3128 00000000`00000001 : nt!CmOpenKey+0x2a0
fffff880`1671eac0 fffff802`d04f0053 : 00000000`00000000 fffffa80`0728a280 fffff880`1671eb80 00000052`d241d488 : nt!NtOpenKeyEx+0xf
fffff880`1671eb00 000007fe`ace33c0b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000052`d241cd18 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`ace33c0b


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt!KiFastFailDispatch+d0
fffff802`d04f0690 c644242000      mov     byte ptr [rsp+20h],0

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiFastFailDispatch+d0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5010ac4b

IMAGE_VERSION:  6.2.9200.16384

BUCKET_ID_FUNC_OFFSET:  d0

FAILURE_BUCKET_ID:  0x139_3_nt!KiFastFailDispatch

BUCKET_ID:  0x139_3_nt!KiFastFailDispatch

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x139_3_nt!kifastfaildispatch

FAILURE_ID_HASH:  {36173680-6f08-995f-065a-3d368c996911}

Followup: MachineOwner
 

5.

 

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041201, The subtype of the bugcheck.
Arg2: fffff6805ddf6410
Arg3: aed0000160026867
Arg4: fffffa800855e8f0

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


BUGCHECK_STR:  0x1a_41201

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  MsMpEng.exe

CURRENT_IRQL:  0

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

LAST_CONTROL_TRANSFER:  from fffff803f4f2c3fc to fffff803f4e9a040

STACK_TEXT:  
fffff880`15e6c748 fffff803`f4f2c3fc : 00000000`0000001a 00000000`00041201 fffff680`5ddf6410 aed00001`60026867 : nt!KeBugCheckEx
fffff880`15e6c750 fffff803`f4e68def : aed00001`60026867 00000000`00000003 00000000`00000003 00000000`00001000 : nt! ?? ::FNODOBFM::`string'+0x34be2
fffff880`15e6c7a0 fffff803`f4e6b370 : 00000000`00000002 fffff803`f4ee28dd d4004b8e`0287d717 fffff803`f4ed6ef0 : nt!MiQueryAddressState+0x383
fffff880`15e6c890 fffff803`f5219aac : 00000000`00000001 000000bb`bec82000 00000000`00000003 000000bb`bea80001 : nt!MiQueryAddressSpan+0xba
fffff880`15e6c900 fffff803`f521bdb2 : 00000000`00000000 fffff803`f523f8cb fffffa80`08c8b080 000000f8`e563a5a8 : nt!MmQueryVirtualMemory+0x42a
fffff880`15e6ca40 fffff803`f4e99053 : 00000000`00000000 000000f8`e5639eb8 fffff6fb`7dbed008 fffff6fb`7da01f18 : nt!NtQueryVirtualMemory+0x22
fffff880`15e6ca90 000007ff`9b6e2dda : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
000000f8`e563a638 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007ff`9b6e2dda


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+34be2
fffff803`f4f2c3fc cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+34be2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5010ac4b

IMAGE_VERSION:  6.2.9200.16384

BUCKET_ID_FUNC_OFFSET:  34be2

FAILURE_BUCKET_ID:  0x1a_41201_nt!_??_::FNODOBFM::_string_

BUCKET_ID:  0x1a_41201_nt!_??_::FNODOBFM::_string_

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x1a_41201_nt!_??_::fnodobfm::_string_

FAILURE_ID_HASH:  {48c83227-3944-10a1-bf0f-11b43dc9c13b}

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

6.

 

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000000031, The subtype of the bugcheck.
Arg2: fffffa8009146dc0
Arg3: fffff88002c98000
Arg4: fffff8a00234c91b

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


BUGCHECK_STR:  0x1a_31

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  WerFault.exe

CURRENT_IRQL:  0

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

LAST_CONTROL_TRANSFER:  from fffff8037ba6d8d1 to fffff8037b4ea040

STACK_TEXT:  
fffff880`07ce6668 fffff803`7ba6d8d1 : 00000000`0000001a 00000000`00000031 fffffa80`09146dc0 fffff880`02c98000 : nt!KeBugCheckEx
fffff880`07ce6670 fffff803`7b837063 : 00000000`00214000 00000000`62760000 fffff8a0`0234c8fe 00000000`001327ca : nt! ?? ::NNGAKEGL::`string'+0x355a1
fffff880`07ce66d0 fffff803`7b86e2f9 : fffff8a0`02344000 fffffa80`09146dc0 fffff880`02c98000 fffff880`00002c98 : nt!MiPerformFixups+0x7b
fffff880`07ce6730 fffff803`7b4ba31e : fffffa80`09146ff0 fffffa80`07857828 fffffa80`07857858 fffff880`00000000 : nt!MiRelocateImagePfn+0x149
fffff880`07ce6790 fffff803`7b4dc83f : fffffa80`00000000 fffffa80`07857898 fffffa80`08a69000 fffffa80`09146ff0 : nt!MiValidateInPage+0x16e
fffff880`07ce6810 fffff803`7b4db2c3 : 00000000`00000003 fffff880`07ce6970 fffffa80`071499a8 fffff880`07ce6960 : nt!MiWaitForInPageComplete+0x21f
fffff880`07ce68f0 fffff803`7b524e1c : fffffa80`090351c0 fffffa80`071499a8 00000000`c0033333 fffff880`07ce6a50 : nt!MiIssueHardFault+0x183
fffff880`07ce69c0 fffff803`7b4e7aee : 00000000`00000008 00000000`0000014c fffff880`07ce6b01 fffff880`07ce6b00 : nt!MmAccessFault+0x7fc
fffff880`07ce6b00 00000000`72974b20 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`003fdec4 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x72974b20


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt! ?? ::NNGAKEGL::`string'+355a1
fffff803`7ba6d8d1 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::NNGAKEGL::`string'+355a1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5010ac4b

IMAGE_VERSION:  6.2.9200.16384

BUCKET_ID_FUNC_OFFSET:  355a1

FAILURE_BUCKET_ID:  0x1a_31_nt!_??_::NNGAKEGL::_string_

BUCKET_ID:  0x1a_31_nt!_??_::NNGAKEGL::_string_

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x1a_31_nt!_??_::nngakegl::_string_

FAILURE_ID_HASH:  {7463ed29-5dcd-e31a-7dee-ab4eb1f70624}

Followup: MachineOwner
 



BC AdBot (Login to Remove)

 


#2 Anshad Edavana

Anshad Edavana

  • BC Advisor
  • 2,805 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:India
  • Local time:03:23 PM

Posted 22 January 2014 - 01:24 AM

:welcome: to the forum mate.

 

 

 

 I also ran the memory test in windows 8 and it claimed I had a memory problem.

 

It means there is a RAM related issue in your machine. It could be either a failing RAM module, a faulty Motherboard memory slot or the memory you are using might be incompatible with the board.

 

Please try the below steps.

 

:step1: Reset CMOS and load default values.

 

      http://pcsupport.about.com/od/fixtheproblem/tp/clearcmos.htm

 

This is necessary to make sure neither RAM nor CPU voltage and frequency settings are modified either willingly or unwillingly.

 

:step2: Run Memtest86+ 5.01 to stress test the modules. 

 

Please read the below guide for detailed instructions on running memory test.

 

      http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

 

     

 

Run Memtest86+ for at least eight passes and report whether it detects any errors ( you will see red lines). You can stop the test immediately even if a single error is found. 


Edited by Anshad Edavana, 22 January 2014 - 01:26 AM.


#3 Kimito

Kimito
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:10:53 AM

Posted 22 January 2014 - 02:10 AM

Thank you!

 

Before I try that, I want to ask you a question because what you wrote got me to check the spesifications of my order. It seems the SSD I got, the Samsung SSD 840 EVO 250GB BK OEM, is for DDR2, while my motherboard, MSI B85M-E45, Socket-1150 and memory Corsair Vengeance DDR3 1600MHz 8GB CL9 are DDR3.

 

Is that it?



#4 Kimito

Kimito
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:10:53 AM

Posted 22 January 2014 - 03:52 AM

Thank you!

 

Before I try that, I want to ask you a question because what you wrote got me to check the spesifications of my order. It seems the SSD I got, the Samsung SSD 840 EVO 250GB BK OEM, is for DDR2, while my motherboard, MSI B85M-E45, Socket-1150 and memory Corsair Vengeance DDR3 1600MHz 8GB CL9 are DDR3.

 

Is that it?

OK. I called support and they claimed that the above didn't have anything to do with it.

 

The memtest showed loads of red lines when I ran it, but I am not entirely sure I did reset the cmos. I found a "reset-settings-choice" in the BIOS. Is that enough? What to do next?



#5 Anshad Edavana

Anshad Edavana

  • BC Advisor
  • 2,805 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:India
  • Local time:03:23 PM

Posted 22 January 2014 - 04:48 AM

Hi

 

When you enter BIOS setup, you will find a menu item Save and Exit. Navigate to it and select Restore Defaults and then choose Save Changes and Reboot. This will load optimal default values. Refer the manual if you are in doubt.

 

http://www.msi.com/service/download/manual-21536.html

 

Then rerun the Memtest program and if it detects errors, please refer part three of the guide (from my previous post). What you need is unplug all modules and test each of them one by one at a time to find the failed one. If the modules came as a pair, you should submit all modules for replacement. Otherwise find the failed one and submit it for warranty.


Edited by Anshad Edavana, 22 January 2014 - 04:51 AM.


#6 Kimito

Kimito
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:10:53 AM

Posted 22 January 2014 - 05:45 AM

Thank you once again! Very helpful!
 
I have tried and tested the ram modules and it seems one of them is to blame (one is running without memory problems by itself, but when I tried both in the blue slots the problem reappeared). Do I have to test if the other (the one I think is at fault) can run by itself as well, or can I just send it in for warranty? (I haven't got time to test it before work now and would like to ship it after work :))

Edited by Kimito, 22 January 2014 - 06:07 AM.


#7 Anshad Edavana

Anshad Edavana

  • BC Advisor
  • 2,805 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:India
  • Local time:03:23 PM

Posted 22 January 2014 - 06:33 AM

Hi

 

Can you confirm both modules are from same manufacturer and they are same models ?. Both memory should be tested separately to find the bad one. 



#8 Kimito

Kimito
  • Topic Starter

  • Members
  • 5 posts
  • OFFLINE
  •  
  • Local time:10:53 AM

Posted 23 January 2014 - 12:24 AM

Hi
 
Can you confirm both modules are from same manufacturer and they are same models ?. Both memory should be tested separately to find the bad one.

 
Hi again,
 
Yes, they are from the same manufacurer and are the same models. I testet the bad one separapely when I came back from work yesterday and it was erronous. Now I only need to send in the bad ram module instead of the whole cabinet as suggested by customer service earlier. Best of all, I can still use the computer.
 
Thank you ever so much!
 
K.


Edited by Kimito, 23 January 2014 - 12:42 AM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users