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

Please help with BSOD, here is degugged analysis:


  • Please log in to reply
1 reply to this topic

#1 radtech46

radtech46

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:02:51 PM

Posted 21 September 2013 - 08:06 AM

Can someone please help with the following BSOD debugged analysis.

 

Microsoft ® Windows Debugger Version 6.2.9200.20512 AMD64

Loading Dump File [C:\Windows\Minidump\092113-28687-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 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533

Kernel base = 0xfffff800`02c14000 PsLoadedModuleList = 0xfffff800`02e576d0

Debug session time: Sat Sep 21 07:45:50.188 2013 (UTC - 4:00)

System Uptime: 0 days 0:04:24.079

Loading Kernel Symbols.........................

Loading User Symbols

Loading unloaded module list.....

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa80015fb550, ffff, 0}

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

Followup: MachineOwner -v

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

MEMORY_MANAGEMENT (1a)

    # Any other values for parameter 1 must be individually examined.

Arguments:

Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2

                contains the address of the PFN for the corrupted page table page.

                On a 32 bit OS, parameter 2 contains a pointer to the number of used

                PTEs, and parameter 3 contains the number of used PTEs.

Arg2: fffffa80015fb550

Arg3: 000000000000ffff

Arg4: 0000000000000000

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

BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  taskhost.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002cfad40 to fffff80002c89b80

STACK_TEXT: 

fffff880`0602e958 fffff800`02cfad40 : 00000000`0000001a 00000000`00041790 fffffa80`015fb550 00000000`0000ffff : nt!KeBugCheckEx

fffff880`0602e960 fffff800`02c763cf : fffffa80`00000000 00000000`1600ffff 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x35084

fffff880`0602eb20 fffff800`02c88e13 : ffffffff`ffffffff 00000000`261bf248 00000000`261bf240 00000000`00008000 : nt!NtFreeVirtualMemory+0x61f

fffff880`0602ec20 00000000`7716149a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13

00000000`261bf208 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7716149a

STACK_COMMAND:  kb

FOLLOWUP_IP:

nt! ?? ::FNODOBFM::`string'+35084

fffff800`02cfad40 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+35084

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  51fb06cd

FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35084

BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35084

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

 

THANK YOU SO MUCH!!!

 



BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 55,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:01:51 PM

Posted 21 September 2013 - 04:41 PM

If I received a BSOD which pointed to Memory Managerment...first thing I'd do is test the RAM modules via Memtest 86+.

 

Memtest86+ - Advanced Memory Diagnostic Tool - http://www.memtest.org/#downiso

Memtest86+ Guide-How To's - Overclockers Forums - http://www.overclockers.com/forums/showthread.php?t=409152

 

Louis






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users