BSOD now and then. New to longtime stable PC. Not seeing much pattern.

System was ultra stable for a very long time. No BSOD. Very solid. I recently started having BSOD issues. I am posting looking for some help and insight on my issue. Anything is very much appreciated.

Here are some images of the Blue Screens:
imgur: the simple image sharer
imgur: the simple image sharer


Who Crashed is pasted at the bottom of this post.

This machine is a Workstation / Gaming / Everything else.
Bloomfield I7.
G.Skill 24GB Ripjaws
1 240gb Kingston SSDNOW C Drive with Windows 7 Ultimate 64 Fully updated.
1 Seagate 1tb D Drive 7200rpm
Nvidia GTX 780 (latest drivers. BSOD has happened while on 2 dif driver versions)
Drobo is often connected via USB (have had it for ages)
APC 1300 UPS

A few days before the first Blue Screen my D drive disappeared in Windows. It came back upon reboot. It has not happened since.

Things I have done:
- Memtest in Windows
- Memtest86 boot off USB and ran for ~3-4 hrs.
- Seatools to test the HDD
- Crystal Disk (Good)
- Full windows update of critical/needed updates (has Blue Screened Since)
- Full scans with Avast / Malware Bytes / Spybot S&D (BSOD since)
- Prime95 torture test (CPU Temps). Seem fine.


What should I do/try now?


My current course of action is to air gun and make sure everything is fine cable-wise etc...
Then perhaps replace the D drive with a new Seagate 3tb 7200.
Then if that doesn't work I was thinking getting a new SSD which sadly means full new installs

I have not ran chkdsk or done a "use last known good configuration". Would those be good to do?



Thanks!!!



WhoCrashed:
On Wed 2/12/2014 10:47:42 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\021214-19562-01.dmp
This was probably caused by the following module: scsiport.sys (SCSIPORT+0x178AC)
Bugcheck code: 0x7A (0xFFFFF6FC400089E8, 0xFFFFFFFFC000009D, 0x42CEA9860, 0xFFFFF8800113D8AC)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\scsiport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: SCSI Port Driver
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Wed 2/12/2014 10:47:42 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: scsiport.sys (SCSIPORT+0x178AC)
Bugcheck code: 0x7A (0xFFFFF6FC400089E8, 0xFFFFFFFFC000009D, 0x42CEA9860, 0xFFFFF8800113D8AC)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\drivers\scsiport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: SCSI Port Driver
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Fri 2/7/2014 2:40:31 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020614-26941-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0xF4 (0x3, 0xFFFFFA8013FAC060, 0xFFFFFA8013FAC340, 0xFFFFF80003781350)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 1/30/2014 8:47:13 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\013014-17222-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x7A (0xFFFFF6FB40000050, 0xFFFFFFFFC000009D, 0x59B55E884, 0xFFFFF6800000A000)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the requested page of kernel data from the paging file could not be read into memory.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

Thanks!

Uploaded the file.

Thanks!

Also. This could be a coincidence but 3 of the BSOD's have been while in the middle of sending a network render over to another machine on the network. Or possibly while saving a file.

It is funny that they seem to happen when I do a big operation and get up and walk away from my machine!

My latest BSOD references SCSIPORT.SYS


note:
- I have done this process on a different project a ton of times before I started to get BSOD's. Same machine. Same setup. And all was fine.

- I've had BSOD's that did not involve that same project or network rendering etc....

Yet another BSOD in the middle of saving what would be a 2.2gb file from a program, and to the D Drive. File made it to 300m before BSOD occurred.

I still do not know enough about Blue Screens to know exactly what is going on though.

I did all of that stuff. Nothing showed up on chkdsk and seatools. Things were good for about a week and I thought I was fine and then today I just got 2 blue screens. One was shortly after I plugged my IPAD into a USB hub. The other was just while youtube videos were playing and I wasn't really doing anything. Nothing in the hub or front panel usb.

Both of the blue screens reference SCSIPORT.SYS


This is going to sound really strange. But at this point i'd say 75% of the blue screens have occurred after I get up and walk away from the computer. Within like 15 seconds. So much so it is almost a joke where I will get up to get water or check on something and I will listen to hear if it blue screens.

I know my house can have really bad static electricity. But I've been here for 4 years and never had BSODs.

Golden said:

Additional information is required.

1. Download the Designer Media Log Collector file to your desktop by clicking the icon

Download


2. Run it by double-clicking the icon, and follow the prompts.
3. Locate the .ZIP file created on your desktop, and upload it here in your next reply.

It says invalid link.


So the standing up / walking away from computer thing has become oddly consistent. I went the whole week with no BSOD. When I would get up and walk away from the computer I would always look back.
Today I stood up to go do something and was standing there. Then I heard the audio from the music I was listening to freaking out and getting wacky. My mouse would barely move. Everything got stutttery and then BSOD.

Now i'm trying to secure wires and things.

I can try what you were posting if you think it would help. I would really like to keep this machine. But right now the BSOD's are a one step forward 2 steps back for my work.
thanks

I thought I would come back and post about this.

It has been a couple of weeks since my last BSOD. Although I have had 2 hard-locks on my machine since (and usually didn't get those). But no BSOD.

I like to think I figured it out the issue and it was Spotify. If it wasn't spotify then it is related to the PLAY button on my keyboard that I used to start and stop Spotify.

Previously I had mentioned the crazy behavior of the machine usually doing a BSOD shortly after getting up from my computer and walking around. Well! I would hit play on spotify or on my keyboard for spotify and get up and do dishes or clean the house. I started to figure this out after a while. I uninstalled Spotify. So far no BSOD, for weeks now. But also I do not press the Play button on my keyboard either.

Just thought I would post this incase anybody is searching around and comes across it.

I will say I did run searches for BSOD + Spotify before and saw a few posts but it wasn't until later that I was quite sure of it and uninstalled.