Vista BSOD - Intermittent on BootUp

[MilhouseGB]

I'm getting blue screen when I boot my new Vista Ultimate 32bit PC. After a number of reboots it boots correctly. I've tried various drivers, especially nvidia ones, tested the memory for almost 24 hours using memtest86 (no problems found). Once it's booted up the PC is quite stable (outside of games that is). An example dmp file is below (though Vista sometimes says it's produced dmp file but I can't find one in C:\Windows\Minidump):


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


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

Symbol search path is: SRV*c:\symbols*
Executable search path is:
Windows Vista Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6000.16514.x86fre.vista_gdr.070627-1500
Kernel base = 0x82400000 PsLoadedModuleList = 0x82511db0
Debug session time: Wed Sep 19 09:03:09.142 2007 (GMT+1)
System Uptime: 0 days 0:00:19.688
Loading Kernel Symbols
...................................................................... ...................................................
Loading User Symbols
Loading unloaded module list
....
********************************************************************** *********
* *
* Bugcheck Analysis *
* *
********************************************************************** *********

Use !analyze -v to get detailed debugging information.

BugCheck 50, {80000000, 8, 80000000, 0}

Probably caused by : ntkrpamp.exe ( nt!KiTrap0E+dc )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: 80000000, memory referenced.
Arg2: 00000008, value 0 = read operation, 1 = write operation.
Arg3: 80000000, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 825315ac
Unable to read MiSystemVaType memory at 82511780
80000000

FAULTING_IP:
+ffffffff80000000
80000000 ?? ???

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: csrss.exe

CURRENT_IRQL: 0

TRAP_FRAME: 8ab679f0 -- (.trap 0xffffffff8ab679f0)
ErrCode = 00000010
eax=00000000 ebx=866bb7a8 ecx=00000007 edx=8ab67998 esi=867b5740 edi=862ca008
eip=80000000 esp=8ab67a64 ebp=8674a008 iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010282
80000000 ?? ???
Resetting default scope

LAST_CONTROL_TRANSFER: from 8248fa34 to 824a9df2

STACK_TEXT:
8ab679d8 8248fa34 00000008 80000000 00000000 nt!MmAccessFault+0x106
8ab679d8 80000000 00000008 80000000 00000000 nt!KiTrap0E+0xdc
WARNING: Frame IP not in any known module. Following frames may be wrong.
8ab67a60 5666c359 be665066 0000152c 25255fe8 0x80000000
8ab67a64 be665066 0000152c 25255fe8 e8c10600 0x5666c359
8ab67a68 00000000 25255fe8 e8c10600 36f48b09 0xbe665066


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiTrap0E+dc
8248fa34 85c0 test eax,eax

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KiTrap0E+dc

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 468308e9

FAILURE_BUCKET_ID: 0x50_W_nt!KiTrap0E+dc

BUCKET_ID: 0x50_W_nt!KiTrap0E+dc

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

Spec is:
Processor:
Intel Core2Duo 6600@2.4Ghz
Motherboard:
Gigabyte GA-P35-S3
Memory:
2x1GB Elixir DDR2 PC2-8500
PSU:
PSU Corsair HX520
Cooling:
Intel Retail CPU Fan + 3 coolermaster case fans and Smart Drive2002 dock
Videocard:
XFX 7950GT (PV-T71J-UHE4)
Hard Disk(s):
Seagate ST3320620AS;Samsung HD401LJ
Case:
CoolerMaster WaveMaster


Any help most appreciated. Thanks.

[Neil T]

Hey mate,

I don't know how much I can help, I had similar issues myself but when using Vista 64 bit. I was having BSOD mainly just after the computer started but also much more rarely during video playback and general internet use. It was very fustrating.

I tried numerous drivers and memory tests and nothing seemed to work. I then loaded Vista 32 bit and everything sorted itself out. I know this doesn't seem very helpful but maybe you could try a fresh install. Sorry for not being much help, but persistence will solve the issue.

[speardane]

what do you want to use this PC for?
any reason why you couldn't use XP?

most stores will agree to let you take XP now (and upgrade later) because the current driver set is so poor, if this is a new computer.

Personally I'd use Linux but that is a different kettle of fish entirely!

[Splash]

I'd disagree that the driver set for Vista is poor, especially on modern hardware (yes, the latest nVidia drivers suck, and the Creative ones always have/always will but...)

CSRSS.exe is the Client Server Runtime Server Subsystem, and as such if this is failing to start cleanly I can imagine that it would be a fairly major issue... Pointers for troubleshooting anyways (I believe that's why you posted, not to be told to use Linux)

Run Memtest86+ for a good 12 hours or so, that'll help rule out RAM though if you're always getting the same fault I would suggest it may be your hard drive (s). If the memory passes fine then run a chkdsk /r on each disk and see what happens.

There are also reports of issues with the chipset drivers for that motherboard causing BSODs, not sure if there's an updated version available?

[excalibur2]

Well if it was my computer would first check if the memory is seated in firmly, then do the memory check.......still a problem? Check that the voltage for cpu etc are correct in the bios............still a problem? Then as it's new and not filled with docs, programs, jpgs etc would format the drive and have dual boot for xp and Vista......still a problem? Then pop in and old PCI graphic card, I was using a very old Matrox mystique with 4 meg memory for vista, till I upgraded so vista and winxp are very tolerant.
I would be suprised if you still have a problem after the above.

[speardane]

the key bit of my post was "what do you want to use the machine for?"

Evidently you use it for games - most gamers want to extract all available horsepower
but what else? There may be something that drives the upgrade? You are running 32 bit, rather than 64 bit; you don't have so much memory that it would be ignored

If you don't need vista - maybe you should consider XP?

The vista driver issues are well documented. They have changed architecture and are also providing 64 bit options. There is a fundamental design change; whereas the XP driver set were an incremental change. A lot of people are resisting upgrades as a consequence. see for instance:
UK Daily Telegraph this week
ZDNet on MS allowing corporate downgrades - a few weeks back

[Rant on]
It seems a fundamental principle of personal computers that you should buy them and use them according to your needs - not according to the needs of a manufacturer - or corporate IT [/Rant off] To design (or redesign) anything properly you need to understand the purpose...

-----------
BTW

... not to be told to use Linux...

to be a bit more explicit

• I said "personally I'd use Linux, but that's another kettle of fish" - it's personal choice
• I guessed for a gamer it's probably not the platform of choice!

sorry if I distracted with a throwaway comment