beta212 - The RAM has been memtested individually recently so not the problem.
I'm running 7 on another machine and don't have the need nor want to run it on this one - xp does exactly what I need it to here.
This is a "decent" PC and I have no interest in a full reinstall- kind of besides the point and not very helpful.
scout_03, thanks - here is what who crashed came up with (kind of confusing to be honest - any ideas, thanks?):
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Fri 10/05/2013 00:52:49 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini051013-02.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x335C)
Bugcheck code: 0x1000000A (0x1, 0x2, 0x0, 0xFFFFFFFF8051B910)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Fri 10/05/2013 00:05:08 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini051013-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x335C)
Bugcheck code: 0x1A (0x781, 0xFFFFFFFFC0688BA8, 0x0, 0xFFFFFFFFE3B2DFA8)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that a severe memory management error occurred.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Thu 09/05/2013 22:51:51 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini050913-09.dmp
This was probably caused by the following module: sandbox.sys (SandBox+0x2C9B)
Bugcheck code: 0x1A (0x781, 0xFFFFFFFFC068CBA8, 0x0, 0xFFFFFFFFE39A99A8)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\drivers\sandbox.sys
product: Agnitum Ltd. Host Protection Component
company: Agnitum Ltd.
description: Host Protection Component
Bug check description: This indicates that a severe memory management error occurred.
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.
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: sandbox.sys (Host Protection Component, Agnitum Ltd.).
Google query: Agnitum Ltd. MEMORY_MANAGEMENT
On Thu 09/05/2013 22:47:58 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini050913-08.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x335C)
Bugcheck code: 0x1000000A (0x0, 0x2, 0x0, 0xFFFFFFFF8051B910)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Thu 09/05/2013 22:34:47 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini050913-07.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x29E35)
Bugcheck code: 0x1A (0x781, 0xFFFFFFFFC06B4B28, 0xFFFFFFFF83167670, 0xFFFFFFFF83167680)
Error: MEMORY_MANAGEMENT
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that a severe memory management error occurred.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Thu 09/05/2013 21:04:03 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini050913-06.dmp
This was probably caused by the following module: sandbox.sys (SandBox+0x6DBC)
Bugcheck code: 0x1000000A (0x1CE330E, 0x2, 0x0, 0xFFFFFFFF8051BBED)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\sandbox.sys
product: Agnitum Ltd. Host Protection Component
company: Agnitum Ltd.
description: Host Protection Component
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: sandbox.sys (Host Protection Component, Agnitum Ltd.).
Google query: Agnitum Ltd. CUSTOM_ERROR
On Thu 09/05/2013 19:13:41 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini050913-05.dmp
This was probably caused by the following module: gmouusb.sys (gMouUsb+0xEB0)
Bugcheck code: 0x1000000A (0x4, 0x1C, 0x0, 0xFFFFFFFF804FA2A3)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\gmouusb.sys
product: Low Filter Driver
description: WDM NULL filter driver
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: gmouusb.sys (WDM NULL filter driver, ).
Google query: gmouusb.sys CUSTOM_ERROR
On Thu 09/05/2013 16:22:52 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini050913-04.dmp
This was probably caused by the following module: gmouusb.sys (gMouUsb+0xEB0)
Bugcheck code: 0x1000000A (0x4, 0x1C, 0x0, 0xFFFFFFFF804FA2A3)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\gmouusb.sys
product: Low Filter Driver
description: WDM NULL filter driver
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: gmouusb.sys (WDM NULL filter driver, ).
Google query: gmouusb.sys CUSTOM_ERROR
On Thu 09/05/2013 01:07:42 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini050913-03.dmp
This was probably caused by the following module: sandbox.sys (SandBox+0x2750)
Bugcheck code: 0x4E (0x2, 0x7D891, 0xDFD77, 0x1)
Error: PFN_LIST_CORRUPT
file path: C:\WINDOWS\system32\drivers\sandbox.sys
product: Agnitum Ltd. Host Protection Component
company: Agnitum Ltd.
description: Host Protection Component
Bug check description: This indicates that the page frame number (PFN) list is corrupted.
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.
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: sandbox.sys (Host Protection Component, Agnitum Ltd.).
Google query: Agnitum Ltd. PFN_LIST_CORRUPT
On Thu 09/05/2013 00:49:09 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini050913-02.dmp
This was probably caused by the following module: gmouusb.sys (gMouUsb+0xEB0)
Bugcheck code: 0x1000000A (0x4, 0x1C, 0x0, 0xFFFFFFFF804DF0BC)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\gmouusb.sys
product: Low Filter Driver
description: WDM NULL filter driver
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: gmouusb.sys (WDM NULL filter driver, ).
Google query: gmouusb.sys CUSTOM_ERROR
On Thu 09/05/2013 00:12:34 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini050913-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x10A595)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF805DE595, 0xFFFFFFFFF78CAC60, 0xFFFFFFFFF78CA95C)
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
--------------------------------------------------------------------------------
11 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:
gmouusb.sys (WDM NULL filter driver, )
sandbox.sys (Host Protection Component, Agnitum Ltd.)
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.
beta212 :
Northwinds :
Hi all
PC was working great then suddenly starts throwing bsods with increasing regularity until it is hardly usable now - even after multiple system restores.
I have a bunch of minidumps- though not sure how to attach them here?
Thanks.
I'm guessing it's the ram, do a ram check http://hcidesign.com/memtest/ . If that doesn't work just do a complete reinstall, if that doesn't work, shell out 300 bucks and buy a decent pc using windows 7/8.
Facebook
Twitter
Instagram