Statement about Bannings and Malicous Rumors @ [H]

If anything, out of the thousands and thousands that have already been sold in North America, we can point to less than 15 cards being RMA’d in total to the companies listed above. Kyle @ HardOCP

Those numbers sound really good for a return rate, especially when you consider the issues with Prophet and his "170+" figure being returned.

I didn't expect Kyle to get so in depth of this fiasco, good looking out and I sure hope the other websites are focusing on this thread and learning a thing or two from Kyle, squash the bullshit, get the truth out there.
 
Nice work there Kyle. Any bets on whether or not The Inquirer will post an update or retraction? ;)
 
Personally, I see [H] as not your average computer forums.
I see [H] as an enthusiast site that holds itself to a higher, more mature standard then many others.
Keeping the facts up, and nub flamewars down. With the hundreds of other forums on the internet, I applaud [H] for doing what it can to resist the bandwagon bullshit threads.
 
There are a lot of reasons I have been reading HardOCP for 10 years now. This, is one of them. Not only do Kyle and Crew know how to keep their forums clean, but they know how to treat their readers with some respect. From in depth reviews all the way to getting to the bottom, and I mean bottom line of a rumor, Kyle and Crew are there to keep us informed 24/7.

Keep up the great work and please don't let a few bad apples bring you down!
 
170 isn't even a bad rate, if its taken as a whole. If the GT has only sold 10,000 units, a 2% return rate would be 200 units. I think the original poster claimed that one CSR alone had 170 returns, multiplied by several CSR's is ONE BILLION BAD CARDS GUYS LETS SHIT BRICKS.
 
I don't see what the guy's problem is really. Crap happens. If I got upset everytime I bought something new and it was bad or went bad in a very short time, I would be dead from a heart attack.

I've owned BFG products and have dealt with their tech support and RMA system and they have always been awesome. They are quick and have cross shipped and so on. One of the best companies out there to deal with, along with XFX.

Nice going Kyle for getting to and publishing the truth.
 
The [H] is my homepage, I come here several times a day to check for news and reviews. I like how he pulls no punches and calls a spade a spade, and doesn't back down when threatened. I also like how he helps support other review sites by posting reviews they have done.
I got to say my opinion is a bit biased in that I don't visit hardly any of the other sites unless they have a review I am interested in. I really don't feel like I even need to as I get the news I want and the honest opinions!

This is just another reason I like the [H], Kyle don't care if it is an individual or multibillion dollar corporation, you start spreading the BS, Kyles gonna be there to rub your face in it!!!!
 
This is a difficult issue. The bannee's lie could have been less obvious, eg 17 cards instead of 170, and he could have gotten away with it and still have done some damage. In fact, anyone can lie about having serious errors with a single card and thus damage the brand's reputation, and no questions would be asked. Typically, lonely people with low self-esteem may lie about such things just to get some attention.
 
Or better yet claim how Kyle/Steve is raking in the money for paid reviews.

If that were true, Kyle would censor what I write in my motherboard reviews. To date he has never done anything of the kind. I think many people will agree that I am one of the most difficult to please or impress when it comes to hardware.
 
Kyle (and the rest of ya), please keep up the good work, don't ever think it goes unnoticed. :)


Agreed

It doesnt here on my end.I have told many people that [H] is the place to go to,for honest insight into the pc world.
 
So, I bought a BFG 8800 GT OC 512 meg from CompUsa last night (got a great deal from a friend).

My machine runs XP64 SP2 all updates with 8 gigs of memory, Radeon x1900xtx, Dual 290 Opterons on a K8WE board (dual nforce), 800W power supply. It is also my main Dev PC so it absolutely must be stable and has been for 9 months now.

I put the card in, installed the drivers (169.02). BSOD. Since I develop drivers also, I figured I would take a look at the crashdump. The bugcheck is: SYSTEM_PTE_MISUSE (da) but you will you will probably see it as Driver mismanaging system PTE. (Page Table Entry)

If you use the VGA driver, it is stable all day, all nite. However with 169.02 or .04 drivers, different story. Now, the BSOD only happens when an accelerated action is requested or any 3d operation. Pull up a browser with flash, you may crash out. Open up the display panel, you will crash out. It is easy to reproduce. It took about 30 minutes last night to get through, and troubleshoot with the support tech. Good guy, good manners, kudos to BFG on the support.

Unfortunately, he gave a bad diagnosis that the video memory on the card was bad. I like to make sure of things so I put it in my other test PC. It has a clean copy of XP32, 64, vista32 and 64. I fired up the XP64 copy which was running SP1. Installed the card, installed the driver, rebooted. No issues. Ran crysis demo as a test, no issues. Rock solid. I installed SP2 on the test PC and retested, no issues.

Now I have only started researching this, but in the crash dump. The dump is suggesting that our offender here is: nv4_mini!grContextInstanceToObject+0xf which is flagging nv4_mini.sys and nv4_disp.dll. No I did not export the nv4_mini.sys, but windbg says its a routine in there.

So, if you are running XP64, there is something that is causing an issue. If you do a google search on "mismanaging pte xp 64 nvidia" you will find this is an old issue that has been around, but never addressed (or at least from what I could find). I think the sudden rage is because the 8800 GT is a compelling reason to get a new card. More people, more squeaky wheels, more flame.

