Newish computer BSOD and restart problems.


  1. Posts : 6
    Windows 7 home premium x64
       #1

    Newish computer BSOD and restart problems.


    Ok so i built a brand new computer about 5 months ago, since ive gotten it it has really not impressed me I have been getting constant BSOD and just recently restarting for no reason.

    I have an AMD phenom x6 1055t processor
    ATI HIS HD5850 gpu
    asus m4a89 series mobo
    700W power supply (four fans running on medium speed)
    WD 1tb HDD
    patriot 60GB SSD
    OCZ obsidian 1600MHZ ram (8 gigs)
    At first i was BSOD alot on start up but soon found out it was two bad sticks of ram, I replace those and all was good for a while but most of the time when iam playing a game or just browsing the internet I will BSOD with a few different errors

    1: BAD_POOL_CALLER
    2: BAD_POOL_HEADER
    3: SYSTEM_SERVICE_EXCEPTION
    4:VIDEO SCHEDULER HAS ENCOUNTERED A FATAL ERROR

    It happens when i play Aion, WoW,Cod pretty much any game it seems to happen when i click on something and or close a program
    I never run over 50 degrees C for my CPU and i have constantly kept updating my video drivers, along with ALL my device drivers I am not sure if motherboard needs drivers but one thing i did notice was when i boot in safe mode it says loading something or other and in the lines of text it says windows32\ would someone please help me out or suggest some free to use trouble shooting programs!!!
    thanks.
      My Computer


  2. Posts : 6
    Windows 7 home premium x64
    Thread Starter
       #2

    I found ALL of the BSOD errors in C:\Windows\Minidump there is about 26 of them, i open it in wordpad but i do not know how to find the error or even how to read it
      My Computer


  3. Posts : 9,606
    Win7 Enterprise, Win7 x86 (Ult 7600), Win7 x64 Ult 7600, TechNet RTM on AMD x64 (2.8Ghz)
       #3

    Welcome Gaupo

    If you wish to have others assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder. The procedure:
    * Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
    * Zip up the copy.
    * Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
    * Briefly describe the problem history and circumstances in the same post. Somebody will attend to your query as soon as possible.


    https://www.sevenforums.com/crashes-d...tml#post836073
    Last edited by DocBrown; 25 Jan 2011 at 08:50. Reason: added Link
      My Computer


  4. Posts : 6
    Windows 7 home premium x64
    Thread Starter
       #4

    ok here are the last 5 (probably from today )
      My Computer


  5. Posts : 6
    Windows 7 home premium x64
    Thread Starter
       #5

    was also wondering what a good tempature is for a GPU and how fast i should run the fan
      My Computer


  6. Posts : 6
    Windows 7 home premium x64
    Thread Starter
       #6

    open my world of warcraft up (four clients, 3 on lowest settings capped at 15 fps, and one with 60 fps cap and high settings) no more than three minutes and i BSOD with this
      My Computer


  7. Posts : 13,354
    Windows 7 Professional x64
       #7

    Hello, and apologies for the delay. Your thread got missed somehow!

    First, for the GPU question. That depends on the GPU, honestly. nVidia chips can safely operate at temperatures up to 105C, but if my ATI chip got about maybe 90C, I would be concerned.

    Most likely, this is being caused by hardware. Have you run Furmark?

    Video Card - Stress Test with Furmark

    Also, run Prime95; all 3 tests would be good (Blend, Small FFTs, Large FFTs).

    https://www.sevenforums.com/tutorials...t-prime95.html

    ...Summary of the dumps:
    Code:
    
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sun Jan  9 11:31:51.203 2011 (UTC - 5:00)
    System Uptime: 0 days 0:17:54.201
    Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+40ec0 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID:  X64_0x50_nt!_??_::FNODOBFM::_string_+40ec0
    SystemProductName = System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sun Jan  9 01:17:20.969 2011 (UTC - 5:00)
    System Uptime: 0 days 15:56:41.280
    Probably caused by : ntkrnlmp.exe ( nt!KiInsertQueueApc+144 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xA
    PROCESS_NAME:  csrss.exe
    FAILURE_BUCKET_ID:  X64_0xA_nt!KiInsertQueueApc+144
    SystemProductName = System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Fri Jan  7 07:41:21.533 2011 (UTC - 5:00)
    System Uptime: 0 days 1:36:43.828
    Probably caused by : audiodg.exe
    BUGCHECK_STR:  0xc2_7_KSsh
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  audiodg.exe
    FAILURE_BUCKET_ID:  X64_0xc2_7_KSsh_IMAGE_audiodg.exe
    SystemProductName = System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Sun Jan  2 05:13:30.476 2011 (UTC - 5:00)
    System Uptime: 1 days 8:52:58.412
    Probably caused by : memory_corruption ( nt!MmCheckCachedPageStates+41f )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  plugin-contain
    FAILURE_BUCKET_ID:  X64_0x3B_nt!MmCheckCachedPageStates+41f
    SystemProductName = System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Tue Jan  1 23:56:46.258 2002 (UTC - 5:00)
    System Uptime: 0 days 1:32:19.569
    *** WARNING: Unable to verify timestamp for dxgmms1.sys
    *** ERROR: Module load completed but symbols could not be loaded for dxgmms1.sys
    Probably caused by : dxgmms1.sys ( dxgmms1+25232 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  System
    BUGCHECK_STR:  0x7E
    FAILURE_BUCKET_ID:  X64_0x7E_dxgmms1+25232
    SystemProductName = System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Debug session time: Tue Jan  1 20:50:33.588 2002 (UTC - 5:00)
    System Uptime: 0 days 1:33:50.899
    Probably caused by : memory_corruption ( nt!MiGetProtoPteAddressExtended+17 )
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  Wow.exe
    FAILURE_BUCKET_ID:  X64_0x3B_nt!MiGetProtoPteAddressExtended+17
    SystemProductName = System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      
    
      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 22:25.
Find Us