Bluescreenofdea

These is steps of proceses I've done on my PC over couple of days

1. No logon box, lead me to re install windows, after couldn't repair.

2. Reinstaleld windows and reformated D drive

3. I installed motehr board drivers from CD, video card, monitor, windows update, direct X. Install all latest drivers.

4. Couldn't run, launch games.

5. uninstalled ATI drivers and downloaed Omega ones.

6. Could run games fine, but over last 3 times I've played games, twice during about an hour I got a Blue screen crash, this is details of some of it.


Page fault in nore page oea or something like that, page fault is right lol

ati3duas.dll Address BF268A5C base BF1700

Documen~\user\locals~1\temp\wcr3efe.dir00
Documen~\user\locals~1\temp\minio82409=01.dmp

Today i got Documen~\user\locals~1\temp\Mini02509-01.dmp

Dump of phsyical memory

Any ideas, I got 1 GB DDR2 RAm, Radeon x1650 pro 512mb ATI, Windows XP Home sp2, Intel 2.8Ghz.

What possible solutions can i try, List them and I will try them

THanks

Bluescreenofdea

I also see black parts in the game. Textures, graphics turn black.

MY PSU is 500w

ebackhus

What is the brand and model of your power supply?

Try removing the Omega drivers and use the ATI drivers.

Phædrus2401

What is the brand of the PSU?

What's your GPU temperature on the desktop and during games (before you crash)? Use GPU-Z to check: http://www.techpowerup.com/gpuz/

gameguru

Post the dump file someone from admin will look at it.
Navigate to Documen~\user\locals~1\temp\Mini02509-01.dmp.
You may want to look at your Ram perhaps, run Memtest on it to rule that out.

All the Best

Bluescreenofdea

The dump file being the Blue screen? or in that folder where abouts I can'ts see Mini, could it be a sub folder?


MY PSU, card and everything was running fine on games before reformat, nothing has changed. I've NEVER had any crashes and that before, settings are pretty much the same with maybe one setting higher. I noticed I see black parts of maps, then it loads.

Also I've just had the game just close and go to desktop. After presssing Esc to get to game menu

I've tried removing all drivers and using dirver cleaner, I folder some Nvdia files, I deleted them manually and throw drivercleaner, but on restart their still showing, they are files nv4_disp.dll and nv4_mini.

My memory hasnt changed, all programs even games run smoother, less lag, and my computer speed has benefited from the reformat. I quick formated my D drive. And installed updates, games and drivers.

I also have a windows 7 transofmration pack, just makes the taskbar and icons like windows 7, I had the same before system reformat, but just the vista version.

Bluescreenofdea

any help guys. I've been playing games on this system for 3 years now .I reformat install, and i got problems :(

Phædrus2401

We can't help you without *full* system specifications, *especially* the power supply and preferably the make and model of that x1650 as well.

Bluescreenofdea

Radeon x1650 Pro AGP 512mb
HN hands G LCD monitor
Artic cooler case with 500 watt PSU
Intel P 4 2.8 Ghz
1 GB DDR2 Ram
GIGAByte motherboard


It's a graphics card problem. My PSU hasn't changed, it indicates a graphics card problem. Not sure If I should reinstall games? But It's been 4 years, and since a reformat, I can't see why the PSU would make all the difference

Thanks
Rich

Phædrus2401

Because a power supply going bad can *cause* the graphics card to fail. We see it a lot on here. 500w should be sufficient for an x1650, but could you humor us and read off the brand?

joeten

hi you could try looking for the dump files in C:\windows\minidump

Bluescreenofdea

Sorry I do not know the brand
This is my case with the PSU
http://www.advancetec.co.uk/acatalog..._PFC_Case.html


This is the first BF2 dump

1.
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\Lewis\My Documents\Battlefield 2\dmp\bf2_v1.1.2965-797.0_2009-08-24_18.09.29.dmp]
User Mini Dump File: Only registers, stack and portions of memory are available

Comment: 'Battlefield2 MiniDump. Address: 04104371 (In Windbg type: .ecxr)
ASSERT INFORMATION:
[...]
D:\Aphrodite\BF2_1.4\Code\BF2\RendDX9\RendDX9Init.cpp(468): Error: RendDX9: Failed to create d3d device. Unknown cause. Invalid call
[EOF]'
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
Windows XP Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: SingleUserTS Personal
Machine Name:
Debug session time: Mon Aug 24 18:09:30.000 2009 (GMT+1)
System Uptime: not available
Process Uptime: 0 days 0:00:19.000
................................................................
.....
This dump file has a breakpoint exception stored in it.
The stored exception information can be accessed via .ecxr.
eax=00000000 ebx=00000000 ecx=00000002 edx=7efeff53 esi=00000384 edi=00000000
eip=7c90e514 esp=0012e834 ebp=0012e898 iopl=0 vif nv up ei pl zr na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00280246
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll.dll -
ntdll!KiFastSystemCallRet:
7c90e514 c3 ret


2.

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\Lewis\My Documents\Battlefield 2\dmp\bf2_v1.1.2965-797.0_2009-08-24_18.20.17.dmp]
User Mini Dump File: Only registers, stack and portions of memory are available

Comment: 'Battlefield2 MiniDump. Address: 04104371 (In Windbg type: .ecxr)
ASSERT INFORMATION:
[...]
D:\Aphrodite\BF2_1.4\Code\BF2\RendDX9\RendDX9Init.cpp(468): Error: RendDX9: Failed to create d3d device. Unknown cause. Invalid call
[EOF]'
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
Windows XP Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: SingleUserTS Personal
Machine Name:
Debug session time: Mon Aug 24 18:20:17.000 2009 (GMT+1)
System Uptime: not available
Process Uptime: 0 days 0:00:12.000
................................................................
.....
This dump file has a breakpoint exception stored in it.
The stored exception information can be accessed via .ecxr.
eax=00000000 ebx=00000000 ecx=00000002 edx=7efeff53 esi=00000388 edi=00000000
eip=7c90e514 esp=0012e834 ebp=0012e898 iopl=0 vif nv up ei pl zr na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00280246
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll.dll -
ntdll!KiFastSystemCallRet:
7c90e514 c3 ret


Not sure where to find any other .dmp. in the Documen~\user\locals~1\temp\ i found nothing using the search

Bluescreenofdea

OKAY THIS IS ONE OF 3 WINDOWS DUMPS I'VE FOUND IN THE FOLDER



Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini082509-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a6a0
Debug session time: Tue Aug 25 21:41:35.828 2009 (GMT+1)
System Uptime: 0 days 10:52:12.416
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
...
Loading User Symbols
Loading unloaded module list
.......................................
Unable to load image ati3duag.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ati3duag.dll
*** ERROR: Module load completed but symbols could not be loaded for ati3duag.dll
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {e9a5c0a0, 1, bf268a5c, 1}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : ati3duag.dll ( ati3duag+f8a5c )

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

Bluescreenofdea

Can anybody spot a problem from them logs, possibly?