BSOD with normal usage DRIVER_IRQL_NOT_LESS_OR_EQUAL

[kroobs]

It's been a while that I was here.
Although I marked the thread as solved, BSODs came back in a while.
I just decided to live with it as the computer would work okay sometimes.

I finally decided to try my local computer store recently and see what they can do.
I got it back real quickly and they told me that it was overheating issues.
So all they did was clean it and change the ram out (to some fancy looking ones with heat dissipaters?). They showed me it up and running so everything seemed fine. They let me into the back and I even tried the Prime 95 test (which would normally result in a BSOD) and it was working.

It did work for a day or two, but then the BSODs came back.
So.. I don't think I want to bring it back there.
I was just hoping someone can find a problem?
I'll attach the files. I just hope it's some sort of driver issue.
If not, I honestly kind of give up.. I've been working on it on and off for a good couple of months, looking at other's threads and trying solutions/debugs/memtest/furmark/prime95..

System Specs:
Operating System
MS Windows 7 Home Premium 64-bit

CPU
AMD Athlon II X4 635
Propus 45nm Technology

RAM
4.0GB Dual-Channel DDR3 @ 666MHz (9-9-9-24)

Motherboard
Biostar Group TA890GXB HD (CPU 1)

Graphics
ASUS VH198 (1440x900@60Hz)
1024MB GeForce 9500 GT (ASUStek Computer Inc)

Hard Drives
488GB Hitachi Hitachi HDS721050CLA362 ATA Device (SATA)

Optical Drives
TSSTcorp CDDVDW SH-S223L ATA Device

Audio
Realtek High Definition Audio

PSU
A-Power AK 750W 20+4-pin ATX Power Supply
115/230V, 50/60 Hz
+3.3V, 25A
+5V, 28A
+12V1, 27A
+12V2, 27A
-12V, 0.5A
+5Vsb, 3A

 

[kroobs]

I even tried removing the side panel to see if it was still overheating.
Also, I am not surprised to just have run a prime 95 blend test and have it fail during a couple of seconds.
The new BSOD said "PFN list is corrupt".

Should I reinstall windows?
I've done it tons of times before and it doesn't seem to fix anything..

 

[SledgeDG]

re installing W7 wouldn't help in this case since the error is not in the OS. But you could try and reset the CMOS/BIOS (load "safe defaults" or equivalent)
The crashes point towards memory corruption. Since the RAM is new and worked, chances are there are unfortunate settings for timings, voltage etc.

For the slim chance a defective PSU has "eaten" the new RAM test it after this tut

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

There is also a puzzling reference about your PCI controller overlapping address space with the DMA controller so check if you get updated chipset drivers for your biostar.
Here
or HERE
-DG

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


