Multiple BSODs Windows 7 x64 Help !

I am running win 7 x64 on a q8200 quad-core on Asus P5E VM HDMI motherboard, 4 GB OCZ memory. I am getting random and increasingly more frequent BSODs. I replaced the memory, tried 2 new video cards as well as the built-in graphics, but still get BSODs. Re-installed Windows, remains stable for some days and then BSODs start again. The latest information of the BSOD is as follows. I am also attaching the latest 4 dumps. Any advice please?



Locale ID: 1033

Additional information about the problem:
BCCode: 4e
BCP1: 0000000000000099
BCP2: 000000000003C425
BCP3: 0000000000000002
BCP4: 00000000001181CD
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

 

Another BSOD. This time the code is different:


Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.4
Locale ID: 1033

Additional information about the problem:
BCCode: a
BCP1: 0000000000000080
BCP2: 0000000000000002
BCP3: 0000000000000001
BCP4: FFFFF8000348FC1F
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1


Dump file attached. Help please!

 

Hi gss100 and welcome to Majorgeeks

So a bad device driver sits at the top of the most likely list. Debug output for the latest dump:

Code:

System Uptime: 0 days 0:51:16.000
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {80, 2, 1, fffff8000348fc1f}

Probably caused by : ntkrnlmp.exe ( nt!KeAcquireInStackQueuedSpinLock+5f )

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: 0000000000000080, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff8000348fc1f, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800036b8100
 0000000000000080 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KeAcquireInStackQueuedSpinLock+5f
fffff800`0348fc1f 488717          xchg    rdx,qword ptr [rdi]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff880033936f0 -- (.trap 0xfffff880033936f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=fffff88003393900 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000348fc1f rsp=fffff88003393880 rbp=0000000000000000
 r8=fffff88003393900  r9=0000000000000000 r10=00000000fffffff9
r11=fffffa80039df760 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!KeAcquireInStackQueuedSpinLock+0x5f:
fffff800`0348fc1f 488717          xchg    rdx,qword ptr [rdi] ds:be80:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800034851e9 to fffff80003485c40

