Random BSOD in Win7

[pacaveli420]

every once in a while I'll get a BSOD randomly. I haven't been able to associate it with any software or action. IRQL_NOT_LESS_OR_EQUAL is the error I get. the last BSOD I woke up to and it seemed to have scrolled down the page past the error code so I'm not sure if it was the same. I have upgraded my video driver and pulled an unused PCI card in efforts to solve. I've also installed and attempted to gather some helpful info from the dmp files. I feel that someone with some more experience might be able to do this better though and pull some useful info. I've included the dumps from my last 6 bsods along with the xml from the most recent. can someone take a look at these for me and see if there's any consistencies or some potential link to what's causing the issue?

also I ran a full memory test today, no errors

system:
AMD Phenom II x3 720 BE
Gigabyte MA-770T-UD3P
EVGA GTS 250
6GB OCZ GOLD DDR3

 

[torrentg]

Hello,

I see that you have OCZ ram. Visit OCZ's site and find the correct timings and Vdimm (voltage) for them. Then adjust the bios accordingly.

Update these drivers too (or uninstall them along with the associated apps if they're unimportant to system functioning). Google to find out what they are:

speedfan speedfan.sys Sun Sep 24 09:26:48 2006 <<probably app should be uninstalled
Ultra Ultra.sys Fri Jul 28 00:01:47 2006 <<probably for Promise card

Update the motherboard chipset drivers.

Let us know how it goes and post another crash dump if it happens. Good luck.

 

[pacaveli420]

thanks for the reply torrentg I updated speedfan to the latest version, I use it to monitor temps so I don't want to get rid of it the ultra driver was for the pci card that I pulled so it shouldn't matter anymore, but I did uninstall/remove the driver anyways I updated sound / lan drivers. I've had a bit of trouble with the sound before so it might've had something to do with that I also installed north bridge filter and AMD usb filter drivers but win7 seems to have had an issue with them as it ran an auto repair after restarting and it seems they're no longer installed I only get the BSOD every once in a great while (week or 2) so I'll just have to wait and see, thanks for the info!

Edit: scratch that, the issue was removing that ultra driver, not the usb/bridge driver installs. I told it to delete it but it just ended up corrupting it somehow. manually removed it then readded the USB filter driver. installing the north bridge filter doesn't seem to stick. seems that's cuz I already have an appropriate one installed.

so as I said, will just have to see if any of that fixes it!

 

[pacaveli420]

another BSOD today: BAD_POOL_HEADER

dump file attached

I see other forums / posts suggesting this and the IRQ BSOD may be related
plz let me know what you guys think

 

[torrentg]

You could install the latest nForce 15.51 drivers to see if it helps any.

download from Guru3D.com

Also visit NVIDIA's site for latest video card driver.

And update this driver too:

point64k point64k.sys Thu Dec 04 04:47:58 2008

 

[pacaveli420]

---------------------------
NVIDIA Windows Software - InstallShield Wizard
---------------------------
The NVIDIA Setup program could not locate any drivers that are compatible with your current hardware. Setup will now exit.
---------------------------
OK
---------------------------
my chipsets are AMD, I've d/led and installed the latest drivers on those.
I had originally updated my vid drivers as one of the first things when I started getting BSODs
there's a new set again though so those are now updated
lastly I assume that's my mouse driver so I'll check MS site and see if there's a newer version
will post again if any more bsod's
thnx again for the help

 

[torrentg]

Never download drivers from Microsoft. They tend to mess systems up. Always from the manufacturers' websites.

 

[pacaveli420]

lol, the mouse is a MS mouse =)

 

[torrentg]

Ah...alright then. That's a different story because they actually make the drivers for that themselves. lol

 

[usasma]

Info on the STOP 0x19: BAD_POOL_HEADER error: BSOD Index
Info on the STOP 0xA: IRQL_NOT_LESS_OR_EQUAL: BSOD Index

Two different creatures - the first is due to Pool issues, while the second is due to IRQL issues. It's possible that the same driver could cause both issues tho' - so it's best to troubleshoot them together.

I specifically recommend Driver Verifier whenever I see a POOL problem, due to Driver Verifier's ability to stress the POOL. Please run it by following these directions:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.


So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista Startup Repair feature).


Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Automatically select unsigned drivers" and click "Next"
If no drivers show up, then select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.


Reboot the system and waitfor it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.


Reboot into Windows (after the crash) and turn offDriver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.


If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.


More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users
​

 

[pacaveli420]

well got a new one for ya torretg

 

[zigzag3143]

well got a new one for ya torretg

Hi and welcome