Loading Dump File [C:\Users\David\Desktop\Windows_NT6_BSOD_jcgriff2\100511-29608-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03019000 PsLoadedModuleList = 0xfffff800`0325e670
Debug session time: Wed Oct  5 18:36:53.919 2011 (GMT-4)
System Uptime: 0 days 0:00:51.511
Loading Kernel Symbols
..............................................
Loading User Symbols
Missing image name, possible paged-out or corrupt data.
Missing image name, possible paged-out or corrupt data.
Loading unloaded module list
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
Missing image name, possible paged-out or corrupt data.
Missing image name, possible paged-out or corrupt data.
..Missing image name, possible paged-out or corrupt data.
..Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.
.
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffaa003ac25e0, 2, 0, fffff80003071e94}

Probably caused by : ntkrnlmp.exe ( nt!EtwpEventWriteFull+104 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffffaa003ac25e0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80003071e94, address which referenced memory

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


[COLOR="Red"]OVERLAPPED_MODULE: Address regions for 'AtiPcie64' and 'Unknown_Module_00000000`00000000' overlap[/COLOR]

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032c8100
 fffffaa003ac25e0 

CURRENT_IRQL:  0

FAULTING_IP: 
nt!EtwpEventWriteFull+104
fffff800`03071e94 43397c1770      cmp     dword ptr [r15+r10+70h],edi

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

LAST_CONTROL_TRANSFER:  from fffff8000309f4a9 to fffff880010ab7f2

STACK_TEXT:  
fffff800`00b9cc98 fffff800`0309f4a9 : fffffa80`0396c890 fffffa80`051ca3a8 fffff800`03219cc0 00000000`00000002 : 0xfffff880`010ab7f2
fffff800`00b9cca0 fffff800`0308d93c : fffff800`0320be80 fffff800`00000000 00000000`00000000 fffff880`01457a00 : nt!PoIdle+0x52a
fffff800`00b9cd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nt!EtwpEventWriteFull+104
fffff800`03071e94 43397c1770      cmp     dword ptr [r15+r10+70h],edi

SYMBOL_NAME:  nt!EtwpEventWriteFull+104

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0xA_nt!EtwpEventWriteFull+104

BUCKET_ID:  X64_0xA_nt!EtwpEventWriteFull+104

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

0: kd> lmntsm
start             end                 module name
fffff880`00f06000 fffff880`00f5d000   ACPI     ACPI.sys     Sat Nov 20 04:19:16 2010 (4CE79294)
fffff880`00ff1000 fffff880`00ffc000   amdxata  amdxata.sys  Fri Mar 19 12:18:18 2010 (4BA3A3CA)
fffff880`00e1a000 fffff880`00e23000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
fffff880`00e23000 fffff880`00e4d000   ataport  ataport.SYS  Sat Nov 20 04:19:15 2010 (4CE79293)
fffff880`019dd000 fffff880`019e5000   AtiPcie64 AtiPcie64.sys Wed Mar 10 09:33:45 2010 (4B97ADC9)
fffff880`00d14000 fffff880`00dd4000   CI       CI.dll       Sat Nov 20 08:12:36 2010 (4CE7C944)
fffff880`019ad000 fffff880`019dd000   CLASSPNP CLASSPNP.SYS Sat Nov 20 04:19:23 2010 (4CE7929B)
fffff880`00cb6000 fffff880`00d14000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`01186000 fffff880`011f8000   cng      cng.sys      Sat Nov 20 05:08:45 2010 (4CE79E2D)
fffff880`01997000 fffff880`019ad000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
fffff880`01114000 fffff880`01128000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
fffff880`010c8000 fffff880`01114000   fltmgr   fltmgr.sys   Sat Nov 20 04:19:24 2010 (4CE7929C)
fffff880`013f1000 fffff880`013fb000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
fffff880`0195d000 fffff880`01997000   fvevol   fvevol.sys   Sat Nov 20 04:24:06 2010 (4CE793B6)
fffff880`01860000 fffff880`018aa000   fwpkclnt fwpkclnt.sys Sat Nov 20 04:21:37 2010 (4CE79321)
fffff800`03602000 fffff800`0364b000   hal      hal.dll      Sat Nov 20 08:00:25 2010 (4CE7C669)
fffff880`01954000 fffff880`0195d000   hwpolicy hwpolicy.sys Sat Nov 20 04:18:54 2010 (4CE7927E)
fffff800`00baf000 fffff800`00bb9000   kdcom    kdcom.dll    Sat Feb 05 11:52:49 2011 (4D4D8061)
fffff880`013c5000 fffff880`013e0000   ksecdd   ksecdd.sys   Sat Nov 20 04:21:15 2010 (4CE7930B)
fffff880`015a9000 fffff880`015d4000   ksecpkg  ksecpkg.sys  Sat Nov 20 05:10:34 2010 (4CE79E9A)
fffff880`00c95000 fffff880`00ca2000   mcupdate_AuthenticAMD mcupdate_AuthenticAMD.dll Mon Jul 13 21:29:09 2009 (4A5BDF65)
fffff880`00e00000 fffff880`00e1a000   mountmgr mountmgr.sys Sat Nov 20 04:19:21 2010 (4CE79299)
fffff880`00f66000 fffff880`00f70000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
fffff880`01128000 fffff880`01186000   msrpc    msrpc.sys    Sat Nov 20 04:21:56 2010 (4CE79334)
fffff880`01942000 fffff880`01954000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
fffff880`01456000 fffff880`01549000   ndis     ndis.sys     Sat Nov 20 04:23:30 2010 (4CE79392)
fffff880`01549000 fffff880`015a9000   NETIO    NETIO.SYS    Sat Nov 20 04:23:13 2010 (4CE79381)
fffff800`03019000 fffff800`03602000   nt       ntkrnlmp.exe Wed Jun 22 22:53:23 2011 (4E02AAA3)
fffff880`01222000 fffff880`013c5000   Ntfs     Ntfs.sys     Sat Nov 20 04:20:57 2010 (4CE792F9)
fffff880`00fb0000 fffff880`00fc5000   partmgr  partmgr.sys  Sat Nov 20 04:20:00 2010 (4CE792C0)
fffff880`00f70000 fffff880`00fa3000   pci      pci.sys      Sat Nov 20 04:19:11 2010 (4CE7928F)
fffff880`00fda000 fffff880`00fe1000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
fffff880`00fe1000 fffff880`00ff1000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
fffff880`013e0000 fffff880`013f1000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
fffff880`00ca2000 fffff880`00cb6000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
fffff880`01908000 fffff880`01942000   rdyboost rdyboost.sys Sat Nov 20 04:43:10 2010 (4CE7982E)
fffff880`018fe000 fffff880`01908000   speedfan speedfan.sys Fri Mar 18 12:08:46 2011 (4D83838E)
fffff880`018f6000 fffff880`018fe000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
fffff880`0165c000 fffff880`01860000   tcpip    tcpip.sys    Mon Jun 20 23:33:55 2011 (4E001123)
8009ea00`01a00400 8009ea00`01a30400   Unknown_Module_8009ea00_01a00400 Unknown_Module_8009ea00`01a00400 unavailable (00000000)
fffff880`00fa3000 fffff880`00fb0000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
fffff880`00fc5000 fffff880`00fda000   volmgr   volmgr.sys   Sat Nov 20 04:19:28 2010 (4CE792A0)
fffff880`00c00000 fffff880`00c5c000   volmgrx  volmgrx.sys  Sat Nov 20 04:20:43 2010 (4CE792EB)
fffff880`018aa000 fffff880`018f6000   volsnap  volsnap.sys  Sat Nov 20 04:20:08 2010 (4CE792C8)
fffff880`00e53000 fffff880`00ef7000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
fffff880`00ef7000 fffff880`00f06000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
fffff880`00f5d000 fffff880`00f66000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
Missing image name, possible paged-out or corrupt data.
Missing image name, possible paged-out or corrupt data.

Unloaded modules:
fffffa80`057577c0 fffffa81`00000000   Unknown_Module_fffffa80`057577c0
    Timestamp: unavailable (00000000)
    Checksum:  00000000
Missing image name, possible paged-out or corrupt data.
fffffa80`04517cd0 fffffa80`0498ee30   Unknown_Module_fffffa80`04517cd0
    Timestamp: unavailable (00000000)
    Checksum:  00000000
Missing image name, possible paged-out or corrupt data.
e56c6946`02150016 e56c6946`06b6f588   Unknown_Module_e56c6946`02150016
    Timestamp: unavailable (00000000)
    Checksum:  00000000
Missing image name, possible paged-out or corrupt data.
Missing image name, possible paged-out or corrupt data.
Missing image name, possible paged-out or corrupt data.
00000000`00000001 00000000`06b70030   Unknown_Module_00000000`00000001
    Timestamp: unavailable (00000000)
    Checksum:  00000000
00000000`0002ee00 00000000`057578b0   Unknown_Module_00000000`0002ee00
    Timestamp: unavailable (00000000)
    Checksum:  00000000
Missing image name, possible paged-out or corrupt data.
00000001`00000002 00000001`06b71858   Unknown_Module_00000001`00000002
    Timestamp: unavailable (00000000)
    Checksum:  00000000
00000000`00060001 00000000`057572a8   Unknown_Module_00000000`00060001
    Timestamp: unavailable (00000000)
    Checksum:  00000000
Missing image name, possible paged-out or corrupt data.
719b3800`aa000080 719b3801`00000001   Unknown_Module_719b3800`aa000080
    Timestamp: unavailable (00000000)
    Checksum:  00000000
Missing image name, possible paged-out or corrupt data.
719b3800`aa000080 719b3801`00000001   Unknown_Module_719b3800`aa000080
    Timestamp: unavailable (00000000)
    Checksum:  00000000

 

[kroobs]

See. I would have paid you that $75 for the work you did haha.

But anyways,
Alright, I will try running Memtest overnight for the 7 passes.
For resetting the bios/cmos, I think there is only a "load optimal defaults"
I'll double check for default, but can I also do that.. something about resetting with the motherboard jumper?
I think I've done it before and it takes me to the bios instructing me to input time/date/settings.

The last thing about the PCI I've never really heard of.
Forgive me but I'm not sure what that means.
Is there anything I can do to check/diagnose that?

Just saw your links, taking a look.
Also thank you for all your help!

 

[SledgeDG]

No need for that

Those "default" settings have different names, depending on BIOS version/producer so if you don't find anything else optimum defaults should work. You don't have to shortcut the mobo jumper. Yes it takes you to time/date entry since it completely deletes all CMOS settings.
Finally every board has a set of standard drivers, needed to coordinate the inner communication between several hardware elements on your motherboard, the so called chipset drivers.
Usually you find those at your motherboard producers webpage just check the links i posted.

-DG

 

[kroobs]

Ahh. So that's what they're for.
Alright I'll go with whatever defaults I find!

Also, I couldn't quite find my mobo on the site you linked.
How about here under drivers? TA890GXB HD :: Motherboard :: BIOSTAR
I don't know if it's updated, but I can always try it?
Do I need to un-install anything then install the chipset driver?

Also, I was wondering if updating the Bios would help?
I've never done so and don't want to damage my computer any more than it already is.
But if it can help I can try.

 

[SledgeDG]

yes you've got the correct page but the driver seems to be the installed one (same release date).
Chipset drivers you just install on top of existing ones (removing of old drivers is mainly advised with graphics drivers)
I don't think a BIOS update would help but if you want to do it, go for it. (In my book it's something to leave alone if not absolutely necessary). So let's hope the RAM Test brings anything or the optimum defaults. So we know if they put in faulty modules. (like I said before: there is always a slim chance that a defective PSU kills the RAMs but that would usually fry the CPU as well)