If I can get more time, I will begin to dissect whats going on. Both test PC and my main PC have the same NTOSKRNL (5.2.3790.4045) and VIDEOPORT.SYS (5.2.3790.3959) which is the last update I had seen (hotfix from in october).

Call chain is as follows from newest to oldest (you read from bottom up) and all 5 dumps I have are completely identical:

nt!KeBugCheckEx (Say hello to Mr. Blue screen)
nt!MmUnmapIoSpace+0x37b (NTOSKRNL.EXE)
VIDEOPRT!pVideoPortFreeDeviceBase+0x93 (VIDEOPRT.SYS) - (NV4_Mini.sys)
VIDEOPRT!VideoPortUnmapMemory+0xe (VIDEOPRT.SYS) - (NV4_Mini.sys)
nv4_mini!grContextInstanceToObject+0xf

I'll start tearing it apart later, but I do have to say that I'm a little irritated that putting a video card in my system that was completely stable shouldn't force me to reload my OS or start doing low level debugging.

I called BFG back, waited for another tech and reported my findings. But from what I see preliminarily, this isnt a hardware issue, its more of a driver / OS update issue that has been around awhile.

One other thing. I also cleaned all traces of ATI and Nvidia out of the system and retested twice, same crashing result.

--Royal
 
So, I bought a BFG 8800 GT OC 512 meg from CompUsa last night (got a great deal from a friend).

My machine runs XP64 SP2 all updates with 8 gigs of memory, Radeon x1900xtx, Dual 290 Opterons on a K8WE board (dual nforce), 800W power supply. It is also my main Dev PC so it absolutely must be stable and has been for 9 months now.

I put the card in, installed the drivers (169.02). BSOD. Since I develop drivers also, I figured I would take a look at the crashdump. The bugcheck is: SYSTEM_PTE_MISUSE (da) but you will you will probably see it as Driver mismanaging system PTE. (Page Table Entry)

If you use the VGA driver, it is stable all day, all nite. However with 169.02 or .04 drivers, different story. Now, the BSOD only happens when an accelerated action is requested or any 3d operation. Pull up a browser with flash, you may crash out. Open up the display panel, you will crash out. It is easy to reproduce. It took about 30 minutes last night to get through, and troubleshoot with the support tech. Good guy, good manners, kudos to BFG on the support.

Unfortunately, he gave a bad diagnosis that the video memory on the card was bad. I like to make sure of things so I put it in my other test PC. It has a clean copy of XP32, 64, vista32 and 64. I fired up the XP64 copy which was running SP1. Installed the card, installed the driver, rebooted. No issues. Ran crysis demo as a test, no issues. Rock solid. I installed SP2 on the test PC and retested, no issues.

Now I have only started researching this, but in the crash dump. The dump is suggesting that our offender here is: nv4_mini!grContextInstanceToObject+0xf which is flagging nv4_mini.sys and nv4_disp.dll. No I did not export the nv4_mini.sys, but windbg says its a routine in there.

So, if you are running XP64, there is something that is causing an issue. If you do a google search on "mismanaging pte xp 64 nvidia" you will find this is an old issue that has been around, but never addressed (or at least from what I could find). I think the sudden rage is because the 8800 GT is a compelling reason to get a new card. More people, more squeaky wheels, more flame.

If I can get more time, I will begin to dissect whats going on. Both test PC and my main PC have the same NTOSKRNL (5.2.3790.4045) and VIDEOPORT.SYS (5.2.3790.3959) which is the last update I had seen (hotfix from in october).

Call chain is as follows from newest to oldest (you read from bottom up) and all 5 dumps I have are completely identical:

nt!KeBugCheckEx (Say hello to Mr. Blue screen)
nt!MmUnmapIoSpace+0x37b (NTOSKRNL.EXE)
VIDEOPRT!pVideoPortFreeDeviceBase+0x93 (VIDEOPRT.SYS) - (NV4_Mini.sys)
VIDEOPRT!VideoPortUnmapMemory+0xe (VIDEOPRT.SYS) - (NV4_Mini.sys)
nv4_mini!grContextInstanceToObject+0xf

I'll start tearing it apart later, but I do have to say that I'm a little irritated that putting a video card in my system that was completely stable shouldn't force me to reload my OS or start doing low level debugging.

I called BFG back, waited for another tech and reported my findings. But from what I see preliminarily, this isnt a hardware issue, its more of a driver / OS update issue that has been around awhile.

One other thing. I also cleaned all traces of ATI and Nvidia out of the system and retested twice, same crashing result.

--Royal


That odd, I installed my 8800GT on XP64 SP2 this afternoon, and have had no problems yet. I've played videos run UT3, Crysis, and Oblivion, and fooled about on the internet, and gotten no crashes, besides some business trying to get HDR+AA to work on Oblivion. I'm using the latest beta drivers. Should this affect all XP64 SP2 users?

Specs:

