[UrbanArcher]

Hey, my name is Justin and I've been getting Stop Errors since somewhere around June 28th. I really need my computer for school, and it's getting pretty hard to deal with only being able to be on my computer certain minutes at a time with some different Blue Screen coming up after about 10 - 30 minutes at a time on the computer. I also use my computer to communicate with friends who don't have cellphones yet, since we do compete in technological events during the school year. None of them involve troubleshooting a computer by the way. (lol) However, I still need help determining the cause of the Blue Screens because it rarely gives me the same error number. I called Best Buy, and they tried to rip my pockets open with that $200 price just to run a list of scans to determine what's wrong. And I also called the computer store that I got it from and they said it'd be a $40 dollar diagnostic fee up front and then another set of cash to fix the problem once they determine it. I'm only a sophomore living with two older brothers and a single mom, so I don't really want to have any of them coming out of their pockets to fix this problem if it's not necessary. I've looked over some other posts, so I think I know what to provide, but if it's not enough to determine the cause, please tell me what else I can provide.

I have run chkdsk, and have done multiple uninstallations since the time it started. It doesn't seem like those were the problems since I uninstalled everything I had installed around the time it first started happening.

This is what I've gotten from using Blue Screen View. I hope this helps.

==================================================
Dump File : 080812-19141-01.dmp
Crash Time : 8/8/2012 2:15:34 AM
Bug Check String : PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code : 0x00000050
Parameter 1 : fffffca0`0c657d88
Parameter 2 : 00000000`00000000
Parameter 3 : fffff800`02eeaa10
Parameter 4 : 00000000`00000007
Caused By Driver : fltmgr.sys
Caused By Address : fltmgr.sys+24e80
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\080812-19141-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 274,688
==================================================

==================================================
Dump File : 080812-19936-01.dmp
Crash Time : 8/8/2012 2:08:17 AM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : ffffffff`c000001d
Parameter 2 : fffff800`031675fc
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f1c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17835 (win7sp1_gdr.120503-2030)
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\080812-19936-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 274,688
==================================================

==================================================
Dump File : 080712-20982-01.dmp
Crash Time : 8/7/2012 2:23:25 AM
Bug Check String :
Bug Check Code : 0x0000010e
Parameter 1 : 00000000`0000001f
Parameter 2 : fffff8a0`0d005980
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00007800
Caused By Driver : watchdog.sys
Caused By Address : watchdog.sys+122f
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\080712-20982-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 274,688
==================================================

==================================================
Dump File : 071512-25568-01.dmp
Crash Time : 7/15/2012 7:52:48 PM
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff800`02ecdea7
Parameter 3 : fffff880`045ff5c8
Parameter 4 : fffff880`045fee20
Caused By Driver : dxgkrnl.sys
Caused By Address : dxgkrnl.sys+16e6
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+74ea7
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\071512-25568-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 274,744
==================================================

==================================================
Dump File : 070212-19890-01.dmp
Crash Time : 7/2/2012 10:06:06 AM
Bug Check String : BAD_POOL_HEADER
Bug Check Code : 0x00000019
Parameter 1 : 00000000`00000003
Parameter 2 : fffffa80`06105c90
Parameter 3 : fffffa80`06105c90
Parameter 4 : fbfffa80`06105c90
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+7f1c0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.1.7601.17835 (win7sp1_gdr.120503-2030)
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\070212-19890-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================

==================================================
Dump File : 070212-21652-01.dmp
Crash Time : 7/2/2012 7:10:12 AM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver :
Caused By Address :
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\070212-21652-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 262,144
==================================================

==================================================
Dump File : 070212-29421-01.dmp
Crash Time : 7/2/2012 6:14:01 AM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000001
Parameter 4 : fffff800`02ea0f2c
Caused By Driver : dxgmms1.sys
Caused By Address : dxgmms1.sys+7f76
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7f1c0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\070212-29421-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 274,744
==================================================

==================================================
Dump File : 070212-31855-01.dmp
Crash Time : 7/2/2012 4:08:30 AM
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : 00000000`00000000
Parameter 2 : 00000000`00000000
Parameter 3 : 00000000`00000000
Parameter 4 : 00000000`00000000
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+539a0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+7f190
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\070212-31855-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 7601
Dump File Size : 317,760
==================================================

[Advertisements]

