Identical BSOD's on my two Win7 Machines (2nd system Main Desktop PC)

usasma · November 23, 2017

I'd keep it turned off for now. Just remember that, when we're done, you'll have to turn it back on then.

The 0xC000000D error:

Quote


// MessageId: STATUS_INVALID_PARAMETER
//
// MessageText:
//
// An invalid parameter was passed to a service or function.
//
#define STATUS_INVALID_PARAMETER         ((NTSTATUS)0xC000000DL)    // winnt

Be careful about the times in Event Viewer - especially if using the Administrative log file
Sometimes you'll find that "right before" is actually a gap of several hours - or that the time for "right before" is actually after.

CPUID is usually a stable program, but it won't hurt things to uninstall it.
And, with that, it's one less thing to worry about.

I'm also about to suggest uninstalling:
- Elby
- MalwareBytes (all of it)
- Virtual Clone CD

After that, if the BSOD's continue, then we'd work on removing the other drivers and updating them one-by-one.

CommonCurt · November 27, 2017

Okay, had another BSOD with Driver Verifier turned on again.

Ugg, you listed 3 of the programs i'd really prefer not to have to get rid of.

112717-21512-01.zip

usasma · November 27, 2017

Late for work right now, and have to work early tomorrow - hope to get to this in the AM

As for removing them - it's only needed temporarily.
Just remove them long enough to see if it stops the BSOD's.

usasma · November 28, 2017

Basically the same as the last time......

Uninstalling the programs is just one step in the process.

Next, I'll likely suggest a clean install of Windows - to definitely rule out the 3rd party drivers, and to ensure that it's not a Windows corruption.
That'll either fix it - or not.
If it does fix it - then the problem was either the 3rd party software or the Windows installation.
If it doesn't fix it - then the problem is hardware.

Analysis:
The following is for information purposes only.
The following information contains the relevant information from the blue screen analysis:

**************************Mon Nov 27 07:34:43.007 2017 (UTC - 5:00)**************************

