Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Blue screen problem More Help Needed (SOLVED)
New Posts  All Forums:Forum Nav:

Blue screen problem More Help Needed (SOLVED) - Page 6

post #51 of 138
Thread Starter 
Quote:
Originally Posted by Sevada88 View Post

Do you have by any chance your OS installed on a Crucial M4 SSD?


Nope
post #52 of 138
Thread Starter 
ok guys I have another problem my computer has stop loading and it turns out to be a bad video driver when I roll back the driver the computer loads but as soon as the computer updates the video card and I have to restart the computer goes as far as the windows logo Starting Windws and no further,, but I am using the latest driver for my video card..
Could it be that the card is going bad or just the drivers acting up?????
video card is a = 512mb DDR5 NVidia Geforce GT240 PCI-E 2.0
post #53 of 138
Try a different version other than the latest.
post #54 of 138
Thread Starter 
ok I finally found older drivers 196.21 installed it and the same thing happen windows started to load then sticks at the windows logo mad.gifmad.gif
post #55 of 138
Let's give enabling Driver Verifier a shot. If this is a 3rd party driver causing these freezes and BSODs, it will show up in a verifier enabled dump. If you cannot access Windows, enable it in Safe Mode and start Windows and hopefully it'll BSOD rather than freeze. Once it has, go back into Safe Mode and attach the verifier enabled dump.
post #56 of 138
Thread Starter 
ok did what you said I pick the drivers and restarted and it still stuck at the logo window for about 30 mins, then i rebooted in safemode and remove all video drivers and rebooted, it loaded right up, window updated the video drivers to NVidia 8.1.17.9621 then rebooted as soon as it started to boot, BSOD happen, so i restarted and I boot in to safe mode uninstall all drivers and rebooted again, it loaded right up and give me the windows has recovered from unexpected shutdown etc,
I have attach the dump file below
I am thinking my be the video card is faulty or just bad drivers what do you think?



040112-39468-01.zip 16k .zip file
Edited by bajanboy - 4/1/12 at 7:47am
post #57 of 138
The culprit in the newly attached dump is HDAudBus.sys. HDAudBus.sys is the Microsoft High Definition Bus Driver for your audio, since it's a Microsoft file, the likelihood of this being the cause is very slim, and we always assume that Microsoft's files are never a culprit / cause of the crash, but in fact what was crashed because of the original culprit, or just an incorrect probable cause due to Windows having no idea what the cause is because it's hardware, for example.

If you'd like to know a little bit more, the reason Microsoft is generally never blamed as a cause (which it really never is) is because Microsoft specific files are protected by the SFC (System File Checker). In some cases the probable Microsoft listed causes may point us to a cause, but in most cases, it does not.

If it actually does happen to be your audio sub system that is giving BSODs, you can fully uninstall your currently audio drivers for Win 7 / sound card, and then reinstall the latest versions provided by the vendor or manufacturer.

If the above does not help, I would recommend a clean install of Windows with brand new up to date drivers, etc. If you are still BSOD'ing on the fresh install, it's hardware, or a driver that you keep managing to install that is causing issues, but may be easier to pinpoint on a fresh install.

Your nVidia drivers are from 2010, I would recommend updating those, by the way. Do not let Windows update the drivers, disable that if you have to for the time being:
Quote:
Go to Start–>Search type in gpedit.msc
Click the file to open the Local Group Policy Editor and show Windows who is in control!!
You want to go here: Computer Configuration->Administrative Templates->System->Device Installation. Click on the subfolder Device Installation on the left and on the right side you will see the possible restrictions.
Right Click on Prevent Installation of Devices not described by other policy settings and edit this option, set it on ENABLED.
Reboot Windows and enjoy its inability to pollute your system with its standard driver, open gpedit.msc again and revert the change so you will be able to install your driver.

Dump for reference:
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Icarus\Downloads\040112-39468-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e64000 PsLoadedModuleList = 0xfffff800`030a9670
Debug session time: Sun Apr  1 09:58:12.811 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:11.388
Loading Kernel Symbols
...............................................................
.........................
Loading User Symbols
Loading unloaded module list
.
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, 10329246a, fffff880037c7d28, fffff880037c7580}

Probably caused by : HDAudBus.sys ( HDAudBus!_NULL_IMPORT_DESCRIPTOR+1bc )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: ffffffffc0000005, The exception code that was not handled
Arg2: 000000010329246a, The address that the exception occurred at
Arg3: fffff880037c7d28, Exception Record Address
Arg4: fffff880037c7580, Context Record Address

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


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

FAULTING_IP: 
+1bc
00000001`0329246a ??              ???

EXCEPTION_RECORD:  fffff880037c7d28 -- (.exr 0xfffff880037c7d28)
ExceptionAddress: 000000010329246a
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000008
   Parameter[1]: 000000010329246a
Attempt to execute non-executable address 000000010329246a