Asus A8N SLI Premium
Opteron 165 OCed to 2.4GHz
2GB DDR 400
EVGA 8800GT (Super Clocked apparently. The box says it's a regular one, but it runs at 650/1950)
Windows XP x64 SP2
 
Honestly, I dont think it will affect all SP2 users. From the thread history i could piece together, It seemed to appear when SP2 came out, but was never really addressed. However, I did run it on my test PC with SP1, updated to SP2, and had no issues as well.

My only thought is perhaps an interim hotfix that may have come out between SP1 and SP2 (january to march) that may have stuck or something. I loaded the test machine back in June, Just never service packed it. But it worked just fine with the card.

It is an isolated bug of some sort since I only see a handful of threads out on the net about it. But I was unable to find a resolve outside of reloading your OS to fix the situation. For some its no big deal, but for me, its a full weekend chore due to the number of SDKs, dev studio tools, debuggers and etc I use.

That said, if more people run into the same issue as I have, it may be something that needs to be addressed.

--Royal
 
Well good luck fixing it. Xp64 is a great OS, but it's not supported with a darn.
 
I completely agree.

Once you get past the driver thing (which has improved significantly), it is just flat out rock solid. I cant remember the last time I actually had to hold the power button down to get out of a hard lock and thats with it under 6Gb+ memory load + procs getting pounded. (3 VMs, couple compilers, editors, debuggers / etc).
 
Thank you Kyle for getting to the bottom of this, I think banning is a little extream but there is nothing else that I can come up with that would shock the original poster enufh to do anything. as for the RMAs, I can't speak in any official capacity regarding EVGA but as a lvl2 tech for them and dealing with customers on a daily basis and the MASSIVE and I mean MASSIVE amount of just calls with questions about the 8800GT, I personally have only fielded 2 calls regarding problems with the 8800GT, one was a software issue that took a while to figure out (it was something to do with the old drivers from the customers previous video card) and the second card which had a fan fail on it and I set up an RMA for that customer. the rest were just general tech support questions regarding installing he card and drivers. and I have not heard from the other CS Reps either about the cards failing.
 
RMA on the GTS here is highest of all cards according to some people, never heard of GT, btw. norwegian temperatures is harsh, from hot to cold hot to cold. its killing nvidia's chips, experienced it alot with nvidia. so I'm a faithfull ati user now.

Norway is VERY cold at wintertimes can be 40- celcius etc.

Who'd expect a card should survive that, well after my personal experience is ati better in quality at that area, and overheating perhaps, was I can tell ya.

Hardocp should do, what happens if we disconnect the fan on the videocard. to see if there can be overheating issues, with HD series x1000 series 7xxx 8xxx cards
 
Thank you, too often one person can start a ripple that turns into a wave unless it is dealt with. You went far beyond the extra mile.

Thanks
 
So, I bought a BFG 8800 GT OC 512 meg from CompUsa last night (got a great deal from a friend).

--Royal


Great feedback Royal! You are the man. I have sent this post link to NVIDIA, BFGTech, EVGA, and XFX with you CCd.
 
RMA on the GTS here is highest of all cards according to some people, never heard of GT, btw. norwegian temperatures is harsh, from hot to cold hot to cold. its killing nvidia's chips, experienced it alot with nvidia. so I'm a faithfull ati user now.

Norway is VERY cold at wintertimes can be 40- celcius etc.

Who'd expect a card should survive that, well after my personal experience is ati better in quality at that area, and overheating perhaps, was I can tell ya.

Hardocp should do, what happens if we disconnect the fan on the videocard. to see if there can be overheating issues, with HD series x1000 series 7xxx 8xxx cards

Yes, the card can overheat if you unplug the fan. No testing required to answer that. Now if you are in Norway outside at -40C, YMMV. ;)
 
I got my 8800GT in yesterday and I have no problems yet. The fan does ramp the frack up upon bootup though. I thought something was goinig to explode. But playing crysis as it was meant to be played is something i would pay $236 for again and again.
 
The well known "bottom line" with Kyle is don't cross him. sure he can be brutal or an outright asshole to some in his axe swinging endeavors (and even in some of his reviews) but who here expects him to write a song or a poem expressing grief, regret or mourning when lowering the boom on someone or some company? i sure as hell don't and if i ever hear that song or read that poem here it will be the day i find a new site to read first thing in the morning as [H] has been for the last decade.

Kyle and Steve thank you for everything you do with [H].

- Robert (PmR)DeathInJune

I can only hope the same level of enthusiasm will be applid to Nvidia by the Hard staff, if Nvidia shit-bags on the 1TF in 07 deal.

I would love to see the boy's that run the tech forums, to help us enthusiasts voyce our disappointment to Nvidia....
 
I can only hope the same level of enthusiasm will be applid to Nvidia by the Hard staff, if Nvidia shit-bags on the 1TF in 07 deal.

I would love to see the boy's that run the tech forums, to help us enthusiasts voyce our disappointment to Nvidia....

Why? It wouldn't be the first time a tech company has missed their ETA on a product... I don't see how there is any reason to be upset at them over this. When they launch it, they launch it and I'll expect it to be a hardlaunch and in stores the day reviews hit the web =)

nVidia is far better than any others with all their hard launches.
 
I can tell you weren't waiting months on this cards release, nor do you seem have any disappointment about the situaction.

If you were, mabey then you could see a reason to be upset?

I believed their VP. My bad.

I won't let it happin again.
 
So, I bought a BFG 8800 GT OC 512 meg from CompUsa last night (got a great deal from a friend).

I put the card in, installed the drivers (169.02). BSOD. Since I develop drivers also, I figured I would take a look at the crashdump. The bugcheck is: SYSTEM_PTE_MISUSE (da) but you will you will probably see it as Driver mismanaging system PTE. (Page Table Entry)

If you use the VGA driver, it is stable all day, all nite. However with 169.02 or .04 drivers, different story. Now, the BSOD only happens when an accelerated action is requested or any 3d operation. Pull up a browser with flash, you may crash out. Open up the display panel, you will crash out. It is easy to reproduce. It took about 30 minutes last night to get through, and troubleshoot with the support tech. Good guy, good manners, kudos to BFG on the support.


