Random Blue screens after installing windows 7 and new hard disk

You have supplied a lot of crash dumps, but not some other necessary information as per the BSOD posting instructions.

Anyway, checked the crash dumps of today only. Three different bugchecks, but it is giving a chance of three alternatives (collectively, not separately).

• HDD related
• Memory related
• Virus infection

► The strongest possibility is a HDD is malfunctioning. Check it physically. It is screwed up properly? Are all the screws utilized and all those are tightly screwed? Are the sata and power cables properly connected? Change the sata cables. Also apply those cables in different ports in the motherboard.

Then plan for a HDD check. Take the HDD manufacturer's disc check tool and test if the HDD is in a good condition.

► Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

► Ataport.sys is the staorge controller, but most vulnerable to a special kind of malware called rootkit. Scan the system for possible virus infection with the following programs.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

Let us know the results.

_________________________________________________________________________________________________

Code:

BugCheck A, {a8, 2, 1, fffff80002f05622}

Probably caused by : ataport.SYS ( ataport!IdePortTickHandler+3f )

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

BugCheck 3B, {c0000005, fffff80002e913d3, fffff88008eaa020, 0}

Probably caused by : memory_corruption ( nt!MiCheckForConflictingNode+13 )

Followup: MachineOwner
----------------------------------------------------------------------------
BugCheck 24, {1904fb, fffff880022d5ba8, fffff880022d5400, fffff88001251ef7}

