BSOD's (IRQL, Bad Pool and many more)

yooz3r · 31 Jul 2010

Hello I'm looking for some help/advice on what to do with my computer, I'm suffering random BSOD's mostly during a game but it happens browsing websites too.

What I tried?
- Upgraded GTX275 Driver, Soundblaster driver, Asus Motherboard drivers
- Running memtest whole night only at one stick of ram - Passed
- Stressing CPU and ram in Prime95 about 6hours - Passed
- Torture GPU test in Furmark - Passed
- Some stability tests in Everest Ultimate - Passed
- I borrowed another DDR3 and random BSOD occured while browsing.
- Runned driver verifier and last BSOD from 31.07.2010 10:33 I think it's from it during a boot.

What doesn't helped?
- Re-installed OS
- Rising Voltages, Lowering Timings on DDR3
- Running all on auto in BIOS
- Disabling C1E in Bios
- Disabled Realtek built-in audio processor

On usb port's I got:
scanner, printer, keyboard and mouse.

I upgraded this computer half year ago, and bsod's started a month ago.
Please help me, what can it be? CPU? Mobo? Sending motherboard to a service will not help because they will start OS on it... and say that everything is ok.

Might be some driver error cause I did run driver verifier and it BSOD during a boot.

attached bsod's and perfmon report.

Last BSOD:

Code:

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


Loading Dump File [C:\Windows\Minidump\073110-19359-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\localsymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows Vista Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Kernel base = 0xfffff800`02e5b000 PsLoadedModuleList = 0xfffff800`03098e50
Debug session time: Sat Jul 31 10:32:44.048 2010 (GMT+2)
System Uptime: 0 days 0:00:19.749
Loading Kernel Symbols
...............................................................................................................................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff80003170a86, 2, 0, fffff80002ef8662}

Probably caused by : ntkrnlmp.exe ( nt!RtlDispatchException+122 )

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

3: 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: fffff80003170a86, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff80002ef8662, address which referenced memory

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


READ_ADDRESS: GetUlongFromAddress: unable to read from fffff800031030e0
 fffff80003170a86 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!RtlDispatchException+122
