BSOD: WIN8_DRIVER_FAULT


Joined
Aug 7, 2015
Messages
2
Reaction score
0
Hello All,


Last week, I installed Windows 10 on my Lenovo W530; ever since I'm getting random BSOD's: MEMORY_MANAGEMENT.
When investigating the MEMORY.DMP files, the process_name is always different, but the DEFAULT_BUCKET_ID is always WIN8_DRIVER_FAULT.

I've ran "Memory Diagnostics" and all was fine;
since this started appearing after installing Windows 10 and given the error msg, of course this looks like one of my installed drivers is to blame.

I'm new to WinDbg and I'm unable to figure out which driver I should update / uninstall.
Below you'll find the result of running !analyze -v on the dump.


If anybody could give me some advice on what to look for, that would be great.

Thanks for your time,
Koen


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

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041793, The subtype of the bugcheck.
Arg2: fffff6bffca95c80
Arg3: 0000000000000002
Arg4: 0000000000000001

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


BUGCHECK_STR: 0x1a_41793

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: csc.exe

CURRENT_IRQL: 2

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

LAST_CONTROL_TRANSFER: from fffff802d217e7b8 to fffff802d214e220

STACK_TEXT:
ffffd000`26716508 fffff802`d217e7b8 : 00000000`0000001a 00000000`00041793 fffff6bf`fca95c80 00000000`00000002 : nt!KeBugCheckEx
ffffd000`26716510 fffff802`d202deb0 : ffffe001`b7b9ecf0 ffffd000`267167d9 ffffe001`bc321578 ffffe001`b99a5240 : nt! ?? ::FNODOBFM::`string'+0x219b8
ffffd000`26716710 fffff802`d24c2cb7 : ffffe001`b9919e00 ffffe001`b9919e00 ffffe001`bc7ec800 ffffe001`bc321080 : nt!MiDeleteVad+0x4b0
ffffd000`26716840 fffff802`d24c2a13 : 00000000`00040000 ffffd000`26716a99 00000000`00000000 ffffe001`bc321080 : nt!MmCleanProcessAddressSpace+0xef
ffffd000`267168a0 fffff802`d24bb61b : ffffe001`bc321080 ffffc000`7adfc060 ffffd000`26716a99 00000000`00000000 : nt!PspRundownSingleProcess+0x12b
ffffd000`26716930 fffff802`d24a232a : 00000000`00000001 ffffd000`26716a01 00007ff6`8039c000 ffffe001`bc321080 : nt!PspExitThread+0x5fb
ffffd000`26716a30 fffff802`d2158863 : ffffe001`bc7ec800 00000000`00000000 ffffe001`bc7ec800 ffffd000`26716b80 : nt!NtTerminateProcess+0x11a
ffffd000`26716b00 00007ff9`56cf37ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
0000004a`87f9fdd8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`56cf37ba


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+219b8
fffff802`d217e7b8 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+219b8

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 55b99f32

BUCKET_ID_FUNC_OFFSET: 219b8

FAILURE_BUCKET_ID: 0x1a_41793_nt!_??_::FNODOBFM::_string_

BUCKET_ID: 0x1a_41793_nt!_??_::FNODOBFM::_string_

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x1a_41793_nt!_??_::fnodobfm::_string_

FAILURE_ID_HASH: {2bb49b32-09fa-a96d-8b93-292cf7a50b3f}

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

Advertisements

Shintaro

Moderator
Joined
Apr 16, 2014
Messages
70
Reaction score
15
May I suggest that you run the Free version of Malwarebytes and TDSSKiller. I would make sure that there isn't any virus or malware on your computer first.

Please post the logs.
 
Ad

Advertisements

Joined
Aug 7, 2015
Messages
2
Reaction score
0
Hello all,

I ran another memory test, this time using the memtest tool.
On this run, it did find errors on one of my mem sticks.
(not sure why the built-in windows "memory diagnostic tool" did not detect those errors)


I replaced this stick and hope all will be fine now.
(also not sure why Windows 8 ran fine for all this time.. It would be a rare coincidence
that the memory stick broke down at exactly the same time as installing windows 10).


Thanks for your time,
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top