computer name: JORDAN-PC windows version: Windows 7 Service Pack 1, 6.1, build: 7601 windows dir: C:\Windows CPU: AuthenticAMD AMD Athlon(tm) X3 450 Processor AMD586, level: 16 3 logical processors, active mask: 7 RAM: 4294103040 total VM: 2147352576, free: 1929072640 -------------------------------------------------------------------------------- Crash Dump Analysis -------------------------------------------------------------------------------- Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Thu 05/09/2013 14:50:47 GMT your computer crashed crash dump file: C:\Windows\Minidump\090513-18205-01.dmp This was probably caused by the following module: nvsmu.sys (0xFFFFF880041DD48D) Bugcheck code: 0x50 (0xFFFFF88002EC6000, 0x0, 0xFFFFF880041DD48D, 0x0) Error: PAGE_FAULT_IN_NONPAGED_AREA file path: C:\Windows\system32\drivers\nvsmu.sys product: NVIDIA nForce(TM) PCA Driver company: NVIDIA Corporation description: NVIDIA nForce(TM) SMU Microcontroller Driver 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: nvsmu.sys (NVIDIA nForce(TM) SMU Microcontroller Driver, NVIDIA Corporation). Google query: NVIDIA Corporation PAGE_FAULT_IN_NONPAGED_AREA On Thu 29/08/2013 15:34:12 GMT your computer crashed crash dump file: C:\Windows\Minidump\083013-13026-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80) Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002E0EE80, 0x1, 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 Thu 22/08/2013 14:19:50 GMT your computer crashed crash dump file: C:\Windows\Minidump\082513-12511-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80) Bugcheck code: 0xF7 (0xFFFFF88076E30B80, 0x1D4071F496E8, 0xFFFFE2BF8E0B6917, 0x0) Error: DRIVER_OVERRAN_STACK_BUFFER 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 driver has overrun a stack-based buffer. 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 21/08/2013 16:05:29 GMT your computer crashed crash dump file: C:\Windows\Minidump\082213-13228-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80) Bugcheck code: 0xE3 (0xFFFFFA8005D9A838, 0xFFFFFA80039F8B50, 0xFFFFFA8005C41410, 0x3) Error: RESOURCE_NOT_OWNED 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 thread tried to release a resource it did not own. 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 21/08/2013 16:03:44 GMT your computer crashed crash dump file: C:\Windows\Minidump\082113-12854-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80) Bugcheck code: 0xFC (0xFFFFF880009EB180, 0x80000000A7EF2963, 0xFFFFF88002F1BBF0, 0x2) Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY 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 an attempt was made to execute non-executable memory. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. There is a possibility this problem was caused by a virus or other malware. 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 21/08/2013 15:17:30 GMT your computer crashed crash dump file: C:\Windows\Minidump\082113-13462-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75B80) Bugcheck code: 0xF4 (0x3, 0xFFFFFA80059E0B30, 0xFFFFFA80059E0E10, 0xFFFFF80002FD90D0) Error: CRITICAL_OBJECT_TERMINATION 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 process or thread crucial to system operation has unexpectedly exited or been terminated. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Tue 20/08/2013 17:46:44 GMT your computer crashed crash dump file: C:\Windows\Minidump\082013-14991-01.dmp This was probably caused by the following module: nvsmu.sys (0xFFFFF88007B4648D) Bugcheck code: 0x50 (0xFFFFF88008F40000, 0x0, 0xFFFFF88007B4648D, 0x0) Error: PAGE_FAULT_IN_NONPAGED_AREA file path: C:\Windows\system32\drivers\nvsmu.sys product: NVIDIA nForce(TM) PCA Driver company: NVIDIA Corporation description: NVIDIA nForce(TM) SMU Microcontroller Driver 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: nvsmu.sys (NVIDIA nForce(TM) SMU Microcontroller Driver, NVIDIA Corporation). Google query: NVIDIA Corporation PAGE_FAULT_IN_NONPAGED_AREA On Tue 20/08/2013 17:43:03 GMT your computer crashed crash dump file: C:\Windows\Minidump\082013-16426-01.dmp This was probably caused by the following module: nvsmu.sys (0xFFFFF8800731948D) Bugcheck code: 0x50 (0xFFFFF88006E80000, 0x0, 0xFFFFF8800731948D, 0x0) Error: PAGE_FAULT_IN_NONPAGED_AREA file path: C:\Windows\system32\drivers\nvsmu.sys product: NVIDIA nForce(TM) PCA Driver company: NVIDIA Corporation description: NVIDIA nForce(TM) SMU Microcontroller Driver 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: nvsmu.sys (NVIDIA nForce(TM) SMU Microcontroller Driver, NVIDIA Corporation). Google query: NVIDIA Corporation PAGE_FAULT_IN_NONPAGED_AREA On Mon 12/08/2013 18:02:51 GMT your computer crashed crash dump file: C:\Windows\Minidump\081313-18205-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00) Bugcheck code: 0x18 (0x0, 0xFFFFFA80048AD460, 0x2, 0xFFFFFA80048AD42F) Error: REFERENCE_BY_POINTER 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 the reference count of an object is illegal for the current state of the object. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. -------------------------------------------------------------------------------- Conclusion -------------------------------------------------------------------------------- 9 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: nvsmu.sys (NVIDIA nForce(TM) SMU Microcontroller Driver, NVIDIA Corporation) 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 actually 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.