System Specs
OS Name: Microsoft Windows 7 Home Premium
Version: 6.1.7601 Service Pack 1 Build 7601
No other OS Description
OS Manufacturer: Microsoft Corporation
System Name: JUSTIN-HP
System Manufacturer: Hewlett-Packard
System Model: HP Pavilion P6000 Series
System Type: x64-based PC
Processor: AMD Athlon™ II X4 640 Processor, 3000 Mhz, 4 Core(s), 4 Logical Processor(s)
BIOS Version/Date: American Megatrends Inc. 6.06, 3/22/2011
SMBIOS Version: 2.6
Windows Directory: C:\Windows
System Directory: C:\Windows\system32
Boot Device: \Device\HarddiskVolume1
Locale: United States
HArdware Abstraction Layer: Version = "6.1.7601.17514"
Time Zone: Central Daylight Time
Installed Physical Memory (RAM): 4.00 GB
Total Physical Memory: 3.75 GB
Available Physical Memory: 2.25 GB
Total Virtual Memory: 7.50 GB
Available Virtual Memory: 5.87 GB
Page File Space: 3.75
Display Adapter: ATI Radeon HD 4200

[UrbanArcher]

System Specs
OS Name: Microsoft Windows 7 Home Premium
Version: 6.1.7601 Service Pack 1 Build 7601
No other OS Description
OS Manufacturer: Microsoft Corporation
System Name: JUSTIN-HP
System Manufacturer: Hewlett-Packard
System Model: HP Pavilion P6000 Series
System Type: x64-based PC
Processor: AMD Athlon™ II X4 640 Processor, 3000 Mhz, 4 Core(s), 4 Logical Processor(s)
BIOS Version/Date: American Megatrends Inc. 6.06, 3/22/2011
SMBIOS Version: 2.6
Windows Directory: C:\Windows
System Directory: C:\Windows\system32
Boot Device: \Device\HarddiskVolume1
Locale: United States
HArdware Abstraction Layer: Version = "6.1.7601.17514"
Time Zone: Central Daylight Time
Installed Physical Memory (RAM): 4.00 GB
Total Physical Memory: 3.75 GB
Available Physical Memory: 2.25 GB
Total Virtual Memory: 7.50 GB
Available Virtual Memory: 5.87 GB
Page File Space: 3.75
Display Adapter: ATI Radeon HD 4200

[rshaffer61]

Hello UrbanArcher.... Welcome to
GeeksToGo,


I'm sorry to hear about your issue. We will try to help you resolve this as soon as possible.

• Please understand we are all volunteers and we are not here all the time.
• Sometimes it may be a extended amount of time to get back to you. If it has been
  more then 3 days please shoot me a PM and I will try to get back to you quickly
  then.
• Please do the following and supply the requested information as needed. If you
  don't understand my instructions please ask and I will try to explain them
  clearer for you.
• Do not attempt any steps unless instructed or ask before to
  make sure they will not cause any further issues.
• If you are receiving assistance in any other forum site please let us know as there may be conflicting advice given.

Before we can help you need to provide the following so I can start you in the right direction.
Laptop or Desktop?

• If a name brand system then what brand, make and model is the system?
• If custom built then what brand, make and model is the motherboard
• Total memory installed
• Total hard drive capacity and free space
• What was the original issue
• What steps have you taken so far to resolve the issue

Download WhoCrashed from the link in my signature below
This program checks for any drivers which may have been causing your computer to crash....

Click on the file you just downloaded and run it.

Put a tick in Accept then click on Next
Put a tick in the Don't create a start menu folder then click Next
Put a tick in Create a Desktop Icon then click on Install and make sure there is a tick in Launch Whocrashed before clicking Finish
Click Analyze
It will want to download the Debugger and install it Say Yes
WhoCrashed will create report but you have to scroll down to see it
Copy and paste it into your next reply

http://www.resplendence.com/downloads

[UrbanArcher]

Thank you, rshaffer61, for your quick response and warm welcome. I currently do not know what the original issue was. However, I did install WhoCrashed, as you recommended, and I am currently running my computer in safe mode. All the info you asked for should be in the second post. And this is a desktop. I also understand that you will not be available at all times of the day, which is fine because I have a book to worry about reading anyways, which I doubt I would be if my computer were in fine working order. That is sad to say, but I am distracted easily at home. More to the point, I will link my e-mail to my phone, so when you do respond, I should be notified, even if I don't have access to a computer that won't allow me more than 15 minutes at a time out of safe mode. I did notice, however, that my computer will work for hours at a time, without a hint of a Blue Screens, but I cannot determine why. WhoCrashed Identified two unknown modules as the main cause of the blue screens. It also stated that they are third party drivers. Any idea as to where these might be found? They each had a *.sys ending to the file name, so I will try looking into the system and system32 folders.