Loading Dump File [C:\Users\john\SysnativeBSODApps\112717-21512-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: 7601.23915.amd64fre.win7sp1_ldr.170913-0600
System Uptime:4 days 7:38:27.750
*** WARNING: Unable to verify timestamp for iaStorA.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys
Probably caused by :iaStorA.sys ( iaStorA+877b8 )
BugCheck D1, {10, 2, 1, fffff880016e97b8}
BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
Arguments:
Arg1: 0000000000000010, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff880016e97b8, address which referenced memory
BUGCHECK_STR: 0xD1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_0xD1_iaStorA+877b8
CPUID: "Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz"
MaxSpeed: 3500
CurrentSpeed: 3503
BIOS Version F16h
BIOS Release Date 07/11/2016
Manufacturer Gigabyte Technology Co., Ltd.
Product Name To be filled by O.E.M.
Baseboard Product Z77X-UD5H
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

3rd Party Drivers:
The following is for information purposes only.
My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft. You can find links to the driver information and where to update the drivers in the section after the code box:

**************************Mon Nov 27 07:34:43.007 2017 (UTC - 5:00)**************************
MpKsld163fb0c.sys Mon Feb 27 20:54:41 1989 (2409FBE1)
intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
MBfilt64.sys Thu Jul 30 23:40:32 2009 (4A7267B0)
amdxata.sys Fri Mar 19 12:18:18 2010 (4BA3A3CA)
VClone.sys Sat Jan 15 11:21:04 2011 (4D31C970)
ArcSec.sys Wed Nov 9 22:05:33 2011 (4EBB3F7D)
mvxxmm.sys Thu Jan 19 01:50:44 2012 (4F17BD44)
mvs91xx.sys Thu Jan 19 01:51:00 2012 (4F17BD54)
iaStor.sys Wed Feb 1 19:15:24 2012 (4F29D59C)
e1c62x64.sys Thu Mar 15 23:57:28 2012 (4F62BA28)
iusb3hub.sys Mon May 21 03:21:36 2012 (4FB9ED00)
iusb3xhc.sys Mon May 21 03:21:40 2012 (4FB9ED04)
iusb3hcs.sys Mon May 21 03:23:42 2012 (4FB9ED7E)
L1C62x64.sys Wed Jul 18 22:55:34 2012 (50077726)
cpuz136_x64.sys Fri May 10 08:42:51 2013 (518CEB4B)
iaStorA.sys Thu Aug 1 21:39:52 2013 (51FB0DE8)
iaStorF.sys Thu Aug 1 21:39:54 2013 (51FB0DEA)
TeeDriverx64.sys Thu Sep 5 14:02:18 2013 (5228C72A)
RTKVHD64.sys Wed Dec 10 02:53:17 2014 (5487FBED)
ElbyCDIO.sys Wed Dec 17 18:30:51 2014 (5492122B)
AnyDVD.sys Mon Dec 28 07:52:15 2015 (5681307F)
MpFilter.sys Mon Aug 8 19:01:17 2016 (57A90F3D)
nvhda64v.sys Tue May 16 09:02:27 2017 (591AF863)
nvlddmkm.sys Tue Jun 27 16:00:30 2017 (5952B95E)
mwac.sys Thu Sep 7 12:04:06 2017 (59B16DF6)
mbam.sys Thu Oct 12 11:23:13 2017 (59DF88E1)
mbamswissarmy.sys Fri Oct 13 14:58:51 2017 (59E10CEB)
MbamChameleon.sys Mon Oct 30 12:34:36 2017 (59F7549C)

Edited November 28, 2017 by usasma

CommonCurt · November 28, 2017

I'll definitely try uninstalling some things, but the whole reason I created this thread was to avoid having to do Windows7 re-installs.

usasma · November 29, 2017

I understand and sympathize with you.
But sometimes a repair just isn't possible.
I know that I'm about out of ideas here.

Maybe you should try this at several different forums in order to see if there are any different approaches that might work for you.
Good luck!

CommonCurt · December 5, 2017

Just found another BSOD when I woke up today.

WhoCrashed is again saying that it's iaStorA+877b8.

120517-19952-01.zip

usasma · December 5, 2017

There's less in the way of drivers in this one.
If we presume that the drivers in the dump are the only ones to blame - then there's less to worry about here.
The drawback is what if the faulting driver isn't present in the dump?
And, just to make it a bit more difficult - what if the developers have stopped updating the drivers for W7 (so they can spend more profitable time working on W10 drivers)?

Analysis:
The following is for information purposes only.
The following information contains the relevant information from the blue screen analysis:
**************************Tue Dec 5 08:21:10.384 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\120517-19952-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: 7601.23915.amd64fre.win7sp1_ldr.170913-0600
System Uptime:4 days 5:52:51.101
*** WARNING: Unable to verify timestamp for iaStorA.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys
Probably caused by :iaStorA.sys ( iaStorA+877b8 )
BugCheck D1, {10, 2, 1, fffff880017057b8}
BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
Arguments:
Arg1: 0000000000000010, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff880017057b8, address which referenced memory
BUGCHECK_STR: 0xD1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_0xD1_iaStorA+877b8
CPUID: "Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz"
MaxSpeed: 3500
CurrentSpeed: 3503
BIOS Version F16h
BIOS Release Date 07/11/2016
Manufacturer Gigabyte Technology Co., Ltd.
Product Name To be filled by O.E.M.
Baseboard Product Z77X-UD5H
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

3rd Party Drivers:
The following is for information purposes only.
My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft. You can find links to the driver information and where to update the drivers in the section after the code box:
**************************Tue Dec 5 08:21:10.384 2017 (UTC - 5:00)**************************
MpKsl1e7e9c77.sys Mon Feb 27 20:54:41 1989 (2409FBE1)
intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
MBfilt64.sys Thu Jul 30 23:40:32 2009 (4A7267B0)
amdxata.sys Fri Mar 19 12:18:18 2010 (4BA3A3CA)
VClone.sys Sat Jan 15 11:21:04 2011 (4D31C970)
ArcSec.sys Wed Nov 9 22:05:33 2011 (4EBB3F7D)
mvxxmm.sys Thu Jan 19 01:50:44 2012 (4F17BD44)
mvs91xx.sys Thu Jan 19 01:51:00 2012 (4F17BD54)
iaStor.sys Wed Feb 1 19:15:24 2012 (4F29D59C)
e1c62x64.sys Thu Mar 15 23:57:28 2012 (4F62BA28)
iusb3hub.sys Mon May 21 03:21:36 2012 (4FB9ED00)
iusb3xhc.sys Mon May 21 03:21:40 2012 (4FB9ED04)
iusb3hcs.sys Mon May 21 03:23:42 2012 (4FB9ED7E)
L1C62x64.sys Wed Jul 18 22:55:34 2012 (50077726)
cpuz136_x64.sys Fri May 10 08:42:51 2013 (518CEB4B)
iaStorA.sys Thu Aug 1 21:39:52 2013 (51FB0DE8)
iaStorF.sys Thu Aug 1 21:39:54 2013 (51FB0DEA)
TeeDriverx64.sys Thu Sep 5 14:02:18 2013 (5228C72A)
RTKVHD64.sys Wed Dec 10 02:53:17 2014 (5487FBED)
ElbyCDIO.sys Wed Dec 17 18:30:51 2014 (5492122B)
AnyDVD.sys Mon Dec 28 07:52:15 2015 (5681307F)
MpFilter.sys Mon Aug 8 19:01:17 2016 (57A90F3D)
nvhda64v.sys Tue May 16 09:02:27 2017 (591AF863)
nvlddmkm.sys Tue Jun 27 16:00:30 2017 (5952B95E)
mwac.sys Thu Sep 7 12:04:06 2017 (59B16DF6)
mbam.sys Thu Oct 12 11:23:13 2017 (59DF88E1)
mbamswissarmy.sys Fri Oct 13 14:58:51 2017 (59E10CEB)
MbamChameleon.sys Mon Oct 30 12:34:36 2017 (59F7549C)

Edited December 5, 2017 by usasma

CommonCurt · December 12, 2017

Had another when I came home today.

121117-18439-01.zip

usasma · December 12, 2017

I can't recall - have you tried a clean boot on either of the systems?
Perform a Clean Boot: http://www.thewindowsclub.com/what-is-clean-boot-state-in-windows

If that stops the problem, then re-enable things a few at a time until you figure out what's causing it.
Then uninstall the problem program (from Start...Settings...Apps...Apps & Features - if you don't find it there, check the right sidebar for Programs and Features and see if you can remove it from there).

Beyond that, this memdory dump is basically the same as the others.
We're at a point now where there's not much else we can do here.
Further analysis by an expert who is more skilled with WinDbg than I am might reveal something.
Try posting on the BSOD forums at http://www.sysnative.com , I haven't been active there in years so I'm unsure of who's still working there.
Beyond that, you're looking at a live debugging session to do this - and that can get very, very expensive very quickly. For more info on that, I'd talk with the people at https://www.osr.com/

Analysis:
The following is for information purposes only.
The following information contains the relevant information from the blue screen analysis:
**************************Mon Dec 11 07:31:52.682 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\121117-18439-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: 7601.23915.amd64fre.win7sp1_ldr.170913-0600
System Uptime:5 days 23:09:46.510
*** WARNING: Unable to verify timestamp for iaStorA.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys
Probably caused by :iaStorA.sys ( iaStorA+877b8 )
BugCheck D1, {10, 2, 1, fffff880016887b8}
BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
Arguments:
Arg1: 0000000000000010, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff880016887b8, address which referenced memory
BUGCHECK_STR: 0xD1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_0xD1_iaStorA+877b8
CPUID:        "Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: 3503
BIOS Version                  F16h
BIOS Release Date             07/11/2016
Manufacturer                  Gigabyte Technology Co., Ltd.
Product Name                  To be filled by O.E.M.
Baseboard Product             Z77X-UD5H
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``]

3rd Party Drivers:
The following is for information purposes only.
My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft. You can find links to the driver information and where to update the drivers in the section after the code box:
**************************Mon Dec 11 07:31:52.682 2017 (UTC - 5:00)**************************
MpKsl7aaa59a6.sys   Mon Feb 27 20:54:41 1989 (2409FBE1)
intelppm.sys        Mon Jul 13 19:19:25 2009 (4A5BC0FD)
MBfilt64.sys        Thu Jul 30 23:40:32 2009 (4A7267B0)
amdxata.sys         Fri Mar 19 12:18:18 2010 (4BA3A3CA)
VClone.sys          Sat Jan 15 11:21:04 2011 (4D31C970)
ArcSec.sys          Wed Nov 9 22:05:33 2011 (4EBB3F7D)
mvxxmm.sys          Thu Jan 19 01:50:44 2012 (4F17BD44)
mvs91xx.sys         Thu Jan 19 01:51:00 2012 (4F17BD54)
iaStor.sys          Wed Feb 1 19:15:24 2012 (4F29D59C)
e1c62x64.sys        Thu Mar 15 23:57:28 2012 (4F62BA28)
iusb3hub.sys        Mon May 21 03:21:36 2012 (4FB9ED00)
iusb3xhc.sys        Mon May 21 03:21:40 2012 (4FB9ED04)
iusb3hcs.sys        Mon May 21 03:23:42 2012 (4FB9ED7E)
L1C62x64.sys        Wed Jul 18 22:55:34 2012 (50077726)
cpuz136_x64.sys     Fri May 10 08:42:51 2013 (518CEB4B)
iaStorA.sys         Thu Aug 1 21:39:52 2013 (51FB0DE8)
iaStorF.sys         Thu Aug 1 21:39:54 2013 (51FB0DEA)
TeeDriverx64.sys    Thu Sep 5 14:02:18 2013 (5228C72A)
RTKVHD64.sys        Wed Dec 10 02:53:17 2014 (5487FBED)
ElbyCDIO.sys        Wed Dec 17 18:30:51 2014 (5492122B)
AnyDVD.sys          Mon Dec 28 07:52:15 2015 (5681307F)
MpFilter.sys        Mon Aug 8 19:01:17 2016 (57A90F3D)
nvhda64v.sys        Tue May 16 09:02:27 2017 (591AF863)
nvlddmkm.sys        Tue Jun 27 16:00:30 2017 (5952B95E)
mwac.sys            Thu Sep 7 12:04:06 2017 (59B16DF6)
mbam.sys            Thu Oct 12 11:23:13 2017 (59DF88E1)
mbamswissarmy.sys   Fri Oct 13 14:58:51 2017 (59E10CEB)
MbamChameleon.sys   Tue Nov 28 23:17:27 2017 (5A1E34D7)

CommonCurt · December 17, 2017

I haven't tried doing a clean boot on either system because of how long it takes for the BSODs to show up (this system around 5 days, and on the other system 7-10 days).

It never happens right after a restart. After I try uninstalling somethings if that doesn't flush out what's causing it I might consider trying clean boot, but it would take a long time with how long in between the BSODs are.

I also will look into the other forum that you mentioned. Then, as a last resort, I might go back and start installing the Monthly roll up Updates starting with the Month when my problem started.

Just for the sake of it I attached the first two BSODs I received on this system when all of this started. Maybe one of them can give some information that we haven't gotten from the current ones.

071317-7956-01.zip

071317-8782-01.zip

CommonCurt · January 6, 2018

On 12/12/2017 at 8:46 AM, usasma said:

I can't recall - have you tried a clean boot on either of the systems?
Perform a Clean Boot: http://www.thewindowsclub.com/what-is-clean-boot-state-in-windows

If that stops the problem, then re-enable things a few at a time until you figure out what's causing it.
Then uninstall the problem program (from Start...Settings...Apps...Apps & Features - if you don't find it there, check the right sidebar for Programs and Features and see if you can remove it from there).

Beyond that, this memdory dump is basically the same as the others.
We're at a point now where there's not much else we can do here.
Further analysis by an expert who is more skilled with WinDbg than I am might reveal something.
Try posting on the BSOD forums at http://www.sysnative.com , I haven't been active there in years so I'm unsure of who's still working there.
Beyond that, you're looking at a live debugging session to do this - and that can get very, very expensive very quickly. For more info on that, I'd talk with the people at https://www.osr.com/

Hey,

Not sure if you saw my last post above due to the holidays, but I managed to find the first BSOD (when all this started), and it looks like the very first one might say something a little different.

usasma · January 6, 2018

In general, I don't usually mess with memory dumps older than about 2 months.
The reason for this are that the system has likely changed too much for an analysis to be significant.
Also, I've seen systems like this that have had BSOD issues from months ago that were fixed back then - just as the new BSOD's started. And this makes an analysis that much more difficult - as you don't have any idea which of the things are actually causing problems - and which are "red herrings".

In this case, the first memory dump is one that doesn't point specifically to a problem driver. If this were a current memory dump, I'd ask you to run Driver Verifier - but as it's very old, the chances of us getting anything significant out of it aren't very good.

And the second memory dump is just another of the iaStorA.sys ones

Analysis:
The following is for information purposes only.
The following information contains the relevant information from the blue screen analysis:
**************************Thu Jul 13 04:07:55.669 2017 (UTC**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\071317-7956-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: 7601.23807.amd64fre.win7sp1_ldr.170512-0600
System Uptime:0 days 0:00:11.481
Probably caused by :Pool_Corruption ( nt!ExDeferredFreePool+192 )
BugCheck C5, {fffff810038086b0, 2, 0, fffff800037ada5e}
BugCheck Info: DRIVER_CORRUPTED_EXPOOL (c5)
Arguments:
Arg1: fffff810038086b0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff800037ada5e, address which referenced memory
BUGCHECK_STR: 0xC5_2
PROCESS_NAME: svchost.exe
FAILURE_BUCKET_ID: X64_0xC5_2_nt!ExDeferredFreePool+192
CPUID: "Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz"
MaxSpeed: 3500
CurrentSpeed: 3503
BIOS Version F16h
BIOS Release Date 07/11/2016
Manufacturer Gigabyte Technology Co., Ltd.
Product Name To be filled by O.E.M.
Baseboard Product Z77X-UD5H
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jul 13 01:28:35.855 2017 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\071317-8782-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Built by: 7601.23807.amd64fre.win7sp1_ldr.170512-0600
System Uptime:9 days 21:09:03.260
*** WARNING: Unable to verify timestamp for iaStorA.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys
Probably caused by :iaStorA.sys ( iaStorA+877b8 )
BugCheck D1, {10, 2, 1, fffff880017787b8}
BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
Arguments:
Arg1: 0000000000000010, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff880017787b8, address which referenced memory
BUGCHECK_STR: 0xD1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
FAILURE_BUCKET_ID: X64_0xD1_iaStorA+877b8
CPUID: "Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz"
MaxSpeed: 3500
CurrentSpeed: 3503
BIOS Version F16h
BIOS Release Date 07/11/2016
Manufacturer Gigabyte Technology Co., Ltd.
Product Name To be filled by O.E.M.
Baseboard Product Z77X-UD5H
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
3rd Party Drivers:
The following is for information purposes only.
My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft. You can find links to the driver information and where to update the drivers in the section after the code box:

*************************Thu Jul 13 04:07:55.669 2017 (UTC - 5:00)**************************
intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
MBfilt64.sys Thu Jul 30 23:40:32 2009 (4A7267B0)
amdxata.sys Fri Mar 19 12:18:18 2010 (4BA3A3CA)
VClone.sys Sat Jan 15 11:21:04 2011 (4D31C970)
vstor2-mntapi10-shared.sys Tue Jul 12 12:35:21 2011 (4E1C77C9)
ArcSec.sys Wed Nov 9 22:05:33 2011 (4EBB3F7D)
mvxxmm.sys Thu Jan 19 01:50:44 2012 (4F17BD44)
mvs91xx.sys Thu Jan 19 01:51:00 2012 (4F17BD54)
iaStor.sys Wed Feb 1 19:15:24 2012 (4F29D59C)
e1c62x64.sys Thu Mar 15 23:57:28 2012 (4F62BA28)
vmci.sys Mon Apr 30 21:14:27 2012 (4F9F38F3)
vsock.sys Mon Apr 30 21:15:24 2012 (4F9F392C)
iusb3hub.sys Mon May 21 03:21:36 2012 (4FB9ED00)
iusb3xhc.sys Mon May 21 03:21:40 2012 (4FB9ED04)
iusb3hcs.sys Mon May 21 03:23:42 2012 (4FB9ED7E)
HECIx64.sys Mon Jul 2 18:14:58 2012 (4FF21D62)
VMNET.SYS Sun Jul 8 03:58:34 2012 (4FF93DAA)
vmnetadapter.sys Sun Jul 8 03:58:35 2012 (4FF93DAB)
vmnetbridge.sys Sun Jul 8 03:59:19 2012 (4FF93DD7)
L1C62x64.sys Wed Jul 18 22:55:34 2012 (50077726)
hcmon.sys Wed Aug 1 20:10:29 2012 (5019C575)
vmnetuserif.sys Wed Aug 15 16:31:54 2012 (502C073A)
vmx86.sys Wed Aug 15 18:05:11 2012 (502C1D17)
iaStorA.sys Thu Aug 1 21:39:52 2013 (51FB0DE8)
iaStorF.sys Thu Aug 1 21:39:54 2013 (51FB0DEA)
RTKVHD64.sys Wed Dec 10 02:53:17 2014 (5487FBED)
ElbyCDIO.sys Wed Dec 17 18:30:51 2014 (5492122B)
AnyDVD.sys Mon Dec 28 07:52:15 2015 (5681307F)
mbae64.sys Fri Apr 29 06:10:09 2016 (57233301)
MpFilter.sys Mon Aug 8 19:01:17 2016 (57A90F3D)
nvvad64v.sys Mon Feb 6 04:37:01 2017 (589843BD)
nvhda64v.sys Wed Mar 15 08:48:41 2017 (58C93829)
nvlddmkm.sys Mon May 1 15:58:03 2017 (5907934B)
MBAMSwissArmy.sys Thu May 18 14:34:35 2017 (591DE93B)
MBAMChameleon.sys Fri May 26 16:53:01 2017 (592895AD)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Thu Jul 13 01:28:35.855 2017 (UTC - 5:00)**************************
WinRing0x64.sys Sat Jul 26 09:29:37 2008 (488B26C1)
cpuz136_x64.sys Fri May 10 08:42:51 2013 (518CEB4B)
MpKslf8d96674.sys Tue May 19 21:50:37 2015 (555BE86D)
farflt.sys Fri Mar 24 11:34:26 2017 (58D53C82)
mbam.sys Fri May 19 12:02:10 2017 (591F1702)
mwac.sys Thu May 25 15:13:56 2017 (59272CF4)

Identical BSOD's on my two Win7 Machines (2nd system Main Desktop PC)

Recommended Posts

Link to post

Share on other sites

Link to post

Share on other sites

Link to post

Share on other sites

Link to post

Share on other sites

Link to post

Share on other sites

Link to post

Share on other sites

Link to post

Share on other sites

Link to post

Share on other sites

Link to post

Share on other sites

Link to post

Share on other sites

Link to post

Share on other sites

Link to post

Share on other sites

Link to post

Share on other sites

Create an account or sign in to comment

Create an account

Sign in

Recently Browsing 0 members

Important Information