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 Help


  • Please log in to reply
3 replies to this topic

#1 catmandoo07

catmandoo07

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:03:59 AM

Posted 20 October 2012 - 04:58 AM

Hi I'm having trouble with Blue screens. I have already reformatted a couple times and still have the same problem. My drivers are all up to date per Driver Reviver. I ran Memtest86 and everything passed. After my last BSOD only one of my screens are being detected, so I'm leaning towards a graphics issue now, but thought I should get some help before taking everything apart. Not really sure where to proceed from here.

Specs are:

Win 7 64bit SP1
WD Blue 1TB 7200 RPM
Mushkin 40 GB SSD
16GB G.SKILL Ripjaws X Series DDR3 1600
i7-2600 Sandy Bridge 3.4 GHz
EVGA GTX 560 (Fermi)
Asus P8P67 Deluxe

The Memdump is as follows:


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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is 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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`03066000 PsLoadedModuleList = 0xfffff800`032aa670
Debug session time: Fri Oct 19 21:30:44.465 2012 (UTC - 8:00)
System Uptime: 0 days 0:06:44.309
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`fffdf018). Type ".hh dbgerr001" for details
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffffffffffff8b, 1, fffff88005985160, 0}

Page 3bb8b1 not present in the dump file. Type ".hh dbgerr004" for details
Probably caused by : memory_corruption

Followup: memory_corruption
---------

2: 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: ffffffffffffff8b, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff88005985160, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)

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


WRITE_ADDRESS: ffffffffffffff8b

FAULTING_IP:
dxgmms1!VIDMM_GLOBAL::CreateOneAllocation+db8
fffff880`05985160 ff488b dec dword ptr [rax-75h]

MM_INTERNAL_CODE: 0

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAULTING_MODULE: fffff8800596b000 dxgmms1

DEFAULT_BUCKET_ID: CODE_CORRUPTION

BUGCHECK_STR: 0x50

PROCESS_NAME: rift.exe

CURRENT_IRQL: 0

TRAP_FRAME: fffff8800a745f50 -- (.trap 0xfffff8800a745f50)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000001
rdx=00000000000001a8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88005985160 rsp=fffff8800a7460e0 rbp=fffffa80117dc000
r8=000000006d4d6956 r9=fffffa80117dc000 r10=0000000000000020
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
dxgmms1!VIDMM_GLOBAL::CreateOneAllocation+0xdb8:
fffff880`05985160 ff488b dec dword ptr [rax-75h] ds:ffffffff`ffffff8b=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff8000308ceec to fffff800030e4fc0

STACK_TEXT:
fffff880`0a745de8 fffff800`0308ceec : 00000000`00000050 ffffffff`ffffff8b 00000000`00000001 fffff880`0a745f50 : nt!KeBugCheckEx
fffff880`0a745df0 fffff800`030e30ee : 00000000`00000001 ffffffff`ffffff8b 00000000`00020000 00000000`000001a8 : nt! ?? ::FNODOBFM::`string'+0x4514f
fffff880`0a745f50 fffff880`05985160 : 00000000`00000000 00000000`fffffff1 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`0a7460e0 fffff880`0596c8e3 : 00000000`00000000 fffff8a0`083fe510 00000000`00160000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CreateOneAllocation+0xdb8
fffff880`0a746210 fffff880`058b83af : fffff880`78100500 fffff880`00000002 00000000`00000000 00000000`0000000e : dxgmms1!VidMmCreateAllocation+0x173
fffff880`0a7462f0 fffff880`058b1610 : fffff880`0a746558 00000000`00000000 fffff880`0a746730 fffff880`0a746730 : dxgkrnl!DXGDEVICE::CreateVidMmAllocations<_DXGK_ALLOCATIONINFO>+0x1d7
fffff880`0a746380 fffff880`058b426b : fffff8a0`095f1000 fffff880`0a7469f0 fffff880`0a746b01 00000000`00000000 : dxgkrnl!DXGDEVICE::CreateAllocation+0xca8
fffff880`0a746980 fffff960`0027006e : 00000000`000fdfa0 00000000`40002dc0 00000000`fffdb000 00000000`000007d3 : dxgkrnl!DxgkCreateAllocation+0x42b
fffff880`0a746ab0 fffff800`030e4253 : fffffa80`127de060 00000000`000006c0 00000000`00000000 fffffa80`12d1b6e0 : win32k!NtGdiDdDDICreateAllocation+0x12
fffff880`0a746ae0 00000000`727713aa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`000fdf58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x727713aa


STACK_COMMAND: kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !dxgmms1
fffff8800598515b - dxgmms1!VIDMM_GLOBAL::CreateOneAllocation+db3
[ ff:bf ]
1 error : !dxgmms1 (fffff8800598515b)

MODULE_NAME: memory_corruption

IMAGE_NAME: memory_corruption

FOLLOWUP_NAME: memory_corruption

MEMORY_CORRUPTOR: ONE_BIT

FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT

Followup: memory_corruption
---------

Any help would be much appreciated.

Edited by hamluis, 22 October 2012 - 12:24 PM.
Moved from Win 7 to Internal Hardware - Hamluis.


BC AdBot (Login to Remove)

 


#2 hamluis

hamluis

    Moderator


  • Moderator
  • 55,748 posts
  • ONLINE
  •  
  • Gender:Male
  • Location:Killeen, TX
  • Local time:06:59 AM

Posted 21 October 2012 - 02:32 PM

Uninstall current video drivers...then reinstall same or updated.

Louis

#3 catmandoo07

catmandoo07
  • Topic Starter

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:03:59 AM

Posted 22 October 2012 - 03:59 AM

Okay, so I just looked, my video card is not showing up in Device Manager and when I go to install the driver from EVGA it doesn't detect any compatible hardware. Wondering where to go from here. Should I just reformat the drive and start over?

#4 iceremover

iceremover

  • Members
  • 32 posts
  • OFFLINE
  •  
  • Local time:12:59 PM

Posted 22 October 2012 - 05:25 AM

you could try to download the latest driver files and boot into safe mode.
from there try and install the video driver through device manager




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users