BSOD after new installation of OS


  1. hurricaneCH
    Posts : 2
    Win 7 Professional 32bit
       New #1

    BSOD after new installation of OS


    Hello everybody

    I got the old Computer from my brother (HP-Desktop :/). First, i reinstalled Vista (yes it had Vista ).
    BSOD has already appeared...
    I installed win7
    BSOD still there...

    RAM: checked and shouldn't be the Problem
    graphic Card: changed, still same Problem
    HDD: tried on another one... still the same Problem
    updated some Drivers

    the BSOD appeared AFTER new Installation... what can i do now
    BSOD happens often when i download something... if i dont touch the Computer... nothing happens...

    WhoCrashed-Information:

    Code:
     
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: NF456AA-UUZ a6720ch, HP-Pavilion, MSI, Boston
CPU: GenuineIntel Intel(R) Pentium(R) Dual CPU E2220 @ 2.40GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 3487752192 total
VM: 2147352576, free: 1951567872
 
On Mon 02.06.2014 11:09:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060214-26707-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x40B7F) 
Bugcheck code: 0xC5 (0xFFFFFFFFCBFF7A02, 0x2, 0x1, 0xFFFFFFFF829354C1)
Error: DRIVER_CORRUPTED_EXPOOL
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 the system attempted to access invalid memory at a process IRQL that was too high.
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. 
 
 
 
On Mon 02.06.2014 11:09:35 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!Kei386EoiHelper+0x28B7) 
Bugcheck code: 0xC5 (0xFFFFFFFFCBFF7A02, 0x2, 0x1, 0xFFFFFFFF829354C1)
Error: DRIVER_CORRUPTED_EXPOOL
Bug check description: This indicates that the system attempted to access invalid memory at a process IRQL that was too high.
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: ntkrpamp.exe . 
Google query: ntkrpamp.exe DRIVER_CORRUPTED_EXPOOL
 
 

On Mon 02.06.2014 10:44:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060214-25272-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x190AF7) 
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF829CCAF7, 0xFFFFFFFF9E82C7AC, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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 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 Mon 02.06.2014 10:39:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060214-27986-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x1AB29) 
Bugcheck code: 0x24 (0x1904FB, 0xFFFFFFFF8D70372C, 0xFFFFFFFF8D703310, 0xFFFFFFFF828DCC8E)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: NT-Dateisystemtreiber
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 Mon 02.06.2014 10:33:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060214-27378-01.dmp
This was probably caused by the following module: fltmgr.sys (fltmgr+0x1EBB5) 
Bugcheck code: 0x50 (0xFFFFFFFFF274F93D, 0x1, 0xFFFFFFFF82FB69C0, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: Microsoft Dateisystem-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 Mon 02.06.2014 10:01:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060214-26956-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x79DB9) 
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8287DDB9, 0xFFFFFFFFA1DAF8A4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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 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 Mon 02.06.2014 09:55:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060214-25287-01.dmp
This was probably caused by the following module: hal.sys (hal+0x3839) 
Bugcheck code: 0xA (0xFFFFFFFFDD0897ED, 0x2, 0x1, 0xFFFFFFFF82811839)
Error: IRQL_NOT_LESS_OR_EQUAL
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. 
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: hal.sys . 
Google query: hal.sys IRQL_NOT_LESS_OR_EQUAL
 
 

On Sun 01.06.2014 22:44:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060214-27456-01.dmp
This was probably caused by the following module: hal.sys (hal+0x3839) 
Bugcheck code: 0xA (0x2BDA7CB1, 0x2, 0x1, 0xFFFFFFFF82807839)
Error: IRQL_NOT_LESS_OR_EQUAL
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. 
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: hal.sys . 
Google query: hal.sys IRQL_NOT_LESS_OR_EQUAL
 
 

On Sun 01.06.2014 22:36:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060214-27237-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x40B7F) 
Bugcheck code: 0xD1 (0xBDED6A8, 0x2, 0x8, 0xBDED6A8)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 Sun 01.06.2014 22:16:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060214-29078-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x193AC5) 
Bugcheck code: 0x50 (0xFFFFFFFFDA38FFD6, 0x0, 0xFFFFFFFF91BBDAAA, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 337.88 
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 337.88 
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 337.88 , NVIDIA Corporation). 
Google query: NVIDIA Corporation PAGE_FAULT_IN_NONPAGED_AREA
      My Computer
    Quote Quote

  3. hurricaneCH
    Posts : 2
    Win 7 Professional 32bit
    Thread Starter
       New #2

    sorry, here is the file
      My Computer
    Quote Quote

 

  Related Discussions
I am trying to install Windows 7 on my laptop. When I click on "upgrade" it takes me to a compatibility report that says "the computer started using the windows installation disc. Remove the installation disc and restart your computer so that windows starts normally." When I remove the disc and try...
BSOD on new Win 7 installation.
in BSOD Help and Support

Hello there forum, upon returning to my pc I found a dialog box stating "windows had just recovered from an unexpected shutdown". As to what I was doing before this happened I can't answer because I left my pc to take a nap and upon resuming from sleep mode I was greeted with this message. May I...
BSOD after OS re-installation
in BSOD Help and Support

Hello! I have recently encountered multiple BSODs over the last few days. I initially thought that it was OS related, and my first course of action was to re-install Windows 7 Professional 32-Bit. Unfortunately, I am still suffering the same BSOD issues I had prior OS re-installation. I had just...
BSOD in XP Installation
in BSOD Help and Support

Hi, would appreciate if someone fixes this asap... I want to dual boot my system (Sony VAIO VGN-NS25G) with Windows XP. I can't use Virtual Machines because my CPU doesn't support Hardware Virtualization. So my only choice was to dual boot Windows XP. I created a 25GB partition (off Disk...
BSOD during Installation
in BSOD Help and Support

I've tried installing Windows 7 build 6801 and I keep getting a BSOD during the installation. I have a 186GB HD and I've partitioned it the following way: 93.1GB - Vista 58.1GB - XP 20GB - for 7 15GB - Debian and they're all primary partitions. My XP partition used to be 78.1GB, but I resized...
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

 © Designer Media Ltd
All times are GMT -5. The time now is 20:49.
Find Us