Multiple BSOD errors

R

Red Tangent

New member
Local time
2:33 PM
Messages
1
I have been experiencing multiple BSOD errors for the last week. For a while no minidumps were created but after re-imaging my drive it seems some (not all) have been logged. Since this problem began I have had various games crashed. Chrome tabs crashing. Atleast 2 of the games that were crashing required a file check to repair themselves.

Tried fresh install of windows on my ssd which BSOD multiple times trying to boot for the first time once it finally was able to boot the system was missing drivers which should have installed automatically. Re-imaged the SSD with a backup. Cloned my SSD to an HDD I had. The HDD will BSOD every time I try to use it. It also does not show up as an available drive to my system while booted from the SSD, but it does show up in my bios, other programs, and to disk part. Im not sure if this is related at all but it seems weird.

After I have a BSOD it will BSOD on every reboot attempt. After powering down my PSU for a few seconds and booting it will usually boot fine, Though lately it may also just give me a blank screen after the starting windows screen and reboot after a minute or so.

I hate not being able to figure out my own issue, but I am at my wits end with these problems.
 

My Computer

Computer type
PC/Desktop
OS
Windows 7 Ultimate x64
CPU
Intel Core i5 2500K @ 3.30GHz
Motherboard
MSI Z77A-G43 (MS-7758)
Memory
8.00GB Dual-Channel DDR3 @ 666MHz (9-9-9-24)
Graphics Card(s)
2047MB NVIDIA GeForce GTX 760 (EVGA)
Hard Drives
465GB Western Digital WDC WD5000AAKS-22V1A SCSI Disk Device
232GB Samsung SSD 840 EVO 250G SCSI Disk Device (SSD)
Welcome.

Some BSOD's seem related to your NVIDIA drivers.

Roll back to a last known stable version.

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


Loading Dump File [C:\Users\YUSRA\Downloads\Compressed\HUNTER-PC-Thu_03_12_2015_234540_48\031215-6692-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*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
Built by: 7601.18717.amd64fre.win7sp1_gdr.150113-1808
Machine Name:
Kernel base = 0xfffff800`02a12000 PsLoadedModuleList = 0xfffff800`02c56890
Debug session time: Fri Mar 13 08:43:19.417 2015 (UTC + 6:00)
System Uptime: 0 days 0:00:03.634
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
...............................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c000001d, fffff88006161b05, fffff88006bd98b0, 0}

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

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c000001d, Exception code that caused the bugcheck
Arg2: fffff88006161b05, Address of the instruction which caused the bugcheck
Arg3: fffff88006bd98b0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

FAULTING_IP: 
nvlddmkm+74db05
fffff880`06161b05 ff              ???

CONTEXT:  fffff88006bd98b0 -- (.cxr 0xfffff88006bd98b0;r)
rax=fffff88006bda2b8 rbx=00000000ff0a0000 rcx=fffffa8009574da8
rdx=0000000033333333 rsi=0000000000000000 rdi=fffffa8009574da8
rip=fffff88006161b05 rsp=fffff88006bda290 rbp=0000000033333333
 r8=0000000000000000  r9=0000000000000000 r10=0000000000800001
r11=fffff88006bda1f0 r12=0000000000000001 r13=fffffa8009574da8
r14=fffffa8009574000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nvlddmkm+0x74db05:
fffff880`06161b05 ff              ???
Last set context:
rax=fffff88006bda2b8 rbx=00000000ff0a0000 rcx=fffffa8009574da8
rdx=0000000033333333 rsi=0000000000000000 rdi=fffffa8009574da8
rip=fffff88006161b05 rsp=fffff88006bda290 rbp=0000000033333333
 r8=0000000000000000  r9=0000000000000000 r10=0000000000800001
r11=fffff88006bda1f0 r12=0000000000000001 r13=fffffa8009574da8
r14=fffffa8009574000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nvlddmkm+0x74db05:
fffff880`06161b05 ff              ???
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff88006161b05

STACK_TEXT:  
fffff880`06bda290 00000000`00000000 : fffffa80`09574000 fffffa80`09574da8 00000000`00000001 fffff880`06bda320 : nvlddmkm+0x74db05


FOLLOWUP_IP: 
nvlddmkm+74db05
fffff880`06161b05 ff              ???

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nvlddmkm+74db05

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  54b0548e

STACK_COMMAND:  .cxr 0xfffff88006bd98b0 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nvlddmkm+74db05

BUCKET_ID:  X64_0x3B_nvlddmkm+74db05

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x3b_nvlddmkm+74db05

FAILURE_ID_HASH:  {91705c40-8fed-04a3-e1c0-d9dc1bcaa747}

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

2: kd> lmvm nvlddmkm
start             end                 module name
fffff880`05a14000 fffff880`06422000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Sat Jan 10 04:22:06 2015 (54B0548E)
    CheckSum:         009D73FA
    ImageSize:        00A0E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Also test RAM.

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.
Click to expand...
   Information
Errors are sometimes found after 8 passes.

   Tip
Memtest should be done overnight.


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


Loading Dump File [C:\Users\YUSRA\Downloads\Compressed\HUNTER-PC-Thu_03_12_2015_234540_48\031215-15241-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*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
Built by: 7601.18717.amd64fre.win7sp1_gdr.150113-1808
Machine Name:
Kernel base = 0xfffff800`02a56000 PsLoadedModuleList = 0xfffff800`02c9a890
Debug session time: Fri Mar 13 09:27:15.493 2015 (UTC + 6:00)
System Uptime: 0 days 0:39:14.321
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa80051e4030, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35084 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
	contains the address of the PFN for the corrupted page table page.
	On a 32 bit OS, parameter 2 contains a pointer to the number of used
	PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa80051e4030
Arg3: 000000000000ffff
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER:  from fffff80002b3d010 to fffff80002acaec0

STACK_TEXT:  
fffff880`0a5e66e8 fffff800`02b3d010 : 00000000`0000001a 00000000`00041790 fffffa80`051e4030 00000000`0000ffff : nt!KeBugCheckEx
fffff880`0a5e66f0 fffff800`02afe759 : 00000000`00000000 00000000`05db2fff fffffa80`00000000 fffff800`00000000 : nt! ?? ::FNODOBFM::`string'+0x35084
fffff880`0a5e68b0 fffff800`02de6db1 : fffffa80`0bb36ef0 00000000`00000000 fffffa80`0aa3c090 fffffa80`0aa3c090 : nt!MiRemoveMappedView+0xd9
fffff880`0a5e69d0 fffff800`02de71b3 : 0000007f`00000000 00000000`04780000 fffffa80`00000001 00000000`002fe701 : nt!MiUnmapViewOfSection+0x1b1
fffff880`0a5e6a90 fffff800`02aca153 : 00000000`00000001 00000000`01a9c312 fffffa80`092a1b30 00000000`01290000 : nt!NtUnmapViewOfSection+0x5f
fffff880`0a5e6ae0 00000000`7726155a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`002fde68 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7726155a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+35084
fffff800`02b3d010 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+35084

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  54b5f6ff

IMAGE_VERSION:  6.1.7601.18717

FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35084

BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+35084

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x1a_41790_nt!_??_::fnodobfm::_string_+35084

FAILURE_ID_HASH:  {f6a6ed79-e275-9f8c-d5a4-3a37a32b0b4e}

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

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
You must log in or register to reply here.
Back
Top