Win 7 BSOD



Hello All

Just built a new sytem with the following specs:

CPU Intel I7 3.5Ghz
Motherboard ASUS Maximus V exrtreme
GPU GTX 670.....two
Sound Creative fatal1ty
RAM Corsair 6GB
Drive SSD ...two
PSU Antec 1200
OS Win 7 64bit

Did a new install....updated win 7, updated and a clean install of GPU drivers, updated all other drivers.

Only software loaded as yet is MSoffice 2010....updated and Norton.

No overclocking as yet and the system randomly either freezes or I get a BSOD. Can anyone help out?

14 answers Last reply
More about bsod
  1. BSOD details?
    Meanwhile try clean startup to see if you can isolate the prob
  2. How do I upload the dump files?
  3. Just the BSOD a good start. If it's restarting too fast to read :-
    Right Click on “My Computer” and go to “Properties”. Then go to the “Advanced” tab and under the headline “Startup and Recovery”, press the “Settings” button. Untick the “Automatically Restart” box and press Ok.
  4. How do I upload the zipped dump files
  5. Here is one of the dump file analysis

    Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
    Machine Name:
    Kernel base = 0xfffff800`0304c000 PsLoadedModuleList = 0xfffff800`03290670
    Debug session time: Sun Nov 11 15:41:59.365 2012 (UTC - 5:00)
    System Uptime: 0 days 0:08:16.334
    * *
    * Bugcheck Analysis *
    * *

    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.
    Some common problems are exception code 0x80000003. This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG. This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG. This will let us see why this breakpoint is
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff800030ce1e6, The address that the exception occurred at
    Arg3: fffff8800c1a5668, Exception Record Address
    Arg4: fffff8800c1a4ec0, Context Record Address

    Debugging Details:

    TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

    fffff800`030ce1e6 4983be1801000000 cmp qword ptr [r14+118h],0

    EXCEPTION_RECORD: fffff8800c1a5668 -- (.exr 0xfffff8800c1a5668)
    ExceptionAddress: fffff800030ce1e6 (nt!SwapContext_PatchXSave+0x0000000000000046)
    ExceptionCode: c0000005 (Access violation)
    ExceptionFlags: 00000000
    NumberParameters: 2
    Parameter[0]: 0000000000000000
    Parameter[1]: ffffffffffffffff
    Attempt to read from address ffffffffffffffff

    CONTEXT: fffff8800c1a4ec0 -- (.cxr 0xfffff8800c1a4ec0)
    rax=0000000000000005 rbx=fffff88003564180 rcx=fffff8800db09cc0
    rdx=0000000000000000 rsi=fffffa800caeb7a0 rdi=fffffa80052dbac0
    rip=fffff800030ce1e6 rsp=fffff8800c1a58a0 rbp=fffff8800db095e0
    r8=000000000000002b r9=000000000000000c r10=fffffa80052dba00
    r11=0000000000200246 r12=000000007efa7000 r13=0000000002b9fd20
    r14=5bfffa800515c9e0 r15=00000000752c2450
    iopl=0 nv up ei pl zr na po nc
    cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00210246
    fffff800`030ce1e6 4983be1801000000 cmp qword ptr [r14+118h],0 ds:002b:5bfffa80`0515caf8=????????????????
    Resetting default scope


    PROCESS_NAME: System


    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

    EXCEPTION_PARAMETER1: 0000000000000000

    EXCEPTION_PARAMETER2: ffffffffffffffff

    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032fa100
    GetUlongFromAddress: unable to read from fffff800032fa1c0

    fffff800`030ce1e6 4983be1801000000 cmp qword ptr [r14+118h],0


    LAST_CONTROL_TRANSFER: from fffff800030cde7a to fffff800030ce1e6

    fffff880`0c1a58a0 fffff800`030cde7a : 90869264`91230072 00000000`90560074 00000000`00000073 00000000`00000000 : nt!SwapContext_PatchXSave+0x46
    fffff880`0c1a58e0 fffff800`030c0a32 : fffffa80`0caeb7a0 fffffa80`0caeb7a0 00000000`00000000 fffff800`00000000 : nt!KiSwapContext+0x7a
    fffff880`0c1a5a20 fffff800`030d25d3 : fffffa80`00000000 ffffffff`00000000 fffffa80`00000085 fffffa80`09097000 : nt!KiCommitThreadWait+0x1d2
    fffff880`0c1a5ab0 fffff800`030d4619 : fffff800`03268200 fffff800`033bd501 fffffa80`0caeb700 fffffa80`00000000 : nt!KeRemoveQueueEx+0x323
    fffff880`0c1a5b70 fffff800`03361e5a : 00000000`050f1674 fffffa80`0caeb7a0 00000000`00000080 fffffa80`0515c9e0 : nt!ExpWorkerThread+0xe9
    fffff880`0c1a5c00 fffff800`030bbd26 : fffff880`03564180 fffffa80`0caeb7a0 fffffa80`0c641590 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`0c1a5c40 00000000`00000000 : fffff880`0c1a6000 fffff880`0c1a0000 fffff880`0c1a58a0 00000000`00000000 : nt!KiStartSystemThread+0x16


    SYMBOL_NAME: nt!SwapContext_PatchXSave+46

    FOLLOWUP_NAME: MachineOwner


    IMAGE_NAME: ntkrnlmp.exe


    STACK_COMMAND: .cxr 0xfffff8800c1a4ec0 ; kb

    FAILURE_BUCKET_ID: X64_0x7E_nt!SwapContext_PatchXSave+46

    BUCKET_ID: X64_0x7E_nt!SwapContext_PatchXSave+46
  6. Not much experience here. Seems you need to enable debugging to progress. Found this
    On a windows 7 machine we can enable kernel debugging by doing the following steps.
    ■Open a elevated command prompt(For more information see
    ■From the command prompt run the below commands

    bcdedit /debug ON
    bcdedit /dbgsettings SERIAL DEBUGPORT:1 BAUDRATE:115200

    Perhaps an experienced Dump analyser will step in and help! Almost certainly a driver, GPUs often the culprit. Clean Startup could isolate.
  7. All right....will check it out. Thanks for all the help
  8. SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (0x7E) typically indicates bad RAM. Given how this is a clean install, that farther points to H/W.

    Download/run memtest86+ to test RAM.
  9. Its 95% a ram issue. You PSu is more than enougth, so its not that. You have a clean install so its not drivers (most likely).

    That usually leaves ram as the most common suspect.
    as gamerk316 said, run mem test. after that, if it has issues, try changing the ram sockets. Sometimes the ram is just simply having a problem with the bios, and works better on another socket. (if you are really lucky).

    If not, probably one of the ram moduls is faulty, so you will have to test individually to figure out wich one it is.
  10. My motherboard has 4 sockets for RAM two red and two black. I have 3 sticks of 2GB each. The motherboard manual shows where to put the RAM if one stick or two sticks or four sticks.

    I had simply put two in the red ones and one in black? DO you think that is the issue. The sticks are brand new so chances of one of it being bad would be silm....right?

  11. Not impossible to get bad sticks from the vendors. Try running with one removed in turn to see if the system is stable. Also it's possible to have one bad slot, so work that into your deliberations! And sometimes merely re-seating them does the trick... so if you identify one bad one re-insert it to make sure...
  12. Another possibility is a GPU problem, if you find no fault with the RAM try removing your GPUs and connect up to the iGPU to rule them out of the equation...
  13. ok.....problem solved. Seems like the motherboard will support 1, 2 or 4 sticks of RAM not 3. Ran smoothly with 1 stick and two sticks. I interchanged also the sticks in combinations of 1 and 2 and there was no problem.

    Thanks guys for all your inputs
Ask a new question

Read More

Blue Screen Windows 7