Continuous blue screen of death after Windows 7 clean install

[TigerTValum]

Hi everyone and that's for taking the time out to read my issue. I recently did a clean install of Windows 7 from Windows Vista. It took me a good 24 hours to install because my computer did a loop of restarts on the last step of the install. Once Windows 7 installed, I have been getting constant bsod. The computer worked perfectly fine with Vista, and this problem didn't start unitl I installed Win7.

Here is the problem detail:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: 50
BCP1: C4F27AB0
BCP2: 00000001
BCP3: 828A3977
BCP4: 00000002
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\013014-25474-01.dmp
C:\Users\Brandi\AppData\Local\Temp\WER-43539-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt


I have download WhoCrashed and here are the results:

System Information (local)
--------------------------------------------------------------------------------

computer name: BRANDI-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: Compaq Presario CQ50 Notebook PC, Hewlett-Packard, Wistron, 360A
CPU: AuthenticAMD AMD Athlon Dual-Core QL-60 AMD586, level: 17
2 logical processors, active mask: 3
RAM: 2951139328 total
VM: 2147352576, free: 1950834688




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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 1/30/2014 6:30:52 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\013014-25474-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x8D879)
Bugcheck code: 0x50 (0xFFFFFFFFC4F27AB0, 0x1, 0xFFFFFFFF828A3977, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntkrnlpa.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 that cannot be identified at this time.



On Thu 1/30/2014 6:30:52 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!IoGetRelatedDeviceObject+0x80B)
Bugcheck code: 0x50 (0xFFFFFFFFC4F27AB0, 0x1, 0xFFFFFFFF828A3977, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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: ntkrpamp.exe .
Google query: ntkrpamp.exe PAGE_FAULT_IN_NONPAGED_AREA



On Wed 1/29/2014 4:39:15 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012814-53274-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x31988)
Bugcheck code: 0xFC (0xFFFFFFFF8B934BB8, 0xFFFFFFFFA8D4B963, 0xFFFFFFFF8B934A4C, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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 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 1/29/2014 3:07:30 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012814-53196-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x63BA)
Bugcheck code: 0x50 (0xFFFFFFFFCA39DE88, 0x8, 0xFFFFFFFFCA39DE88, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
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 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 1/28/2014 9:27:22 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012814-19921-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x1A9A9)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFFFFF9D62F5B0, 0xFFFFFFFF9D62F190, 0xFFFFFFFF828C9DF7)
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 1/28/2014 8:53:19 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012814-27003-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xD0931)
Bugcheck code: 0x50 (0xFFFFFFFFD5E101F4, 0x0, 0xFFFFFFFF95CF0931, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 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.
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 1/28/2014 6:47:12 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012814-20607-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x41D0B)
Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 Tue 1/28/2014 12:44:14 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012814-35115-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x1836)
Bugcheck code: 0x1000008E (0xFFFFFFFFC000001D, 0xFFFFFFFF8A34E836, 0xFFFFFFFF965A7B58, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
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 that cannot be identified at this time.



On Tue 1/28/2014 10:56:11 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012814-25287-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x1A9A9)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFFFFF8C499654, 0xFFFFFFFF8C499230, 0xFFFFFFFF8A497AAB)
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 1/28/2014 9:58:31 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\012814-40123-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x8E41B)
Bugcheck code: 0x50 (0xFFFFFFFF8D2DF61C, 0x8, 0xFFFFFFFF8D2DF61C, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntkrnlpa.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 that cannot be identified at this time.




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

15 crash dumps have been found and analyzed. Only 10 are included in this report. 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:

ntkrpamp.exe

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.


Thank you again for your time!

 

[johnbl]

- Before you install a OS a old mechanical hard drive you will want to do a full format of the drive. Do this to reduce errors cause by read/write problems in the drive that develop as the drive wears. It takes a while to complete but will give you the best chance of success with the drive.

- very old laptop that has a wistron 360a mother board and built in VGA. You will want to try to find a graphics driver for that board before you even attempt to run windows 7. (maybe hp has one or you can search the internet)

if you get window 7 to boot: Install the custom vga driver and any other required custom drivers and reboot and start to check your system out.
-second thing is to disable any sleep functions by going into windows power management and set the system to be high performance, then reboot
- now you need to verify your copy of windows is not corrupt. do that by running a command prompt as a admin and use the
system file checker utility command:
sfc.exe /scannow <---- this will locate any corrupt system files and replace them from a hidden backup copy.
reboot
next you will want to update your OS to the current version including service packs and all updates.
reboot (several times until you are done)

I think getting a working VGA driver is going to be the hardest part.
you can turn off lazy writes in the hard drive to prevent hard disk corruption when your system bugchecks but better to focus on getting a stable system.

You may also consider running a memory tests like memtest86 and basic hardware tests on the system. A system like that is beyond its expected lifetime and will have various failures you will want to check for.

most people would not attempt to keep this system alive because of the custom hardware and low value.