BSOD after fresh install

Page 8 of 9 FirstFirst ... 6789 LastLast

  1. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #71

    Suggested AMD Radeon™ HD 6950 System Requirements said:
    500 Watt or greater power supply with two 75W 6-pin PCI Express® power connectors recommended
    550 W would be pushing the envelope a little. Usually, you want 100-150 W more than what is recommended. Can you borrow a power supply from someone who has one rated around 600-750 W and see if it helps?

    DRAM can go up to 1.65 V with CPU/NB at 1.25 V (CPU/NB, not CPU/NB offset). Went through your thread and saw that Dave recommended 1.275 V for CPU/NB; are you still running with that voltage?
      My Computer


  2. Posts : 69
    Windows 7 Home Premium 64-bit (Installed: Apr 2012)
    Thread Starter
       #72

    have a 750w coming in a day or so to test.

    CPU/NB voltages are set to default. the lower

    thanks for the reply :)

    updated graphics card in system specs i'd listed incorrect one.
    mine has an 8 and a 6 pin power connection
      My Computer


  3. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #73

    Let us know how things go with the new PSU.

    As to the system requirements I gave, they were for the AMD Radeon™ HD 6950, which is why the power pin connections were different. They are still essentially the same card and require the same power supply specs.
      My Computer


  4. Posts : 69
    Windows 7 Home Premium 64-bit (Installed: Apr 2012)
    Thread Starter
       #74

    Ok, tried with 750w PSU still crashes same way.
    Tried with Radeon 3450. (EAH 3450) GPU is on QVL. still crashes....

    The crashes can be reproduced at will by stressing the computer by playing a game or a program i use prime which computer will do just fine for as long as i want.
    If I then close the program and leave it on desktop for instance the display will fail and produce a horizontally jagged screen mostly green or blue in colour then blue screen with either, NVQL less than equal, memory_management,bad_pool_caller or a USB related one.

    Will sometimes fail to reboot especially when i was nudging voltages and would reset the BIOS settings itself to be able boot. it hasn't done that recently though.

    Stumped.

    to recap what has been tried.

    Reinstalled OS

    RAM testing with different modules in different slots. and completely different modules too.

    MEMTEST ran no errors

    HD diag ran no errors

    Prime and furmark ran with stable low temps for hours.

    new CPU installed

    rolled back display drivers for 6950

    VMT ran on 6950 no errors

    Asus EAH 6950 swapped for QVL approved Asus EAH 3450

    550w PSU swapped for Corsair TX750w

    WLAN USB dongle swapped for wired ethernet LAN

    all USB devices removed new mouse and keyboard tried

    MOBO Bios updated to latest ver.

    antimalware ran (monthes ago now)

    tried upping voltages for DRAM and CPU/NB, CPU/NB offset. (after many resets all are
    now set to default/auto)

    not 100% sure if i installed all the correct drivers after installing OS it was the first time ive had to do it so i might need re-try?? any guidance there would be good...

    currently using 750w PSU and EAH3450 GPU

    except for swappin mobo, HDD or Disk drive or reinstalling OS again. im out of ideas

    any help appreciated

    i will post recent crashes
    Last edited by carlocgc; 07 Apr 2012 at 16:58.
      My Computer


  5. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #75

    Can you post screenshots of your Uninstall a program list? Start Menu -> Control Panel -> Uninstall a program. Take a screenshot, scroll down, take another screenshot, etc. until all programs are included. I want to see if there are any conflicts visible.
      My Computer


  6. Posts : 69
    Windows 7 Home Premium 64-bit (Installed: Apr 2012)
    Thread Starter
       #76
      My Computer


  7. Posts : 69
    Windows 7 Home Premium 64-bit (Installed: Apr 2012)
    Thread Starter
       #77

    Recent crashes (after new PSU and GPU)

    im going to run MEMTEST on all sticks and slots over the weekend to be certain about RAM even though it is on qvl...
    many other threads with same problem come down to RAM or Board

    advice still appreciated obv :)
    Last edited by carlocgc; 07 Apr 2012 at 14:31.
      My Computer


  8. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #78

    Code:
    1. Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\Kingston\BSODDmpFiles\carlocgc\Windows_NT6_BSOD_jcgriff2\040712-18267-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330 Machine Name: Kernel base = 0xfffff800`02c10000 PsLoadedModuleList = 0xfffff800`02e54650 Debug session time: Sat Apr 7 08:42:15.641 2012 (UTC - 6:00) System Uptime: 0 days 0:32:49.186 Loading Kernel Symbols ............................................................... ................................................................ .......................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff960001acb98, fffff880027b6fe0, 0} Probably caused by : win32k.sys ( win32k!DelQEntry+28 ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff960001acb98, Address of the instruction which caused the bugcheck Arg3: fffff880027b6fe0, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. 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!DelQEntry+28 fffff960`001acb98 48894208 mov qword ptr [rdx+8],rax CONTEXT: fffff880027b6fe0 -- (.cxr 0xfffff880027b6fe0) rax=0000000000000000 rbx=fffff900c1d46260 rcx=fffff900c0727ec8 rdx=0000000000000060 rsi=fffff900c1d46260 rdi=0000000000000000 rip=fffff960001acb98 rsp=fffff880027b79c0 rbp=fffff880027b7ca0 r8=0000000000000000 r9=0000000000000000 r10=0000000000000000 r11=fffff880027b7bd8 r12=fffff880027b7bd8 r13=fffff900c0727ec8 r14=0000000000000001 r15=0000000000000000 iopl=0 nv up ei pl nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206 win32k!DelQEntry+0x28: fffff960`001acb98 48894208 mov qword ptr [rdx+8],rax ds:002b:00000000`00000068=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: RtWLan.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff960001acb98 STACK_TEXT: fffff880`027b79c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!DelQEntry+0x28 FOLLOWUP_IP: win32k!DelQEntry+28 fffff960`001acb98 48894208 mov qword ptr [rdx+8],rax SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: win32k!DelQEntry+28 FOLLOWUP_NAME: MachineOwner MODULE_NAME: win32k IMAGE_NAME: win32k.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4f2b63bd STACK_COMMAND: .cxr 0xfffff880027b6fe0 ; kb FAILURE_BUCKET_ID: X64_0x3B_win32k!DelQEntry+28 BUCKET_ID: X64_0x3B_win32k!DelQEntry+28 Followup: MachineOwner ---------
    2. Loading Dump File [D:\Kingston\BSODDmpFiles\carlocgc\Windows_NT6_BSOD_jcgriff2\040712-18189-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330 Machine Name: Kernel base = 0xfffff800`02c4c000 PsLoadedModuleList = 0xfffff800`02e90650 Debug session time: Sat Apr 7 05:26:40.541 2012 (UTC - 6:00) System Uptime: 0 days 0:17:18.696 Loading Kernel Symbols ............................................................... ................................................................ ............................. Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1E, {ffffffffc0000005, fffff80002ccecfe, 0, ffffffffffffffff} Probably caused by : ntkrnlmp.exe ( nt!ExAcquireResourceSharedLite+4e ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KMODE_EXCEPTION_NOT_HANDLED (1e) 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: ffffffffc0000005, The exception code that was not handled Arg2: fffff80002ccecfe, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: ffffffffffffffff, Parameter 1 of the exception Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: nt!ExAcquireResourceSharedLite+4e fffff800`02ccecfe f0480fba696000 lock bts qword ptr [rcx+60h],0 EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: ffffffffffffffff READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002efa100 ffffffffffffffff ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. BUGCHECK_STR: 0x1E_c0000005 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: WerFault.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002d13a08 to fffff80002cc8d40 STACK_TEXT: fffff880`0a58ba98 fffff800`02d13a08 : 00000000`0000001e ffffffff`c0000005 fffff800`02ccecfe 00000000`00000000 : nt!KeBugCheckEx fffff880`0a58baa0 fffff800`02cc83c2 : fffff880`0a58c278 e56b6f54`035d041d fffff880`0a58c320 fffff880`0a58c600 : nt! ?? ::FNODOBFM::`string'+0x48d2d fffff880`0a58c140 fffff800`02cc6cca : 80000001`00000007 fffff800`02fca21c 00000000`00000000 fffff800`02ce74dd : nt!KiExceptionDispatch+0xc2 fffff880`0a58c320 fffff800`02ccecfe : 00000000`00000202 fffff880`00961000 00000000`00000000 fffffa80`06b8bb60 : nt!KiGeneralProtectionFault+0x10a fffff880`0a58c4b0 fffff800`02fc196a : 00000000`00000011 fffff8a0`0a5aea00 00000000`00000001 fffffa80`074413f8 : nt!ExAcquireResourceSharedLite+0x4e fffff880`0a58c520 fffff800`02fc20d6 : fffffa80`076c7b60 fffffa80`076c7b60 fffff8a0`0a5aea00 fffff800`0000005a : nt!SeQueryInformationToken+0x3a fffff880`0a58c5b0 fffff800`02fc3796 : 00000000`00000000 fffffa80`071a1010 00000000`00000002 fffffa80`06c10660 : nt!ObpLookupObjectName+0xe6 fffff880`0a58c6a0 fffff800`02fc509c : fffffa80`076c7b60 00000000`00000000 00000000`00000000 fffff800`02e71d08 : nt!ObOpenObjectByName+0x306 fffff880`0a58c770 fffff800`02fb08c4 : fffff880`0a58c8f0 00000000`80100000 fffff880`0a58c930 fffff880`0a58c8f8 : nt!IopCreateFile+0x2bc fffff880`0a58c810 fffff800`031226f1 : fffff880`000004a2 00000000`00000000 fffff800`02fca200 fffff800`02fca1c0 : nt!NtOpenFile+0x58 fffff880`0a58c8a0 fffff800`03124409 : 00000000`00000000 00000000`00000001 00000000`00000001 00000000`00000000 : nt!PfSnGetPrefetchInstructions+0x101 fffff880`0a58c980 fffff800`030234ff : 00000000`00000000 00000000`e69f695a fffffa80`0c440b20 00000000`00000000 : nt!PfSnBeginAppLaunch+0x2f9 fffff880`0a58ca50 fffff800`02fb5ccc : fffffa80`076c7b60 fffffa80`0c440b20 00000000`14050800 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x50eb0 fffff880`0a58ca80 fffff800`02cb9af5 : fffff800`02e3de80 00000000`00000000 fffff800`02fb5b84 fffffa80`076c7b60 : nt!PspUserThreadStartup+0x148 fffff880`0a58cae0 fffff800`02cb9a77 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartUserThread+0x16 fffff880`0a58cc20 00000000`773ec500 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartUserThreadReturn 00000000`0024faa8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x773ec500 STACK_COMMAND: kb FOLLOWUP_IP: nt!ExAcquireResourceSharedLite+4e fffff800`02ccecfe f0480fba696000 lock bts qword ptr [rcx+60h],0 SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: nt!ExAcquireResourceSharedLite+4e FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4ec79dd2 FAILURE_BUCKET_ID: X64_0x1E_c0000005_nt!ExAcquireResourceSharedLite+4e BUCKET_ID: X64_0x1E_c0000005_nt!ExAcquireResourceSharedLite+4e Followup: MachineOwner ---------
    1. Blames a Windows network process...
    2. Caused by your USB wireless network device. Explains 1.
    3. Rather inconclusive. Possible causes are Memory problems... Viruses... Corrupted hard disk file system... Corrupted System Files... Lack of Windows updates... Drivers...

    Have you been using the USB wireless network adapter in all crashes, or is this something new? USB wireless network adapters are inherently unstable. USB does not provide the proper power support for wireless network adapters, which can lead to crashes with these devices installed. We usually recommend replacing such devices with a PCI card wireless network adapter instead.


    In regards to your programs that are installed. It appears you are currently using the ATI graphics card. If so, you should remove NVIDIA PhysX because it can cause conflicts with the ATI driver. I would also suggest a full uninstall of the ATI software and drivers by uninstalling the ATI Catalyst Install Manager and then install the latest drivers and software for that graphics card from the manufacturer's site: ASUS - Graphics Cards- ASUS EAH6950 DCII/2DI4S/2GD5.

    Do the re-install of the ATI drivers after removing NVIDIA PhysX.
      My Computer


  9. Posts : 69
    Windows 7 Home Premium 64-bit (Installed: Apr 2012)
    Thread Starter
       #79

    progress at last! managed to run prime twice and battlefield 3 without crashing

    also not getting flickering of the display on startup (which looked alot like the screen i get on the crashes)

    my internet icon in the system tray has changed back to normal

    i used the OC utility in the BIOS menu which changed most of the frequencies.

    only been running comp for a few hours but seems stable just getting a few graphical glitches in games. hopefully updating to latest vga driver will fix it.

    will post changes made
      My Computer


  10. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #80

    That is great news after eight pages of help!

    Let us know how things go after updating the graphics drivers.
      My Computer


 
Page 8 of 9 FirstFirst ... 6789 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 05:27.
Find Us