[rshaffer61]

Please if possible do not use the registry part of that program.

[Advertisements]

I didn't get around to doing the drivers, at least yet anyway. I don't know where to start, maybe just the video driver and/or sound, but I think they are good.
Here are the latest crashes:

Spoiler

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 11/20/2013 4:13:39 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111913-26379-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4688)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800394BDF8, 0xFFFFF8800394B650, 0xFFFFF880012FE4FC)
Error: NTFS_FILE_SYSTEM
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 a problem occurred in the NTFS file system.
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 Wed 11/20/2013 4:13:39 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4688)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800394BDF8, 0xFFFFF8800394B650, 0xFFFFF880012FE4FC)
Error: NTFS_FILE_SYSTEM
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 a problem occurred in the NTFS file system.
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 Tue 11/19/2013 4:13:37 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111913-33087-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR

The times are wrong for some reason. It must have to do with the CMOS resetting randomly.

[Draye]

I didn't get around to doing the drivers, at least yet anyway. I don't know where to start, maybe just the video driver and/or sound, but I think they are good.
Here are the latest crashes:

Spoiler

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 11/20/2013 4:13:39 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111913-26379-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4688)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800394BDF8, 0xFFFFF8800394B650, 0xFFFFF880012FE4FC)
Error: NTFS_FILE_SYSTEM
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 a problem occurred in the NTFS file system.
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 Wed 11/20/2013 4:13:39 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4688)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800394BDF8, 0xFFFFF8800394B650, 0xFFFFF880012FE4FC)
Error: NTFS_FILE_SYSTEM
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 a problem occurred in the NTFS file system.
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 Tue 11/19/2013 4:13:37 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111913-33087-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR

The times are wrong for some reason. It must have to do with the CMOS resetting randomly.

[rshaffer61]

The CMOS resetting the time and date is a indication of a possible failing CMOS battery and may need to be replaced.

[Draye]

Would that cause any of the other symptoms?
I have an 3v cmos battery from an old system that I had saved. It was in a ziplock sandwich bag with a bunch of computer case screws. Will that affect it in any way?
The battery doesn't have a voltage marking, and I couldn't find it online. Maybe you know?

[rshaffer61]

Is it the same battery that is in the desktop now?

[Draye]

No, the original is still in the motherboard.
The other is from an old 1999 or something compaq computer. I could also take one from two other old ones.

[rshaffer61]

No what I mean is if the batteries are the same type of battery. In other words a cmos battery looks like this:

[attachment=67758:Battery.jpeg]

[Draye]

the one in my computer is that exact one (not sure about model number). yes they are all coin

Edited by Draye, 20 November 2013 - 03:47 PM.

[rshaffer61]

OK they should work. If not they should be like $5 at any store like Radio Shack or even a watch store may have them.

[Draye]

Swapped the batteries, and I still froze. I am about to wipe everything and start over, but I'm not sure if that would even fix the system because of the booting issues. However, the crash logs suggest that it is a third party driver, though I do not know which.
I will try to play around on a portable os.

Edited by Draye, 20 November 2013 - 04:58 PM.

[rshaffer61]

Have you updated the video driver?
Can you supply a new whocrashed and\or BlueScreenView please.

[Draye]

Mini Windows XP off of Hirens Boot CD worked fine. I used Prime95 for about 20min and it stayed stable and cool.
It must be a third party driver. I'll try to reinstall video and or sound later

Spoiler

==================================================
Dump File : 111913-26379-01.dmp
Crash Time : 11/19/2013 11:13:39 PM
Bug Check String : NTFS_FILE_SYSTEM
Bug Check Code : 0x00000024
Parameter 1 : 00000000`001904fb
Parameter 2 : fffff880`0394bdf8
Parameter 3 : fffff880`0394b650
Parameter 4 : fffff880`012fe4fc
Caused By Driver : Ntfs.sys
Caused By Address : Ntfs.sys+a64fc
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+75bc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\111913-26379-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
Dump File Time : 11/19/2013 11:17:45 PM
==================================================

==================================================
Dump File : 112013-26785-01.dmp
Crash Time : 11/20/2013 2:24:25 PM
Bug Check String : UNEXPECTED_KERNEL_MODE_TRAP
Bug Check Code : 0x0000007f
Parameter 1 : 00000000`00000008
Parameter 2 : 00000000`80050031
Parameter 3 : 00000000`000006f8
Parameter 4 : fffff800`03497ef6
Caused By Driver : Unknown_Module_fffffa80`0495d820
Caused By Address : Unknown_Module_fffffa80`0495d820+10cbd38
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address :
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\112013-26785-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
Dump File Time : 11/20/2013 2:54:12 PM
==================================================

Spoiler

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 11/20/2013 7:24:25 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\112013-26785-01.dmp
This was probably caused by the following module: unknown_module_00000000`00000012.sys (Unloaded_Unknown_Module_00000000`00000012+0x2FD828)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80003497EF6)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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: unknown_module_00000000`00000012.sys .
Google query: unknown_module_00000000`00000012.sys UNEXPECTED_KERNEL_MODE_TRAP



On Wed 11/20/2013 7:24:25 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeRemoveQueueEx+0x1849)
Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF80003497EF6)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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 11/20/2013 4:13:39 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111913-26379-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4688)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800394BDF8, 0xFFFFF8800394B650, 0xFFFFF880012FE4FC)
Error: NTFS_FILE_SYSTEM
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 a problem occurred in the NTFS file system.
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 Tue 11/19/2013 4:13:37 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111913-33087-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

4 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:

unknown_module_00000000`00000012.sys

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.

Edited by Draye, 20 November 2013 - 05:45 PM.

[rshaffer61]

Again the errors are just to vague as the root of the issue. Some point to hardware or software or even memory as being the issue.


I may have asked before but I apologize is the OS preinstalled or was it installed using a genuine Microsoft disk or a burned copy or some body else had a disk?

[Draye]

It's a burned copy.

[rshaffer61]

OK can I ask where it came from?
Has this problem happened since installing it from the burned copy?