Jump to content

Rebooting


Dj Walker

Recommended Posts

Hey again :hello:

Im having another problem with my system rebooting i have reason to believe its my video card/drivers but i just want to make sure :} the card is in fact not on the motherboard compatible list :no:

this is the error i recently received last restart

BCCode : 1000000a BCP1 : 00000188 BCP2 : 00000002 BCP3 : 00000001

BCP4 : 804E7F3A OSVer : 5_1_2600 SP : 2_0 Product : 256_1

i tried to do the whole verifier process but i couldnt seem to get the error again in safe mode and my computer refused to start normaly with it enabled

Mini120507_01.zip

Link to comment
Share on other sites


Hey again :hello:

Im having another problem with my system rebooting i have reason to believe its my video card/drivers but i just want to make sure :} the card is in fact not on the motherboard compatible list :no:

this is the error i recently received last restart

BCCode : 1000000a BCP1 : 00000188 BCP2 : 00000002 BCP3 : 00000001

BCP4 : 804E7F3A OSVer : 5_1_2600 SP : 2_0 Product : 256_1

i tried to do the whole verifier process but i couldnt seem to get the error again in safe mode and my computer refused to start normaly with it enabled

Your processor may be overheating or you have an bad processor overclock.

This is a common symptom for first time processor overclockers.

Link to comment
Share on other sites

I... don't think win32k.sys is the culprit, but a victim of the display driver itself. Just because !analyze -v tells you a module is at fault doesn't mean it's right (it is usually, but not in situations like gde32 or win32k or ntdll, etc, api .dlls - these are usually victims, because some driver called an API they expose, and because we were using that API during the crash, !analyze -v tags that system file as the culprit).

// The STOP 0x50
1: kd> .bugcheck
Bugcheck code 10000050
Arguments 819af42f 00000000 bf9e14fe 00000000

// Thread running at the time of the bugcheck
1: kd> kb
ChildEBP RetAddr Args to Child
WARNING: Stack unwind information not available. Following frames may be wrong.
afd9409c bf9df4fa afd946b0 000004c0 00000494 ati2dvag+0xc4fe
afd94680 bfa0f837 e21f72d8 00000000 00000001 ati2dvag+0xa4fa
afd946f0 bf805da2 e2ae0e90 e3ca8010 00000000 ati2dvag+0x3a837
afd9473c bf86e78d e2ae0e90 e3ca8010 00000000 win32k!WatchdogDrvCopyBits+0x53
afd94784 bf86e5a5 bf805d56 afd9482c e2ae0e90 win32k!OffCopyBits+0x7d
afd94838 bf86e7da e2ae0e90 e3ca8010 00000000 win32k!SpBitBlt+0xfc
afd9486c bf80a587 e2ae0e90 e3ca8010 00000000 win32k!SpCopyBits+0x27
afd94900 804dd99f e2ae0e80 bf9a5740 e15c2de0 win32k!NtGdiBitBlt+0x51c
afd94900 7c90eb94 e2ae0e80 bf9a5740 e15c2de0 nt!KiFastCallEntry+0xfc
0012e31c 00000000 00000000 00000000 00000000 0x7c90eb94

// Registers - note that we're trying to write the data located in the memory pointed to
// by the esi register into the memory address at eax (0x000004c0), which is invalid,
// which is why we bugchecked:
1: kd> r
eax=000004c0 ebx=afd946b0 ecx=40cd7a17 edx=00000000 esi=819af42f edi=89b53240
eip=bf9e14fe esp=afd9408c ebp=afd9409c iopl=0 ov up ei pl nz na pe cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010a07
ati2dvag+0xc4fe:
bf9e14fe 8b06 mov eax,dword ptr [esi] ds:0023:819af42f=????????

// Invalid memory address, within the first 64K of VA which is marked
// PAGE_NO_ACCESS (always):
1: kd> dc 0x000004c0
000004c0 ???????? ???????? ???????? ???????? ????????????????
000004d0 ???????? ???????? ???????? ???????? ????????????????
000004e0 ???????? ???????? ???????? ???????? ????????????????
000004f0 ???????? ???????? ???????? ???????? ????????????????
00000500 ???????? ???????? ???????? ???????? ????????????????
00000510 ???????? ???????? ???????? ???????? ????????????????
00000520 ???????? ???????? ???????? ???????? ????????????????
00000530 ???????? ???????? ???????? ???????? ????????????????

