Sven Gothel. I have to admit I am confused.. NV 8xxx driver For sure I am more than willing to triage these bugs if information is available, or I could even reproduce them. I guess we need a summary index of these bugs now, Wade? Thank you. I only need to know what to do and what to feedback : Here are the builds I tested for now : - b : works but very bad performances when antialiasing is enabled.
I'm sorry if I added confusion to this thread. I have updated bug report with additional information that the Nvidia problem is only with driver Now I'll let those with ATI continue the discussion. In reply to this post by Djak. I'm still working on this, tracing slowly through the code and trying to figure out what's going on. Hopefully I'll have something to report soon. Still digging into this.
This has been a good learning experience -- I never had to trace into JNI code and look at the assembly before. I think I've found the root cause of this bug. It looks like the GL context is not set up on the main thread. This one looks too hard for me to fix by myself, though I've looked at the code paths involved, and there's no obvious way to get a context set up on it.
We'll need to wait for Sven to do it so the fix makes sense with the rest of the code. Sven Gothel wrote. In reply to this post by Wade Walker. Then devide and conquer.. Hi : a few words to say I could put the laptop accessible via ssh, if needed. Hi, I've just tested on a Sapphire Radeon Atlantis where b worked but not newer builds and b works very fine. Thank you very much for the work Wade and Sven : Bye. In reply to this post by Djak I'm still working on this, tracing slowly through the code and trying to figure out what's going on.
I'm hoping that someone can point me to more information to use when solving this problem. I had a similar issue earlier this year after upgrading from WinXP to Windows 7. I opened a ticket with Microsoft and they were very diligent about trying to solve it but the only suggestions were to upgrade the drivers and BIOS. After installing the card, I installed the drivers that came with the card and then the latest drivers.
I began having crashes almost right away. Arguments: Arg1: c, Exception code that caused the bugcheck Arg2: fffffa, Address of the instruction which caused the bugcheck Arg3: fffffd1f, Address of the context record for the exception that caused the bugcheck Arg4: , zero.
Hi, Tip - because the 1st parameter was c suspect memory or other hardware reseat the card. If the system included on-board video be sure it is disabled in the BIOS.
Windows 7 Upgrade Advisor - please run this now. Check with the System maker Motherboard Maker for custom built systems and the Device maker for information about drivers for Windows 7.
BIOS, low level chipset drivers, and other major device drivers. Check with ATI Support and ask in their forums for known issues with those drivers. If you have the latest version then possible reverting back to an older version might help.
Some of it you do not need however I will post the entire message in case others have the same issue. We can analyze the minidumps if you make them available from the SkyDrive or other file sharing sites.
Windows Vista automatically restarts if your PC encounters an error that causes it to crash. Try removing and reseating all cards, memory, and cables both ends when possible - actually remove and replace - do not just snug on a PC and clean out the dust bunnies and vents.
On a laptop about all that can be done is reseat the memory and clean the vents. BCCode: 3b 0xb Cause. This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code. References to Vista also apply to Windows 7. For each driver in the list, additional useful information is displayed: load address of the driver, description, version, product name, company that created the driver, and more.
Control Panel - Device Manager - Display Adapter - write down the make and complete model of your video adapter - double click - Driver's tab - write down the version info. Always check in Device Manager - Drivers tab to be sure the version you are installing actually shows up. This is because some drivers rollback before the latest is installed sound drivers particularly do this so install a driver - reboot - check to be sure it is installed and repeat as needed.
Manually look at manufacturer's sites for drivers - and Device Maker's sites. So it is best to also swap sticks in and out to check for those even if all memory tests fail to show a problem. Was this reply helpful? Yes No. Sorry this didn't help. Thanks for your feedback. Ran this. When I rant it for the old card X Pro , it was fine for Win7. I just ran it for this card. Done already and updated already. Going to the ATI support web page just shows knowledgebase articles. Had Catalyst and removed it since a lot people have problems with it.
Some testing by others, one person at MS specifically, seemed to show that Catalyst was causing the problem.
0コメント