STACK_TEXT:  
fffff880`033935a8 fffff800`034851e9 : 00000000`0000000a 00000000`00000080 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`033935b0 fffff800`03483e60 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`033936f0 fffff800`0348fc1f : fffffa80`069c0a68 fffffa80`069c0a68 fffffa80`069c0960 fffff800`034b6216 : nt!KiPageFault+0x260
fffff880`03393880 fffff800`0353cfbe : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00041000 : nt!KeAcquireInStackQueuedSpinLock+0x5f
fffff880`033938d0 fffff800`034e3dd8 : 52d00000`398c7921 fffff800`034ac4e5 fffff6fc`c01cdf78 fffffa80`03a0f680 : nt!MiReleaseConfirmedPageFileSpace+0x5e
fffff880`03393950 fffff800`034c75e1 : fffffa80`03a0f680 00000000`00000000 fffff880`03393c58 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x15f87
fffff880`03393a50 fffff800`034caf76 : fffffa80`03c2bed8 00000000`00000001 fffffa80`00000001 fffffa80`00041000 : nt!CcFlushCache+0x561
fffff880`03393b50 fffff800`034cb938 : fffff880`00000000 fffff880`03393c58 fffffa80`06da81a0 fffff800`03687801 : nt!CcWriteBehind+0x1c6
fffff880`03393c00 fffff800`03490001 : fffffa80`03a44cc0 fffff800`0377c901 fffff800`036878c0 fffffa80`00000002 : nt!CcWorkerThread+0x1c8
fffff880`03393cb0 fffff800`03720fee : fffff8a0`001b52e8 fffffa80`03a0f680 00000000`00000080 fffffa80`039ea9e0 : nt!ExpWorkerThread+0x111
fffff880`03393d40 fffff800`034775e6 : fffff880`03163180 fffffa80`03a0f680 fffff880`0316dfc0 fffff8a0`0019fd30 : nt!PspSystemThreadStartup+0x5a
fffff880`03393d80 00000000`00000000 : fffff880`03394000 fffff880`0338e000 fffff880`03393620 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KeAcquireInStackQueuedSpinLock+5f
fffff800`0348fc1f 488717          xchg    rdx,qword ptr [rdi]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KeAcquireInStackQueuedSpinLock+5f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0xA_nt!KeAcquireInStackQueuedSpinLock+5f

BUCKET_ID:  X64_0xA_nt!KeAcquireInStackQueuedSpinLock+5f

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

2: kd> .bugcheck
Bugcheck code 0000000A
Arguments 00000000`00000080 00000000`00000002 00000000`00000001 fffff800`0348fc1f
2: kd> kb
RetAddr           : Args to Child                                                           : Call Site
fffff800`034851e9 : 00000000`0000000a 00000000`00000080 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff800`03483e60 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`0348fc1f : fffffa80`069c0a68 fffffa80`069c0a68 fffffa80`069c0960 fffff800`034b6216 : nt!KiPageFault+0x260
fffff800`0353cfbe : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00041000 : nt!KeAcquireInStackQueuedSpinLock+0x5f
fffff800`034e3dd8 : 52d00000`398c7921 fffff800`034ac4e5 fffff6fc`c01cdf78 fffffa80`03a0f680 : nt!MiReleaseConfirmedPageFileSpace+0x5e
fffff800`034c75e1 : fffffa80`03a0f680 00000000`00000000 fffff880`03393c58 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x15f87
fffff800`034caf76 : fffffa80`03c2bed8 00000000`00000001 fffffa80`00000001 fffffa80`00041000 : nt!CcFlushCache+0x561
fffff800`034cb938 : fffff880`00000000 fffff880`03393c58 fffffa80`06da81a0 fffff800`03687801 : nt!CcWriteBehind+0x1c6
fffff800`03490001 : fffffa80`03a44cc0 fffff800`0377c901 fffff800`036878c0 fffffa80`00000002 : nt!CcWorkerThread+0x1c8
fffff800`03720fee : fffff8a0`001b52e8 fffffa80`03a0f680 00000000`00000080 fffffa80`039ea9e0 : nt!ExpWorkerThread+0x111
fffff800`034775e6 : fffff880`03163180 fffffa80`03a0f680 fffff880`0316dfc0 fffff8a0`0019fd30 : nt!PspSystemThreadStartup+0x5a
00000000`00000000 : fffff880`03394000 fffff880`0338e000 fffff880`03393620 00000000`00000000 : nt!KxStartSystemThread+0x16
2: kd> kv
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`033935a8 fffff800`034851e9 : 00000000`0000000a 00000000`00000080 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`033935b0 fffff800`03483e60 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`033936f0 fffff800`0348fc1f : fffffa80`069c0a68 fffffa80`069c0a68 fffffa80`069c0960 fffff800`034b6216 : nt!KiPageFault+0x260 (TrapFrame @ fffff880`033936f0)
fffff880`03393880 fffff800`0353cfbe : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00041000 : nt!KeAcquireInStackQueuedSpinLock+0x5f
fffff880`033938d0 fffff800`034e3dd8 : 52d00000`398c7921 fffff800`034ac4e5 fffff6fc`c01cdf78 fffffa80`03a0f680 : nt!MiReleaseConfirmedPageFileSpace+0x5e
fffff880`03393950 fffff800`034c75e1 : fffffa80`03a0f680 00000000`00000000 fffff880`03393c58 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x15f87
fffff880`03393a50 fffff800`034caf76 : fffffa80`03c2bed8 00000000`00000001 fffffa80`00000001 fffffa80`00041000 : nt!CcFlushCache+0x561
fffff880`03393b50 fffff800`034cb938 : fffff880`00000000 fffff880`03393c58 fffffa80`06da81a0 fffff800`03687801 : nt!CcWriteBehind+0x1c6
fffff880`03393c00 fffff800`03490001 : fffffa80`03a44cc0 fffff800`0377c901 fffff800`036878c0 fffffa80`00000002 : nt!CcWorkerThread+0x1c8
fffff880`03393cb0 fffff800`03720fee : fffff8a0`001b52e8 fffffa80`03a0f680 00000000`00000080 fffffa80`039ea9e0 : nt!ExpWorkerThread+0x111
fffff880`03393d40 fffff800`034775e6 : fffff880`03163180 fffffa80`03a0f680 fffff880`0316dfc0 fffff8a0`0019fd30 : nt!PspSystemThreadStartup+0x5a
fffff880`03393d80 00000000`00000000 : fffff880`03394000 fffff880`0338e000 fffff880`03393620 00000000`00000000 : nt!KxStartSystemThread+0x16
2: kd> .trap fffff880`033936f0
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=fffff88003393900 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000348fc1f rsp=fffff88003393880 rbp=0000000000000000
 r8=fffff88003393900  r9=0000000000000000 r10=00000000fffffff9
r11=fffffa80039df760 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!KeAcquireInStackQueuedSpinLock+0x5f:
fffff800`0348fc1f 488717          xchg    rdx,qword ptr [rdi] ds:be80:00000000`00000000=????????????????
2: kd> kb
  *** Stack trace for last set context - .thread/.cxr resets it
RetAddr           : Args to Child                                                           : Call Site
fffff800`0353cfbe : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00041000 : nt!KeAcquireInStackQueuedSpinLock+0x5f
fffff800`034e3dd8 : 52d00000`398c7921 fffff800`034ac4e5 fffff6fc`c01cdf78 fffffa80`03a0f680 : nt!MiReleaseConfirmedPageFileSpace+0x5e
fffff800`034c75e1 : fffffa80`03a0f680 00000000`00000000 fffff880`03393c58 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x15f87
fffff800`034caf76 : fffffa80`03c2bed8 00000000`00000001 fffffa80`00000001 fffffa80`00041000 : nt!CcFlushCache+0x561
fffff800`034cb938 : fffff880`00000000 fffff880`03393c58 fffffa80`06da81a0 fffff800`03687801 : nt!CcWriteBehind+0x1c6
fffff800`03490001 : fffffa80`03a44cc0 fffff800`0377c901 fffff800`036878c0 fffffa80`00000002 : nt!CcWorkerThread+0x1c8
fffff800`03720fee : fffff8a0`001b52e8 fffffa80`03a0f680 00000000`00000080 fffffa80`039ea9e0 : nt!ExpWorkerThread+0x111
fffff800`034775e6 : fffff880`03163180 fffffa80`03a0f680 fffff880`0316dfc0 fffff8a0`0019fd30 : nt!PspSystemThreadStartup+0x5a
00000000`00000000 : fffff880`03394000 fffff880`0338e000 fffff880`03393620 00000000`00000000 : nt!KxStartSystemThread+0x16

That means almost nothing to me, just pointing to a device driver.



The following are all drivers that I consider old or potentially bad. Any of them could cause issues, please either update, uninstall or disable them:

pstrip64.sys = Power Strip http://entechtaiwan.com/util/ps.shtm

ASACPI.sys - Asus ATK0110 ACPI Utility (a known BSOD maker in Win7). Also a part of the Asus PCProbe and AISuite Utilities http://support.asus.com/download/download.aspx

speedfan.sys = SpeedFan http://www.almico.com/sfdownload.php

tifsfilt.sys = Acronis True Image FS Filter also included in Seagate DiscWizard Support: http://www.acronis.com/support/ Download: http://www.acronis.com/support/?TS=4-0

Sandra.sys = SiSoft Sandra http://www.sisoftware.net/?d=&f=downandbuy&l=en&a=

igdkmd64.sys Intel Graphics driver http://downloadcenter.intel.com/Default.aspx

l160x64.sys = NDIS Miniport Driver for Atheros L1 Gigabit Ethernet Controller http://www.atheros.cz/

RTL8187.sys = Realtek networking driver http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=7&PFid=10&Level=3&Conn=2

savonaccess.sys = Sophos Anti-Virus On-Access Driver http://www.sophos.com/support/

CFRPD.sys = Comodo System Cleaner http://www.comodo.com/home/support-maintenance/system-cleaner.php




Install MSE and check that the built-in Windows firewall is enabled.

 

Thank you very much! I will try your suggestions and report back tomorrow.

Apologies as a noob, but what is MSE?

 

No apology needed, I should have linked it or spelled it out

Microsoft Security Essentials - it's probably the least likely AV to cause problems with Windows. Uninstall any other antivirus first. The version on the page here may be outdated but it links directly to MSFT so the version you download should be the most recent.

 

I did it, and so far no BSODs I think it is the ASUS driver that is causing the problem - I have a similar problem in another computer with the same motherboard. I will try this solution on that machine as well.

Thanks a lot!

 

Yup, those motherboard utilities are a frequent cause of BSOD's

Good luck with the other machine

 

I am still getting crashes but now with this message:

Display driver igfx stopped responding and has successfully recovered.

Except that it does not recover.....

Help please!

 

I updated the Intel graphics driver - and now get a BSOD :-(.

Dump file is attached.


Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.4
Locale ID: 1033

Additional information about the problem:
BCCode: 1a
BCP1: 0000000000000403
BCP2: FFFFF68000006778
BCP3: B1D000003992282D
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Please help!

I am now thinking of junking everything and do a clean Windows 8 install :-(

 

You forgot to attach the dump also describe what was happening during the five minutes or so before the last crash please.

A fresh install would only help if we knew it was a Windows problem, we need to rule out any 3rd party software and be sure the hardware is good.

 

Sorry - here is the dump file. I was just surfing the web and checking email when it crashed.

You are right of course that fresh install may not solve my problem.

It crashed again today, with the message about the display driver (no dump file since I had to manually reboot). Again, I was just using google chrome. Nothing major. Could it that my power supply is going bad? But that is unlikely to happen on 2 machines simultaneously...

Thanks a lot for all your help.

 

ASACPI.sys dating from 2005 is still present - this has been known to cause BSOD's on Windows 7, you must uninstall, disable or upgrade it.

This too is very old, 2007 ---> tifsfilt.sys Acronis True Image FS Filter also included in Seagate DiscWizard Support: http://www.acronis.com/support/
Download: http://www.acronis.com/support/?TS=4-0 uninstall or upgrade it. Snapman.sys, tdrpman.sys and timntr.sys are also v. old, loaded and part of Acronis.

This driver also pre-dates W7 ---> netr28x.sys Ralink RT2860 series Wireless LAN Card (you may have a different manufacturer) http://www.ralinktech.com/en/04_support/support.php?sn=500

From mid 2009, still old ---> igdkmd64.sys Intel Graphics driver http://downloadcenter.intel.com/Default.aspx

2009 ---> l160x64.sys NDIS Miniport Driver for Atheros L1 Gigabit Ethernet Controller http://www.atheros.cz/

Code:

Debug session time: Sat Mar 10 04:50:41.381 2012 (UTC + 0:00)
System Uptime: 0 days 1:41:23.895
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {403, fffff68000006778, b1d000003992282d, 0}

Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+a7 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000000403, The subtype of the bugcheck.
Arg2: fffff68000006778
Arg3: b1d000003992282d
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_403

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800034393f6 to fffff80003491c40

STACK_TEXT:  
fffff880`05571ef8 fffff800`034393f6 : 00000000`0000001a 00000000`00000403 fffff680`00006778 b1d00000`3992282d : nt!KeBugCheckEx
fffff880`05571f00 fffff800`034c3bb7 : 00000000`00000000 fffff680`00006ff8 fffffa80`05497b30 c2d00000`548b282d : nt! ?? ::FNODOBFM::`string'+0x330bc
fffff880`055720b0 fffff800`034c5569 : 00000000`00000000 00000000`0104dfff 00000000`00000000 00000000`00000000 : nt!MiDeleteVirtualAddresses+0x41f
fffff880`05572270 fffff800`037a9221 : fffffa80`03adf950 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9
fffff880`05572390 fffff880`04e20aef : fffffa80`00000000 fffffa80`067405e0 00000000`00000001 00000000`000007ff : nt!MiUnmapViewOfSection+0x1b1
fffff880`05572450 fffff880`04e1b523 : fffffa80`067405e0 00000000`00000001 fffff8a0`046d2820 00000000`00000001 : dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+0xa7
fffff880`05572500 fffff880`04e01ecc : fffffa80`00000000 fffffa80`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x19b
fffff880`055725d0 fffff880`04f36ccc : fffff8a0`049a2d30 fffff8a0`027b6000 fffff8a0`027b6000 00000000`00000001 : dxgmms1!VidMmCloseAllocation+0x44
fffff880`05572600 fffff880`04f373ac : fffff8a0`00312460 fffff8a0`00312460 00000000`00000001 fffff8a0`027b6000 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x248
fffff880`055726f0 fffff880`04f36651 : fffff8a0`027b6000 fffff8a0`027b6000 fffff8a0`0e6c9790 00000000`00000799 : dxgkrnl!DXGDEVICE::DestroyResource+0x84
fffff880`05572720 fffff880`04f368e1 : fffff8a0`027b6000 fffff8a0`027b6000 00000000`00000001 fffff8a0`0529e7f0 : dxgkrnl!DXGDEVICE::ProcessTerminationList+0x95
fffff880`05572770 fffff880`04f3a3e7 : fffff8a0`027b6000 00000000`40001a80 00000000`00000000 fffff880`04f013af : dxgkrnl!DXGDEVICE::TerminateAllocations+0xb9
fffff880`055727c0 fffff880`04f43fc1 : fffff8a0`027b6000 fffff880`055728b8 00000000`c0002200 fffffa80`0549c830 : dxgkrnl!DXGDEVICE::DestroyAllocation+0x93
fffff880`05572850 fffff960`0065e816 : fffff900`c2df0cb0 00000000`00000000 fffff900`c2660f00 00000000`00000002 : dxgkrnl!DxgkCddDestroyAllocation+0x241
fffff880`05572900 fffff960`00659483 : fffffa80`00000000 fffff900`c2660020 00000000`00000000 00000000`00000002 : cdd!CddBitmapHw::InvalidateDeviceAllocations+0x66
fffff880`05572930 fffff960`006596de : fffffa80`fffffcf0 ffffffff`ffe17b80 fffff900`c2660020 00000000`00000006 : cdd!CDDPDEV::InvalidateInternalBitmaps+0x1bf
fffff880`05572980 fffff960`00655e07 : ffffffff`fffffc4c 00000000`00000006 00000000`00000002 00000000`00000006 : cdd!CDDPDEV::DestroyDevice+0x5a
fffff880`055729b0 fffff800`0372cfee : fffff880`00000003 fffffa80`04591670 00000000`00000080 fffffa80`05497b30 : cdd!PresentWorkerThread+0xa9b
fffff880`05572d40 fffff800`034835e6 : fffff880`02fd3180 fffffa80`04591670 fffff880`02fddfc0 fffff880`0125ecb0 : nt!PspSystemThreadStartup+0x5a
fffff880`05572d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+a7
fffff880`04e20aef eb7e            jmp     dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+0x127 (fffff880`04e20b6f)

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+a7

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