Lol, that is how my XFX card acted. Can't believe it was just a driver issue though, since I picked up another 8800gt from BFG and it did not lock up like the XFX card did. Performance though with the 169.02 - 04 drivers is horrible, only around 5fps. This is on Vista 64...


Ply
 
You've lost a reader here, unforunately, the handling of this situation has severely damaged by view on HardOCP and it's members and owners. The person who was banned may have overreacted, very much so even, but to then start banning others because they agreed with him or did not agree with the ban is inexcusable.

On top of that you also publicly annouced his ban along with the others, I was lead to believed that on a site as large as this these situations would be handled privately and gracefully, I was severely mislead. This has essentially become a forum lynching of its members.

I thank all of those HardOCP members who have helped me in the past. I know that I am not active on the forums, but I hope what I say will not be deleted or my account banned for my words.
 
You've lost a reader here, unforunately, the handling of this situation has severely damaged by view on HardOCP and it's members and owners. The person who was banned may have overreacted, very much so even, but to then start banning others because they agreed with him or did not agree with the ban is inexcusable.

On top of that you also publicly annouced his ban along with the others, I was lead to believed that on a site as large as this these situations would be handled privately and gracefully, I was severely mislead. This has essentially become a forum lynching of its members.

I thank all of those HardOCP members who have helped me in the past. I know that I am not active on the forums, but I hope what I say will not be deleted or my account banned for my words.


See you later! And I bet you still read the free articles. I dare you not to come back and miss all the good stuff coming up. :p
 
Plywood:

Please note that this was for XP64. I have not seen any issues with vista 32 or 64 and this particular issue. If your system made a minidump (C:\windows\minidump) thats under a meg, I'd be interested to see if its the same thing going on.

That said, loading up my rig is always a pain, so I keep a 25 gig partition backup of a clean image with half of everything loaded (yep, its the weekend, and I would like to get on to this 8800GT). I backed up my crashing partition (45 gig) and rolled back. It was still on SP1 dated december 2006. I loaded up the 169.02 drivers and the card is stable, no BSODs.

I'm going to install all service packs and bring my stuff back up to date. And see how it fares. My thought is that if i can get back to where I was before and no crashes, then I'll be more inclined to think there was an interim service pack in those 3 months that screwed things up.

I have seen MS push updates for one item and update the version on another file without you really knowing it. I've also seen updates where a file was updated in a hot fix marked 'beta retail' with a higher build number, then when the next service pack comes out, or hotfix with a final retail on it, it skips that beta file because of the versioning.

Update: And on a side note... Installed SP2, and BSOD. Mismanaging PTEs, so something in SP2 is whats blowing things up.

Update: Uninstalled SP2, and its stable again.

--Royal
 
Please post all information from the blue screen, including all parameters and any other information displayed. I'll see what I can find.

Thanks,
-Raystonn

PM me your email and I will send you the minidump.
 
OBWANDO,

I have a possible fix for you. SP2 comes with a new HAL, which unfortunately breaks some drivers during the upgrade process.

Create a slipstreamed CD with the network full version of XP64 SP2 (not the web update version) and the latest version of IE7. Do a clean install of that slipstreamed version of Windows, then install the latest NVIDIA drivers. Let us know how it goes.

I realize that reinstalling your operating system is a major nuisance. But this should be able to get you operational at least.

-Raystonn
 
I had read that somewhere. I am downloading the Windows 2003 server SP2 64-bit(since the XP SP2 is only 32 bit) net install, and lets see how it goes. The same filename is referenced from the XP64 SP2 and Win2k3 SP2 for net installs.

WindowsServer2003.WindowsXP-KB914961-SP2-x64-ENU.exe

Here is the stack. I wouldnt worry about the process name named here as it may (and usually is) whatever was in process at the time.
One thing to note from the Microsoft Driver docs:

Callers of VideoPortUnmapMemory, (which calls MmUnmapIoSpace and also) must be running at IRQL = PASSIVE_LEVEL
And you can see that in this case, we are elevated when the call was made. Maybe a forgotten check to KeGetCurrentIrql() for a safe call in nv4_mini!grContextInstanceToObject?

BugCheck DA, {400, fffffadf111c5000, 420, 0}

Unable to load image nv4_mini.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nv4_mini.sys
Unable to load image nv4_disp.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nv4_disp.dll
Probably caused by : nv4_mini.sys ( nv4_mini!grContextInstanceToObject+f )

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

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_PTE_MISUSE (da)
The stack trace identifies the guilty driver.
Arguments:
Arg1: 0000000000000400, Type of error.
Arg2: fffffadf111c5000
Arg3: 0000000000000420
Arg4: 0000000000000000

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


CUSTOMER_CRASH_COUNT: 3

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xDA

PROCESS_NAME: nvcplui.exe

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff800010e328e to fffff8000102e950

