Colif :
this will help both of us
download this and do a scan:
http://www.resplendence.com/whocrashed
It will look at those error logs you have and print them out in a form most of us can understand - it might even make it obvious to you'
If not, paste them in here
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Wed 4/6/2016 8:43:30 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\040616-26000-01.dmp
This was probably caused by the following module: bedaisy.sys (BEDaisy+0x9A2C)
Bugcheck code: 0x50 (0xFFFFF961C2F9003C, 0x0, 0xFFFFF80105E49A2C, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: bedaisy.sys .
Google query: bedaisy.sys PAGE_FAULT_IN_NONPAGED_AREA
On Wed 4/6/2016 8:43:30 AM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: bedaisy.sys (BEDaisy+0x9A2C)
Bugcheck code: 0x50 (0xFFFFF961C2F9003C, 0x0, 0xFFFFF80105E49A2C, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: bedaisy.sys .
Google query: bedaisy.sys PAGE_FAULT_IN_NONPAGED_AREA
On Tue 4/5/2016 5:25:42 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\040616-21859-01.dmp
This was probably caused by the following module: scmndisp.sys (scmndisp+0x16D1)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF801EA48FBAA)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\scmndisp.sys
product: SerComm® Neutral Wireless Solution
company: Windows (R) Win 7 DDK provider
description: SerComm NDIS User mode I/O Driver
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: scmndisp.sys (SerComm NDIS User mode I/O Driver, Windows (R) Win 7 DDK provider).
Google query: Windows (R) Win 7 DDK provider IRQL_NOT_LESS_OR_EQUAL
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
3 crash dumps have been found and analyzed. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
scmndisp.sys (SerComm NDIS User mode I/O Driver, Windows (R) Win 7 DDK provider)
bedaisy.sys
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.
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.
Facebook
Twitter
Instagram