HELP! about BSOD

[Vanderkaum]

Nobody has been able to help me fix this. This issue is plaguing me, and I cannot seem to figure it out.

Here is how it goes, this build was made on the 20th of October of 2007 with this Video Card Replacing my 8800GT that I thought was causing the issue in the first place. When I first bench marked this system (With the 8800GT) it came in around 10k in 3dMark06 until recently I noticed some games just appear sluggish and choppy though no artifacts or errors...although I did get a random BSOD at boot up a few weeks ago and it was right around the performance problems started, and one while idle this morning.

A few days ago I decided to update the BIOS, they updated successfully, problem is actually a little worse, the Frames dropped by 9 FPS on average. So I reinstalled 3dMark06 only to notice my score is 4k marks worse than when I first got this build running, it's now around 6130 (Both Video Cards did the same).

Everything at a glance seems to be running ok, even though I noticed some sluggishness about the PC before the BIOS update I kind of suspect that as a big culprit but I'm not exactly sure, could use someone else's input.

My system specs:
Operating System: Microsoft Windows XP Home Edition SP2
CPU: AMD Athlon 64 X2, 2800 MHz (14 x 200) 5600+
Motherboard: Gigabyte GA-M57SLI-S4 Rev 2.0
System Memory: A-Data Extreme Edition 2048 MB (DDR2-800 DDR2 SDRAM)
Video Card: eVGA GeForce 8800 GTS (G92) (512 MB) (Brand New, still same issue which had originally thought to be the 8800GT to be the problem)
Monitor: Acer AL2016W [20" LCD]
Sound Card: Creative SB Live! 24-bit
Power Supply: 600W OCZ GameXStream
Hard Drive: Western Digital Caviar SE 160GB
BIOS: Award Modular (03/07/08) ( Note: This up to date BIOS version is FG, the BIOS the board came with were FC, but I can't seem to find that anywhere...)

This system has never been overclocked and this is a fresh install of Windows only a few weeks old. My Video drivers were up to date at 169.21, I tried downgrading to 169.02 to see if there was an issue with the drivers, but that didn't help. (Yes, I used Driver Cleaner Pro during Safe Mode in between Drivers and card swaps)

I also know that my Video Card is getting enough power, the +12v is at 12.35 which maybe a little much, but still I suspect it's exceptable. My Video Card stays around 45-50 Degrees C around 60 under load. I swapped the seating of video card also switched PCI-e slots and tried different PSU variations to still no avail.

There are no rogue processes running, I keep everything off usually I only keep my AV AS and Firewall on. Total I have 27 processes, that's it. I know 3dmark06 shouldn't be my focal point on my issue, it's not, but it shows the most significant change.

A couple other random benchmarks marked my video card(s) low as well. Funny thing there, I tried both cards in my old P4 system they hit 5k in 3dmark06, yeah...doubt it's my video card. I've run Diagnostic tests on memory and CPU and GPU all come out with no errors. Although my CPU is only running at 201.0 HT Link, shouldn't it be over 1000? All my drivers are up to date.

Here is the BSOD picture. http://xs225.xs.to/xs225/08120/picture_001519.jpg
 Microsoft claims it points to either faulty hardware, drivers, or firmware.

[runn3R]

Hi

Have you considered changing your RAM modules into other modules ? Just for checking as BSOD are often caused by memory problems.

What is voltage of your memory modules declared by the manufacturer ?

Have you tried different brand of VGA (different manufacturer, like Gigabyte for instance) ?

[antonyfrn]

have you run memtest yet?

[Labriskus]

This may help;

http://msdn.microsoft.com/en-gb/library/ms793589.aspx


quote;

Bug Check 0xA: IRQL_NOT_LESS_OR_EQUAL

The IRQL_NOT_LESS_OR_EQUAL bug check has a value of 0x0000000A. This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
Parameters

The following parameters are displayed on the blue screen.
Parameter    Description
1    Memory referenced
2    IRQL at time of reference
3    0: Read

1: Write

4    Address which referenced memory

Cause

This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high.

The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.

If you encounter bug check 0xA while upgrading to a later version of Windows, this error might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version.
Resolving the Problem

If a kernel debugger is available, obtain a stack trace.
To resolve an error caused by a faulty device driver, system service, or BIOS

   1. Restart your computer.
   2. Press F8 at the character-based menu that displays the operating system choices.
   3. Select the Last Known Good Configuration option from the Windows Advanced Options menu. This option is most effective when only one driver or service is added at a time.

To resolve an error caused by an incompatible device driver, system service, virus scanner, or backup tool

   1. Check the System Log in Event Viewer for error messages that might identify the device or driver that caused the error.
   2. Try disabling memory caching of the BIOS.
   3. Run the hardware diagnostics supplied by the system manufacturer, especially the memory scanner. For details on these procedures, see the owner's manual for your computer.
   4. Make sure the latest Service Pack is installed.
   5. If your system has small computer system interface (SCSI) adapters, contact the adapter manufacturer to obtain updated Windows drivers. Try disabling sync negotiation in the SCSI BIOS, checking the cabling and the SCSI IDs of each device, and confirming proper termination.
   6. For integrated device electronics (IDE) devices, define the onboard IDE port as Primary only. Also, check each IDE device for the proper master/subordinate/stand-alone setting. Try removing all IDE devices except for hard disks.

If the message appears during an installation of Windows, make sure that the computer and all installed peripherals are listed in the Microsoft Windows Marketplace Tested Products List.

Here is a debugging example:

kd> .bugcheck       [lists bug check data.]
Bugcheck code 0000000a
Arguments 00000000 0000001c 00000000 00000000

kd> kb       [lists the stack trace.]
ChildEBP RetAddr  Args to Child
8013ed5c 801263ba 00000000 00000000 e12ab000 NT!_DbgBreakPoint
8013eecc 801389ee 0000000a 00000000 0000001c NT!_KeBugCheckEx+0x194
8013eecc 00000000 0000000a 00000000 0000001c NT!_KiTrap0E+0x256
8013ed5c 801263ba 00000000 00000000 e12ab000
8013ef64 00000246 fe551aa1 ff690268 00000002 NT!_KeBugCheckEx+0x194

kd> kv       [lists the trap frames.]
ChildEBP RetAddr  Args to Child
8013ed5c 801263ba 00000000 00000000 e12ab000 NT!_DbgBreakPoint (FPO: [0,0,0])
8013eecc 801389ee 0000000a 00000000 0000001c NT!_KeBugCheckEx+0x194
8013eecc 00000000 0000000a 00000000 0000001c NT!_KiTrap0E+0x256 (FPO: [0,0] TrapFrame @ 8013eee8)
8013ed5c 801263ba 00000000 00000000 e12ab000
8013ef64 00000246 fe551aa1 ff690268 00000002 NT!_KeBugCheckEx+0x194

kd> .trap 8013eee8       [Gets the registers for the trap frame at the time of the fault.]
eax=dec80201 ebx=ffdff420 ecx=8013c71c edx=000003f8 esi=00000000 edi=87038e10
eip=00000000 esp=8013ef5c ebp=8013ef64 iopl=0         nv up ei pl nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
ErrCode = 00000000
00000000        [The current instruction pointer is NULL.]

kd> kb       [Gives the stack trace before the fault.]
ChildEBP RetAddr  Args to Child
8013ef68 fe551aa1 ff690268 00000002 fe5620d2 NT!_DbgBreakPoint
8013ef74 fe5620d2 fe5620da ff690268 80404690
NDIS!_EthFilterIndicateReceiveComplete+0x31
8013ef64 00000246 fe551aa1 ff690268 00000002 elnkii!_ElnkiiRcvInterruptDpc+0x1d0

Comments

Before upgrading to a new version of Windows, remove all third-party device drivers and system services, and disable any virus scanners. Contact the software manufacturers to obtain updates of these third-party tools.