Welcome to the TechSpot OpenBoards. Please read the FAQ if you have any questions. Sign up or Login to participate.
|
|||||||
Download Now:
Minidump analysis. BSOD, help please
|
|
Thread Tools | Search this Thread |
|
#1
|
|||
|
|||
|
Minidump analysis. BSOD, help please
Well, i've had several BSOD in the last couples of months. Changed the MB and it seemed more stable. After that i had several more, regarding a Realtek audio driver, which, with a proper update, was fixed. Stability was paradise, up until now...
My specs: Gigabyte GA-MA69G-S3H, AMD690g Chipset DualCore AMD Athlon 64 X2 +4400@2305 1GB DDR2 800 Patriot x2/512 ATI Radeon HD 2600xt 256mb Thermaltake PurePower ATX 12v 2.0 460w OS: Windows XP Professional SP2 (up to date) Drivers: All up to date Anyway, i was playing Gears of War and when trying to quit the game, the PC BSOD'd with the following: *************************************************************************** **** * * * Bugcheck Analysis * * * *************************************************************************** **** Use !analyze -v to get detailed debugging information. BugCheck 10000050, {e1d0c304, 0, bf8afed3, 1} Could not read faulting driver name Probably caused by : win32k.sys ( win32k!WatchdogDrvGetDirectDrawInfo+b1 ) Followup: MachineOwner --------- 0: 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: e1d0c304, 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: e1d0c304 FAULTING_IP: win32k!WatchdogDrvGetDirectDrawInfo+b1 bf8afed3 8b0e mov ecx,dword ptr [esi] MM_INTERNAL_CODE: 1 CUSTOMER_CRASH_COUNT: 2 DEFAULT_BUCKET_ID: DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: WarGame-G4WLive LAST_CONTROL_TRANSFER: from bf008af2 to bf8afed3 STACK_TEXT: aaf07390 bf008af2 e1040080 e48a9754 aaf073cc win32k!WatchdogDrvGetDirectDrawInfo+0xb1 aaf073d8 bf009033 00000001 e14246d8 aaf07460 dxg!vDdEnableDriver+0x8a aaf073f4 bf892b95 e48a9008 00000001 e31499c8 dxg!DxDdEnableDirectDraw+0xbf aaf07414 bf8ad4e5 aaf075b4 e192de78 00000000 win32k!PDEVOBJ::bMakeSurface+0xe2 aaf07440 bf8adee5 e192de78 e3b7e8b0 e1f1e7c8 win32k!hCreateHDEV+0x3a9 aaf075b8 bf8b4828 aaf07680 00000000 00000001 win32k!DrvCreateMDEV+0x4dc aaf076ac bf8b6a8d aaf07680 e1f26008 00000000 win32k!DrvChangeDisplaySettings+0x251 aaf076f0 bf8b6980 024cf9e8 00000000 00000000 win32k!xxxUserChangeDisplaySettings+0x141 aaf07718 805409ac 024cf9e8 00000000 00000000 win32k!NtUserChangeDisplaySettings+0x4a aaf07718 7c91eb94 024cf9e8 00000000 00000000 nt!KiFastCallEntry+0xfc WARNING: Frame IP not in any known module. Following frames may be wrong. 024cf9f0 00000000 00000000 00000000 00000000 0x7c91eb94 STACK_COMMAND: kb FOLLOWUP_IP: win32k!WatchdogDrvGetDirectDrawInfo+b1 bf8afed3 8b0e mov ecx,dword ptr [esi] SYMBOL_STACK_INDEX: 0 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 --------- |
|
#2
|
|||
|
|||
|
same happened 1 day ago...this time with PES2008:
*************************************************************************** **** * * * Bugcheck Analysis * * * *************************************************************************** **** Use !analyze -v to get detailed debugging information. BugCheck 10000050, {e4ed4304, 0, bf8afed3, 1} Could not read faulting driver name Probably caused by : win32k.sys ( win32k!WatchdogDrvGetDirectDrawInfo+b1 ) Followup: MachineOwner --------- 0: 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: e4ed4304, 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: e4ed4304 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 PROCESS_NAME: PES2008.exe LAST_CONTROL_TRANSFER: from bf008af2 to bf8afed3 STACK_TEXT: 9837e9c0 bf008af2 e1342080 e4fdf754 9837e9fc win32k!WatchdogDrvGetDirectDrawInfo+0xb1 9837ea08 bf009033 00000001 e1e8cc00 9837ea90 dxg!vDdEnableDriver+0x8a 9837ea24 bf892b95 e4fdf008 00000001 e48f1008 dxg!DxDdEnableDirectDraw+0xbf 9837ea44 bf8ad4e5 00000000 e190eac8 00000000 win32k!PDEVOBJ::bMakeSurface+0xe2 9837ea70 bf8adee5 e190eac8 e1c4e550 e1bc6dd0 win32k!hCreateHDEV+0x3a9 9837ebe8 bf8b4828 9837ecb0 e895a838 00000001 win32k!DrvCreateMDEV+0x4dc 9837ecdc bf8b6a8d 9837ecb0 e160e008 00000000 win32k!DrvChangeDisplaySettings+0x251 9837ed20 bf8b6980 0022fb88 02f7ddf0 00000000 win32k!xxxUserChangeDisplaySettings+0x141 9837ed48 805409ac 0022fb88 02f7ddf0 00000000 win32k!NtUserChangeDisplaySettings+0x4a 9837ed48 7c91eb94 0022fb88 02f7ddf0 00000000 nt!KiFastCallEntry+0xfc WARNING: Frame IP not in any known module. Following frames may be wrong. 0022fb90 00000000 00000000 00000000 00000000 0x7c91eb94 STACK_COMMAND: kb FOLLOWUP_IP: win32k!WatchdogDrvGetDirectDrawInfo+b1 bf8afed3 8b0e mov ecx,dword ptr [esi] SYMBOL_STACK_INDEX: 0 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 --------- |
|
#3
|
||||
|
||||
|
Have you run a MemTest on your RAM?
|
|
#4
|
|||
|
|||
|
yes i did, let it pass 7 times as suggested and it passed.. :/
|
|
#5
|
|||
|
|||
|
Any suggestions anyone?
|
|
|
![]() |
| Similar Topics | ||||
| Topic | Replies | Forum | ||
Minidump analysis please
|
4 | Windows BSOD, Freezing, Restarting Help | ||
BSOD, Minidump File Analysis
|
1 | Windows BSOD, Freezing, Restarting Help | ||
Constant BSOD - help with analysis of minidump
|
9 | Device Drivers | ||
Please, help me analysis minidump.
|
1 | Windows BSOD, Freezing, Restarting Help | ||
0x000000d1 BSOD, minidump analysis requested
|
7 | Windows BSOD, Freezing, Restarting Help | ||
| Thread Tools | Search this Thread |
|
|
All times are GMT -4. The time now is 06:21 AM.



Minidump analysis please