BSOD Problems


  1. Posts : 6
    Windows 7 Ultimate x64
       #1

    BSOD Problems


    I just started getting BSOD today. I haven't made any software or hardware changes.

    Im running Windows 7 Ultimate x64 OEM
    Hardware is about a year old.
    Last edited by Blaze420; 04 Dec 2010 at 02:01.
      My Computer


  2. Posts : 6
    Windows 7 Ultimate x64
    Thread Starter
       #2

    ran memtest86, didnt get any errors. disk check won't run it's giving message that windows can't check disk while it's in use.
      My Computer


  3. Posts : 6
    Windows 7 Ultimate x64
    Thread Starter
       #3

    BSOD Please Help, Dont view If you can't


    i did a system restore and still getting BS. it's giving 0x3b service exception message and a IRQ not less or equal BS

    can anyone please help me with this? i see people viewing this post but their not helping.
    Last edited by Blaze420; 04 Dec 2010 at 05:28.
      My Computer


  4. Posts : 507
    Windows 7 Ultimate x64 SP1
       #4

    Hi,
    Your dmp bugcheck = 0xA, 0x1E, 0x3B → most likely caused by drivers.

    Remove Alcohol or Daemon software because they use sptd.sys which is notorious for causing BSOD in windows 7.
    Uninstall sptd.sys with this tools --> DuplexSecure - Downloads
    Then for alternative software, you may use MagicIso.

    Perform system file checker:
    Right click Command Prompt → run as admin → sfc /scannow

    Also turn on your windows update and go to device manager.
    If there is any yellow exclamation, you must install the correct driver for its device.

    Update these drivers:
    Code:
    AsIO.sys     Mon Dec 17 01:11:49 2007Asus PCProbe Utility
    Lycosa.sys   Fri Jan 18 00:51:42 2008 → Razer Tarantula Keyboard Driver
    nvm62x64.sys Fri Oct 17 14:01:06 2008 →    nVidia Ethernet Networking 
    nvlddmkm.sys Thu May 14 13:48:07 2009 → nVdia video driver
    teamviewervpn.sys Thu Dec 13 01:22:09 2007 → TeamViewerVPN Network Adapter
    sptd.sys     Sun Oct 11 13:55:14 2009 → Uninstall it
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {0, 2, 0, fffff8000349a306}
    
    Probably caused by : win32k.sys ( win32k!HmgNextOwned+3f )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 0000000000000000, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, bitfield :
        bit 0 : value 0 = read operation, 1 = write operation
        bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff8000349a306, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800036b20e0
     0000000000000000 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nt!IopCompleteRequest+c73
    fffff800`0349a306 488b09          mov     rcx,qword ptr [rcx]
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  wermgr.exe
    
    IRP_ADDRESS:  ffffffffffffff88
    
    TRAP_FRAME:  fffff8800dbaf350 -- (.trap 0xfffff8800dbaf350)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff8800dbaf408 rbx=0000000000000000 rcx=0000000000000000
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8000349a306 rsp=fffff8800dbaf4e0 rbp=fffff8800dbaf630
     r8=fffffa800d4a2010  r9=fffff8800dbaf5e0 r10=0000000000000002
    r11=fffffa800bcebad0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz ac pe cy
    nt!IopCompleteRequest+0xc73:
    fffff800`0349a306 488b09          mov     rcx,qword ptr [rcx] ds:07ff:00000000`00000000=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80003479b69 to fffff8000347a600
    
    STACK_TEXT:  
    fffff880`0dbaf208 fffff800`03479b69 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff880`0dbaf210 fffff800`034787e0 : fffffa80`0d53a810 fffffa80`0d53a810 00000000`00000000 fffff8a0`0c09a858 : nt!KiBugCheckDispatch+0x69
    fffff880`0dbaf350 fffff800`0349a306 : fffff900`c2158f40 fffff800`035af2dd fffff900`c2158f40 00000000`00000000 : nt!KiPageFault+0x260
    fffff880`0dbaf4e0 fffff800`03456fcf : 00000000`00000000 fffff880`0dbafc20 00000000`00000000 fffff8a0`00228a13 : nt!IopCompleteRequest+0xc73
    fffff880`0dbaf5b0 fffff800`03457387 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x1d7
    fffff880`0dbaf630 fffff960`000ddd8b : fffffa80`0775dc90 00000000`00000030 00000000`00000001 fffff900`c2c5e320 : nt!KiApcInterrupt+0xd7
    fffff880`0dbaf7c0 fffff960`000dd395 : 00000000`000013ec 00000000`000013ec fffff880`0dbafc00 00000000`ffffffff : win32k!HmgNextOwned+0x3f
    fffff880`0dbaf7f0 fffff960`000d4a60 : 00000000`000013ec fffff880`0dbafc00 fffff900`c2c5e320 fffff900`00000000 : win32k!NtGdiCloseProcess+0x85
    fffff880`0dbaf850 fffff960`000d41a7 : fffffa80`0a936600 fffff880`0dbafc20 fffff880`0dba0000 fffffa80`0af79010 : win32k!GdiProcessCallout+0x200
    fffff880`0dbaf8d0 fffff800`03760881 : fffffa80`0a936660 00000000`00000000 00000000`00000000 fffffa80`07914b60 : win32k!W32pProcessCallout+0x6b
    fffff880`0dbaf900 fffff800`037394d1 : 00000000`00000000 fffffa80`07056401 fffffa80`78457300 00000000`00000000 : nt!PspExitThread+0x561
    fffff880`0dbaf9c0 fffff800`034570e3 : fffffa80`07ad2510 fffffa80`07ad26c8 fffff880`0dbafa10 fffff800`037966c7 : nt!PsExitSpecialApc+0x1d
    fffff880`0dbaf9f0 fffff800`03457520 : 00000000`00248cd0 fffff880`0dbafa70 fffff800`037395dc 00000000`00000001 : nt!KiDeliverApc+0x2eb
    fffff880`0dbafa70 fffff800`034798f7 : ffffffff`ffffffff fffff8a0`00000000 00000000`022df0c0 0000007f`00000030 : nt!KiInitiateUserApc+0x70
    fffff880`0dbafbb0 00000000`7765008a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
    00000000`022df168 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7765008a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    win32k!HmgNextOwned+3f
    fffff960`000ddd8b 740e            je      win32k!HmgNextOwned+0x4f (fffff960`000ddd9b)
    
    SYMBOL_STACK_INDEX:  6
    
    SYMBOL_NAME:  win32k!HmgNextOwned+3f
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: win32k
    
    IMAGE_NAME:  win32k.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4bdc4376
    
    FAILURE_BUCKET_ID:  X64_0xA_win32k!HmgNextOwned+3f
    
    BUCKET_ID:  X64_0xA_win32k!HmgNextOwned+3f
    
    Followup: MachineOwner
    ---------
      My Computer


  5. Posts : 6
    Windows 7 Ultimate x64
    Thread Starter
       #5

    i downloaded DuplexSecure - Downloads but when i go to install it a message come up saying that SPTDinst-v175-x64.exe is not a valid win32 app
      My Computer


  6. Posts : 507
    Windows 7 Ultimate x64 SP1
       #6

    Select uninstall not install.
      My Computer


  7. Posts : 6
    Windows 7 Ultimate x64
    Thread Starter
       #7

    could a bad video card be causing these problems? i am seeing that theres no activaty in my video cards control center, even when a game is running. going to try and update the driver and see if that helps.
      My Computer


  8. Posts : 6
    Windows 7 Ultimate x64
    Thread Starter
       #8

    just said the hell with it and reinstalled windows. I was getting to many BSOD. will post back if it still happens
      My Computer


 

  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 10:27.
Find Us