BSOD Fresh install of windows 7 pro

jag3498 · 07 Sep 2011

I have been experiencing a BSOD on my fresh install of windows 7. I ran the upgrade adviser before upgrading and it said my hardware was 100% compatible. Here is the info:
-32bit windows 7 pro
-The original OS was XP home
-Retail version of 7 pro
-2.5 years since the date of purchase today at 6:05 PM
-I installed 7 a week ago
-It is a windows 7 and Ubuntu dual boot.

Here is the crash message text:

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: a
BCP1: 10000000
BCP2: 00000002
BCP3: 00000001
BCP4: 81897400
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\090711-61791-01.dmp
C:\Users\Jack\AppData\Local\Temp\WER-78905-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

And .zip is attached.

seth500 · 07 Sep 2011

I would test you ram and cpu:

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Administrator\Downloads\BSOD stuff\Windows_NT6_BSOD_jcgriff2\090111-39343-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*F:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0x8184d000 PsLoadedModuleList = 0x81997850
Debug session time: Thu Sep  1 18:12:12.608 2011 (UTC - 6:00)
System Uptime: 0 days 0:01:58.201
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {10000000, 2, 1, 818c5400}

Probably caused by : hardware

Followup: MachineOwner
---------
 *** Possible invalid call from 818eadc2 ( nt!MiInsertPageInFreeOrZeroedList+0x1e7 )
 *** Expected target 818c53d0 ( nt!KeAcquireInStackQueuedSpinLockAtDpcLevel+0x0 )

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 10000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 818c5400, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 819b7718
Unable to read MiSystemVaType memory at 819971a0
 10000000 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KeAcquireQueuedSpinLockAtDpcLevel+20
818c5400 8908            mov     dword ptr [eax],ecx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  explorer.exe

TRAP_FRAME:  903f1ef8 -- (.trap 0xffffffff903f1ef8)
ErrCode = 00000002
eax=10000000 ebx=0000030c ecx=903f1f8c edx=830f1d9d esi=82ad1644 edi=830f1d8c
eip=818c5400 esp=903f1f6c ebp=903f1f98 iopl=0         nv up ei ng nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010282
nt!KeAcquireQueuedSpinLockAtDpcLevel+0x20:
818c5400 8908            mov     dword ptr [eax],ecx  ds:0023:10000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 818eadc7 to 818c5400

POSSIBLE_INVALID_CONTROL_TRANSFER:  from 818eadc2 to 818c53d0

STACK_TEXT:  
903f1f68 818eadc7 82b3dc84 82ad1644 82ad164c nt!KeAcquireQueuedSpinLockAtDpcLevel+0x20
903f1f98 818e0644 82b3dc84 82ad1644 82ad164c nt!MiInsertPageInFreeOrZeroedList+0x1ec
903f1fd8 818f2728 00001b8b c07f00f0 00000057 nt!MiPfnShareCountIsZero+0x18c
903f20c8 818ec4e4 c07f0248 0000002c 00000000 nt!MiDeleteSystemPagableVm+0x352
903f21a4 8196d45a fe01e000 00000000 00057000 nt!MiFreePagedPoolPages+0x3c3
903f2288 8196eef1 fe01e000 00057000 903f2340 nt!MiFreePoolPages+0x455
903f22f0 911a30cf fe01e000 00000000 903f234c nt!ExFreePoolWithTag+0x436
903f2300 911afee6 fe01e000 00000005 903f24f8 win32k!FreeObject+0x2e
903f234c 91215dd3 903f2c84 903f2c6c 00000000 win32k!SURFMEM::~SURFMEM+0x129
903f2604 91183d5a fdc17010 fe64e010 00000000 win32k!EngHTBlt+0xe54
903f293c 91184f68 fdc17010 fe64e010 00000000 win32k!EngStretchBltNew+0x1c3
903f29c8 912352e7 fdc17010 fe64e010 00000000 win32k!EngStretchBlt+0x34d
903f2a64 9122b2b6 fdc17010 fe64e010 00000000 win32k!EngStretchBltROP+0x397
903f2b44 9115e0f7 00000000 903f2c84 91234f50 win32k!BLTRECORD::bStretch+0x459
903f2cc0 9115adab 9b010222 00000000 00000000 win32k!GreStretchBltInternal+0x785
903f2cfc 8188b1ea 9b010222 00000000 00000000 win32k!GreStretchBlt+0x30
903f2cfc 77d470b4 9b010222 00000000 00000000 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0316e568 00000000 00000000 00000000 00000000 0x77d470b4


STACK_COMMAND:  .trap 0xffffffff903f1ef8 ; kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  CPU_CALL_ERROR

