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

BSOD New Custom Built PC


  • Please log in to reply
1 reply to this topic

#1 dalotheman

dalotheman

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:12:36 AM

Posted 25 June 2013 - 09:18 PM

I just built a new PC and am toying with overclocking. My problem is that I've experienced 2 BSOD's in the last few weeks and can't tell if it's drivers or possibly defective "NEW" hardware.

 

Here's my mem.dmp

 

Microsoft ® Windows Debugger Version 6.2.9200.20512 AMD64
Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

WARNING: Whitespace at end of path element
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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Machine Name:
Kernel base = 0xfffff800`03a63000 PsLoadedModuleList = 0xfffff800`03ca6670
Debug session time: Mon Jun 24 22:04:49.676 2013 (UTC - 7:00)
System Uptime: 0 days 0:00:08.472
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffd8001234ed3b, 0, fffff80003a32189, 7}

Probably caused by : hardware ( vga!InitializeModeTable+157 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffffd8001234ed3b, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80003a32189, If non-zero, the instruction address which referenced the bad memory
 address.
Arg4: 0000000000000007, (reserved)

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

READ_ADDRESS:  ffffd8001234ed3b

FAULTING_IP:
hal!XmEmulateStream+d9
fffff800`03a32189 d844895b        fadd    dword ptr [rcx+rcx*4+5Bh]

MM_INTERNAL_CODE:  7

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880037bd4c0 -- (.trap 0xfffff880037bd4c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff80003a42f60
rdx=000000000000335a rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003a32189 rsp=fffff880037bd650 rbp=0000000000000000
 r8=00000000000c335a  r9=0000000000009e48 r10=fffff80003a42f60
r11=0000000000000066 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
hal!XmEmulateStream+0xd9:
fffff800`03a32189 d844895b        fadd    dword ptr [rcx+rcx*4+5Bh] ds:ffffd800`1234ed3b=????????
Resetting default scope

MISALIGNED_IP:
hal!XmEmulateStream+d9
fffff800`03a32189 d844895b        fadd    dword ptr [rcx+rcx*4+5Bh]

LAST_CONTROL_TRANSFER:  from fffff80003b5552b to fffff80003ad8c00

STACK_TEXT: 
fffff880`037bd358 fffff800`03b5552b : 00000000`00000050 ffffd800`1234ed3b 00000000`00000000 fffff880`037bd4c0 : nt!KeBugCheckEx
fffff880`037bd360 fffff800`03ad6d2e : 00000000`00000000 ffffd800`1234ed3b 00000000`35e18f00 fffff800`03a42f60 : nt! ?? ::FNODOBFM::`string'+0x43781
fffff880`037bd4c0 fffff800`03a32189 : fffff800`03a42f60 fffff800`03a42f60 00000000`00000000 fffff800`03a1a000 : nt!KiPageFault+0x16e
fffff880`037bd650 fffff800`03a31fb0 : fffff800`03a42f60 fffff880`037bd720 00000000`00000000 fffff880`037bd720 : hal!XmEmulateStream+0xd9
fffff880`037bd680 fffff800`03a2b2fd : 00000000`00000000 fffffa80`0eb4e618 00000000`00000200 fffff880`037bd798 : hal!x86BiosExecuteInterruptShadowed+0xfc
fffff880`037bd6b0 fffff880`03081289 : 00000000`00000000 40000000`00000000 00000000`35e18f00 00000000`00000000 : hal!x86BiosCall+0x45
fffff880`037bd6f0 fffff880`0306f443 : 00000000`00000007 00000000`00000000 fffff880`00000000 00000000`000007ff : VIDEOPRT!VpInt10CallBios+0xb1
fffff880`037bd750 fffff880`0306cb16 : fffffa80`0eb4e618 fffffa80`0eb40000 00000000`00002000 fffff880`037bd9c0 : vga!InitializeModeTable+0x157
fffff880`037bd810 fffff880`0308f25b : 00000000`00000000 fffff8a0`00000000 00000000`00000000 00000000`00000000 : vga!VgaInitialize+0x1e
fffff880`037bd840 fffff880`0308ee6e : 00000000`00000000 fffff8a0`003bb790 00000000`00000000 00000000`00000000 : VIDEOPRT!VideoPortLegacyFindAdapter+0x3a3
fffff880`037bd930 fffff880`0306c819 : fffffa80`00000004 00000000`00000000 00000000`00000000 fffff8a0`003bb790 : VIDEOPRT!VideoPortInitialize+0x58a
fffff880`037bd9a0 fffff800`03e76bb7 : 00000000`00000001 00000000`00000001 00000000`69526f49 fffffa80`0d2da860 : vga!VgaReinitializationCallback+0x99
fffff880`037bda60 fffff800`03bdadf6 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : nt!IopCallDriverReinitializationRoutines+0x57
fffff880`037bda90 fffff800`03bdb684 : 00000000`00000000 00000000`00000000 00000000`32706e50 00000000`00000084 : nt!PnpCompleteSystemStartProcess+0x76
fffff880`037bdad0 fffff800`03ae2251 : fffff800`03bdb4f0 fffffa80`0ca77001 00000000`00000000 00000000`0000055a : nt!PnpDeviceActionWorker+0x194
fffff880`037bdb70 fffff800`03d76ede : 00000000`00000000 fffffa80`0ca77040 00000000`00000080 fffffa80`0ca63040 : nt!ExpWorkerThread+0x111
fffff880`037bdc00 fffff800`03ac9906 : fffff880`03574180 fffffa80`0ca77040 fffff880`0357f0c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`037bdc40 00000000`00000000 : fffff880`037be000 fffff880`037b8000 fffff880`037bcdc0 00000000`00000000 : nt!KiStartSystemThread+0x16

STACK_COMMAND:  kb

FOLLOWUP_IP:
vga!InitializeModeTable+157
fffff880`0306f443 3bc3            cmp     eax,ebx

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  vga!InitializeModeTable+157

FOLLOWUP_NAME:  MachineOwner

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

IMAGE_NAME:  hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

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

 

 



BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 55,887 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:02:36 AM

Posted 26 June 2013 - 03:25 PM

Try not overclocking...and see if stability returns.

 

Louis






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users