fffff800`02ef8662 410fb60c24       movzx   ecx,byte ptr [r12]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_BETA2

BUGCHECK_STR:  0xA

LAST_CONTROL_TRANSFER:  from fffff80002ecab69 to fffff80002ecb600

STACK_TEXT:  
fffff880`02fae668 fffff800`02ecab69 : 00000000`0000000a fffff800`03170a86 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02fae670 fffff800`02ec97e0 : 00000000`00000000 00000000`0000005a 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02fae7b0 fffff800`02ef8662 : fffff800`03170a86 fffff880`02fae988 fffff880`02faf7e8 fffff800`02e5b000 : nt!KiPageFault+0x260
fffff880`02fae940 fffff800`02f058df : fffff880`02faf7e8 fffff880`02faf050 fffff880`00000000 00000000`00000000 : nt!RtlDispatchException+0x122
fffff880`02faf020 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x16f


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nt!RtlDispatchException+122
fffff800`02ef8662 410fb60c24       movzx   ecx,byte ptr [r12]

FAULTING_SOURCE_CODE:  


SYMBOL_STACK_INDEX:  3

FOLLOWUP_NAME:  MachineOwner

SYMBOL_NAME:  nt!RtlDispatchException+122

MODULE_NAME:  nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4b88cfeb

FAILURE_BUCKET_ID:  X64_0xA_VRF_nt!RtlDispatchException+122

BUCKET_ID:  X64_0xA_VRF_nt!RtlDispatchException+122

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

Tews · 31 Jul 2010

Blue Screen of Death (BSOD) Posting Instructions

yooz3r · 31 Jul 2010

I followed instructions that was first Thread I read here, I've read other IRQL and simillar problems but didn't found the solution for me.

Tews · 31 Jul 2010

Looking at them now... may take a few minutes... Have called in a specialist ...

Tews · 31 Jul 2010

Quick question, are you over clocking anything???

swarfega · 31 Jul 2010

This error is usually associated with ram problems. Try with just one stick installed then add 1 each time. Remembering of course to turn your computer off each time you swap out ram.

yooz3r · 31 Jul 2010

I'm not overclocking atm, I tried with 1 stick and still get bsod's I borrowed another ddr3 and problem occured again so I think it's not ram problem

(
I have no idea what to do now

This is BSOD from yesterday, dxgmms1.sys I google some problems with it, some guy replaced mobo other one graphic card - as I can see 90% of people had AMD chipset and having this bsod...

Code:

....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck BE, {fffff8a008482148, 800000012a16c101, fffff8800875c360, b}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+17f )

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

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

ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory.  The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff8a008482148, Virtual address for the attempted write.
Arg2: 800000012a16c101, PTE contents.
Arg3: fffff8800875c360, (reserved)
Arg4: 000000000000000b, (reserved)

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_BETA2

BUGCHECK_STR:  0xBE

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002ef1a22 to fffff80002e71600

STACK_TEXT:  
fffff880`0875c1f8 fffff800`02ef1a22 : 00000000`000000be fffff8a0`08482148 80000001`2a16c101 fffff880`0875c360 : nt!KeBugCheckEx
fffff880`0875c200 fffff800`02e6f6ee : 00000000`00000001 fffffa80`04a3b740 00000000`00000000 fffff880`0433bee3 : nt! ?? ::FNODOBFM::`string'+0x423be
fffff880`0875c360 fffff880`04351507 : fffffa80`04a3b740 fffffa80`04a3b740 fffff8a0`0a295ce0 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`0875c4f0 fffff880`04337ecc : fffff8a0`00000000 fffffa80`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x17f
fffff880`0875c5c0 fffff880`04279c10 : 00000000`00000000 fffff8a0`0a6bd000 fffff8a0`0a6bd000 00000000`00000001 : dxgmms1!VidMmCloseAllocation+0x44
fffff880`0875c5f0 fffff880`0428c67c : 00000000`00000001 00000000`00000000 00000000`00000000 fffff8a0`00000799 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x248
fffff880`0875c6e0 fffff880`04271815 : 00000000`fffffeda fffff8a0`09ffb710 fffff8a0`0a6bd000 fffffa80`07148000 : dxgkrnl!DXGDEVICE::~DXGDEVICE+0x19c
fffff880`0875c750 fffff880`042afca6 : 00000000`00000001 fffffa80`07148000 fffff8a0`09ffb710 fffff8a0`09ffb790 : dxgkrnl!DXGADAPTER::DestroyDevice+0x1c9
fffff880`0875c780 fffff880`042af63c : fffff900`c2b5b480 00000000`00000000 00000000`00000001 fffff900`c2b5b480 : dxgkrnl!DXGPROCESS::Destroy+0xba
fffff880`0875c830 fffff960`00174aa4 : 00000000`0000126c fffff900`c2b5b480 00000000`00000000 fffff900`c2b5b480 : dxgkrnl!DxgkProcessCallout+0x268
fffff880`0875c8c0 fffff960`001741a7 : fffffa80`0723ba00 fffff880`0875cc20 00000000`00000000 fffff880`0875cc20 : win32k!GdiProcessCallout+0x244
fffff880`0875c940 fffff800`03157881 : fffffa80`0723ba60 00000000`00000000 00000000`00000000 fffffa80`041e4060 : win32k!W32pProcessCallout+0x6b
fffff880`0875c970 fffff800`031304d1 : 00000000`20010000 00000000`20010001 fffffa80`78457300 fffffa80`03d98b60 : nt!PspExitThread+0x561
fffff880`0875ca30 fffff800`02e4e0e3 : 00000000`00000100 fffffa80`041e4120 00000000`00000001 fffff800`02e7895d : nt!PsExitSpecialApc+0x1d
fffff880`0875ca60 fffff800`02e4e520 : 00000000`00000000 fffff880`0875cae0 fffff800`031305dc 00000000`00000001 : nt!KiDeliverApc+0x2eb
fffff880`0875cae0 fffff800`02e708f7 : fffffa80`041e4060 00000000`000004d0 00000000`00000000 fffffa80`043de170 : nt!KiInitiateUserApc+0x70
fffff880`0875cc20 00000000`75212dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`1166f0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x75212dd9


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+17f
fffff880`04351507 488908           mov     [rax],rcx

FAULTING_SOURCE_CODE:  


SYMBOL_STACK_INDEX:  3

FOLLOWUP_NAME:  MachineOwner

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+17f

MODULE_NAME:  dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578

FAILURE_BUCKET_ID:  X64_0xBE_dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+17f

BUCKET_ID:  X64_0xBE_dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+17f

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

Jonathan_King · 31 Jul 2010

Try a RAM test just to make sure. Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes. Be sure to run it with all sticks in at the same time.

It appears your video card or its drivers is the cause. Your drivers are up to date, so I don't suspect them.

Do you have another video card you can test with?

ASACPI.sys should be updated. Please install the latest ATK0110 Utility for Vista/7 from this link: ASUSTeK Computer Inc.-Support-

...Summary of the Dumps:

Code:


Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jul 31 04:32:44.048 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:19.749
BugCheck A, {fffff80003170a86, 2, 0, fffff80002ef8662}
Probably caused by : ntkrnlmp.exe ( nt!RtlDispatchException+122 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jul 31 04:07:55.526 2010 (UTC - 4:00)
System Uptime: 0 days 0:39:57.211
BugCheck C2, {d, fffffa80044a87d0, 20206f49, fffffa800519b060}
Probably caused by : win32k.sys ( win32k!xxxMsgWaitForMultipleObjects+108 )
BUGCHECK_STR:  0xc2_d
PROCESS_NAME:  csrss.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Fri Jul 30 12:05:51.856 2010 (UTC - 4:00)
System Uptime: 0 days 3:41:25.541
BugCheck BE, {fffff8a008482148, 800000012a16c101, fffff8800875c360, b}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+17f )
BUGCHECK_STR:  0xBE
PROCESS_NAME:  SC2.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jul 29 14:45:38.367 2010 (UTC - 4:00)
System Uptime: 0 days 0:43:01.052
BugCheck A, {fffffa7f9fffffe0, 2, 1, fffff80002f04209}
Probably caused by : memory_corruption ( nt!MmZeroPageThread+3d4 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jul 29 11:55:14.327 2010 (UTC - 4:00)
System Uptime: 0 days 3:16:19.639
BugCheck A, {8, 2, 1, fffff80002ed74b2}
Probably caused by : ntkrnlmp.exe ( nt!KiTimerExpiration+f2 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

yooz3r · 31 Jul 2010

I did run Memtest I write it above in first post :) each memtest runned whole night on just one stick of ram with no errors at all. I will try tonight with all sticks together, but as I mentioned BSOD happened on borrowed other sticks of Patriot Rams that were in Qualified Vendor List posted by Asus to my motherboard.

Strange I upgraded that ATK0110 yesterday
from Asus website:
Description ATK0110 driver for WindowsXP/Vista/Win7 32&64-bit

File Size 119.88 (KBytes) 2009/12/07 update

No I don't have any video card to borrow cause bsod happen randoms sometimes only once a day.

I updated BIOS a week ago.

zigzag3143 · 31 Jul 2010

yooz3r said:

I did run Memtest I write it above in first post :) each memtest runned whole night on just one stick of ram with no errors at all. I will try tonight with all sticks together, but as I mentioned BSOD happened on borrowed other sticks of Patriot Rams that were in Qualified Vendor List posted by Asus to my motherboard.

Strange I upgraded that ATK0110 yesterday
from Asus website:
Description ATK0110 driver for WindowsXP/Vista/Win7 32&64-bit

File Size 119.88 (KBytes) 2009/12/07 update

No I don't have any video card to borrow cause bsod happen randoms sometimes only once a day.

I updated BIOS a week ago.

yooz3r Hi and welcome

The date on the ATK0110 driver is a year and a half before windows seven even came out. If that is the most rrecent driver I suspect the hardware is much older. You have several old drivers built before win 7 come out that need updating

Code:

ctac32k.sys        fffff880`05600000    fffff880`056ae000    0x000ae000    0x486b3e7e    7/2/2008 04:38:22                        
spldr.sys        fffff880`01410000    fffff880`01418000    0x00008000    0x4a0858bb    5/11/2009 12:56:27                        
ASACPI.sys        fffff880`03f2b000    fffff880`03f33000    0x00008000    0x4a0b72fd    5/13/2009 21:25:17                        
amdxata.sys        fffff880`00e00000    fffff880`00e0b000    0x0000b000    0x4a12f2eb    5/19/2009 13:56:59

You have the following causes of your BDOS"s. your video driver of course.
that needs to be completely removed before installing a new one.

Your USBPORT.sys and of course that needs fixing (how many unpowered external USB devices do you have)?

Several other causes pointing to the win 7 OS but in reality not. there are at least three things you should do.

I suspect hardware. Memory, or a device.

As Jonathan_Kng correctly said run Memtest (with one stick at a time if necessary). Find one good ram stick. test it in each mobo slot to decide if it is ram or mobo.

Run a system file check. while I suspect hardware you want to eliminate software as well
(type cmd in search>right click and run as admin>SFC /SCANNOW)

Let us know the results

Update the old drivers especially ASACPI.sys as it has a known history with BSOD.

The usual is also suggested
If overclocking stop (yes ZI know you arent)
If you are running a RAID update its driver.

Your .dmp file shows various stop errors which is may be a general hardware error .. You can read more on this error and what to try here... - what it means and what to try Stop 0x124 - what it means and what to try

Thanks

Ken