Followup: MachineOwner
---------
 *** Possible invalid call from 818eadc2 ( nt!MiInsertPageInFreeOrZeroedList+0x1e7 )
 *** Expected target 818c53d0 ( nt!KeAcquireInStackQueuedSpinLockAtDpcLevel+0x0 )

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Administrator\Downloads\BSOD stuff\Windows_NT6_BSOD_jcgriff2\090211-34351-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*F:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0x81813000 PsLoadedModuleList = 0x8195d850
Debug session time: Fri Sep  2 00:40:57.317 2011 (UTC - 6:00)
System Uptime: 0 days 3:23:04.036
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {da6a595d, 2, 1, 85fdd2e3}

Probably caused by : ataport.SYS ( ataport!IdepInterpretTransportErrors+9 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: da6a595d, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 85fdd2e3, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 8197d718
Unable to read MiSystemVaType memory at 8195d1a0
 da6a595d 

CURRENT_IRQL:  2

FAULTING_IP: 
ataport!IdepInterpretTransportErrors+9
85fdd2e3 57              push    edi

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  8193bb14 -- (.trap 0xffffffff8193bb14)
ErrCode = 00000002
eax=832bcb40 ebx=831450e0 ecx=00000000 edx=00000000 esi=832bcb20 edi=85feb0a0
eip=85fdd2e3 esp=8193bb88 ebp=8193bb8c iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
ataport!IdepInterpretTransportErrors+0x9:
85fdd2e3 57              push    edi
Resetting default scope

LAST_CONTROL_TRANSFER:  from 85fdd2e3 to 818545cb

STACK_TEXT:  
8193bb14 85fdd2e3 badb0d00 00000000 00000000 nt!KiTrap0E+0x2cf
8193bb8c 85fdd372 831450e0 832bcb20 832bcb20 ataport!IdepInterpretTransportErrors+0x9
8193bbac 85fe3474 831450e0 832bcb20 832bcb20 ataport!IdeTranslateCompletedRequest+0x16
8193bc24 85fe3677 831450e0 832bcb20 8314509c ataport!IdeProcessCompletedRequests+0x2a0
8193bc78 8188b1b5 8314509c 83145028 00000000 ataport!IdePortCompletionDpc+0xab
8193bcd4 8188b018 8193ed20 81948380 00000000 nt!KiExecuteAllDpcs+0xf9
8193bd20 8188ae38 00000000 0000000e 00000000 nt!KiRetireDpcList+0xd5
8193bd24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38


STACK_COMMAND:  kb

FOLLOWUP_IP: 
ataport!IdepInterpretTransportErrors+9
85fdd2e3 57              push    edi

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  ataport!IdepInterpretTransportErrors+9

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ataport

IMAGE_NAME:  ataport.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce788e8

FAILURE_BUCKET_ID:  0xD1_ataport!IdepInterpretTransportErrors+9

BUCKET_ID:  0xD1_ataport!IdepInterpretTransportErrors+9

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

Memtest86: RAM - Test with Memtest86+

CPU Test Prime95: https://www.sevenforums.com/tutorials...t-prime95.html

Repair boot files: Startup Repair - Run 3 Separate Times

Please let us know the results of these test and follow the tutorials very carefully. Thanks

Seth

jag3498 · 11 Sep 2011

The Memory test was fine, but the CPU test caused temps of around 80c. Is that my problem? I stopped the test because I thought that might be to hot. Is that to hot?

seth500 · 12 Sep 2011

That's pretty warm yes, how old are the cables connecting your drives to your mobo? You might have a bad one..

jag3498 · 12 Sep 2011

It is a 3 year old netbook so the cables are 3 years old. The cooling fan went about 4 months ago so that is replaced. Also, my Friend broke the hinge and cracked the plastic on top of it, so it is hard to open up.

seth500 · 12 Sep 2011

The second code I posted is pointing towards ataport.sys and I'm wondering if the HDD is going bad in it. Open up a command prompt and run chkdsk /r to see if you have any bad files or sectors and also download crystal disk info from here:

CrystalDiskInfo - Software - Crystal Dew World

and post a screen shot of the results..

jag3498 · 12 Sep 2011

Ok. The image of crystal disk info is attached.

As for chkdsk /r, when I tried as admin, it gave me this message

screen shot attached) .

If I say Y will I be able to take a screen shot?

As a side note, how can I embed pictures into a post?

seth500 · 14 Sep 2011

Hi Jag when you run the chkdsk /r you won't be able to take a screen shot because chkdsk has to run in dos mode so when you say yes the operation will be performed upon the next reboot of the computer. The crystal disk info looks very good though but go ahead and run the chkdsk on the drive.

jag3498 · 31 Oct 2011

Hello. Sorry it's been so long but I've been really busy. The chkdsk/r came up clean. Also, could overheating be the problem. I removed the bottom plate and added a cooling pad and it has not blue screened for over a day with heavy use. With the cooling pad temps are around 70-80 no load. Now temps are 30-40 no load.

Jack