-DG

 

[kroobs]

Okay. The chipset download just finished so I'll try it to see if anything happens.
I shall leave the BIOS updating alone (Maybe a last resort if nothing else works).
And I'll run the ram test.

Something worth noting about a possibility of a defective psu.
After removing the side panel, the computer hasn't crashed (maybe speaking too soon but so far, no crashes like when it was acting up and barely useable 2 hours ago).
It only did so when I ran the prime 95 blend test.
Would that indicate a bad psu?

Well, I'm going to run the memtest, will post up tomorrow.
Again thanks for all the help.

 

[SledgeDG]

After removing the side panel, the computer hasn't crashed (maybe speaking too soon but so far, no crashes like when it was acting up and barely useable 2 hours ago).
It only did so when I ran the prime 95 blend test.
Would that indicate a bad psu?

That would rather point toward a thermal problem. make sure, your fan is working, fan blades and the heat sink are free from debris, dustbunnies etc.
You could also monitor your CPU temps with
Core Temp
or with SIV
-DG

 

[kroobs]

Scratch my previous post, it was crashing even with the side panel off.
Fans are working, and they just cleaned the machine.
It used to be really dusty near the heatsink/cpu but I can see it and everything now.
as for temps, I've measured before and the highest it went to on prime 95 (when it could run) was around 60C
I tried furmark and my 6850 ran up to 90C then slowly went down and sat at 75C

The memtest ran and passed 8 times. No errors.
However, when I closed it, switched boot to hard drive, it loaded to windows, but froze a few seconds in.
I force-shutdown by holding the power button and tried turning it on. This time it froze up on the bios.
I gave it a min or two and tried, but it froze again at the windows logo.
So I pretty much just left it alone for about 20 mins, and decided to try again.
It loaded and suggested to run system diagnostics and is trying to do a system restore.

Does this tell us anything new?

 

[Beast52702]

First of all, your temps are relatively high. I recently built a rig with an 95W athlon II and it's prime stable at 37-40C. That sounds like a poor thermal interface, ie bad thermal compound or too much thermal grease. Your VGA temps are also relatively high, that card should not get close to 90C. At that high of a temperature you're going to burn out your VRMs.

Given that it crashes when running prime, it could be CPU voltage, CPU-NB voltage(IMC), or your ram voltage/timings.

Set CPU voltage to 1.25 V
CPU-NB to 1.175 V - 1.25 V
DRAM voltage to 1.55 V
DRAM timings should match the spd tab in cpu-z