Edit: I currently have 333 GB of 684 GB left on my hard drive.

Edited by UrbanArcher, 08 August 2012 - 02:55 PM.

[rshaffer61]

Can you post the WhoCrashed log?
If no problems in Safe Mode you can try Safe Mode with networking and that would allow you access to the internet then.

[UrbanArcher]

Apparently there's also a third one.

On Wed 8/8/2012 9:04:54 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080912-15600-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF88003FA37F2)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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: Unknown .
Google query: Unknown KMODE_EXCEPTION_NOT_HANDLED




On Wed 8/8/2012 9:04:54 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFF88003FA37F2)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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: Unknown .
Google query: Unknown KMODE_EXCEPTION_NOT_HANDLED




On Wed 8/8/2012 9:53:48 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080812-32510-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x5A88)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF88008AB9C88, 0xFFFFF88008AB94E0, 0xFFFFF80002EE2BA6)
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 which cannot be identified at this time.


On Wed 8/8/2012 7:14:27 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080812-19141-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x50 (0xFFFFFCA00C657D88, 0x0, 0xFFFFF80002EEAA10, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Tue 8/7/2012 7:30:16 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080812-19936-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF800031675FC, 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 which cannot be identified at this time.


On Tue 8/7/2012 4:34:05 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080712-20982-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x122F)
Bugcheck code: 0x10E (0x1F, 0xFFFFF8A00D005980, 0x0, 0x7800)
Error: VIDEO_MEMORY_MANAGEMENT_INTERNAL
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video memory manager has encountered a condition that it is unable to recover from.
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 which cannot be identified at this time.


On Mon 7/16/2012 12:51:30 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\071512-25568-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EA7)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002ECDEA7, 0xFFFFF880045FF5C8, 0xFFFFF880045FEE20)
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 which cannot be identified at this time.


On Mon 7/2/2012 12:10:25 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070212-19890-01.dmp
This was probably caused by the following module: unknown_module_00000000`00000000.sys (Unloaded_Unknown_Module_00000000`00000000+0x19)
Bugcheck code: 0x19 (0x3, 0xFFFFFA8006105C90, 0xFFFFFA8006105C90, 0xFBFFFA8006105C90)
Error: BAD_POOL_HEADER
Bug check description: This indicates that a pool header is corrupt.
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: unknown_module_00000000`00000000.sys .
Google query: unknown_module_00000000`00000000.sys BAD_POOL_HEADER




On Mon 7/2/2012 12:09:17 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070212-21652-01.dmp
This was probably caused by the following module: unknown_module_00000000_0000003a.sys (Unknown_Module_00000000_0000003a+0x4DF)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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: unknown_module_00000000_0000003a.sys .
Google query: unknown_module_00000000_0000003a.sys KMODE_EXCEPTION_NOT_HANDLED




On Mon 7/2/2012 11:12:47 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070212-29421-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7F1C0)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80002EA0F2C)
Error: IRQL_NOT_LESS_OR_EQUAL
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 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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 6/28/2012 9:22:31 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\070212-31855-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x539A0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP 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.
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 which cannot be identified at this time.



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

11 crash dumps have been found and analyzed. 3 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:

unknown_module_00000000`00000000.sys

unknown_module_00000000_0000003a.sys

unknown

[UrbanArcher]

Hey, rshaffer61, I figured out why my computer stays on for long periods of times without a blue screen. I have game booster, which I use for disabling a lot which I don't use for either playing games or speeding up my computer for general usage. But whatever the case, Game Booster is stopping whatever corrupted third party applications that are causing my computer to crash to not enable. I figure I can give a list of those to see if we can further narrow it down to something unheard of or known to cause problems by the both of us.

Here's a list of Non-Windows Services Game Booster stopped.

• HP Support Assistant Service
• RoxioNow Service
• UMVPFSrv
• Windows Live ID Sign-in Assistant

I'll have a list of Unnecessary Services Game Booster stopped, when I get back from school.

[rshaffer61]

OK first a explanation of each error code you are gettting.

0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
The Windows kernel detected an illegal or unknown processor instruction. A Stop 0x1E condition can be caused by invalid memory and access violations similar to those that generate Stop 0xA errors. This default Windows error handler typically intercepts these problems if error-handling routines are not present in the code itself.



0x00000024: NTFS_FILE_SYSTEM
A problem occurred within NTFS.SYS, the driver file that allows the system to read and write to NTFS file system drives. There may be a physical problem with the disk, or an Interrupt Request Packet (IRP) may be corrupted. Other common causes include heavy hard drive fragmentation, heavy file I/O, problems with some types of drive-mirroring software, or some antivirus software. I suggest running ChkDsk or ScanDisk as a first step; then disable all file system filters such as virus scanners, firewall software, or backup utilities. Check the file properties of NTFS.SYS to ensure it matches the current OS or SP version. Update all disk, tape backup, CD-ROM, or removable device drivers to the most current versions.



0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Requested data was not in memory. An invalid system memory address was referenced. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause this Stop message, as may other hardware problems (e.g., incorrect SCSI termination or a flawed PCI card).


0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
A system thread generated an exception which the error handler did not catch. There are numerous individual causes for this problem, including hardware incompatibility, a faulty device driver or system service, or some software issues. Check Event Viewer (EventVwr.msc) for additional information.


0x00000019: BAD_POOL_HEADER
A pool header issue is a problem with Windows memory allocation. Device driver issues are probably the msot common, but this can have diverse causes including bad sectors or other disk write issues, and problems with some routers. (By theory, RAM problems would be suspect for memory pool issues, but I haven’t been able to confirm this as a cause.)

I did not list them all because we were back to the beginning of July already. There are several ways to go at this but I'm going to try and take the most direct route to a resolution.



Tutorial for running chkdsk in Vista\Win 7 located HERE.




Run hard drive diagnostics: http://www.tacktech....ay.cfm?ttid=287
Make sure, you select tool, which is appropriate for the brand of your hard drive.
Depending on the program, it'll create bootable floppy, or bootable CD.
If downloaded file is of .iso type, use ImgBurn: http://www.imgburn.com/ to burn .iso file to a CD (select "Write image file to disc" option), and make the CD bootable.

NOTE. If your hard drive is made by Toshiba, try the Hitachi DFT CD Image version of the software

Thanks to Broni for the instructions








A If you have more than one RAM module installed, try starting computer with one RAM stick at a time.

NOTE Keep in mind, the manual check listed above is always superior to the software check, listed below. DO NOT proceed with memtest, if you can go with option A

B. If you have only one RAM stick installed...
...run memtest...


1. Download - Pre-Compiled Bootable ISO (.zip). If you prefer to use the USB version then use this link USB KEY
2. Unzip downloaded /memtest86+-4.20.iso.zip file.
3. Inside, you'll find /memtest86+-4.20.iso file.
4. Download, and install ImgBurn: http://www.imgburn.com/
5. Insert blank CD into your CD drive.
6. Open ImgBurn, and click on Write image file to disc
7. Click on Browse for a file... icon:



8. Locate memtest86+-4.20.iso file, and click Open button.
9. Click on ImgBurn green arrow to start burning bootable memtest86 CD:



10. Once the CD is created, boot from it, and memtest will automatically start to run. You may have to change the boot sequence in your BIOS to make it work right.

To change Boot Sequence in your BIOS

Reboot the system and at the first post screen (where it is counting up memory) start tapping the DEL button
This will enter you into the Bios\Cmos area.
Find the Advanced area and click Enter
Look for Boot Sequence or Boot Options and highlight that click Enter
Now highlight the first drive and follow the directions on the bottom of the screen on how to modify it and change it to CDrom.
Change the second drive to the C or Main Drive
Once that is done then click F10 to Save and Exit
You will prompted to enter Y to verify Save and Exit. Click Y and the system will now reboot with the new settings.


The running program will look something like this depending on the size and number of ram modules installed:




It's recommended to run 5-6 passes. Each pass contains very same 8 tests.

This will show the progress of the test. It can take a while. Be patient, or leave it running overnight.



The following image is the test results area:



The most important item here is the “errors” line. If you see ANY errors, even one, most likely, you have bad RAM.

[UrbanArcher]

So far, I've run chkdsk. No errors to report.

[UrbanArcher]

It's a program on my computer. Something is outdated, and I have to figure out what. I have a temp fix for the time being though. It is definitely one of the programs game booster is deactivating. Until I can figure out which one. I'm using game booster and using Hibernation Mode instead of shutting down regularly.

[rshaffer61]

OK so chkdsk found no disk integrity issues so that is good.