// Driver responsible:
1: kd> lmvm ati2dvag
start end module name
bf9d5000 bfa18000 ati2dvag T (no symbols)
Loaded symbol image file: ati2dvag.dll
Image path: ati2dvag.dll
Image name: ati2dvag.dll
Timestamp: Wed May 03 12:51:00 2006 (4458DF74)
CheckSum: 0004D547
ImageSize: 00043000
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0

// The STOP 0xA
2: kd> .bugcheck
Bugcheck code 1000000A
Arguments 00000188 00000002 00000001 804e7f3a

// Looks like pool corruption, caused by a kernel-mode driver (usermode drivers don't
// corrupt pool directly in most cases):
2: kd> .trap 0xffffffffb0526498
ErrCode = 00000002
eax=00ffffff ebx=0000004b ecx=0000001d edx=0000010f esi=02de0000 edi=02de5000
eip=804e5160 esp=b052650c ebp=b0526540 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!RtlFillMemoryUlong+0x10:
804e5160 f3ab rep stos dword ptr es:[edi] es:0023:02de5000=????????

// The thread running at the time of the bugcheck:
2: kd> kb
*** Stack trace for last set context - .thread/.cxr resets it
ChildEBP RetAddr Args to Child
b052650c bf82f237 02de4c38 0000043c 00ffffff nt!RtlFillMemoryUlong+0x10
b0526540 bf82f0ae b05267b4 0000010f 02de0000 win32k!vSolidFillRect1+0x108
b05266c0 bf82bfa5 bf82f170 b05267b4 00000000 win32k!vDIBSolidBlt+0x19b
b052672c bf8053fb e1c012d8 00000000 00000000 win32k!EngBitBlt+0xe1
b052677c bf80c955 e176f424 b05267d0 b05267b4 win32k!GrePatBltLockedDC+0x1ea
b0526814 bf82f562 b052684c 0000f0f0 0012e7cc win32k!GrePolyPatBltInternal+0x17c
b0526868 804dd99f a9010cbd 00f00021 0012e7cc win32k!NtGdiPolyPatBlt+0xb5
b0526868 7c90eb94 a9010cbd 00f00021 0012e7cc nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012e7a8 00000000 00000000 00000000 00000000 0x7c90eb94

// Since this is a minidump, I can't see the driver that we're using, but these
// functions are for modifying video memory, so it's highly likely it is the same
// video driver as the previous dump, ati2dvag.sys.

Link to comment
Share on other sites

thnx :thumbup

alright so i guess new videocard it is.

i wait for a new card with drivers that should work with my mobo and then see how things go thnx guys :thumbup

Well, I'm not sure the card is at fault - go to ATI's site and get the latest drivers for your card first. Then, uninstall any ATI drivers/software you currently have installed, and reboot. Last, install the new ATI software and drivers you downloaded, and see if that helps.

Link to comment
Share on other sites

thnx :thumbup

alright so i guess new videocard it is.

i wait for a new card with drivers that should work with my mobo and then see how things go thnx guys :thumbup

Well, I'm not sure the card is at fault - go to ATI's site and get the latest drivers for your card first. Then, uninstall any ATI drivers/software you currently have installed, and reboot. Last, install the new ATI software and drivers you downloaded, and see if that helps.

i have tried that mostly of all the drivers possible for this card its its kinda outdated u can say radeon 9250 and my mobo is ASRock 4 core dual SATA2 link

and as for as the voltage idk i cant check CPU-Z or anything now im running in safe mode if it was undervolting wouldnt i still get this error in safe mode? everything seems to run fine in safe mode for some reason minus all the problems as my monitor randomly cutting off and random display problems and restarts. How can i check in realtime for this?

im actually waiting on this new card now off that vga supported list..it should be here anytime now today so i can actually check if its my card plus to be on the safe supported side

Edited by Dj Walker
Link to comment
Share on other sites

I can't remember the post, but there was another issue on this board that I debugged about a week ago with the same issue, and that poster ended up having to reinstall Windows and the latest Radeon driver, and the problem went away.

Link to comment
Share on other sites

I can't remember the post, but there was another issue on this board that I debugged about a week ago with the same issue, and that poster ended up having to reinstall Windows and the latest Radeon driver, and the problem went away.

i will most likely resort to that in the end maybe i just want to try this new card when it gets here

also i checked my voltage with speedfan its at 1.25 but the chart does show it going up and down and i do see it dropping to 1.23 is this what hes talking about? and btw i am running a q6600 link

ok i switched cards...installed driver mentioned on the manufacturer site....so far no restarts yet...will do some stress tests see what happens :)

looks like all is good guys thnx to everyone so much for your help :lol:

guess it really was the video card itself and driver :thumbdown

Edited by Dj Walker
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...