STACK_TEXT:
fffffadf`13b301b8 fffff800`010e328e : 00000000`000000da 00000000`00000400 fffffadf`111c5000 00000000`00000420 : nt!KeBugCheckEx
fffffadf`13b301c0 fffffadf`20783a83 : fffffadf`349beeb0 fffffadf`349beca0 00000000`00000000 fffffadf`37c76d30 : nt!MmUnmapIoSpace+0x37b
fffffadf`13b302b0 fffffadf`207870ee : fffffadf`37eda5f0 fffffadf`13b30380 fffffadf`381d0830 fffffadf`111c5000 : VIDEOPRT!pVideoPortFreeDeviceBase+0x93
fffffadf`13b302e0 fffffadf`25ed962f : 00000000`40000014 fffffadf`25f03424 00000000`00000000 00000000`00000001 : VIDEOPRT!VideoPortUnmapMemory+0xe
fffffadf`13b30310 00000000`40000014 : fffffadf`25f03424 00000000`00000000 00000000`00000001 00000000`00000001 : nv4_mini!grContextInstanceToObject+0xf
fffffadf`13b30318 fffffadf`25f03424 : 00000000`00000000 00000000`00000001 00000000`00000001 fffffadf`111c5000 : 0x40000014
fffffadf`13b30320 00000000`00000000 : 00000000`00000001 00000000`00000001 fffffadf`111c5000 00000000`00000000 : nv4_mini!class046SetImageValues+0x44
fffffadf`13b30328 00000000`00000001 : 00000000`00000001 fffffadf`111c5000 00000000`00000000 fffffadf`25eb18fb : 0x0
fffffadf`13b30330 00000000`00000001 : fffffadf`111c5000 00000000`00000000 fffffadf`25eb18fb 00000000`00000001 : 0x1
fffffadf`13b30338 fffffadf`111c5000 : 00000000`00000000 fffffadf`25eb18fb 00000000`00000001 fffffadf`13b306c0 : 0x1
fffffadf`13b30340 00000000`00000000 : fffffadf`25eb18fb 00000000`00000001 fffffadf`13b306c0 00000000`00000001 : 0xfffffadf`111c5000
fffffadf`13b30348 fffffadf`25eb18fb : 00000000`00000001 fffffadf`13b306c0 00000000`00000001 fffffadf`26177387 : 0x0
fffffadf`13b30350 00000000`00000001 : fffffadf`13b306c0 00000000`00000001 fffffadf`26177387 fffffa80`00000014 : nv4_mini!dacConstructDisplay_Generic+0xfb
fffffadf`13b30358 fffffadf`13b306c0 : 00000000`00000001 fffffadf`26177387 fffffa80`00000014 fffffadf`26177387 : 0x1
fffffadf`13b30360 00000000`00000001 : fffffadf`26177387 fffffa80`00000014 fffffadf`26177387 fffffadf`37eda5f0 : 0xfffffadf`13b306c0
fffffadf`13b30368 fffffadf`26177387 : fffffa80`00000014 fffffadf`26177387 fffffadf`37eda5f0 00000000`00000000 : 0x1
fffffadf`13b30370 fffffa80`00000014 : fffffadf`26177387 fffffadf`37eda5f0 00000000`00000000 fffffadf`348ed960 : nv4_mini!_NULL_IMPORT_DESCRIPTOR <PERF> (nv4_mini+0x329387)
fffffadf`13b30378 fffffadf`26177387 : fffffadf`37eda5f0 00000000`00000000 fffffadf`348ed960 fffffadf`00000000 : 0xfffffa80`00000014
fffffadf`13b30380 fffffadf`37eda5f0 : 00000000`00000000 fffffadf`348ed960 fffffadf`00000000 00000000`80222004 : nv4_mini!_NULL_IMPORT_DESCRIPTOR <PERF> (nv4_mini+0x329387)
fffffadf`13b30388 00000000`00000000 : fffffadf`348ed960 fffffadf`00000000 00000000`80222004 fffffadf`381b2ca0 : 0xfffffadf`37eda5f0
fffffadf`13b30390 fffffadf`348ed960 : fffffadf`00000000 00000000`80222004 fffffadf`381b2ca0 fffffadf`37fb81d0 : 0x0
fffffadf`13b30398 fffffadf`00000000 : 00000000`80222004 fffffadf`381b2ca0 fffffadf`37fb81d0 00000000`00000000 : 0xfffffadf`348ed960
fffffadf`13b303a0 00000000`80222004 : fffffadf`381b2ca0 fffffadf`37fb81d0 00000000`00000000 00000000`00000000 : 0xfffffadf`00000000
fffffadf`13b303a8 fffffadf`381b2ca0 : fffffadf`37fb81d0 00000000`00000000 00000000`00000000 fffffadf`25ed4488 : 0x80222004
fffffadf`13b303b0 fffffadf`37fb81d0 : 00000000`00000000 00000000`00000000 fffffadf`25ed4488 fffffadf`37fae160 : 0xfffffadf`381b2ca0
fffffadf`13b303b8 00000000`00000000 : 00000000`00000000 fffffadf`25ed4488 fffffadf`37fae160 00000000`00000000 : 0xfffffadf`37fb81d0
fffffadf`13b303c0 00000000`00000000 : fffffadf`25ed4488 fffffadf`37fae160 00000000`00000000 00000000`00000000 : 0x0
fffffadf`13b303c8 fffffadf`25ed4488 : fffffadf`37fae160 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
fffffadf`13b303d0 fffffadf`37fae160 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffadf`385c91c0 : nv4_mini!dacSetFlatPanelMode+0x3f8
fffffadf`13b303d8 00000000`00000000 : 00000000`00000000 00000000`00000000 fffffadf`385c91c0 00000000`00000001 : 0xfffffadf`37fae160
fffffadf`13b303e0 00000000`00000000 : 00000000`00000000 fffffadf`385c91c0 00000000`00000001 00000000`80222004 : 0x0
fffffadf`13b303e8 00000000`00000000 : fffffadf`385c91c0 00000000`00000001 00000000`80222004 00000000`00000000 : 0x0
fffffadf`13b303f0 fffffadf`385c91c0 : 00000000`00000001 00000000`80222004 00000000`00000000 fffffadf`37f2d010 : 0x0
fffffadf`13b303f8 00000000`00000001 : 00000000`80222004 00000000`00000000 fffffadf`37f2d010 fffffadf`37fb81d0 : 0xfffffadf`385c91c0
fffffadf`13b30400 00000000`80222004 : 00000000`00000000 fffffadf`37f2d010 fffffadf`37fb81d0 fffffadf`34904a50 : 0x1
fffffadf`13b30408 00000000`00000000 : fffffadf`37f2d010 fffffadf`37fb81d0 fffffadf`34904a50 fffffadf`25e98b3b : 0x80222004
fffffadf`13b30410 fffffadf`37f2d010 : fffffadf`37fb81d0 fffffadf`34904a50 fffffadf`25e98b3b fffff97f`ff55f050 : 0x0
fffffadf`13b30418 fffffadf`37fb81d0 : fffffadf`34904a50 fffffadf`25e98b3b fffff97f`ff55f050 fffffadf`88200000 : 0xfffffadf`37f2d010
fffffadf`13b30420 fffffadf`34904a50 : fffffadf`25e98b3b fffff97f`ff55f050 fffffadf`88200000 00000000`00000000 : 0xfffffadf`37fb81d0
fffffadf`13b30428 fffffadf`25e98b3b : fffff97f`ff55f050 fffffadf`88200000 00000000`00000000 fffff6fc`00000124 : 0xfffffadf`34904a50
fffffadf`13b30430 fffff97f`ff55f050 : fffffadf`88200000 00000000`00000000 fffff6fc`00000124 fffffadf`00000000 : nv4_mini!dacEarlyMonitorSync+0x1eb
fffffadf`13b30438 fffffadf`88200000 : 00000000`00000000 fffff6fc`00000124 fffffadf`00000000 fffff800`00000000 : nv4_disp!CDP2GPU<CDxTri>::nvDP2CaptureSetRenderState+0x20
fffffadf`13b30440 00000000`00000000 : fffff6fc`00000124 fffffadf`00000000 fffff800`00000000 fffffadf`00000590 : 0xfffffadf`88200000
fffffadf`13b30448 fffff6fc`00000124 : fffffadf`00000000 fffff800`00000000 fffffadf`00000590 00000000`00000001 : 0x0
fffffadf`13b30450 fffffadf`00000000 : fffff800`00000000 fffffadf`00000590 00000000`00000001 00000000`80222004 : 0xfffff6fc`00000124
fffffadf`13b30458 fffff800`00000000 : fffffadf`00000590 00000000`00000001 00000000`80222004 00000000`00000000 : 0xfffffadf`00000000
fffffadf`13b30460 fffffadf`00000590 : 00000000`00000001 00000000`80222004 00000000`00000000 fffffadf`13b306b8 : 0xfffff800`00000000
fffffadf`13b30468 00000000`00000001 : 00000000`80222004 00000000`00000000 fffffadf`13b306b8 fffffadf`385c95a8 : 0xfffffadf`00000590
fffffadf`13b30470 00000000`80222004 : 00000000`00000000 fffffadf`13b306b8 fffffadf`385c95a8 00000000`00000000 : 0x1
fffffadf`13b30478 00000000`00000000 : fffffadf`13b306b8 fffffadf`385c95a8 00000000`00000000 fffffadf`2673b663 : 0x80222004
fffffadf`13b30480 fffffadf`13b306b8 : fffffadf`385c95a8 00000000`00000000 fffffadf`2673b663 fffff6fc`bfffaaf8 : 0x0
fffffadf`13b30488 fffffadf`385c95a8 : 00000000`00000000 fffffadf`2673b663 fffff6fc`bfffaaf8 00000000`00000000 : 0xfffffadf`13b306b8
fffffadf`13b30490 00000000`00000000 : fffffadf`2673b663 fffff6fc`bfffaaf8 00000000`00000000 00000000`00000000 : 0xfffffadf`385c95a8
fffffadf`13b30498 fffffadf`2673b663 : fffff6fc`bfffaaf8 00000000`00000000 00000000`00000000 00000000`00000110 : 0x0
fffffadf`13b304a0 fffff6fc`bfffaaf8 : 00000000`00000000 00000000`00000000 00000000`00000110 fffff97f`ff55f050 : nv4_mini!_NULL_IMPORT_DESCRIPTOR <PERF> (nv4_mini+0x8ed663)
fffffadf`13b304a8 00000000`00000000 : 00000000`00000000 00000000`00000110 fffff97f`ff55f050 00000000`00000000 : 0xfffff6fc`bfffaaf8
fffffadf`13b304b0 00000000`00000000 : 00000000`00000110 fffff97f`ff55f050 00000000`00000000 00000000`aebc4801 : 0x0
fffffadf`13b304b8 00000000`00000110 : fffff97f`ff55f050 00000000`00000000 00000000`aebc4801 fffff800`0104a8e9 : 0x0
fffffadf`13b304c0 fffff97f`ff55f050 : 00000000`00000000 00000000`aebc4801 fffff800`0104a8e9 fffff97f`00000000 : 0x110
fffffadf`13b304c8 00000000`00000000 : 00000000`aebc4801 fffff800`0104a8e9 fffff97f`00000000 00000000`80000009 : nv4_disp!CDP2GPU<CDxTri>::nvDP2CaptureSetRenderState+0x20
fffffadf`13b304d0 00000000`aebc4801 : fffff800`0104a8e9 fffff97f`00000000 00000000`80000009 00000000`00000001 : 0x0
fffffadf`13b304d8 fffff800`0104a8e9 : fffff97f`00000000 00000000`80000009 00000000`00000001 00000000`000aebc4 : 0xaebc4801
fffffadf`13b304e0 fffff800`0104a604 : 00000000`00000000 00000000`00000000 fffffadf`34966e50 fffff800`01028090 : nt!MiResolveProtoPteFault+0x3e1
fffffadf`13b30570 00000000`00000000 : 00000000`00000020 fffffadf`80222004 fffffadf`34966d20 fffffadf`34904a50 : nt!MiDispatchFault+0x1062


STACK_COMMAND: kb

FOLLOWUP_IP:
nv4_mini!grContextInstanceToObject+f
fffffadf`25ed962f ?? ???

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: nv4_mini!grContextInstanceToObject+f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nv4_mini

