Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Can't get Vista to work


  • Please log in to reply
12 replies to this topic

#1 dgrillo

dgrillo

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:06:23 PM

Posted 08 March 2009 - 02:13 PM

hello all!

I have been trying to get Vista to work on my machine and just haven't had much luck. Once getting it installed it seems to work ok, but as soon as I install my video drivers and reboot, I get BSOD's

First I will start with my system specs:

MOBO: Evga 780i SLI
Proc: Core2 quad Q6600 @ 2.4 ghz
RAM: 4 gig Corsair Dominator SLI
Video: Evga GeForce 9800GT 512
Sound: Creative ExtremGamer Fatality
HD: Barracuda 250g Sata

Next here is the memory dump from Vista crashing


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


Loading Dump File [G:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (4 procs) Checked x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18000.x86chk.longhorn_rtm.080118-1840
Machine Name:
Kernel base = 0x81847000 PsLoadedModuleList = 0x81c5d650
Debug session time: Sun Mar 8 14:38:13.770 2009 (GMT-4)
System Uptime: 49 days 16:04:08.174 (checked kernels begin at 49 days)
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..
Loading User Symbols

Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7E, {80000003, 8197f168, 8c5e5958, 8c5e5654}

Probably caused by : dxgkrnl.sys ( dxgkrnl!DMMMONITORDESCRIPTORSET::AddDescriptor+e7 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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.
Arguments:
Arg1: 80000003, The exception code that was not handled
Arg2: 8197f168, The address that the exception occurred at
Arg3: 8c5e5958, Exception Record Address
Arg4: 8c5e5654, Context Record Address

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


EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid

FAULTING_IP:
nt!DbgPrompt+46
8197f168 cc int 3

EXCEPTION_RECORD: 8c5e5958 -- (.exr 0xffffffff8c5e5958)
ExceptionAddress: 8197f168 (nt!DbgPrompt+0x00000046)
ExceptionCode: 80000003 (Break instruction exception)
ExceptionFlags: 00000000
NumberParameters: 3
Parameter[0]: 00000002
Parameter[1]: 8eb70bb4
Parameter[2]: 0000001d

CONTEXT: 8c5e5654 -- (.cxr 0xffffffff8c5e5654)
eax=00000002 ebx=8c5e5a6c ecx=8eb70bb4 edx=0000001d esi=8eb70bb5 edi=00000002
eip=8197f168 esp=8c5e5a20 ebp=8c5e5a3c iopl=0 nv up ei pl nz ac pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000216
nt!DbgPrompt+0x46:
8197f168 cc int 3
Resetting default scope

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x7E

PROCESS_NAME: System

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION} Breakpoint A breakpoint has been reached.

EXCEPTION_PARAMETER1: 00000002

EXCEPTION_PARAMETER2: 8eb70bb4

EXCEPTION_PARAMETER3: 0000001d

LAST_CONTROL_TRANSFER: from 8eb6e2dd to 8197f168

STACK_TEXT:
8c5e5a3c 8eb6e2dd 8eb70bb4 8c5e5a6c 00000002 nt!DbgPrompt+0x46
8c5e5a5c 823219e8 00000002 0097fb70 99cf0000 watchdog!WdLogEvent5+0x1c3
8c5e5a8c 82322098 0000102d 8eb6e11a 89e14638 dxgkrnl!DMMMONITORDESCRIPTORSET::AddDescriptor+0xe7
8c5e5acc 82322144 00000002 8c5e5c38 8eb6e11a dxgkrnl!DXGMONITOR::ObtainEEdidV1BlockFromDriver+0x1a2
8c5e5af0 823224a8 822c748c 8c5e5bf8 8c5e5be4 dxgkrnl!DXGMONITOR::ObtainRawEEdidV1BlocksFromDriver+0x5d
8c5e5b50 82322a29 89dbaaa8 8d8e8b40 8181866a dxgkrnl!DXGMONITOR::OnMonitorDriverArrival+0x2e7
8c5e5b68 81d2ce8d 8c5e5be4 00000000 899594d8 dxgkrnl!DmmMonitorPnpInterfaceChangeNotification+0x7e
8c5e5ba8 81d2c1c0 8c5e5be4 8c5e5bcc a49812d8 nt!PnpNotifyDriverCallback+0x15b
8c5e5c10 81d3f870 a498131c 8c5e5c38 81be951c nt!PnpNotifyDeviceClassChange+0x21a
8c5e5d4c 819a1e1e 8a15ae68 854adc08 899594d8 nt!PnpDeviceEventWorker+0x380
8c5e5d84 81eb1197 8a15ae68 91e56a42 00000000 nt!ExpWorkerThread+0x146
8c5e5dc0 819bb97e 819a1cd8 80000001 00000000 nt!PspSystemThreadStartup+0x17b
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


FOLLOWUP_IP:
dxgkrnl!DMMMONITORDESCRIPTORSET::AddDescriptor+e7
823219e8 c74508d2efffff mov dword ptr [ebp+8],0FFFFEFD2h

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: dxgkrnl!DMMMONITORDESCRIPTORSET::AddDescriptor+e7

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME: dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 479186e2

STACK_COMMAND: .cxr 0xffffffff8c5e5654 ; kb

FAILURE_BUCKET_ID: 0x7E_dxgkrnl!DMMMONITORDESCRIPTORSET::AddDescriptor+e7

BUCKET_ID: 0x7E_dxgkrnl!DMMMONITORDESCRIPTORSET::AddDescriptor+e7

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


I have been rather anxious to get Vista working and thought I would try here before completely writing Vista off.

BC AdBot (Login to Remove)

 


#2 Jacee

Jacee

    Bleeping around


  • Malware Response Team
  • 3,716 posts
  • OFFLINE
  •  
  • Gender:Female
  • Local time:04:23 PM

Posted 08 March 2009 - 02:56 PM

Uninstall your graphics drivers and try running with just the drivers that came with Vista .... do you still get the BSOD?

MS_MVP.gif
MS MVP Windows-Security 2006-2016
Member of UNITE, the Unified Network of Instructors and Trusted Eliminators

Admin PC Pitstop


#3 dgrillo

dgrillo
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:06:23 PM

Posted 08 March 2009 - 03:02 PM

Uninstall your graphics drivers and try running with just the drivers that came with Vista .... do you still get the BSOD?


No, if i run with the default vista drivers i do not get the BSOD.

Also, this is not my first go at trying to get this to work. I have tried several drives both from Evga and straight from Nvidia. I have even as much as tried "hacked" drivers.

#4 Jacee

Jacee

    Bleeping around


  • Malware Response Team
  • 3,716 posts
  • OFFLINE
  •  
  • Gender:Female
  • Local time:04:23 PM

Posted 08 March 2009 - 03:18 PM

You could try the reliability performance:
http://support.microsoft.com/kb/955302

Or check here:
http://msdn.microsoft.com/en-us/library/ms796067.aspx

MS_MVP.gif
MS MVP Windows-Security 2006-2016
Member of UNITE, the Unified Network of Instructors and Trusted Eliminators

Admin PC Pitstop


#5 dgrillo

dgrillo
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:06:23 PM

Posted 08 March 2009 - 04:12 PM

You could try the reliability performance:
http://support.microsoft.com/kb/955302

Or check here:
http://msdn.microsoft.com/en-us/library/ms796067.aspx


Tried to install that and it said that it didn't apply to me. The second link was useful in giving me info on what the file does but didn't really point me towards a fix unless I missed something on the page.

#6 Jacee

Jacee

    Bleeping around


  • Malware Response Team
  • 3,716 posts
  • OFFLINE
  •  
  • Gender:Female
  • Local time:04:23 PM

Posted 08 March 2009 - 06:02 PM

The only thing I can think of is, do you need to update the drivers, or have you done that?

MS_MVP.gif
MS MVP Windows-Security 2006-2016
Member of UNITE, the Unified Network of Instructors and Trusted Eliminators

Admin PC Pitstop


#7 dgrillo

dgrillo
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:06:23 PM

Posted 08 March 2009 - 06:05 PM

The only thing I can think of is, do you need to update the drivers, or have you done that?


the drivers are the latest and greatest from EVGA. I can run vista without the drivers but i have feeling that game performance will suffer, maybe not.

#8 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:07:23 PM

Posted 09 March 2009 - 05:45 PM

Try it with only 2 gB of RAM installed. I seem to recall issues with that chipset and large amounts of RAM.
You may be able to reinstall the extra RAM after the driver is completely installed - but there's no sure thing here.

Check the mobo's website for BIOS updates that relate to memory issues. If you do choose to update the BIOS - be very, very careful. Flashing the BIOS is very unforgiving and can easily turn your PC into a large paperweight. Post back here and we'll give some cautions if you do choose to flash the BIOS.
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#9 dgrillo

dgrillo
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:06:23 PM

Posted 10 March 2009 - 07:51 AM

Try it with only 2 gB of RAM installed. I seem to recall issues with that chipset and large amounts of RAM.
You may be able to reinstall the extra RAM after the driver is completely installed - but there's no sure thing here.

Check the mobo's website for BIOS updates that relate to memory issues. If you do choose to update the BIOS - be very, very careful. Flashing the BIOS is very unforgiving and can easily turn your PC into a large paperweight. Post back here and we'll give some cautions if you do choose to flash the BIOS.


I have already flashed the BIOS to the current version. I was reading another article yesterday about problems vista had with systems that have more that 2 gig of ram. I thought this problem was pre-SP1 but maybe there are still some lingering issues. Should I reinstall Vista with just the 2 gigs or just the Nvidia drivers?

#10 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:07:23 PM

Posted 10 March 2009 - 09:20 AM

The issues aren't between Vista and 2 gB, but rather are in the way that the 7xxi chipset/motherboard address the memory when working with Vista.

I'd try it with the 2 gB and if that doesn't fix it I'd reinstall with only 2 gB. As I recall (not 100% sure tho') that the problem occurred during installation and that some people were able to use the 4 gB afterwards.
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#11 dgrillo

dgrillo
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:06:23 PM

Posted 10 March 2009 - 07:38 PM

ok, quick update..

I removed 2 gigs of ram and installed the drivers.. I got the same BSOD after reboot. Out of frustration, i decided I was going to wipe the partition and do a fresh install with the ram out... During the install I got a BSOD and it mentions the usbport.sys driver. Rebootied thinking the install would pick up where it left off and it did however, about 5 minutes into it I got another BSOD referring to usbport.sys.

At this moment, I am reformatting and considering my options... Any guidance that can be offered is much appreciated.

#12 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:07:23 PM

Posted 10 March 2009 - 08:42 PM

If the error is consistent with the usbport.sys driver, try disabling your USB ports in the BIOS.
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#13 dgrillo

dgrillo
  • Topic Starter

  • Members
  • 8 posts
  • OFFLINE
  •  
  • Local time:06:23 PM

Posted 10 March 2009 - 09:07 PM

If the error is consistent with the usbport.sys driver, try disabling your USB ports in the BIOS.


ok, i will need to get a ps2 keyboard before I can try this




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users