CONTEXT:  fffff880037c7580 -- (.cxr 0xfffff880037c7580)
rax=fffff88004a21596 rbx=fffff8000339c228 rcx=000000000053bb3b
rdx=0000000000000100 rsi=0000000000000000 rdi=fffff88004a21594
rip=000000010329246a rsp=fffff880037c7f60 rbp=fffff80000000000
 r8=fffff80003398000  r9=00000000000000ec r10=0000000000000840
r11=00000000000001a3 r12=fffff88004a131a8 r13=fffff88004a00000
r14=fffff80002e64000 r15=fffff80003398000
iopl=0         nv up ei ng nz na po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010287
00000001`0329246a ??              ???
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  System

CURRENT_IRQL:  0

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

EXCEPTION_PARAMETER1:  0000000000000008

EXCEPTION_PARAMETER2:  000000010329246a

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003113100
 000000010329246a 

FOLLOWUP_IP: 
HDAudBus!_NULL_IMPORT_DESCRIPTOR+1bc
fffff880`04a21290 94              xchg    eax,esp

FAILED_INSTRUCTION_ADDRESS: 
+1bc
00000001`0329246a ??              ???

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from 0000000000000010 to 000000010329246a

SYMBOL_ON_RAW_STACK:  1

STACK_ADDR_RAW_STACK_SYMBOL: fffff880037c7ff0

STACK_COMMAND:  dds FFFFF880037C7FF0-0x20 ; kb

STACK_TEXT:  
fffff880`037c7fd0  037c7fe0
fffff880`037c7fd4  fffff880
fffff880`037c7fd8  00010202
fffff880`037c7fdc  00000000
fffff880`037c7fe0  004f63f0
fffff880`037c7fe4  fffff8a0
fffff880`037c7fe8  04a21290
fffff880`037c7fec  fffff880
fffff880`037c7ff0  04a21084
fffff880`037c7ff4  fffff880
fffff880`037c7ff8  032b8812
fffff880`037c7ffc  fffff800
fffff880`037c8000  00000000
fffff880`037c8004  00000000
fffff880`037c8008  04a00000
fffff880`037c800c  fffff880
fffff880`037c8010  0339a128
fffff880`037c8014  fffff800
fffff880`037c8018  04a131a8
fffff880`037c801c  fffff880
fffff880`037c8020  03398000
fffff880`037c8024  fffff800
fffff880`037c8028  00010978
fffff880`037c802c  00000000
fffff880`037c8030  00000000
fffff880`037c8034  00000000
fffff880`037c8038  037c81b8
fffff880`037c803c  fffff880
fffff880`037c8040  800001d4
fffff880`037c8044  00003e8f
fffff880`037c8048  00000001
fffff880`037c804c  00000000


SYMBOL_NAME:  HDAudBus!_NULL_IMPORT_DESCRIPTOR+1bc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: HDAudBus

IMAGE_NAME:  HDAudBus.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7a65e

FAILURE_BUCKET_ID:  X64_0x7E_VRF_BAD_IP_HDAudBus!_NULL_IMPORT_DESCRIPTOR+1bc

BUCKET_ID:  X64_0x7E_VRF_BAD_IP_HDAudBus!_NULL_IMPORT_DESCRIPTOR+1bc

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

post #58 of 138
Thread Starter 
Quote:
Originally Posted by E-Peen View Post

The culprit in the newly attached dump is HDAudBus.sys. HDAudBus.sys is the Microsoft High Definition Bus Driver for your audio, since it's a Microsoft file, the likelihood of this being the cause is very slim, and we always assume that Microsoft's files are never a culprit / cause of the crash, but in fact what was crashed because of the original culprit, or just an incorrect probable cause due to Windows having no idea what the cause is because it's hardware, for example.
If you'd like to know a little bit more, the reason Microsoft is generally never blamed as a cause (which it really never is) is because Microsoft specific files are protected by the SFC (System File Checker). In some cases the probable Microsoft listed causes may point us to a cause, but in most cases, it does not.
If it actually does happen to be your audio sub system that is giving BSODs, you can fully uninstall your currently audio drivers for Win 7 / sound card, and then reinstall the latest versions provided by the vendor or manufacturer.
If the above does not help, I would recommend a clean install of Windows with brand new up to date drivers, etc. If you are still BSOD'ing on the fresh install, it's hardware, or a driver that you keep managing to install that is causing issues, but may be easier to pinpoint on a fresh install.
Your nVidia drivers are from 2010, I would recommend updating those, by the way. Do not let Windows update the drivers, disable that if you have to for the time being:
Quote:
Go to Start–>Search type in gpedit.msc
Click the file to open the Local Group Policy Editor and show Windows who is in control!!
You want to go here: Computer Configuration->Administrative Templates->System->Device Installation. Click on the subfolder Device Installation on the left and on the right side you will see the possible restrictions.
Right Click on Prevent Installation of Devices not described by other policy settings and edit this option, set it on ENABLED.
Reboot Windows and enjoy its inability to pollute your system with its standard driver, open gpedit.msc again and revert the change so you will be able to install your driver.
Dump for reference:
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Icarus\Downloads\040112-39468-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e64000 PsLoadedModuleList = 0xfffff800`030a9670
Debug session time: Sun Apr  1 09:58:12.811 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:11.388
Loading Kernel Symbols
...............................................................
.........................
Loading User Symbols
Loading unloaded module list
.
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, 10329246a, fffff880037c7d28, fffff880037c7580}
Probably caused by : HDAudBus.sys ( HDAudBus!_NULL_IMPORT_DESCRIPTOR+1bc )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: ffffffffc0000005, The exception code that was not handled
Arg2: 000000010329246a, The address that the exception occurred at
Arg3: fffff880037c7d28, Exception Record Address
Arg4: fffff880037c7580, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP: 
+1bc
00000001`0329246a ??              ???
EXCEPTION_RECORD:  fffff880037c7d28 -- (.exr 0xfffff880037c7d28)
ExceptionAddress: 000000010329246a
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000008
   Parameter[1]: 000000010329246a
Attempt to execute non-executable address 000000010329246a
CONTEXT:  fffff880037c7580 -- (.cxr 0xfffff880037c7580)
rax=fffff88004a21596 rbx=fffff8000339c228 rcx=000000000053bb3b
rdx=0000000000000100 rsi=0000000000000000 rdi=fffff88004a21594
rip=000000010329246a rsp=fffff880037c7f60 rbp=fffff80000000000
 r8=fffff80003398000  r9=00000000000000ec r10=0000000000000840
r11=00000000000001a3 r12=fffff88004a131a8 r13=fffff88004a00000
r14=fffff80002e64000 r15=fffff80003398000
iopl=0         nv up ei ng nz na po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010287
00000001`0329246a ??              ???
Resetting default scope
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
CURRENT_IRQL:  0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1:  0000000000000008
EXCEPTION_PARAMETER2:  000000010329246a
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80003113100
 000000010329246a 