Probably caused by : Ntfs.sys ( Ntfs!NtfsAcquirePagingResourceExclusive+27 )

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

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88000efaeac, fffff88002fed4a8, fffff88002fecd00}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : pci.sys ( pci!PciDispatchPnpPower+146 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88000efaeac, The address that the exception occurred at
Arg3: fffff88002fed4a8, Exception Record Address
Arg4: fffff88002fecd00, Context Record Address

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
ACPI!ACPIAmliGetNamedChild+18
fffff880`00efaeac 48394118        cmp     qword ptr [rcx+18h],rax

EXCEPTION_RECORD:  fffff88002fed4a8 -- (.exr 0xfffff88002fed4a8)
ExceptionAddress: fffff88000efaeac (ACPI!ACPIAmliGetNamedChild+0x0000000000000018)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff88002fecd00 -- (.cxr 0xfffff88002fecd00)
rax=0000000000000000 rbx=fffff88002fedc70 rcx=42535f032f5c8600
rdx=00000000564d525f rsi=fffffa80036a32d0 rdi=fffffa8004004398
rip=fffff88000efaeac rsp=fffff88002fed6e8 rbp=fffffa80036987f0
 r8=0000000000000000  r9=0000000000000000 r10=fffff88000f32dcc
r11=0000000000000000 r12=fffffa80036a3201 r13=0000000000000000
r14=0000000000000000 r15=0000000000000008
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
ACPI!ACPIAmliGetNamedChild+0x18:
fffff880`00efaeac 48394118        cmp     qword ptr [rcx+18h],rax ds:002b:42535f03`2f5c8618=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030b6100
GetUlongFromAddress: unable to read from fffff800030b61c0
 ffffffffffffffff 

FOLLOWUP_IP: 
pci!PciDispatchPnpPower+146
fffff880`00f67a4e 8bc3            mov     eax,ebx

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff88000f32e2c to fffff88000efaeac

STACK_TEXT:  
fffff880`02fed6e8 fffff880`00f32e2c : fffffa80`04b21498 00000000`00000000 00000000`00000000 fffff800`02e828fa : ACPI!ACPIAmliGetNamedChild+0x18
fffff880`02fed6f0 fffff880`00f31ca1 : fffffa80`04d30720 00000000`00000004 fffffa80`036987f0 fffff880`02fed960 : ACPI!ACPIBusAndFilterIrpQueryCapabilities+0x60
fffff880`02fed800 fffff880`00efaae8 : fffffa80`04b21453 00000000`00000009 fffffa80`036987f0 fffffa80`04b21380 : ACPI!ACPIIrpCompletionRoutineWorker+0x69
fffff880`02fed830 fffff800`02e825d1 : fffffa80`036987f0 fffff800`02fb2d0e 00000000`00000000 00000000`03c01860 : ACPI!ACPIIrpGenericFilterCompletionHandler+0x44
fffff880`02fed860 fffff880`00f67a4e : fffffa80`04b21450 fffffa80`04b21400 fffffa80`04b21380 00000000`00000000 : nt!IopfCompleteRequest+0x341
fffff880`02fed950 fffff880`00f31c12 : fffffa80`04b21450 fffffa80`036a32d0 fffffa80`04d30720 00000000`000007ff : pci!PciDispatchPnpPower+0x146
fffff880`02fed990 fffff880`00f352c6 : fffff880`00f352a0 fffffa80`036987f0 fffffa80`036a32d0 fffffa80`04b21380 : ACPI!ACPIIrpSetPagableCompletionRoutineAndForward+0xfe
fffff880`02fed9c0 fffff880`00f04a8f : fffffa80`040941b0 fffff800`033fc0d6 fffffa80`04b21380 fffffa80`04b21380 : ACPI!ACPIFilterIrpQueryCapabilities+0x26
fffff880`02feda10 fffff880`010daa3e : fffffa80`04b21380 fffffa80`040941b0 fffffa80`04b21380 00000000`00000000 : ACPI!ACPIDispatchIrp+0x17b
fffff880`02feda90 fffff880`010dab94 : fffffa80`04094060 fffff880`010a0110 fffffa80`04094060 00000000`00000004 : storport!RaidAdapterPnpIrp+0x18e
fffff880`02fedaf0 fffff800`030ec9e1 : fffffa80`04094060 fffff880`02fedbd0 00000000`c00000bb fffffa80`04b21380 : storport!RaDriverPnpIrp+0x94
fffff880`02fedb30 fffff800`0323bdb7 : fffff880`02fedc70 fffffa80`036afd90 00000000`00000040 fffff880`00f6522c : nt!IopSynchronousCall+0xe1
fffff880`02fedba0 fffff800`031c1582 : 00000000`00000000 fffffa80`04d13f98 00000000`00000001 00000000`00000000 : nt!PpIrpQueryCapabilities+0x87
fffff880`02fedc30 fffff880`0531c4ab : 00000000`00000001 00000000`00000001 00000000`0000000f 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x25a56
fffff880`02fedd10 00000000`00000001 : 00000000`00000001 00000000`0000000f 00000000`00000000 fffff880`02fedd50 : nvlddmkm+0xab04ab
fffff880`02fedd18 00000000`00000001 : 00000000`0000000f 00000000`00000000 fffff880`02fedd50 fffff880`0531d484 : 0x1
fffff880`02fedd20 00000000`0000000f : 00000000`00000000 fffff880`02fedd50 fffff880`0531d484 00000001`0000000f : 0x1
fffff880`02fedd28 00000000`00000000 : fffff880`02fedd50 fffff880`0531d484 00000001`0000000f 00000000`0000001b : 0xf


SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  pci!PciDispatchPnpPower+146

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: pci

IMAGE_NAME:  pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7928f

STACK_COMMAND:  .cxr 0xfffff88002fecd00 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_pci!PciDispatchPnpPower+146

BUCKET_ID:  X64_0x7E_pci!PciDispatchPnpPower+146

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

0: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0486c000 fffff880`0534d000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Mon May 13 00:39:45 2013 (518FE8F9)
    CheckSum:         00AB6DED
    ImageSize:        00AE1000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Need to know the graphics environment. And, Storport.sys is still suspect. Need to know more about it too. Upload your MSINFO32.nfo file.

1. Click on the start button
2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
4. Give the time for processing, it will save a .nfo file on your desktop.
5. Zip it, and upload it following the instruction.

Better you post it following the Blue Screen of Death (BSOD) Posting Instructions.

What a joke is this?

Enough of joking!

Unsubscribing from your thread.

If you ever wish to read the instructions and do accordingly, call me back.