Windows VistaPost your Windows Vista related questions here.
Mission Statement
WindowsBBS is an online community dedicated to easily accessible technical support for those using Microsoft operating systems and other Windows software.
Our goal is to become the leading resource for computer users that require assistance with their day-to-day computer usage, including full support for networking PC's, virus & malware removal, system upgrades and general support questions.
I just got Vista Ultimate for my computer and everything was good. But at random times my computer locks up and i get a bluescreen then it resets. I have an AMD Athlon X2 4600+, 2GBram, ATI Radeon X300/X550/X1050 Series video card. Here is the debug log..
Opened log file 'c:\debuglog.txt'
Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\Mini011908-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: C:\Windows;C:\Windows\system32;C:\Windows\system32\drivers
Windows Vista Kernel Version 6000 MP (2 procs) 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 Jan 19 00:43:08.989 2008 (GMT-5)
System Uptime: 0 days 4:00:31.894
Loading Kernel Symbols
........................................................................... .....................................................................
Loading User Symbols
Loading unloaded module list
.....
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****
Use !analyze -v to get detailed debugging information.
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: 904d8e48, The address that the exception occurred at
Arg3: 9075bc54, 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!SetWakeBit+4b
904d8e48 66095806 or word ptr [eax+6],bx
TRAP_FRAME: 9075bc54 -- (.trap 0xffffffff9075bc54)
.trap 0xffffffff9075bc54
ErrCode = 00000002
eax=00e1eaf0 ebx=00000010 ecx=00007530 edx=00000000 esi=fd4b4c98 edi=0000000f
eip=904d8e48 esp=9075bcc8 ebp=9075bcd0 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!SetWakeBit+0x4b:
904d8e48 66095806 or word ptr [eax+6],bx ds:0023:00e1eaf6=????
.trap
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 904dce2a to 904d8e48
STACK_TEXT:
9075bcd0 904dce2a fd4b4c98 00000010 00000001 win32k!SetWakeBit+0x4b
9075bcf8 90408782 00000004 0183ff40 904d8cfe win32k!TimersProc+0x111
9075bd34 90405145 00000001 00000002 8c254478 win32k!RawInputThread+0x5dc
9075bd48 904d8d19 00000004 0183ff40 9075bd64 win32k!xxxCreateSystemThreads+0x4a
9075bd58 8188caaa 00000004 0183ff80 77600f34 win32k!NtUserCallNoParam+0x1b
9075bd58 77600f34 00000004 0183ff80 77600f34 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0183ff80 00000000 00000000 00000000 00000000 0x77600f34
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!SetWakeBit+4b
904d8e48 66095806 or word ptr [eax+6],bx
I have a suspicion it might be the video card driver but i dont know.
There's a possibility this may be the case, but one dump is not enough for the experts to draw a conclusion (note: I'm no expert in reading these dump files!)
Memory checking programs are not adequate because they don't test the memory the way that Windows uses it. Most, if not all, memory checkers use read/write cycles when scanning memory. Since Windows is executing code from the memory, it uses execute cycles. Execute cycles are physically different from read/write cycles and are more vulnerable to parity errors. It is possible for memory checking programs to find parity errors if the memory is extremely faulty.
Don't take this as gospel -- I am a long way from being an expert in troubleshooting Windows Vista problems. I do, however, have some rudimentory experience in the last couple of weeks because of my own problems.
NOTE: Your "BugCheck 1000008E, {c0000005, 904d8e48, 9075bc54, 0}" is the same error I received between removing my ATI x800 GT Ultra and removing the ATI drivers. It never surfaced again after I remove the ATI drivers/catalyst. I did a little GOOGLE searching and came across a note that stated the above error can be caused by the ATI drivers in version 7.1. I don't know whether my problem was connected because I was using the current 8.2 ATA Catalyst suite.
I removed my ATI video card (it had developed a noisy fan problem anyway) and reinstalled the nVidia Geforce 7300LE. All of my crashing problems seemed to dissappear. I then ordered and installed an nVidia Geforce 8600 GT. Suddenly I was getting Bluescreen crashes left and right again and they were all different -- didn't see the same one twice. I could not get the OS to boot up at all. I finally broke down and made the leap that I probably had a memory problem since my original crashes started within two weeks following installation of additional 2GByte of memory. This may have been related to the high-end video because the crashing actually started right after I installed the ATA version 8.2 Catalyst suite, about a week ago, stopped when I went back to the nVidia Gefore 7300LE low-end video and then restarted again after installing the nVidia Gefore 8600GT high-end video; I don't know, maybe it used the memory beyond the original 2Gbyte addressing. The crashing now seems to have stopped after removing the newer 2GByte of memory so I hope that was the problem. I'm a little dissapointed because I installed (2) 1GByte 5300 DDR2 Kingston memory; the original system memory is (2) 1GByte 4200 DDR2 generic. One would think I installed a better quality memory at a more optimum speed rating.
One benefit I got from the ordeal so far is my Windows Vista Performance Index went from 4.8 to 5.1, because the 3D video went from 4.8 to 5.6 -- difference between the ATA X800 GT and the nVidia Geforce 8600GT. Now my performance is limited by the CPU (Intel Core2 Duo 6400 -- 5.1)
Last edited by hilleyja; 22nd January 2008 at 16:05.