FOLLOWUP_IP: 
HDAudBus!_NULL_IMPORT_DESCRIPTOR+1bc
fffff880`04a21290 94              xchg    eax,esp
FAILED_INSTRUCTION_ADDRESS: 
+1bc
00000001`0329246a ??              ???
BUGCHECK_STR:  0x7E
LAST_CONTROL_TRANSFER:  from 0000000000000010 to 000000010329246a
SYMBOL_ON_RAW_STACK:  1
STACK_ADDR_RAW_STACK_SYMBOL: fffff880037c7ff0
STACK_COMMAND:  dds FFFFF880037C7FF0-0x20 ; kb
STACK_TEXT:  
fffff880`037c7fd0  037c7fe0
fffff880`037c7fd4  fffff880
fffff880`037c7fd8  00010202
fffff880`037c7fdc  00000000
fffff880`037c7fe0  004f63f0
fffff880`037c7fe4  fffff8a0
fffff880`037c7fe8  04a21290
fffff880`037c7fec  fffff880
fffff880`037c7ff0  04a21084
fffff880`037c7ff4  fffff880
fffff880`037c7ff8  032b8812
fffff880`037c7ffc  fffff800
fffff880`037c8000  00000000
fffff880`037c8004  00000000
fffff880`037c8008  04a00000
fffff880`037c800c  fffff880
fffff880`037c8010  0339a128
fffff880`037c8014  fffff800
fffff880`037c8018  04a131a8
fffff880`037c801c  fffff880
fffff880`037c8020  03398000
fffff880`037c8024  fffff800
fffff880`037c8028  00010978
fffff880`037c802c  00000000
fffff880`037c8030  00000000
fffff880`037c8034  00000000
fffff880`037c8038  037c81b8
fffff880`037c803c  fffff880
fffff880`037c8040  800001d4
fffff880`037c8044  00003e8f
fffff880`037c8048  00000001
fffff880`037c804c  00000000
SYMBOL_NAME:  HDAudBus!_NULL_IMPORT_DESCRIPTOR+1bc
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: HDAudBus
IMAGE_NAME:  HDAudBus.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7a65e
FAILURE_BUCKET_ID:  X64_0x7E_VRF_BAD_IP_HDAudBus!_NULL_IMPORT_DESCRIPTOR+1bc
BUCKET_ID:  X64_0x7E_VRF_BAD_IP_HDAudBus!_NULL_IMPORT_DESCRIPTOR+1bc
Followup: MachineOwner
---------

was just checking and the video software installed nvidia driver for my audio as well frown.gif
post #59 of 138
Well, fix what it did and ensure that Windows doesn't go ahead and try to install the drivers for you this time.
post #60 of 138
Thread Starter 
ok did a clean windows install then installed the video drivers and it stick again at the windows logo again and thats the only thing I installed mad.gifmad.gifmad.gif
seem either my video card is going or gone bad or bad drivers ???
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Windows
Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Blue screen problem More Help Needed (SOLVED)