Solved New build, multiple random BSOD with various error codes

[Thedoctor44]

You are getting all sorts of errors.

Your ASUS Xonar DG Audio Interface driver is causing issues.

http://support.asus.com/download/download.aspx

fffff880`04e10000 fffff880`0513b000   cmudaxp  T (no symbols)           
    Loaded symbol image file: cmudaxp.sys
    Image path: cmudaxp.sys
    Image name: cmudaxp.sys
    Timestamp:        [COLOR="Red"]Thu Mar 10 07:44:15 2011[/COLOR] (4D78814F)
    CheckSum:         002A05E0
    ImageSize:        0032B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

fffff880`0a9831e8 fffff800`02cd3169 : 00000000`0000000a ffffe480`63a6c9f3 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0a9831f0 fffff800`02cd1de0 : 00000000`00000002 fffff8a0`13c14760 00000000`00000000 fffffa80`13919018 : nt!KiBugCheckDispatch+0x69
fffff880`0a983330 fffff880`05145fb9 : fffffa80`13919018 00000000`00000005 fffffa80`1389b010 fffffa80`13919018 : [COLOR="red"]nt!KiPageFault+0x260[/COLOR] ([COLOR="SeaGreen"]TrapFrame @ fffff880`0a983330[/COLOR])
fffff880`0a9834c0 fffff880`0513e353 : fffff880`00000748 00000000`00000000 fffffa80`156085b0 00000000`00000000 : portcls!CPortPinWaveCyclic::GetPosition+0xe9
fffff880`0a983530 fffff880`05146016 : fffffa80`1553da80 fffffa80`156085b0 fffffa80`1553da70 fffffa80`13919010 : portcls!CIrpStream::GetPosition+0x7b
fffff880`0a983560 fffff880`0514618f : fffffa80`13919010 fffffa80`1553da70 00000000`00000040 00000000`00000001 : portcls!CPortPinWaveCyclic::GetKsAudioPosition+0x2a
fffff880`0a983610 fffff880`051b458f : fffffa80`156085b0 fffffa80`106cd060 fffffa80`1553da70 fffff800`02e85b80 : portcls!CPortPinWaveCyclic::GetKsAudioPosition+0x1a3
fffff880`0a983640 fffff880`051c0a1f : fffffa80`156085b0 fffff880`00000004 fffff880`0a983760 fffff8a0`007ea3b0 : ks!KspPropertyHandler+0x71f
fffff880`0a9836b0 fffff880`05159964 : fffffa80`136bfb30 fffff880`0a983760 00000000`00000001 fffff8a0`007ea3b0 : ks!KsPropertyHandler+0x1b
fffff880`0a983700 fffff880`05167d74 : fffffa80`0c9ebe30 fffffa80`10a1d010 fffffa80`156085b0 fffffa80`106cd060 : portcls!PcHandlePropertyWithTable+0x64
fffff880`0a983730 fffff880`05158f9d : fffffa80`156085b0 fffffa80`106cd060 fffffa80`106cd1b0 fffffa80`1513dc20 : portcls!CPortPinWaveCyclic::DeviceIoControl+0x2bc
fffff880`0a9837a0 fffff880`051b47bb : 00000000`c000000d fffffa80`156087e8 00000000`c0000002 00000001`00000032 : portcls!DispatchDeviceIoControl+0x79
fffff880`0a9837d0 fffff880`0515806c : fffffa80`106cc3e0 fffff880`051dd5fb fffffa80`0c9ebe30 00000000`00000000 : ks!KsDispatchIrp+0xdb
fffff880`0a983800 fffff880`050ef9bd : fffff880`0a9838e0 fffff880`051dda87 fffffa80`156085b0 fffffa80`156085b0 : portcls!PcDispatchIrp+0x5c
fffff880`0a983830 fffff880`0a9838e0 : fffff880`051dda87 fffffa80`156085b0 fffffa80`156085b0 00000000`00000003 : cmudaxp+0x2df9bd
fffff880`0a983838 fffff880`051dda87 : fffffa80`156085b0 fffffa80`156085b0 00000000`00000003 fffffa80`156085b0 : 0xfffff880`0a9838e0
fffff880`0a983840 fffff880`051dd825 : 00000000`00000001 fffffa80`156087e8 fffffa80`15608830 fffffa80`156085b0 : ksthunk!CKSThunkDevice::DispatchIoctl+0xcf
fffff880`0a983870 fffff800`02ff03a7 : fffffa80`0cbf3f20 fffff880`0a983b60 fffffa80`00000000 fffffa80`0cbf3f20 : ksthunk!CKernelFilterDevice::DispatchIrp+0x11d
fffff880`0a9838d0 fffff800`02ff0c06 : 00000000`024ef670 00000000`0000014d 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x607
fffff880`0a983a00 fffff800`02cd2e53 : fffffa80`1381b3b0 00000000`024ef658 fffff880`0a983a88 00000000`00000001 : nt!NtDeviceIoControlFile+0x56
fffff880`0a983a70 00000000`7704132a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 (TrapFrame @ fffff880`0a983ae0)
00000000`024ef628 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7704132a

2: kd> .trap fffff880`0a983330
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8013919100
rdx=0000000000000202 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88005145fb9 rsp=fffff8800a9834c0 rbp=fffffa80156085b0
 r8=0000000000000000  r9=000000002e71e190 r10=0000000000000000
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
[COLOR="rgb(46, 139, 87)"][COLOR="SeaGreen"]portcls!CPortPinWaveCyclic[/COLOR][/COLOR]::GetPosition+0xe9:
fffff880`05145fb9 184c8d43        sbb     byte ptr [rbp+rcx*4+43h],cl ss:0018:ffffe480`63a6c9f3=??

