TechSpot

BSOD Windows 7 64-bit

By Gpanoiah
Mar 26, 2011
Post New Reply
  1. Hello,
    i recently installed 64-bit Windows 7 Operating system,
    And now I'm getting BSOD about 3-4 times a day,
    Importantly, 32-bit system it does not happen to me but only in 64 bit


    I really need your help to figure out where the problem and what is it due
    Thank you in advance!
    +
    i have uploaded zip file with my minidump files .



    ==================================================
    Dump File : 032611-19546-01.dmp
    Crash Time : 26.03.2011 9:38:05
    Bug Check String :
    Bug Check Code : 0x00000109
    Parameter 1 : a3a039d8`98f047ca
    Parameter 2 : b3b7465e`eb6d1730
    Parameter 3 : fffff800`031b41e0
    Parameter 4 : 00000000`00000001
    Caused By Driver : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+80640
    File Description : NT Kernel & System
    Product Name : Microsoft® Windows® Operating System
    Company : Microsoft Corporation
    File Version : 6.1.7601.17514 (win7sp1_rtm.101119-1850)
    Processor : x64
    Computer Name :
    Full Path : C:\Windows\Minidump\032611-19546-01.dmp
    Processors Count : 8
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 286*841
    ==================================================
    ADDITIONAL_DEBUG_TEXT:
    Use '!findthebuild' command to search for the target build information.
    If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

    MODULE_NAME: nt

    FAULTING_MODULE: fffff80003019000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7951a

    BUGCHECK_STR: 0x109

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    CURRENT_IRQL: 0

    LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80003099640

    STACK_TEXT:
    fffff880`033695d8 00000000`00000000 : 00000000`00000109 a3a039d8`98f047ca b3b7465e`eb6d1730 fffff800`031b41e0 : nt+0x80640


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt+80640
    fffff800`03099640 48894c2408 mov qword ptr [rsp+8],rcx

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: nt+80640

    FOLLOWUP_NAME: MachineOwner

    IMAGE_NAME: ntoskrnl.exe

    BUCKET_ID: WRONG_SYMBOLS

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

    Attached Files:

  2. Route44

    Route44 TechSpot Ambassador Posts: 12,155   +34

    Five out six (the sixth is inconclusive) all cite the same issue as the cause of your issue: Memory Corruption. Yet you report this only happens under Windows 7 64-bit and not in a 32-bit OS.

    Before we have you run Memtest, under Windows 7 64-bit find the voltage specs of your RAM and compare it to the voltage setting in your BIOS. Do they match?
     
  3. Gpanoiah

    Gpanoiah TS Rookie Topic Starter

    Hi Route44 and thank you for your reply,

    In fact, to be precise i have got BSOD in 32-bit too but rarely and not so often
    as at the 64-bit windows .

    so basicly i understand , that the problem is with the RAM , am i right !?

    +
    How can i know what is the voltage specs of my RAM?

    Thanks in advance
     
  4. Route44

    Route44 TechSpot Ambassador Posts: 12,155   +34

    Find the make and model # of your RAM and you can find the RAM specs on the manufactures website. However, since you have received BSODs with a 32 OS let's go ahead and run Memtest.

    1. Go to www.memtest.org and download the latest ISO version which is 4.20. It is free and perfectly safe.

    2. Burn ISO to a CD.

    3. Place CD in your drive and reboot with CD in drive. (You might have to place your drive as first bootable in your BIOS) The test will take over.


    There is a Tutorial: How to use Memtest in our Guides and Tutorials forum; follow the instructions. There is a newer version than what is listed; use the newer. If you need to see what the Memtest screen looks like go to reply #21. The third screen is the Memtest screen.

    Step1 - Let it run for a LONG time. The rule is a minimum of 7 Passes; the more Passes after 7 so much the better. The only exception is if you start getting errors before 7 Passes then you can skip to Step 2.

    There are 8 individual tests per Pass. Many people will start this test before going to bed and check it the next day.

    If you have errors you have corrupted memory and it needs to be replaced.

    Step 2 – Because of errors you need to run this test per stick of RAM. Take out one and run the test. Then take that one out and put the other in and run the test. If you start getting errors before 7 Passes you know that stick is corrupted and you don’t need to run the test any further on that stick.


    * Get back to us with the results.
     
  5. Gpanoiah

    Gpanoiah TS Rookie Topic Starter

    Thank you for your reply Route44,

    i've already done this RAM test with this program ( 10 passes) +
    Windows ram test utility couple times, but no errors was found ...

    * edit :

    i've got 4 memory ram sticks,
    each one is a 2 GB,
    3 of them is 1600 Mhz frequency
    and 1 of them is 800 MHZ frequency

    Is that effect some how ?
     
  6. Route44

    Route44 TechSpot Ambassador Posts: 12,155   +34

    yes it will. Remove the 800 MHz stick and tell us if you gain stability. If not, then also remove one of the 2 gig sticks and tell us your results.
     


Add New Comment

TechSpot Members
Login or sign up for free,
it takes about 30 seconds.
You may also...


Get complete access to the TechSpot community. Join thousands of technology enthusiasts that contribute and share knowledge in our forum. Get a private inbox, upload your own photo gallery and more.