Bsod w7 please help!!!

Alex P · 20 Sep 2010

You'll find in this post the problems I encounter.
Please help me because I can't use my computer.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1048

Additional information about the problem:
BCCode: 1a
BCP1: 0000000000005002
BCP2: FFFFF781C0000000
BCP3: 000000000000897B
BCP4: 0004897CFFFFFFFE
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\092010-23010-01.dmp
C:\Users\Alex\AppData\Local\Temp\WER-49140-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

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

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1048

Additional information about the problem:
BCCode: 24
BCP1: 00000000001904FB
BCP2: FFFFF880031858D8
BCP3: FFFFF88003185140
BCP4: FFFFF880014FB72F
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\092010-19671-01.dmp
C:\Users\Alex\AppData\Local\Temp\WER-39140-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

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

On Mon 20.09.2010 08:38:28 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x5002, 0xFFFFF781C0000000, 0x8EE3, 0x48EE1FFFFFFFE)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\092010-20872-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Mon 20.09.2010 08:16:42 your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880031858D8, 0xFFFFF88003185140, 0xFFFFF880014FB72F)
Error: NTFS_FILE_SYSTEM
Dump file: C:\Windows\Minidump\092010-19671-01.dmp
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 the culprit is in another driver on your system which cannot be identified at this time.

On Mon 20.09.2010 07:49:17 your computer crashed
This was likely caused by the following module: ataport.sys
Bugcheck code: 0x1A (0x5002, 0xFFFFF781C0000000, 0x897B, 0x4897CFFFFFFFE)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\092010-23010-01.dmp
file path: C:\Windows\system32\drivers\ataport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: ATAPI Driver Extension
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Sun 19.09.2010 10:20:46 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1A (0x41790, 0xFFFFFA8000FA1BB0, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Dump file: C:\Windows\Minidump\091910-22230-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

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

4 crash dumps have been found and analyzed. Note that it's not always possible to state with certainty whether a reported driver is really 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.

Alex P · 20 Sep 2010

I have installed Windows 3 times. The problems appears only after the first shutdown.
I have tested the drive and Ram, and everything is ok.

Tews · 20 Sep 2010

Please follow these instructions for getting help with a BSOD...

Blue Screen of Death (BSOD) Posting Instructions

Alex P · 20 Sep 2010

w7 64 bit, I purchased the computer 1 a few days ago, so everything is new

Alex P · 20 Sep 2010

NT6_BSOD + Perform Archive

Tews · 20 Sep 2010

The dmp(s) point to ntkrpamp.exe or ntoskrnl.exe as the probable cause. We know this is not the case, as these are core OS files, and will definitely not cause a BSOD. They are just the default files the debuggers blame when they can't see a better cause. Enable driver verifier using the following procedures ...

- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Try removing any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {5002, fffff781c0000000, 897b, 4897cfffffffe}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+29f42 )

Followup: MachineOwner
---------

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {5002, fffff781c0000000, 8ee3, 48ee1fffffffe}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+29f42 )

Followup: MachineOwner
---------


*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff880031858d8, fffff88003185140, fffff880014fb72f}

Probably caused by : Ntfs.sys ( Ntfs!NtfsCommonClose+26f )

Followup: MachineOwner
---------

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa8000fa1bb0, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33906 )

Followup: MachineOwner
---------

This driver should be updated if possible..

Code:

amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)

Alex P · 20 Sep 2010

Do what repeatedly ? I'm waiting to restart after doing the verifier thing, but please tell me what to do after again ?

Tews · 20 Sep 2010

Wait for your system to BSOD, then upload the .dmp files for further analysis...

Alex P · 20 Sep 2010

Here is the new dump files.
please tell me that u figured it out

Thank you very much

Alex P · 20 Sep 2010

Tews, please tell me if u need anything else...I can't wait to resolve this because I can't do my work

Bsod w7 please help!!!

Bsod w7 please help!!!

NT6

NEW BSOD, with the real problem , I hope