portcls is a driver for ports, It seems it's caused by your audio driver.

Your Intel Rapid Storage Technology Filter Driver is causing problems. It doesn't seem too outdated but I would still recommend looking to see if there is a newer version.

http://downloadcenter.intel.com/Default.aspx

fffff880`0a5bd250 fffff800`02dedb90 : 00000000`ce63a000 00000000`00001000 00000000`00009536 00000000`00000000 : nt!MmMapIoSpace+0x2a3
fffff880`0a5bd380 fffff800`02deeb03 : 00000000`000ce63a 00000000`00000000 00000000`00000000 fffff880`0100b6ea : nt!MiAllocateContiguousMemory+0x2d0
fffff880`0a5bd410 fffff880`01007036 : 00000000`00000000 fffff880`0100bb21 00000000`00000000 fffffa80`1b2abcf0 : nt!MmAllocateContiguousMemorySpecifyCache+0x53
fffff880`0a5bd450 fffff880`010196cf : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`0105831a : storport!StorAllocateContiguousIoResources+0x26
fffff880`0a5bd490 fffff880`01019894 : fffffa80`1b2abcf0 fffff880`01002a01 fffff880`00000000 fffff880`00000000 : storport!RaidAdapterScsiMiniportIoctlWithAddress+0x8f
fffff880`0a5bd510 fffff880`01053f2d : 00000000`0000003d 00000000`0000003d fffffa80`1b2abcf0 fffff800`02fbe8b4 : storport!RaidAdapterScsiMiniportIoctl+0x14
fffff880`0a5bd550 fffff880`010530a0 : fffff880`0101f110 fffffa80`0e958060 00000000`00000001 fffffa80`0eb89b70 : storport! ?? ::NNGAKEGL::`string'+0x486
fffff880`0a5bd5a0 fffff880`01d91b9e : fffffa80`0eb89b70 fffffa80`185f6cf0 fffff880`0a5bd730 00000000`00000000 : storport!RaDriverDeviceControlIrp+0x90
fffff880`0a5bd5e0 fffffa80`0eb89b70 : fffffa80`185f6cf0 fffff880`0a5bd730 00000000`00000000 fffffa80`0f229480 : [COLOR="Red"]iaStorF+0x2b9e[/COLOR]
fffff880`0a5bd5e8 fffffa80`185f6cf0 : fffff880`0a5bd730 00000000`00000000 fffffa80`0f229480 fffffa80`0000003d : 0xfffffa80`0eb89b70
fffff880`0a5bd5f0 fffff880`0a5bd730 : 00000000`00000000 fffffa80`0f229480 fffffa80`0000003d 00000000`00000000 : 0xfffffa80`185f6cf0
fffff880`0a5bd5f8 00000000`00000000 : fffffa80`0f229480 fffffa80`0000003d 00000000`00000000 fffff880`0a5bd640 : 0xfffff880`0a5bd730

 

[alexb1187]

Unfortunately the drivers I'm running for my sound card are the newest available.

I thought I removed Intel Rapid Storage a few days ago. Looking back at post http://www.sevenforums.com/bsod-hel...m-bsod-various-error-codes-3.html#post2737536

My device manager doesn't mention IRST as the controller, but I clearly still have the driver files (please see screenshots attached). Maybe I'm confusing two separate things...

 

[alexb1187]

I am running only one stick of ram now, in slot one on the motherboard. Ram tested fine through pass 8. I will let you know if I get another blue screen.

Thank you all for helping me with this.

 

[andrew129260]

Just for fun, I noticed that your WEI score needs to be refreshed. It you clear all scores and rerate the system under performance information and tools-advanced tools. Does running that small benchmark cause any bsod's? If it bsod's on the wei, that would indicate to me a failed hardware as the cause as it tests all hardware one by one.

 

[alexb1187]

Thanks Andrew, I will try that this evening when I get home. I believe the WEI needs refreshing because I removed all but one RAM stick. Should I plug the other sticks back in, then test? Or test as it is now?

 

[andrew129260]

Test as it is now, and use it for awhile with that one stick of ram and let us know if a bsod happens again.

 

[alexb1187]

I re-ran the windows experience index; no blue screen. The overall score didn't change, but the memory subscore did change (now 7.8 where it was 7.9 before).

 

[andrew129260]

Okay, can you confirm you have done these things as suggested:

1. Apologies for I have not read over this whole thread, but Can you remove all ram sticks except one, and run the mem test on that? If that one ram stick works well, can we use the system as normal with one stick of ram and see how things go?
   (since you do not want to do a clean install) You have done this already
2. Also, you could make a system image with windows 7 backup and restore center, or the free macrium.
3. Image your system with free Macrium
4. Then you can do a clean install, add no software (just updated drivers) and use just internet explorer for a while, or test with prime 95 and see if any bsods occur. If they do, it defiantly is not a software problem.
5. Once that is discovered its not a software issue, you can then restore the system image and everything is back to normal and the way it was before we messed with your system. If it is a software problem, we can narrow it down to see what program it is that is causing it.

 

[alexb1187]

I have a system image from windows 7 backup and restore center. Do I still need to use macrium to create a system image? Can I use my original windows 7 installation disk to restore from a system image, or do I need to create a repair disk? In the fresh install, am I still only running 1 memory stick, or am I plugging them all in? Can I use the same product key for the install? (Do I need to use a product key if its going to only be for (hopefully) a few days?)

 

[alexb1187]

Also, you said "add no software (just updated drivers)"... should I install an antivirus?

 

[andrew129260]

Create a system image with your installation the way it is now, all your programs and everything installed. Then format your drive and reinstall windows-and drivers. Then windows updates. No antivirus or anything else. that one stick of ram you tested that's good. You don't even need to connect it to the internet. Try downloading the latest drivers from your motherboard manufacture as well as the latest graphics drivers. With just windows updated, like sp1 for example. (you dont need every windows update) and updated drivers, run prime 95 or some other stress testing program of your choice, and see if the system bluescreens. If so, we know its hardware. If not, its most likely software.

 

[alexb1187]

Been stress testing in the windows reinstall with no blue screens. However, it was never easily reproducible, so I don't know if the stress test would have caused it. Also, with only one stick of RAM in, this feels like an incomplete test. Now that I'm thinking about it, do you think the issue could be with RAM voltage? I think I remember reading that it's a good idea to slightly over-current RAM if you have all 4 slots populated. Is that true? Pretty sure I'm running at the default 1.5v. Maybe it could help to make it 1.510v or something?

Please advise on if I should continue stress testing with one RAM stick, and if when I do go back to 4 stick, if I should overvolt.

 

[andrew129260]

If running prime95 handles fine on 1 stick, go back to having them all in. Then see what happens with running prime 95. I am not a expert on timings and voltages, so I might ask another member for help on that subject, but lets see how it does here.

 

[alexb1187]

I ran prime95 for around 10 hours last night, and SiSoftware Sandra full PC benchmark a couple times today. I also re-ran the WEI test. No errors or blue screens.

 

[alexb1187]

I have restored back into my original windows installation. I uninstalled a bunch of apps that I thought may be causing the problem (ALL mobo utilities, team viewer, corsair link). I will let you know if another blue screen happens.

 

[alexb1187]

Oh and I actually saw the thing about needing to increase voltage with 4 RAM stick here in SevenForums: http://www.sevenforums.com/hardware-devices/240336-memory-causing-bsod.html#post2005362

 

[andrew129260]

Ok great, put the system image back in and see if bsods occur. Because if they do, its software

 

[alexb1187]

Well, that didn't take long. Came home from work and had a blue screen waiting for me. Definitely something wrong with this system image.

 

[andrew129260]

Well, since you ran all the time hardware is most likely not a issue. What programs do you have set to run with your pc?

You can use ccleaner to grab a report, or simply take screenshots of msconfig on the startup tab.

 

[alexb1187]

Here's the list from CCleaner