BSOD Not sure what the cause is

[Josparky]

Every once in a wile I get the dreaded BSOD. I am not sure what is causing this and could really use some help finding the problem. I have recently redone the PC because I put in a Evo Solid State Drive. I think my problems started when I installed a pci card I bought to have 3.0 usb plugs for my WD usb drives but I am not sure of that. Here is a link to the card I bought https://www.jacobsparts.com/items/PCIe-4X-USB3/

Here is what I get from whocrashed

System Information (local)
--------------------------------------------------------------------------------

computer name: JODY-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: p7-1225, Hewlett-Packard, PEGATRON CORPORATION, 2ACF
CPU: AuthenticAMD AMD A8-3820 APU with Radeon(tm) HD Graphics AMD586, level: 18
4 logical processors, active mask: 15
RAM: 8574885888 total




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 5/27/2015 8:26:28 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052715-10280-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0)
Bugcheck code: 0xA (0xFFFFF6FD402A1000, 0x2, 0x0, 0xFFFFF80002CAE076)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 that cannot be identified at this time.



On Wed 5/27/2015 7:15:09 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\052715-9094-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0)
Bugcheck code: 0xA (0xFFFFF6FD402CA000, 0x2, 0x0, 0xFFFFF80002CC0076)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 that cannot be identified at this time.



On Sun 4/19/2015 1:16:54 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041915-9952-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x72A40)
Bugcheck code: 0xA (0xFFFFF6FD402C6000, 0x2, 0x0, 0xFFFFF80002C7C1E6)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 that cannot be identified at this time.





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

3 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

I also uploaded the created file from dm

Thanks for any help.

 

[Arc]

BugCheck A, {fffff6fd402a1000, 2, 0, fffff80002cae076}

[COLOR=Red]Probably caused by : memory_corruption [/COLOR]( nt!MmBuildMdlForNonPagedPool+136 )

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

There are two most commons reasons behind a memory corruption. First, the physical memory is failing; and second, a driver passing any bad info to the memory. Let us test for both the alternatives, one by one.

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+
​

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If it does not show any error, enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable
​

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

 

[Josparky]

Thanks for your reply and any help you can provide.

I ran memtest86+ for 9 passes and no errors. I did have another BSOD this morning though and I will upload that DM Log Collector again from this morning after it happened. Also I will be doing the Driver Verifier as well.

Thanks

 

[Josparky]

Ok I have now run the Driver Verifier for over 24 hours now and it is still running and I have not blue screened but I know it will happen again sooner or later. What do I do next.

Thanks

 

[Arc]

Next ... disable driver verifier. Run the computer normally. If it BSODs again, let us know.

 

[Josparky]

Ok it has been a little while but got another BSOD on 6/22/15 this is very random and I just cannot figure it out. All the things above done and test good every time I have done them.

Here is the who crashed

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 6/22/2015 5:07:24 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\062215-9032-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x748C0)
Bugcheck code: 0xA (0xFFFFF6FD402A4000, 0x2, 0x0, 0xFFFFF80002CB2076)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 that cannot be identified

Also have included another DM Log Collector file.

Thanks for any help.

 

[Arc]

It is Realtek RTL8191SU Wireless LAN 802.11n USB 2.0 Network Adapter driver that caused the issue.

BugCheck A, {fffff6fd402a4000, 2, 0, fffff80002cb2076}

*** WARNING: Unable to verify timestamp for RTL8192su.sys
*** ERROR: Module load completed but symbols could not be loaded for RTL8192su.sys
[COLOR=Red]Probably caused by : RTL8192su.sys[/COLOR] ( RTL8192su+17e32 )

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

Which is old enough.

    Image name: RTL8192su.sys
[COLOR=Red]    Timestamp:        Thu Aug 11 08:06:33 2011[/COLOR] (4E434031)

There is a little update to it, in Realtek. Get it. See how it goes. Let us know.

 

[Josparky]

Hey Arc thanks for looking at my problem. Which one do I need to be downloading then the RTL8191SU or the RTL8192SU or are they both the same driver.

I just looked at the drivers and this is the same driver I have installed already??

Thanks for your help

 

[Arc]

The update time is much later ....

View attachment 363888
​

Try to install it, see what it results.

 

[Josparky]

Yes I know this is the driver I downloaded and installed for it just a few months back though. I will uninstall it and download the one you are pointing to and reinstall again just to make sure but it is saying the same version as what I highlighted.

Thanks

 

[Arc]

If it is really the same driver, and this driver continues to contribute to the BSODs, you will need to use any other USB adapter.