1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

BSoD

Discussion in 'Windows 7' started by craigcoll10, 2014/07/12.

  1. 2014/07/12
    craigcoll10

    craigcoll10 Inactive Thread Starter

    Joined:
    2014/07/12
    Messages:
    26
    Likes Received:
    0
    Malware logs deleted by Moderator as irrelevant at this time.
     
  2. 2014/07/13
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,889
    Likes Received:
    386
    Welcome to WindowsBBS :)

    In order to help you we need a lot more information - it is wrong to assume that a BSOD is necessarily malware related - it is more likely to be software or hardware related.

    Please post the Error Code and detail of when it occurred, i.e., what was the computer doing at the time and we will take it from there and please enter your System Details. It helps us in answering your questions!

    I have moved your thread to the Windows 7 forum and deleted your logs which are irrelevant at this time.
     

  3. to hide this advert.

  4. 2014/07/13
    retiredlearner

    retiredlearner SuperGeek WindowsBBS Team Member

    Joined:
    2004/06/25
    Messages:
    7,145
    Likes Received:
    498
    Hi craigcoll10, Welcome to WindowsBBS. :) As Pete has said we need more info to enable us to help you. Did you get a message on the screen when the BSOD occurred? If you can give us the error code that showed - that will be a start. Neil.
     
  5. 2014/07/14
    craigcoll10

    craigcoll10 Inactive Thread Starter

    Joined:
    2014/07/12
    Messages:
    26
    Likes Received:
    0
    thank you for the reply :)
    i have had the BSoD many times and for many different reasons. I cant think of a particular even or application that causes it. There is no drivers that are needing to be updated according to device manager.
    PC Make & Model
    self assembled
    Operating System
    Windows 7 Home Premium 64-bit SP1
    CPU
    Intel Core i5 3470 @ 3.20GHz 39 °C
    Ivy Bridge 22nm Technology
    RAM
    16.0GB Dual-Channel DDR3 @ 802MHz (9-9-9-24)
    Motherboard
    ASUSTeK COMPUTER INC. P8Z77-V LX2 (LGA1155)
    Graphics
    BenQ GL955 (1366x768@60Hz)
    2048MB ATI AMD Radeon HD 6670 (XFX Pine Group)
    Storage
    1863GB Seagate ST2000DM001-1CH164 (SATA)
    Optical Drives
    TSSTcorp CDDVDW SH-224BB
    Audio
    AMD High Definition Audio Device
    Floppy Drive
    No
    Internet Connectivity
    broadband
    Connection to Internet through...
    router
    Monitor #1
    Benq GL950-TA
     
  6. 2014/07/14
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,889
    Likes Received:
    386
    The next time you get a BSOD note down the Error Code on the blue screen and also see if the file causing the issue is also noted on the blue screen and post the details here.

    Then run the dump file through our Dump Data Collection Tool and post the log produced here. That log should give detail of what caused the BSOD.
     
  7. 2014/07/14
    craigcoll10

    craigcoll10 Inactive Thread Starter

    Joined:
    2014/07/12
    Messages:
    26
    Likes Received:
    0
    thanks again for the help :)
    I recently found out about a program called who crashed that identifies the cause of crashes, would posting the crash analysis from this help ?
    thanks :)
     
  8. 2014/07/14
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,889
    Likes Received:
    386
    It would be a start :)
     
  9. 2014/07/14
    craigcoll10

    craigcoll10 Inactive Thread Starter

    Joined:
    2014/07/12
    Messages:
    26
    Likes Received:
    0
    Crash Dump Analysis
    --------------------------------------------------------------------------------

    Crash dump directory: C:\Windows\Minidump

    Crash dumps are enabled on your computer.

    On Sun 13/07/2014 21:25:40 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\071314-29764-01.dmp
    This was probably caused by the following module: atikmdag.sys (atikmdag+0xD905C4)
    Bugcheck code: 0xFC (0xFFFFF880104565C4, 0xEC500003FE7E3921, 0xFFFFF8800B55B160, 0x2)
    Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
    file path: C:\Windows\system32\drivers\atikmdag.sys
    product: ATI Radeon Family
    company: Advanced Micro Devices, Inc.
    description: ATI Radeon Kernel Mode Driver
    Bug check description: This indicates that an attempt was made to execute non-executable memory.
    This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. There is a possibility this problem was caused by a virus or other malware.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
    Google query: Advanced Micro Devices, Inc. ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY



    On Sun 13/07/2014 21:25:40 GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: atikmdag.sys (atikmdag+0xD905C4)
    Bugcheck code: 0xFC (0xFFFFF880104565C4, 0xEC500003FE7E3921, 0xFFFFF8800B55B160, 0x2)
    Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
    file path: C:\Windows\system32\drivers\atikmdag.sys
    product: ATI Radeon Family
    company: Advanced Micro Devices, Inc.
    description: ATI Radeon Kernel Mode Driver
    Bug check description: This indicates that an attempt was made to execute non-executable memory.
    This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. There is a possibility this problem was caused by a virus or other malware.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
    Google query: Advanced Micro Devices, Inc. ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY



    On Sun 13/07/2014 02:38:13 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\071314-23836-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000372C408, 0xFFFFF88008A4CA60, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Sun 13/07/2014 02:05:03 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\071314-46207-01.dmp
    This was probably caused by the following module: ntfs.sys (Ntfs+0x4688)
    Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800AA105E8, 0xFFFFF8800AA0FE40, 0xFFFFF8800190908F)
    Error: NTFS_FILE_SYSTEM
    file path: C:\Windows\system32\drivers\ntfs.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT File System Driver
    Bug check description: This indicates a problem occurred in the NTFS file system.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



    On Fri 11/07/2014 12:52:20 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\071114-45458-01.dmp
    This was probably caused by the following module: bcmwlhigh664.sys (0xFFFFF8800AEAD007)
    Bugcheck code: 0x50 (0xFFFFFFFF8B482846, 0x0, 0xFFFFF8800AEAD007, 0x5)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    file path: C:\Windows\system32\drivers\bcmwlhigh664.sys
    product: Broadcom 802.11 Network Adapter wireless driver
    company: Broadcom Corporation
    description: Broadcom 802.11 Network Adapter wireless driver
    Bug check description: This indicates that invalid system memory has been referenced.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: bcmwlhigh664.sys (Broadcom 802.11 Network Adapter wireless driver, Broadcom Corporation).
    Google query: Broadcom Corporation PAGE_FAULT_IN_NONPAGED_AREA



    On Sun 06/07/2014 17:02:46 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\070614-42323-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75B90)
    Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
    Error: KMODE_EXCEPTION_NOT_HANDLED
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Wed 02/07/2014 17:18:27 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\070214-42151-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
    Bugcheck code: 0x7F (0x8, 0x80050033, 0x406F8, 0xFFFFF80003843FF2)
    Error: UNEXPECTED_KERNEL_MODE_TRAP
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Tue 01/07/2014 21:47:02 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\070114-21949-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800034BAAC5, 0xFFFFF8800B5F3460, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Mon 23/06/2014 08:34:33 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\062314-39171-01.dmp
    This was probably caused by the following module: dxgmms1.sys (0xFFFFF8800543B085)
    Bugcheck code: 0x50 (0xFFFFFFFF8B484024, 0x0, 0xFFFFF8800543B085, 0x5)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    file path: C:\Windows\system32\drivers\dxgmms1.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: DirectX Graphics MMS
    Bug check description: This indicates that invalid system memory has been referenced.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



    On Fri 06/06/2014 23:37:09 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\060714-24960-01.dmp
    This was probably caused by the following module: avgtdia.sys (avgtdia+0x88A1)
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88000C7E8A1, 0xFFFFF8800A4C19A0, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: avgtdia.sys .
    Google query: avgtdia.sys SYSTEM_SERVICE_EXCEPTION




    --------------------------------------------------------------------------------
    Conclusion
    --------------------------------------------------------------------------------

    26 crash dumps have been found and analyzed. Only 10 are included in this report. 5 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

    bhdrvx64.sys (BASH Driver, Symantec Corporation)
    bcmwlhigh664.sys (Broadcom 802.11 Network Adapter wireless driver, Broadcom Corporation)
    atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.)
    avgtdia.sys
    avgmfx64.sys

    If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


    Read the topic general suggestions for troubleshooting system crashes for more information.

    Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
     
  10. 2014/07/14
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,889
    Likes Received:
    386
    A lot going on there ....

    First off I suggest you check out the memory .....

    Start > type Memory into the Search Box and in the window which appears under Programs (1) you will see Memory Diagnostics - click on it and restart the computer as prompted. Post the results here.

    The other issues need to be looked into one at a time .....

    The first 2 analyses point to your graphics driver ...
    . Go to .....

    AMD Driver Autodetect

    Report back.

    Download and run the AutoDetect Tool and update your graphics driver.
     
  11. 2014/07/14
    craigcoll10

    craigcoll10 Inactive Thread Starter

    Joined:
    2014/07/12
    Messages:
    26
    Likes Received:
    0
    Thank you for your help :)
    I have succesfully run the driver auto detect and downloaded the recomended driver, i am unable to run the memory diagnostics untill later as i dont have as much time as it recomends, i can do this in a few hours though.
    thanks again :)
     
  12. 2014/07/14
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,889
    Likes Received:
    386
    No hurry!
     
  13. 2014/07/14
    craigcoll10

    craigcoll10 Inactive Thread Starter

    Joined:
    2014/07/12
    Messages:
    26
    Likes Received:
    0
    I am starting the memory diagnostic scan just now, i have been told it may take several hours. I will post results as soon as it finishes. Thank you for your time :)
     
  14. 2014/07/15
    craigcoll10

    craigcoll10 Inactive Thread Starter

    Joined:
    2014/07/12
    Messages:
    26
    Likes Received:
    0
    Sorry about the long reply, i ran the memory diagnostic and after completion it said it would display the results when i logged in again. However when i logged in the results did not display, i thought this was just a bug so i ran the memory diagnostic again and no results showed after logging in again. I did see during the scan that there was no errors found throughout the scan but didn't get any conformation as the results didn't appear.
    thank you for your time and support :)
     
  15. 2014/07/15
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,889
    Likes Received:
    386
    See below for the location of the Memory Diagnostic report ....
    I think it would be useful to have a little background about these BSOD's - I see that your system is a self build. Have you has BSOD's from day 1?

    When you assembled the unit did you install the motherboard chipset drivers?
     
  16. 2014/07/15
    craigcoll10

    craigcoll10 Inactive Thread Starter

    Joined:
    2014/07/12
    Messages:
    26
    Likes Received:
    0
    Thank you for the reply :)
    i checked the memory diagnostic results and there was no errors found, "The Windows Memory Diagnostic tested the computer's memory and detected no errors ". The BSoD has been happening for a long time but started a few months the computer was built. The computer wasnt actually built by me, i got it custom built from a website that had already loaded windows and some basic programs on the computer.
     
  17. 2014/07/15
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,889
    Likes Received:
    386
    OK - we'll assume that the chipset drivers, etc. were loaded.

    2 other BSODS were the result of driver issues ....
    This is a system file which is part of AVG. I suggest you download Avast 2014 and save it to your hard drive. Then uninstall AVG - if you have issues here download and run the AVG Removal Tool appropriate to your version. Install Avast and update it. You can always uninstall Avast at a later date and re-install AVG, although Avast is purported to be better.

    The other driver BSOD is caused by ....
    This is the driver for a Broadcom 802.11 Network Adapter. Looking at the Asus web site your motherboard has a Realtec Network adaptor. Have a look in Device Manager and see what is listed there for the network adaptor.
     
  18. 2014/07/15
    craigcoll10

    craigcoll10 Inactive Thread Starter

    Joined:
    2014/07/12
    Messages:
    26
    Likes Received:
    0
    I have run the avg cleaner and avg should now be fully off my computer, i also downloaded avast and that seems to be running well. As for the network adapter, that is a wireless network adapter from netgear that i use to connect to my router wireless.
    Thank you for your time :)
     
  19. 2014/07/16
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,889
    Likes Received:
    386
    You will have 2 Network adaptors if you are using a wireless connection - please let me know what they are as shown in Device Manager.

    My desktop is hard wired to the router, but my laptop connects via wireless - see snip from Device Manager below.

    Have you had any further BSOD's since making the changes suggested above?
     

    Attached Files:

  20. 2014/07/16
    craigcoll10

    craigcoll10 Inactive Thread Starter

    Joined:
    2014/07/12
    Messages:
    26
    Likes Received:
    0
    I had my first BSOD since making the changes this morning. I also checked the network adapters and i have the "Realtek PCIe GBE Family Controller" and "NETGEAR WNDA3100v2 N600 Wireless Dual Band USB Adapter ".
    Thank you for your time and help :)

    On Wed 16/07/2014 12:36:33 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\071614-50403-01.dmp
    This was probably caused by the following module: win32k.sys (win32k+0x2A8478)
    Bugcheck code: 0xBE (0xFFFFF960002D8478, 0xABA00003B30E3021, 0xFFFFF8800AA4F920, 0xB)
    Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
    file path: C:\Windows\system32\win32k.sys
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: Multi-User Win32 Driver
    Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
     
  21. 2014/07/16
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,889
    Likes Received:
    386
    Looking at the Windows core BSOD'S that you posted - for your information and for me to see them altogether ....

    SYSTEM_SERVICE_EXCEPTION - linked to graphics drivers which you have updated.

    NTFS_FILE_SYSTEM - possible cause is disk corruption.

    KMODE_EXCEPTION_NOT_HANDLED - generic - identification of cause well beyond me :)

    UNEXPECTED_KERNEL_MODE_TRAP - typically faulty or mismatched hardware (especially memory) or installed hardware failure. Although Memory Diagnostics indicated no problems here it should be noted that ...
    Not suggesting that you do that right now.

    PAGE_FAULT_IN_NONPAGED_AREA - usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM). Antivirus software can also trigger this error, as can a corrupted NTFS volume.

    You have replaced AVG with Avast so hopefully that rules out one possibility, leaving the question of RAM once more.

    ATTEMPTED_WRITE_TO_READONLY_MEMORY - the BSOD you posted in your last post - most likely a driver error

    I have ascertained that the Broadcom driver which caused one of the BSOD's is part of the driver for your NETGEAR WNDA3100v2 N600 Wireless Dual Band USB Adapter.

    I think again that it would be worth updating that driver .....

    Netgear WNDA3100v2 driver

    I also suggest that you check the integrity of the hard drive with CHKDSK ....

    How to use CHKDSK (Check Disk)

    Keep on posting details of any further BSOD's, if any :)
     

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.