I just installed vista 32 bit ultimate as well as a new CPU and mobo. But now I get a blue screen and the system will restart it self. When windows is at the desktop, I get the following.

There are no errors under device manager.

Any help?

I scanned the memory and there were no errors. I also now get a error message that windows explorer is failing as well. COuld this just be a bad install of vista?

I also booted in safe mode and ran various applications all at the same time. Everything worked fine where as if it was in normal mode, the computer would have got the blue screen of death. So I'm thinking it is a bad copy of vista. ANy thoughts?

Hi, can you give us a run down on your PC specs?

Here's a link to a description of the error message: http://aumha.org/a/stop.php#0xc5

This is most often the result of a driver trying to access memory in a way/level that's not allowed by the system. So the fix is to repair/replace the driver that's causing this.

The first question to ask is "Did you install the Vista drivers for the new mobo/CPU combination?". Next is "Did you install the SATA drivers (if required) when you were installing Vista?". Also we'll have to ask "Is there any new hardware that you've installed that may have caused this?" - this question may not be relevant tho' because it's a fresh install of Vista.

Another way that may let us know what driver is causing this is to analyze the dump file located at C:\Windows\minidump\Mini121407-06.dmp (FYI - the -06 in the file name indicates that it's the 6th crash dump on that day, and that's a lot!). There will be other dump files located there and you can analyze them also if you'd like.

Follow the instructions at this link and post your results back here for us to have a look at: http://forums.majorgeeks.com/showthread.php?t=35246

Was it a new install on a freshly formated partition/hard drive?

Hi Usasma, Here is the 1st crash and last crash of yesterday.... Any input would be great! THX

Microsoft ® Windows Debugger Version 6.8.0004.0 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini121407-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Vista Kernel Version 6000 UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6000.16386.x86fre.vista_rtm.061101-2205
Kernel base = 0x81800000 PsLoadedModuleList = 0x81911db0
Debug session time: Fri Dec 14 18:10:04.192 2007 (GMT-7)
System Uptime: 0 days 1:06:35.829
Loading Kernel Symbols
................................................................................
..........................................................
Loading User Symbols
Loading unloaded module list
....................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41285, 836f1800, 232000, 1}



Probably caused by : memory_corruption ( nt!MiUpdateWsleHash+cf )

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




AND


Microsoft ® Windows Debugger Version 6.8.0004.0 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini121407-14.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:
Windows Vista Kernel Version 6000 UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6000.16575.x86fre.vista_gdr.071009-1548
Kernel base = 0x81800000 PsLoadedModuleList = 0x81911e10
Debug session time: Fri Dec 14 23:03:05.559 2007 (GMT-7)
System Uptime: 0 days 0:06:30.291
Loading Kernel Symbols
................................................................................
...........................................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FC, {8e8afb58, 8109963, 8e8afa9c, 2}



Probably caused by : tcpip.sys ( tcpip!TcpCleanupEndpointWorkQueueRoutine+90 )

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

Hi Chewey,

It a bit dated, but will be used by someone to whee it will be more than enough..

Celeron D 3.3
1 GB DDR
183 GB Maxtor HD
FoxConn 661GX7MJ
9600 Radeon

And it was a fresh install on a newly formed and formatted partition

Thanks!

2 sticks of ram or one, if 2 are they matched/same brand?

2 sticks of exactly the same ram...

The lastest BSOD


Microsoft ® Windows Debugger Version 6.8.0004.0 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini121507-06.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:
Windows Vista Kernel Version 6000 UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6000.16575.x86fre.vista_gdr.071009-1548
Kernel base = 0x81800000 PsLoadedModuleList = 0x81911e10
Debug session time: Sat Dec 15 20:00:50.715 2007 (GMT-7)
System Uptime: 0 days 0:48:07.615
Loading Kernel Symbols
................................................................................
..........................................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {c, 2, 1, 89079959}

Unable to load image \SystemRoot\system32\DRIVERS\athr.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for athr.sys
*** ERROR: Module load completed but symbols could not be loaded for athr.sys


Probably caused by : athr.sys ( athr+d959 )

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

funky wireless card?

Please run the !analyze -v by typing it into the box at the bottom of the debugger after opening the dump file. The additional info should confirm DaChew's supposition that it's an issue with your wireless card.

Attached is the analyize screen from above, the wireless card worked fine with Ultimate before I installed the CPU and MOBO. Should I try to put it on another slot, does it matter what channel it runs on on the board?
Microsoft ® Windows Debugger Version 6.8.0004.0 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini121507-06.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:
Windows Vista Kernel Version 6000 UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6000.16575.x86fre.vista_gdr.071009-1548
Kernel base = 0x81800000 PsLoadedModuleList = 0x81911e10
Debug session time: Sat Dec 15 20:00:50.715 2007 (GMT-7)
System Uptime: 0 days 0:48:07.615
Loading Kernel Symbols
................................................................................
..........................................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {c, 2, 1, 89079959}

Unable to load image \SystemRoot\system32\DRIVERS\athr.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for athr.sys
*** ERROR: Module load completed but symbols could not be loaded for athr.sys


Probably caused by : athr.sys ( athr+d959 )

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

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: 0000000c, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 89079959, address which referenced memory

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




WRITE_ADDRESS: GetPointerFromAddress: unable to read from 819315ac
Unable to read MiSystemVaType memory at 819117e0
0000000c

CURRENT_IRQL: 2

FAULTING_IP:
athr+d959
89079959 ?? ???

CUSTOMER_CRASH_COUNT: 6

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: iexplore.exe