IMAGE_NAME: nv4_mini.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4721477b

FAILURE_BUCKET_ID: X64_0xDA_nv4_mini!grContextInstanceToObject+f

BUCKET_ID: X64_0xDA_nv4_mini!grContextInstanceToObject+f

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

1: kd> lm
start end module name
fffff800`00800000 fffff800`0085e000 hal (deferred)
fffff800`01000000 fffff800`01490000 nt C (pdb symbols) c:\websymbols\ntkrnlmp.pdb\03185083233249D9BB747EA777B80C982\ntkrnlmp.pdb
fffff97f`ff000000 fffff97f`ff45f000 win32k (deferred)
fffff97f`ff45f000 fffff97f`ff487000 dxg (deferred)
fffff97f`ff487000 fffff97f`ffc93200 nv4_disp M (pdb symbols) C:\websymbols\Vista_x86\dll\nv4_disp.pdb
fffffadf`12543000 fffffadf`12581000 RDPWD (deferred)
fffffadf`13fe8000 fffffadf`140ac000 srv (deferred)
fffffadf`14138000 fffffadf`141cf000 HTTP (deferred)
fffffadf`14215000 fffffadf`14292000 amon (deferred)
fffffadf`14292000 fffffadf`142ba000 vmx86 (deferred)
fffffadf`14300000 fffffadf`14349000 mrxdav (deferred)
fffffadf`14663000 fffffadf`1469b000 kmixer (deferred)
fffffadf`146ea000 fffffadf`14715000 sysaudio (deferred)
fffffadf`14715000 fffffadf`14749000 wdmaud (deferred)
fffffadf`1481b000 fffffadf`1485c000 Fastfat (deferred)
fffffadf`15203000 fffffadf`15801000 dump_bcraid (deferred)
fffffadf`168d3000 fffffadf`168f4000 Cdfs (deferred)
fffffadf`168fe000 fffffadf`16913000 HIDCLASS (deferred)
fffffadf`16913000 fffffadf`169e0000 mrxsmb (deferred)
fffffadf`169e0000 fffffadf`16a31000 rdbss (deferred)
fffffadf`16a31000 fffffadf`16a5fb20 truecrypt (deferred)
fffffadf`16a60000 fffffadf`16a80000 arp1394 (deferred)
fffffadf`16a80000 fffffadf`16acd000 afd (deferred)
fffffadf`16acd000 fffffadf`16b0b000 ipnat (deferred)
fffffadf`16b0b000 fffffadf`16b65000 netbt (deferred)
fffffadf`16b65000 fffffadf`16c5a000 tcpip (deferred)
fffffadf`16c5a000 fffffadf`16c85000 ipsec (deferred)
fffffadf`16c85000 fffffadf`16c99000 Npfs (deferred)
fffffadf`18420000 fffffadf`18436b00 nvarm64 (deferred)
fffffadf`18437000 fffffadf`1855fc00 nvmcp64 (deferred)
fffffadf`18560000 fffffadf`185f2680 nvapu64 (deferred)
fffffadf`18838000 fffffadf`1899b000 CTEXFIFX (deferred)
fffffadf`1899b000 fffffadf`189dc000 CT20XUT (deferred)
fffffadf`18bda000 fffffadf`18bfc000 CTHWIUT (deferred)
fffffadf`18d9b000 fffffadf`18e49000 ctac32k (deferred)
fffffadf`18e49000 fffffadf`18e93000 ctsfm2k (deferred)
fffffadf`18e93000 fffffadf`18ee3000 emupia2k (deferred)
fffffadf`18ee3000 fffffadf`190d6000 ha20x2k (deferred)
fffffadf`19469000 fffffadf`19489000 usbhub (deferred)
fffffadf`19589000 fffffadf`1959d000 NDProxy (deferred)
fffffadf`1d589000 fffffadf`1d58ad80 USBD (deferred)
fffffadf`20445000 fffffadf`20460000 update (deferred)
fffffadf`20460000 fffffadf`20476000 termdd (deferred)
fffffadf`20476000 fffffadf`204cd000 rdpdr (deferred)
fffffadf`204cd000 fffffadf`204e3000 msgpc (deferred)
fffffadf`204e3000 fffffadf`20503000 psched (deferred)
fffffadf`20503000 fffffadf`20526000 raspptp (deferred)
fffffadf`20526000 fffffadf`2053a000 raspppoe (deferred)
fffffadf`2053a000 fffffadf`20566000 ndiswan (deferred)
fffffadf`20566000 fffffadf`2058c000 rasl2tp (deferred)
fffffadf`2058c000 fffffadf`205c6000 ctoss2k (deferred)
fffffadf`205c6000 fffffadf`20606000 portcls (deferred)
fffffadf`20606000 fffffadf`206d6980 ctaud2k (deferred)
fffffadf`206f4000 fffffadf`20717000 serial (deferred)
fffffadf`20717000 fffffadf`2076d000 aiegolqg (deferred)
fffffadf`2076d000 fffffadf`20790000 VIDEOPRT (pdb symbols) c:\websymbols\videoprt.pdb\A735567342A448C683C9DB1C8BEB2BEE1\videoprt.pdb
fffffadf`208a8000 fffffadf`208b0000 secdrv (deferred)
fffffadf`241c9000 fffffadf`241d3000 vstor2 (deferred)
fffffadf`241e9000 fffffadf`241f3000 vmnetuserif (deferred)
fffffadf`24209000 fffffadf`24215e00 NVENETFD (deferred)
fffffadf`242eb000 fffffadf`242fd000 wanarp (deferred)
fffffadf`2454a000 fffffadf`24556000 Dxapi (deferred)
fffffadf`2455a000 fffffadf`24567000 mssmbios (deferred)
fffffadf`245ba000 fffffadf`245c7000 hcmon (deferred)
fffffadf`248d3000 fffffadf`248dd000 VMNET (deferred)
fffffadf`248e3000 fffffadf`248ee000 raspti (deferred)
fffffadf`248f3000 fffffadf`24900000 ptilink (deferred)
fffffadf`24b13000 fffffadf`24b1f000 kbdhid (deferred)
fffffadf`24b23000 fffffadf`24b2d000 mouhid (deferred)
fffffadf`24b43000 fffffadf`24b4f000 ndisuio (deferred)
fffffadf`24de0000 fffffadf`24dee000 vmnetbridge (deferred)
fffffadf`25e4e000 fffffadf`2675f080 nv4_mini M (pdb symbols) C:\websymbols\Vista_x86\sys\nv4_mini.pdb
fffffadf`26760000 fffffadf`267ad000 NVSNPU (deferred)
fffffadf`267ad000 fffffadf`2681a400 NVNRM (deferred)
fffffadf`2681b000 fffffadf`26831000 redbook (deferred)
fffffadf`26831000 fffffadf`2684c000 cdrom (deferred)
fffffadf`2684c000 fffffadf`26863000 imapi (deferred)
fffffadf`26863000 fffffadf`268ac000 ks (deferred)
fffffadf`268ac000 fffffadf`268c2000 nvax64 (deferred)
fffffadf`268c2000 fffffadf`268fc000 USBPORT (deferred)
fffffadf`2691c000 fffffadf`26928000 dump_scsiport (deferred)
fffffadf`2693c000 fffffadf`2694b000 TDI (deferred)
fffffadf`2695c000 fffffadf`26966000 ndistapi (deferred)
fffffadf`2696c000 fffffadf`26975000 bccfg (deferred)
fffffadf`2697c000 fffffadf`26989000 mouclass (deferred)
fffffadf`2698c000 fffffadf`2699a000 kbdclass (deferred)
fffffadf`26ec2000 fffffadf`26ede000 nic1394 (deferred)
 
