Jump to content

Blue Screen of Death


BombaTwist

Recommended Posts

So yeah i got my new radeon HD 3850 and i put it in. i'm playing cs:source and its either when i minimize my game or i exit my game i randomly get the BSOD. i don't get it all the time but it happens randomly.

anyway i attached a picture of my BSOD. hope i can get some help! thanks ^^

bsod3850.jpg

Link to comment
Share on other sites


here's the tried and true answer to these problems with new video cards... did you already update your drivers to the latest version? if not, check ATI's site for the latest Catalyst package and install that. Also, what OS are you running? and, like ripken already asked, any overclocking?

Link to comment
Share on other sites

no oc'ing to ram at all. i have the latest drivers yes.

i'm not too completely sure if i've removed the drivers from my last card completely. i went to the device manager and removed the drivers for my old card(radeon x600se) there and that was about it.

how do i remove my drivers completely and install the new ones right? ><

edit: should i uninstall my drivers again through device manager and use driver cleaner pro in safe mode? then reinstall my drivers again?

Edited by BombaTwist
Link to comment
Share on other sites

English isn't my native idiom.

This isn't a Video Card problem, but RAM problem. Most mobo has the memory slots nearest the video card slot (doesn't matter if PCIE or AGP), when you make changes on your video card there's a strong possibility to touch the memory modules, without notice. Remove modules from slots and put them again. I got this problem with a bad memory module and the message was like this, exactly. Blue Screen from video crashes display the video card drive source of problem or anything related.

Link to comment
Share on other sites

English isn't my native idiom.

This isn't a Video Card problem, but RAM problem. Most mobo has the memory slots nearest the video card slot (doesn't matter if PCIE or AGP), when you make changes on your video card there's a strong possibility to touch the memory modules, without notice. Remove modules from slots and put them again. I got this problem with a bad memory module and the message was like this, exactly. Blue Screen from video crashes display the video card drive source of problem or anything related.

my ram slots are above my cpu and my video card slot is placed below my cpu.

btw i uninstalled my drivers, used driver cleaner pro to remove the rest.

i had to uninstall and reinstall the drivers 4 times x.x it was killing me! why?

because my ccc wouldn't load. x.x so i decided to use the cd packaged with my video card. and it worked!

i'll repost if i get the BSOD again. hopefully my problem is solved.

Link to comment
Share on other sites

so what can i do? pull them out and put them back in?

Everyone here is guessing. Read the debug log at bluescreens.homeserver.com (navigate to the BSOD page), install the debugger, debug the memory dumps you're doubtless getting, and post the output of '!analyze -v' here, and you'll then know for sure what the problem is.

Link to comment
Share on other sites

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: e1aba304, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: bf8afed3, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000001, (reserved)

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


Could not read faulting driver name



READ_ADDRESS: e1aba304

FAULTING_IP:
win32k!WatchdogDrvGetDirectDrawInfo+b1
bf8afed3 8b0e mov ecx,dword ptr [esi]

MM_INTERNAL_CODE: 1

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

TRAP_FRAME: a9df122c -- (.trap 0xffffffffa9df122c)
ErrCode = 00000000
eax=e8748bb0 ebx=e8748a24 ecx=bf16e990 edx=bf8c1a6a esi=e1aba304 edi=e74cc8a8
eip=bf8afed3 esp=a9df12a0 ebp=a9df12d0 iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210282
win32k!WatchdogDrvGetDirectDrawInfo+0xb1:
bf8afed3 8b0e mov ecx,dword ptr [esi] ds:0023:e1aba304=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from 8051c22b to 804f8c3f

STACK_TEXT:
a9df11b4 8051c22b 00000050 e1aba304 00000000 nt!KeBugCheckEx+0x1b
a9df1214 8053faac 00000000 e1aba304 00000000 nt!MmAccessFault+0x8e7
a9df1214 bf8afed3 00000000 e1aba304 00000000 nt!KiTrap0E+0xcc
a9df12d0 bf008af2 e1091080 e8748a24 a9df130c win32k!WatchdogDrvGetDirectDrawInfo+0xb1
a9df1318 bf009033 00000001 e74d3b90 a9df13a0 dxg!vDdEnableDriver+0x8a
a9df1334 bf892b95 e87482d8 00000001 e755e008 dxg!DxDdEnableDirectDraw+0xbf
a9df1354 bf8ad4e5 a9df14f4 e19ab820 00000000 win32k!PDEVOBJ::bMakeSurface+0xe2
a9df1380 bf8adee5 e19ab820 e217ebd0 e4a9eb60 win32k!hCreateHDEV+0x3a9
a9df14f8 bf8b4828 a9df15c0 00000000 00000001 win32k!DrvCreateMDEV+0x4dc
a9df15ec bf8b6a8d a9df15c0 e1a10008 00000000 win32k!DrvChangeDisplaySettings+0x251
a9df1630 bf8b6980 0012e330 00000000 00000000 win32k!xxxUserChangeDisplaySettings+0x141
a9df1658 8053cbc8 0012e330 00000000 00000000 win32k!NtUserChangeDisplaySettings+0x4a
a9df1658 7c90eb94 0012e330 00000000 00000000 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012e338 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!WatchdogDrvGetDirectDrawInfo+b1
bf8afed3 8b0e mov ecx,dword ptr [esi]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: win32k!WatchdogDrvGetDirectDrawInfo+b1

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 45f0146f

FAILURE_BUCKET_ID: 0x50_win32k!WatchdogDrvGetDirectDrawInfo+b1

BUCKET_ID: 0x50_win32k!WatchdogDrvGetDirectDrawInfo+b1

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

k im lost x.x

Link to comment
Share on other sites

OK, that points to win32k.sys - which is involved in (amongst other things) graphics display - those functions are involved in sending graphics data to your video driver, so have you tried running in safe mode or vga mode? Also, can you post that .dmp file here?

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...