New
#1
BSOD Not sure what the cause is
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.