FAILURE_BUCKET_ID:  X64_0x1a_403_dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+a7

BUCKET_ID:  X64_0x1a_403_dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+a7

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

This dump blames the video subsystem, the Intel driver needs updating, see above; as it's an Intel chipset you'll need to check that DirectX 9.0C has been installed. Check for any overheating, dust buildup inside the case, etc.

Is this the original computer or the second one you mentioned?

 

Apologies for not responding earlier - I am travelling and having my wife help me with this home computer, so it has taken a little while. This is the first (original) computer. I have not started working on the second one yet.

Sorry for a newbie question - how do I make sure that all of these drivers are removed? I thought I had removed the drivers and updated the Intel drivers twice, but it is not doing it somehow.

I will check for the temperatures and dust too.

Many thanks - you are wonderful.

 

No time restrictions here respond when you can.

It's difficult to know why an updated driver doesn't stick; sometimes, the drivers are actually the same - just the wrapper for the drivers is new - because the actual hardware is based on an older design that will only work with the equivalent of Vista drivers, not W7 drivers.

So, what's the hardware - the Intel video chipset especially? Device Manager should have some details on this. Otherwise, run MSInfo32 and dig out the details - or save it and zip and attach it here.

 

Here is the hardware:

MB: Asus P5E-VM HDMI
Video: Intel G35 chipset (GMA X3500)

