-------------------------------------------------------------------------------- System Information (local) -------------------------------------------------------------------------------- computer name: PC-SALLE windows version: Windows 7 Service Pack 1, 6.1, build: 7601 windows dir: C:\Windows Hardware: imedia S1710, Packard Bell, MCP73T-AD CPU: GenuineIntel Pentium(R) Dual-Core CPU E5200 @ 2.50GHz Intel586, level: 6 2 logical processors, active mask: 3 RAM: 4294168576 total -------------------------------------------------------------------------------- Crash Dump Analysis -------------------------------------------------------------------------------- Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Mon 28/07/2014 12:46:23 GMT your computer crashed crash dump file: C:\Windows\Minidump\072814-35193-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75B90) Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0) Error: KMODE_EXCEPTION_NOT_HANDLED 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 a kernel-mode program generated an exception which the error handler did not catch. 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 Mon 28/07/2014 12:46:23 GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: netr7364.sys (netr7364+0x658FF) Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0) Error: KMODE_EXCEPTION_NOT_HANDLED file path: C:\Windows\system32\drivers\netr7364.sys product: Ralink 802.11 Wireless Adapters company: Ralink Technology, Corp. description: Ralink 802.11 USB Wireless Adapter Driver Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch. 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: netr7364.sys (Ralink 802.11 USB Wireless Adapter Driver, Ralink Technology, Corp.). Google query: Ralink Technology, Corp. KMODE_EXCEPTION_NOT_HANDLED On Fri 25/07/2014 15:46:03 GMT your computer crashed crash dump file: C:\Windows\Minidump\072514-38313-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x35B3F4) Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80003FB33F4, 0xFFFFF880031E7968, 0xFFFFF880031E71C0) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M 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 a system thread generated an exception which the error handler did not catch. 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. A third party driver has 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: netr7364.sys (Ralink 802.11 USB Wireless Adapter Driver, Ralink Technology, Corp.) If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from 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.