Uninstalled, checked.. stable..

Did the network install SP2. Same result. BSOD.
 
I'll just roll back my old build with my x1900xtx. I would rather not have to spend all weekend reloading. If you need a driver tested, I can image in and out my install to assist testing. And I can only give an outside view on whats going on as hooking up a remote debugger isnt going to get me far with just pdbs.

--Royal
 
In your last test did you do a totally clean install, or install on top of an existing installation? The problem seems to be that the SP1 -> SP2 upgrade leaves something in an odd state.

-Raystonn
 
I didnt. I have to go get the Raidcore drivers and other stuff to make up my install. If I get time tomorrow, i'll see about doing that. Not to be rude, but to be honest, I would favor buying another card than have to reload if that were my only option. My images I swapped in / out were with my dev tools 90% loaded.

Once you have your dev workstation set up, you are usually very reluctant to reload. Just too many damn little tools, sdks / etc. It sucks when your head is into a problem, you go to build and find out that you need to install something else, or put another path in that you forgot to / etc before it will compile. Thats why most of the hardware I have in there is fully supported by XP64, simply because xp64 has been solid for awhile now.

However just to note, my test PC had SP1 on it, and I upgraded to SP2 without any issues.

Update: I had some time this evening, so I slipstreamed a new sp2 disc, and it installed, and so far it is stable. I do not expect it to change. It had a hiccup once loading nvtools (in which the system hard locked, but not BSOD). I will run some more tests to see how it works out, then I have to reimage (takes me ~10 minutes) back to my ATI card unfortunately as I need to get work done before the holidays get into full swing. Let me know if any of the information I posted in the debugger log was helpful.

--Royal
 
Back
Top