I think I may not have removed the old drivers properly - what is the best way to get rid of old drivers and delete from registry?

If I did a fresh Windows 8 install and let Windows install the drivers, would that fix the problem?

Thanks.

 

Ok, let's deal with this one step at a time - the asascpi.sys from 2005 is a known bad driver in W7, so we'll begin with updating that: visit the ASUS downloads page for your 'board (select Vista x64 as the OS), expand the link for Utilities and download the ATK0110 driver for WindowsXP/Vista/Win7 32&64-bit (use the Global link) and install it.

After a reboot, test it until it BSODs again - if it doesn't get a BSOD after a week or two, you've probably found the cure.

 

I searched for asacpi.sys. It was previously in C:\windows\system32\drivers folder but I deleted it. It is not there anymore. There is a registry value under "setup/pnplockdownfiles as " %SystemPath%\system32\DRIVERS\ASACPI.sys but I cannot delete this entry ("unable to delete all specified values").

 

Did it. Will keep my fingers crossed. I will let you know if I get BSODs again.

Many thanks again.

 

Any devices flagged in Device Manager now?

It looks like the graphics drivers you have are probably the latest, the 'board seems to be based on some pretty old components. I'm not sure that moving to W8 will give any speed upgrade but it could improve reliability if a hardware fault isn't at the root of this.

 

