Windows 7 BSOD - BugcheckCode 340

andrewstas

New Member
Hi everybody.
So, since last week I had twice a BSOD with BugcheckCode 340.
See attached the minidump file of the latest (today's) BSOD.

I would appreciate any help.

Cheers
 

Attachments

  • W7F_07-04-2019.zip
    471.5 KB · Views: 494
This exception was 154 which is a windows store exception. The dump points to a problem reading data into memory from the hard drive. You may want to run a drive fitness test such as SeaTools SeaTools for Windows | Seagate and see if your drive is starting to fail.
 
oh really? I hope not but I will get prepared.

I was not expecting something like this. Could this be related to the free space available or memory used? Usually the laptop remains on for many days. It was 8 days on before the last BSOD and about 50 days before the previous BSOD. Should I do a restart more frequent or the exception you refer to does not matter how often I restart Windows 10?

It is a new laptop, I bought it on December 2018 and the disk is SSD. I will check with the software you recommend and revert.
Thanks
 
I installed SeaTools and thankfully the result was "Pass" for both the Short and the Long Generic tests.
Could this be a false positive?
Any other suggestion what to check?
 
What anti-virus or anti-malware software are you using?

There is a reference to a filter filt$0 this could be an anti-virus software that's messing up the read from disk to memory.

nt!KeBugCheckEx
fffff200`263f5f00 fffff801`085d41d1 : ffffd886`072e8000 fffff200`263f5fb0 00000000`00000002 00000000`00000000 : nt!SMKM_STORE<SM_TRAITS>::SmStUnhandledExceptionFilter+0x7e
fffff200`263f5f50 fffff801`08597d5f : 00000000`00000002 00000000`00000000 fffff200`263f1000 fffff200`263f8000 : nt!`SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue'::`1'::filt$0+0x22
fffff200`263f5f80 fffff801`085c394d : 00000000`00000000 fffff200`263f6120 fffff200`263f65e0 00000000`00000000 : nt!_C_specific_handler+0x9f
fffff200`263f5ff0 fffff801`084cfb16 : fffff200`263f6120 fffff200`263f65e0 00000000`00000000 fffff200`263f6ef8 : nt!RtlpExecuteHandlerForException+0xd
fffff200`263f6020 fffff801`084d1613 : fffff200`263f6ef8 fffff200`263f6c40 fffff200`263f6ef8 ffff8100`241c7000 : nt!RtlDispatchException+0x416
fffff200`263f6710 fffff801`085cbd42 : ffffed3e`10000000 fffff200`00000000 ffffae57`00003908 00000000`00000000 : nt!KiDispatchException+0x1f3
fffff200`263f6dc0 fffff801`085c88bf : 00000000`e411b839 00000000`0000083b ffffd886`04a48000 ffff8100`241c8000 : nt!KiExceptionDispatch+0xc2
fffff200`263f6fa0 fffff801`085754c0 : fffff200`263f73c8 ffff8100`241c7000 ffff8100`241c7000 fffff801`084e9720 : nt!KiPageFault+0x3ff
fffff200`263f7130 fffff801`084e9720 : ffff8100`241c7000 ffffd886`072e8050 00000000`e43e94e0 00000000`00000000 : nt!RtlDecompressBufferXpressLz+0x50
fffff200`263f7150 fffff801`0856355c : 00000000`00000000 000240f6`00000001 00000000`e43e94e0 00000000`00000001 : nt!RtlDecompressBufferEx+0x60
fffff200`263f71a0 fffff801`085633dd : 00000000`00000004 fffff200`263f73b0 00000000`00000000 00000000`00001677 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageCopy+0x158
fffff200`263f7280 fffff801`085632a2 : 00000000`00000001 00000000`000194e0 fffff200`000194e0 00000000`00002000 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageTransfer+0x95
fffff200`263f72d0 fffff801`085630cd : 00000000`ffffffff ffffd886`04a48000 fffff200`263f73b0 ffffd886`078e20d0 : nt!ST_STORE<SM_TRAITS>::StDmpSinglePageRetrieve+0x186
fffff200`263f7370 fffff801`08562f21 : ffffd886`04a48000 fffff801`00000000 ffffd886`00000001 ffffd886`072e9788 : nt!ST_STORE<SM_TRAITS>::StDmPageRetrieve+0xc1
fffff200`263f7420 fffff801`08562e31 : ffffd886`072e8000 ffffd886`078e20d0 ffffd886`04a48000 ffffd886`072e99b0 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue+0x85
fffff200`263f74a0 fffff801`084d017a : ffffd886`20fb4700 fffff200`263f7570 00000000`00000000 00000000`00000001 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadCallout+0x21
fffff200`263f74d0 fffff801`08565a6d : fffff801`08562e10 fffff200`263f7570 00000000`00000003 ffffd886`04a48000 : nt!KeExpandKernelStackAndCalloutInternal+0x8a
fffff200`263f7530 fffff801`08426bb1 : fffff200`263f7630 fffff801`08426755 00000000`00000000 fffff801`0856501c : nt!SMKM_STORE<SM_TRAITS>::SmStDirectRead+0xad
fffff200`263f7600 fffff801`084265f2 : 00000000`00000000 00000000`00000000 fffff200`263f76b0 ffffd886`078e20d0 : nt!SMKM_STORE<SM_TRAITS>::SmStWorkItemQueue+0x1b1
fffff200`263f7650 fffff801`08564d80 : 00000000`0000000c 00000000`00000002 ffffd886`078e20d0 ffffd886`0fc05340 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmIoCtxQueueWork+0xce
fffff200`263f76d0 fffff801`08566426 : 00000000`00000002 ffffd886`0fc053f8 00000000`00000000 ffffd886`072e8000 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmPageRead+0x168
fffff200`263f7740 fffff801`08489582 : 00000000`00000000 ffffd886`0f0dd580 fffff200`263f7820 fffff801`0846cc86 : nt!SmPageRead+0x2e
fffff200`263f7790 fffff801`084876a4 : 00000000`00000002 fffff200`263f7820 00000000`00000001 ffff8100`166c2180 : nt!MiIssueHardFaultIo+0x122
fffff200`263f77e0 fffff801`0846b3c4 : 00000000`c0033333 00000000`00000001 0000023b`b016cff8 fffff801`00000000 : nt!MiIssueHardFault+0x234
fffff200`263f7890 fffff801`085c87da : 000000b5`323ff088 000000b5`323ff118 0000023b`b01a38e0 00000000`00000001 : nt!MmAccessFault+0x384
fffff200`263f7a00 00007fff`59167161 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x31a
000000b5`323fefc0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`59167161
 
What version are you on? You may need to look in Control Panel > Programs and Features

The other way is go into Webroot > My Account > 'About Secure Anywhere'
Then click on 'Check for software updates'

37684
 
Oh, I use the following for protection too:
- Cybereason Ransomfree (to protect from ransomware)
- Sandboxie (to run apps in a sandbox)
- Panda USB Vaccine (to protect from infected USB sticks)

Could it be any of the above that causes the problem?
I suspect the Cybereason Ransomfree, but on the other hand I use it for couple of years now without problems of this nature.
 
Possibly I would remove panda usb. That would also use a file system filter driver which could cause the issue.
 
Thanks. I will remove it and see how it goes. If another BSOD happens I will be back.
According to your experience, is there anything else to check from the provided information of the minidump file?
 
I'd just wait and see how it goes with Panda USB removed. If you have another BSOD upload it.
 
Not sure if the following has any value as information regarding my BSODs, but both times that they happened the laptop was powered with its battery and it was connected to an external monitor.
 
One and a half month later and no BSOD or other issues. So I guess problem solved.
Thanks so much Neemobeer once again. Your help was priceless.
 
Back
Top