just an FYI TorrentG is no longer here

this crash involved several things the x264x64 file, the directx component of the video driver, and a driver. I suspect it is a one off while playing a game.


You can
run a system file check type cmd in search>right click and run as admin
>sfc /scannow

reinstall the video driver if it happens again. if still happens download and run memtestx86 for 5 runs

Good Luck Mate


Ken J+

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


Loading Dump File [C:\Users\K\Desktop\123009-17206-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`04019000 PsLoadedModuleList = 0xfffff800`04256e50
Debug session time: Wed Dec 30 09:53:36.599 2009 (GMT-5)
System Uptime: 4 days 10:47:34.766
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffaa009fc5738, 2, 0, fffff80004096d99}

Probably caused by : ntkrnlmp.exe ( nt!KiTimerExpiration+d9 )

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

2: 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: fffffaa009fc5738, 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: fffff80004096d99, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800042c10e0
 fffffaa009fc5738 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KiTimerExpiration+d9
fffff800`04096d99 483958f8        cmp     qword ptr [rax-8],rbx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  x264_x64.exe

TRAP_FRAME:  fffff88002f93cd0 -- (.trap 0xfffff88002f93cd0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffaa009fc5740 rbx=0000000000000000 rcx=0000000001780b1a
rdx=000000000000001a rsi=0000000000000000 rdi=0000000000000000
rip=fffff80004096d99 rsp=fffff88002f93e60 rbp=0000000001780b1a
 r8=0000000000000000  r9=00000000000000c0 r10=000000000000001a
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po cy
nt!KiTimerExpiration+0xd9:
fffff800`04096d99 483958f8        cmp     qword ptr [rax-8],rbx ds:8000:fffffaa0`09fc5738=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000408a469 to fffff8000408af00

STACK_TEXT:  
fffff880`02f93b88 fffff800`0408a469 : 00000000`0000000a fffffaa0`09fc5738 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02f93b90 fffff800`040890e0 : 00000000`00000000 0000037f`20e5e414 fffffa80`071ef000 00000000`00e5611d : nt!KiBugCheckDispatch+0x69
fffff880`02f93cd0 fffff800`04096d99 : 00000000`00000000 00000000`00000000 fffffa80`06968018 fffff880`13ef9336 : nt!KiPageFault+0x260
fffff880`02f93e60 fffff800`04096697 : fffff880`13ef92c0 fffff880`01780b1a 00000000`00000000 00000000`0000001a : nt!KiTimerExpiration+0xd9
fffff880`02f93f00 fffff800`04091065 : 00000000`00000000 fffffa80`08059060 00000000`00000000 fffff880`13f3f760 : nt!KiRetireDpcList+0x277
fffff880`02f93fb0 fffff800`04090e7c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
fffff880`06dccbe0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiTimerExpiration+d9
fffff800`04096d99 483958f8        cmp     qword ptr [rax-8],rbx

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KiTimerExpiration+d9

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600

FAILURE_BUCKET_ID:  X64_0xA_nt!KiTimerExpiration+d9

BUCKET_ID:  X64_0xA_nt!KiTimerExpiration+d9

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

 

[pacaveli420]

awww bummer, he was a good guy =P

yeah, I saw the x264x64 in the dump, it's for video encoding. So I've already updated a couple of the things associated with that.

I did run memtest before (found no issues). I believe I only let it run through once, though. whatever the default is. if so, letting it run through 5 times would probably take ~12hrs or so.

as for the video driver I've updated it a couple times while having this issue. I just checked and there is not a never version. I can reinstall it if you think it'll help but it doesn't seem like it's the culprit.

SFC found no errors.

anything else I could possibly try?

 

[zigzag3143]

awww bummer, he was a good guy =P

yeah, I saw the x264x64 in the dump, it's for video encoding. So I've already updated a couple of the things associated with that.

I did run memtest before (found no issues). I believe I only let it run through once, though. whatever the default is. if so, letting it run through 5 times would probably take ~12hrs or so.

as for the video driver I've updated it a couple times while having this issue. I just checked and there is not a never version. I can reinstall it if you think it'll help but it doesn't seem like it's the culprit.

SFC found no errors.

anything else I could possibly try?

letting it run 5 times would take a while but that is the point. You want the ram to fail if it is ever going to. there is another app called prime95 that will also did it and more quickly but if it is a heat issue you wont see it


Ken J+

 

[pacaveli420]

this provide anymore insight?
this was a: "PAGE_FAULT_IN_NONPAGED_AREA"

 

[usasma]

Please try running Driver Verifier according to these directions:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users