BSOD ntoskrnl.exe+70740

[djl]

Since Monday 11 July my workstation has now bluescreened 6 times with the same crash address each time, the last mini dump is attached. Any advice as to how to resolve the problem will be gratefully received.

 

[SmurofNeves]

Please re-post: http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

And welcome to the forums.!!

 

[SmurofNeves]

Since Monday 11 July my workstation has now bluescreened 6 times with the same crash address each time, the last mini dump is attached. Any advice as to how to resolve the problem will be gratefully received.

I don't see any attachments.??:huh:

 

[djl]

not for want of trying, firewall isuues i think...:huh:

 

[djl]

dump file attachment

uploaded over wireless to avoid firewall/proxy constraints...

 

[SmurofNeves]

Analyzing!!:devil2:

Your prob. "msiscsi.sys" = "Microsoft iSCSI Initiator Driver"

Are you running a raid setup? If not...

Use DRIVERSWEEPER to uninstall the scsi initiator driver..

Post back whats up there. Only uninstall if 3rd party driver!!!

Try Integrity Scan = "winkey + R" > "CMD" > "SFC / scannow"

You can also check your "Device Manager" for any warnings.. you can try updating the scsi driver from there aswell.

Device manager = "Right-click Computer" > "Manage" > "DeviceManager"
or
Just post a screenshot of you device manager while the lists are open.

 

[djl]

The local HDD configuration is RAID 1, I also have an iSCSI initiator configuration that connects to a volume on a NAS box. This setup has been unchanged for 3 months, the BSOD started this week it is quite a puzzle.

That said the Microsoft iSCSI Initiator has always been reluctant to establish a connection to the resource. Am going to disable it and try StarWind as an alternative .

BTW a system restore to a time prior to the BSOD happening seemed to stabilise things yesterday but it shutdown unexpectedly overnight at 00:45, same error.