There are no devices flagged in Device Manager (there never were), but the computer continues to crash. "Display Driver has stopped Responding". It says it has recovered but it does not, and eventually I have to re-boot it.

What do we do next?

 

You could try using Latencymon to find drivers that are bogging down (check for any with high DPC's), the downoad link is right of the main banner. An alternative would be Resource Monitor (Perfmon) built-in to Windows.

 

Here is what LatencyMon says re. drivers with highest DPCs:
1. rsp111.64.sys (resplendence Latency Monitor)
2. dxgkrnl,sys (directx graphics kernel)
3. ndis.sys (NDIS 6.20 driver)
4. ataport.sys (ATAPI driver extension)
5. ntoskrnl.exe (NT kernel and system)
6. USBPORT.sys (USB 1.1 and 2.0 port drivers)

The highest ISR counts are ataport.sys, hal.dll (hardware abstraction layer), usbport.sys, dxgkrnl.sys and Wdf0100.sys (kernel mode driver framework).

But what is more alarming is the fact that on the main screen, there are a large number of hard pagefaults, and a high 'highest reported hard pagefault resolution time (us): 1050761.3645 (it is red to the end). Also the main screen shows highest reported DPC routine execution time for ataport.sys and highest reported ISR for dxgkrnl.sys.

The message at the top says that your system seems to be having difficulty handling real-time audio and other tasks. You may experience drop outs, clicks or pops due to buffer underruns. The cause of the problem is not immediately apparent.

CPU temp is 51 degrees, so it is not particularly hot.

Suggestions please?

G.

 

So it's graphics and data transfer that look to be highest, they may be related, how much RAM is installed?

How much BIOS + System memory is given over to the graphics? The display tab of DXDiag will give the total BIOS + System. Check the System tab for page file used amount too, please.

Do you see a big difference in any of the LatencyMon data after running it a second time?

 

Here is an update.

I ran it again and let it run for several hours.

The message is: One or more DPC routines belonging to a driver running in your system appear to be executing for too long. Also one or more ISR routines belonging to a driver in your system appear to be executing for too long. At least one detected problem appears to be network related. You may have to disable wireless adapters to get better results.

Highest reported ISR execution time is Hal.dll (hardware abstraction layer, microsoft corporation) at 199916175941.8750 (red all the way).

Highest reported DPC routine execution time is ndis.sys (NDIS 6.20 drivers, microsoft) at 36830760.3110.

Page faults 8082, resolution time 1665691.5507

I have 4 GB of memory. DxDiag shows 358 mb in the display tab. It also shows no problems found.

Page File 2126 MB used, 6045 MB available.

DxDiag report attached.

 

I updated the wireless card driver, and re-ran the LatencyMon.

Now the problem seems to be ataport.sys - for both ISR as well as DPC. I ran the TDSS Killer application from Kaspersky but it did not find anything.

 

So the biggest holdup is probably disk I/O, possibly excessive page file use. What antivirus and active security programs are you using, Microsoft Security Essentials still? Have you run a full scan with it yet?

You could upload ataport.sys to virustotal.com for a scan if you're concerned about it, if anything is flagged up, link us to the results page please.

How about the hard drive capacity and fragmentation, could you post those stats please? Hard drive make/model# too?

Do you have a disc in an optical drive? If so, remove it and test LatencyMon again.

 

Sophos and Microsoft Security Essentials. I am running a scan now.

Will upload ataport.sys to virustotal and let you know.

Hard drives: 2 Hitachi drive (one 7200 rpm 1 TB, abother 5900 rpm 2 TB). I will defragment them today.

No disc in optical drive.

Still the same message in LatencyMon, and points to ataport.sys with maximum ISR and DPC. Where can I get a new ataport.sys file?

 

Some of the high readings you see may be from trying to access files from the slower HDD.

Once the scans are completed and come up clean, please turn off (uninstall preferably) Panda, actively running 2 antivirus programs can lead to similar problems to those you've been experiencing.

Once ataport has been scanned by Virustotal (insist on a new scan if it says it's been scanned previously - malware definitions change frequently), post the link and we'll decide whether you need to visit the malware forum or replace ataport.

 

Here is the link:

https://www.virustotal.com/file/6a0...45907429f63119413d96c0a8/analysis/1334264588/

It is clean.

 

Clean, yes. The additional info tab at the foot of the page gives enough details to make me think it must be a version from a late W7 RC, rather than from the Release version.

Running SFC /Scannow from an elevated command prompt might fix this, it may ask for the W7 DVD, do you have it?

 

Yes, I have the Win 7 DVD.

I did run SFC /scannow but will do it again now.

Computer still keeps on crashing - says display driver not responding. Of course, I have uninstalled and reinstalled the display drive many time. I have even tried a new video card (and may do that again).

 

SFC/scannow shows no problems. Disk drives are defragmented now. Still keeps on crashing.

 

Any recent memory dumps?

What PSU are you running in that computer, can you find the make/model# ?

Did you uninstall Sophos (sorry, I wrote Panda earlier)?

 

No memory dumps. The computer just crashes.

Actually, Sophos was already uninstalled.

PSU: Antec Earthwatts 650

Today I am thinking of doing a fresh Win 8 install, with a new video card. It crashes several times a day now.

 

Installing W8 should rule out software/drivers, if it still has a problem, it should be hardware.

 

That is exactly what I thought. I will let you know.

 

Windows 8 fixed everything!

Now I need your help with the second computer, with the same hardware and the same problem. I cannot do a clean install on this one since I have a lot of programs for which I do not have disks. So I will work in a step-wise fashion, based on your previous posts.

 

Hi - I am resurrecting an old thread. I have 2 identical PCs with the same problem (as described in this thread originally). I installed Windows 8 on one of them, and it fixed the problem completely. On the second one, I cannot do that since I have some old programs that I will need to re-install.

Since Win 8 fixed the problem in one PC, it should be a driver issue.

Please advise what steps I should take to fix this second PC.

One issue that is different with this PC - it does not give me a memory dump - just crashes.

It is probably the ASUS driver - how do I completely uninstall it? Will not let me delete it from the registry :-(

Many thanks.

 

Go here http://www.intel.com/p/en_US/support/detect
maybe Intel will come up with the proper driver for the video chip on the board.

 

Thanks. Here is the message from the Intel utility : "Your driver is current."

I think the problem is ASACPI - the Asus MB utility. But I cannot seem to remove it from the Registry.

Suggestions?