Solved Random BSOD Memory Management - 0x1A

[Archetype]

So we hashed out an issue with my G19 keyboard causing 0xC1 and other BSOD's (http://www.sevenforums.com/bsod-hel...ool_detected_memory_corruption-new-build.html) last week and the week before... Thank you Golden! I now have a new issue...

I am now receiving seemingly random 0x1A Memory Management BSOD's starting on 1/11/2015 (Everything before 1/11 is most likely linked to the keyboard). One started seemed to start on video playback on a website, the others seemed random.

Troubleshooting I have run both Win 7 Memory Diagnostic (Full Check) and Memtestx86+ (12 Hours and 10 Passes) and both came back clean.

Any ideas?

 

[Golden]

Follow:
1. Log in as administrator, open Windows Explorer and go to C:\Windows\Minidump
2. Delete all .dmp files in that folder
3. Run Driver Verifier as follows:

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

Driver Verifier will cause your computer to run very sluggishly - this is normal. What it is trying to do is force your system to BSOD and isolate the offending driver/s. When it does, reboot, disable driver verifier, reboot as normal, re-run the DM Log Collector, and upload the new ZIP file here.

I recommend creating a system restore point before turning on driver verifier:
http://www.sevenforums.com/tutorials/697-system-restore-point-create.html

If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
http://www.sevenforums.com/tutorials/69585-safe-mode.html

 

[Archetype]

Thank you for the response and your assistance once again.

I enabled Driver Verifier and restarted. Immediately after login (No password set for testing) and desktop loading, I received the attached BSOD's with following BSOD.

The DMA Subsystem has detected an illegal DMA Operation

STOP: 0x000000E6

I rebooted and received the same BSOD and stop code.

 

[Golden]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck E6, {f, 2, 38, fffff88003d18fc0}

Probably caused by : [B][COLOR="red"]SCSIPORT.SYS[/COLOR][/B] ( SCSIPORT!SpProcessCompletedRequest+341 )

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

7: kd> lmvm rr26xx
start             end                 module name
fffff880`0106a000 fffff880`010ab000   rr26xx     (deferred)             
    Image path: \SystemRoot\system32\drivers\rr26xx.sys
    Image name:[B][COLOR="red"] rr26xx.sys[/COLOR][/B]
    Timestamp:        Thu [B][COLOR="red"]Jul 31[/COLOR][/B] 16:45:52 [B][COLOR="Red"]2008[/COLOR][/B] (489166A8)
    CheckSum:         0003007A
    ImageSize:        00041000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Name	RocketRAID 2640X4 SAS Controller
Manufacturer	HighPoint
Status	OK
PNP Device ID	PCI\VEN_1103&DEV_2640&SUBSYS_00041103&REV_02\4&14144E6&0&00E4
I/O Port	0x0000C000-0x0000C07F
Memory Address	0xF7140000-0xF7140FFF
IRQ Channel	IRQ 16
Driver	c:\windows\system32\drivers\rr26xx.sys (1.0.8.731, 181.03 KB (185,376 bytes), 7/31/2008 12:16 AM)

Im just guessing here since the only ISCSI device is the RocketRaid Controller......try updating the driver. Use system as normal - do not run Driver Verifier again - and lets see if we get another BSOD.

 

[Archetype]

I have updated the RR 2640X drivers. Strange thing as I had downloaded them during initial setup and was pretty sure I installed them. I may have removed the new drivers after my array dropped offline and I uninstalled and rebooted.

I restarted and was about to disable Verifier (I missed the Safe boot option) when I received a BSOD linked to Asus drivers which I then proceeded to uninstall and restart. I will close this out and start a new thread if I receive a different BSOD.

Thanks again Golden!