TRAP_FRAME: 82003e5c -- (.trap 0xffffffff82003e5c)
ErrCode = 00000002
eax=00000000 ebx=8906d6d0 ecx=847df538 edx=00000000 esi=85d045f0 edi=00000000
eip=89079959 esp=82003ed0 ebp=82003edc iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010282
athr+0xd959:
89079959 ?? ???
Resetting default scope

LAST_CONTROL_TRANSFER: from 89079959 to 8188fd84

STACK_TEXT:
82003e5c 89079959 badb0d00 00000000 87a6b080 nt!KiTrap0E+0x2ac
WARNING: Stack unwind information not available. Following frames may be wrong.
82003ecc 847df5ec 8481ff58 00000000 82003f10 athr+0xd959
82003edc 89079908 85c76ad0 8481ff30 00000001 0x847df5ec
82003f10 890793c3 85c76ad0 00000000 00000002 athr+0xd908
82003f24 890af5d1 85c76ad0 00000001 82003f44 athr+0xd3c3
82003f34 8906d6f1 87a54020 85c76ad0 82003f68 athr+0x435d1
82003f44 821b5086 85c76ad0 00000000 00000000 athr+0x16f1
82003f68 820fd252 85d04604 00000000 00000000 ndis!ndisMiniportDpc+0x81
82003f88 818a93ae 85d04604 85d045f0 00000000 ndis!ndisInterruptDpc+0x8b
82003ff4 81890ecd 9146bb3c 00905a4d 00000003 nt!KiRetireDpcList+0x147
82003ff8 9146bb3c 00905a4d 00000003 00000004 nt!KiDispatchInterrupt+0x3d
82003ffc 00905a4d 00000003 00000004 0000ffff 0x9146bb3c
82004000 00000000 00000004 0000ffff 000000b8 0x905a4d


STACK_COMMAND: kb

FOLLOWUP_IP:
athr+d959
89079959 ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: athr+d959

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: athr

IMAGE_NAME: athr.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4716cbc7

FAILURE_BUCKET_ID: 0xD1_W_athr+d959

BUCKET_ID: 0xD1_W_athr+d959

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

Another minidump

Microsoft ® Windows Debugger Version 6.8.0004.0 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini121407-05.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:
Windows Vista Kernel Version 6000 UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6000.16575.x86fre.vista_gdr.071009-1548
Kernel base = 0x81800000 PsLoadedModuleList = 0x81911e10
Debug session time: Fri Dec 14 19:15:03.334 2007 (GMT-7)
System Uptime: 0 days 0:06:10.066
Loading Kernel Symbols
................................................................................
...........................................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 8a8cb146, 93e9dbc4, 0}



Probably caused by : hardware ( win32k!InternalInvalidate2+29c )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: c0000005, The exception code that was not handled
Arg2: 8a8cb146, The address that the exception occurred at
Arg3: 93e9dbc4, Trap Frame
Arg4: 00000000

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




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

FAULTING_IP:
win32k!InternalInvalidate2+29c
8a8cb146 1a01 sbb al,byte ptr [ecx]

TRAP_FRAME: 93e9dbc4 -- (.trap 0xffffffff93e9dbc4)
ErrCode = 00000000
eax=00000000 ebx=ff0805a0 ecx=00000000 edx=00000000 esi=00010000 edi=93e9dc64
eip=8a8cb146 esp=93e9dc38 ebp=93e9dc64 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
win32k!InternalInvalidate2+0x29c:
8a8cb146 1a01 sbb al,byte ptr [ecx] ds:0023:00000000=??
Resetting default scope

CUSTOMER_CRASH_COUNT: 5

DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: iexplore.exe

CURRENT_IRQL: 0

MISALIGNED_IP:
win32k!InternalInvalidate2+29c
8a8cb146 1a01 sbb al,byte ptr [ecx]

LAST_CONTROL_TRANSFER: from 8a8cadef to 8a8cb146

STACK_TEXT:
93e9dc64 8a8cadef 00003005 00000001 0104005a win32k!InternalInvalidate2+0x29c
93e9dcb4 8a8dccee ff0805a0 00000001 00001005 win32k!xxxInternalInvalidate+0x11b
93e9dce0 8a8dde11 ff0805a0 00000000 00000000 win32k!xxxRedrawWindow+0x103
93e9dcf8 8a8ddd9f ff0805a0 00000000 00000001 win32k!xxxInvalidateRect+0x32
93e9dd50 8188caaa 0002058a 00000000 00000001 win32k!NtUserInvalidateRect+0x8f
93e9dd50 76e30f34 0002058a 00000000 00000001 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0b9ef9f4 00000000 00000000 00000000 00000000 0x76e30f34


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!InternalInvalidate2+29c
8a8cb146 1a01 sbb al,byte ptr [ecx]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: win32k!InternalInvalidate2+29c

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: hardware

FAILURE_BUCKET_ID: IP_MISALIGNED

BUCKET_ID: IP_MISALIGNED

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

The first one confirms the wireless card drivers - but the second one seems to think that it's either a hardware or a Windows problem.

Download the latest version of the wireless card drivers from the manufacturer's website
Uninstall the wireless drivers (from Device Manager and then from Control Panel (if present)).
Reboot
Install the freshly downloaded drivers and see if that clears things up.

and if John's suggestion doesn't work(there may not be any new drivers)




definitely, plug and play is still too much pray not play

I pulled out my wireless card and still got the BSOD!

doublecheck your bios for any settings that might corrupt an install

make sure you are running the latest bios, some older versions won't work with new OS's

run memtest and HD diagnostics

doublecheck the cd and installer optical drive

and all cables