random bsod

vaughn77

New member
Local time
8:15 AM
Messages
1
need help with this blue screen its driving me nuts thanks
 

My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
custom
OS
7 64bit
CPU
3570 k
Motherboard
msi x77 65
Memory
16gb corsair vengeance 1600
Graphics Card(s)
gtx780
Hard Drives
m4 240 ss
Antivirus
widnows essentials
Browser
firefox
Welcome to the Forum.

Reduce items at start-up: http://www.sevenforums.com/tutorials/1401-startup-programs-change.html

Perform a clean boot: http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

Lately we have experienced some issues with the latest driver. Install the 314.22 WHQL only.

  • Uninstall All nvidia items in Control Panel > Programs and features
    • 3D Vision Control Driver
    • 3D Vision Driver
    • Graphics Driver
    • HD Audio Driver
    • PhysX
    • nvidia Update
    (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
  • Now follow Drivers - Clean Left over Files after Uninstalling
  • Boot normally now. Go to Drivers - Download NVIDIA Drivers, Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:

Let us know the results.

Then do a Stress Test.

How to Stress Test a Video Card with Furmark:

Code:
Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\USER\Downloads\SF_06-01-2014\SF_06-01-2014\010614-4212-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`01e19000 PsLoadedModuleList = 0xfffff800`0205c6d0
Debug session time: Mon Jan  6 14:09:54.240 2014 (UTC + 6:00)
System Uptime: 0 days 10:32:25.114
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {51, 7, 1, fffff88003216486}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : hardware ( nvlddmkm+213486 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000051, memory referenced
Arg2: 0000000000000007, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88003216486, address which referenced memory

Debugging Details:
------------------


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800020c6100
GetUlongFromAddress: unable to read from fffff800020c61c0
 0000000000000051 Nonpaged pool

CURRENT_IRQL:  7

FAULTING_IP: 
nvlddmkm+213486
fffff880`03216486 815a040000440f  sbb     dword ptr [rdx+4],0F440000h

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TAG_NOT_DEFINED_c000000f:  FFFFF80001C40FB0

TRAP_FRAME:  fffff80001c3a560 -- (.trap 0xfffff80001c3a560)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800d05c000 rbx=0000000000000000 rcx=0000000000000000
rdx=000000000000004d rsi=0000000000000000 rdi=0000000000000000
rip=fffff88003216486 rsp=fffff80001c3a6f0 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000000 r10=fffff880033e0834
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nvlddmkm+0x213486:
fffff880`03216486 815a040000440f  sbb     dword ptr [rdx+4],0F440000h ds:00000000`00000051=????????
Resetting default scope

MISALIGNED_IP: 
nvlddmkm+213486
fffff880`03216486 815a040000440f  sbb     dword ptr [rdx+4],0F440000h

LAST_CONTROL_TRANSFER:  from fffff80001e8e169 to fffff80001e8ebc0

STACK_TEXT:  
fffff800`01c3a418 fffff800`01e8e169 : 00000000`0000000a 00000000`00000051 00000000`00000007 00000000`00000001 : nt!KeBugCheckEx
fffff800`01c3a420 fffff800`01e8cde0 : 00000000`00000140 fffff880`031ee82b 00000000`00000000 fffffa80`0d051000 : nt!KiBugCheckDispatch+0x69
fffff800`01c3a560 fffff880`03216486 : 00000000`00000104 fffffa80`0d051000 00000000`00000020 fffff800`01c3a710 : nt!KiPageFault+0x260
fffff800`01c3a6f0 00000000`00000104 : fffffa80`0d051000 00000000`00000020 fffff800`01c3a710 00000000`00000000 : nvlddmkm+0x213486
fffff800`01c3a6f8 fffffa80`0d051000 : 00000000`00000020 fffff800`01c3a710 00000000`00000000 00000000`00000040 : 0x104
fffff800`01c3a700 00000000`00000020 : fffff800`01c3a710 00000000`00000000 00000000`00000040 00000000`00000000 : 0xfffffa80`0d051000
fffff800`01c3a708 fffff800`01c3a710 : 00000000`00000000 00000000`00000040 00000000`00000000 00000000`00000001 : 0x20
fffff800`01c3a710 00000000`00000000 : 00000000`00000040 00000000`00000000 00000000`00000001 fffffa80`0d051000 : 0xfffff800`01c3a710


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+213486
fffff880`03216486 815a040000440f  sbb     dword ptr [rdx+4],0F440000h

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nvlddmkm+213486

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED_nvlddmkm.sys

BUCKET_ID:  X64_IP_MISALIGNED_nvlddmkm.sys

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

0: kd> lmvm nvlddmkm
start             end                 module name
fffff880`03003000 fffff880`03c44000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Mon Nov 11 19:24:05 2013 (5280DA75)
    CheckSum:         00C10283
    ImageSize:        00C41000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
3. Test the next stick of RAM (stick #2) in the next motherboard slot.
*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.
   Information
Errors are sometimes found after 8 passes.

   Tip
Do this test overnight, before going to bed.
 

My Computer

Computer type
PC/Desktop
Computer Manufacturer/Model Number
Self assembled
OS
Windows 10 Home 64Bit
CPU
Intel Core i5 10400 @ 2.90GHz
Motherboard
Intel Corporation DG41WV (PROCESSOR)
Memory
8.00GB Single-Channel Unknown @ 1329MHz (16-20-20-38)
Sound Card
Realtek High Definition Audio
Monitor(s) Displays
DELL E170S
Screen Resolution
1280x1024 pixels
Hard Drives
931GB TOSHIBA DT01ACA100 (SATA)
238GB TEAM TM8PS7256G (SATA SSD)
Case
Nothing Fancy
Cooling
Fans
Keyboard
A4 Tech Co LTD
Mouse
A4 Tech Co Ltd/Logitech
Internet Speed
25 Mbps
Back
Top