Lots of BSOD Issues

Daniel112

Reputable
Jun 16, 2015
1
0
4,510
So basically I have been having BSOD issues for around a week, pretty varying error codes and today I reinstalled Windows due to these issues hoping it would at least partially fix my issues but I am still getting experiencing BSOD.

Here is my latest minidump.

Any and all help would be very appreciated, Thank you.
 
Solution
bug was in the filesystem, this can have various causes.

I would start by assuming it is caused by the storage driver:
\SystemRoot\system32\DRIVERS\iaStor.sys Tue Apr 26 11:06:18 2011
have intel search for a new driver https://downloadcenter.intel.com/
( i don't think intel driver would make this mistake but update the driver if you can)

remove your overclocking software:
C:\Program Files (x86)\MSI Afterburner\RTCore64.sys Fri Apr 24 00:01:47 2015
(I don't think it is a overclocking type bug, freeing the same memory address twice type error)

remove network packet cap driver:
\SystemRoot\system32\drivers\WPRO_41_2001.sys Mon Nov 07 13:04:48 2011

I would expect this to be the cause of your problem.

note:
if you have a USB storage...
bug was in the filesystem, this can have various causes.

I would start by assuming it is caused by the storage driver:
\SystemRoot\system32\DRIVERS\iaStor.sys Tue Apr 26 11:06:18 2011
have intel search for a new driver https://downloadcenter.intel.com/
( i don't think intel driver would make this mistake but update the driver if you can)

remove your overclocking software:
C:\Program Files (x86)\MSI Afterburner\RTCore64.sys Fri Apr 24 00:01:47 2015
(I don't think it is a overclocking type bug, freeing the same memory address twice type error)

remove network packet cap driver:
\SystemRoot\system32\drivers\WPRO_41_2001.sys Mon Nov 07 13:04:48 2011

I would expect this to be the cause of your problem.

note:
if you have a USB storage drive then the USB 3.0 drivers could be involved.

You should run cmd.exe as an admin, then run
verifier.exe /standard /all

then change your memory dump type from mini dump to kernel memory dump:
https://www.sophos.com/en-us/support/knowledgebase/111474.aspx: you need a kernel memory dump, not a full memory dump.


then reboot your system and wait for the next bugcheck. it will make a larger kernel memory dump at C:\windows\memory.dmp

it will have debug info saved in the .dmp file that will indicate the driver name and the error logs.

note: use
verifier.exe /reset
to turn off verifier functions after you are done testing or your machine will run slowly until you do.

post the new memory.dmp file or maybe use bluescreenviewer.exe or whocrashed.exe to get the name of the bad driver.
Otherwise someone with a windows debugger can look.



 
Solution