[SOLVED] Store Exception Error

D

Daniel_Jack

Member
Joined
Jun 19, 2021
Posts
8
http://speccy.piriform.com/results/urX03rr8NVPJo78dEAOJW7F

1. A brief description of your problem (but you can also include the steps you tried)
Upgraded hard drive to a PNY 500gb SSD. Sometimes on startup or restart I'm getting a store exception error. The error will appear, but then the laptop will start up normally.
2. System Manufacturer? HP Pavilion G6 notebook
3. OS ? Windows 10 (64bit)
4. What was original installed OS on system? Windows 7
5. Is the OS an OEM version? OEM version
6. Age of system? Not sure
7. Age of OS installation? Not sure it was upgraded to Windows 10
8. Have you re-installed the OS? NO
9. CPU? AMD A4-3320M
10. RAM? 6GB DDR3@666MHz
11. Video Card? 512 MB ATI AMD radeon HD 6480 G (HP)
12. MotherBoard - HP 169B (Socket FS1)
13. Power Supply - brand & wattage (if laptop, skip this one)
14. Is driver verifier enabled or disabled? Not sure
15. What security software are you using? Norton360, Malwarebytes
16. Are you using proxy, vpn, ipfilters or similar software? No
17. Are you using Disk Image tools? Acronis transfer software
18. Are you currently under/overclocking? Are there overclocking software installed on your system? No, No
 

Attachments

It appears that the issue most likely lies with your SSD, the manufacturer provides a program called SSD Toolbox, I would suggest checking it out and seeing if it provides any testing tools.

I would also suggest disabling Norton Security for now and enabling Windows Defender for troubleshooting purposes. Please also disable Acronis File Protector as well. It's seems odd that the system crashes and then boots normally with no problems.
 
Thank you for the quick response. I'll try those suggestions as soon as I can. I did run the verifier and the laptop thru another error. It was IRQL NOT LESS OR EQUAL. I did a hard shut down because it was taking forever to restart. The laptop started up fine but after about 10-15 minutes it threw the same IRQL NOT LESS OR EQUAL error. I'm assuming I need to stop verifier from running but had to leave and haven't done that yet. If you need any logs (Cbs, etc..) let me know.
 
Daniel_Jack said:
I did run the verifier and the laptop thru another error. It was IRQL NOT LESS OR EQUAL. I did a hard shut down because it was taking forever to restart. The laptop started up fine but after about 10-15 minutes it threw the same IRQL NOT LESS OR EQUAL error. I'm assuming I need to stop verifier from running but had to leave and haven't done that yet.
Click to expand...
That wouldn't have been produced by DV, however, I would disable it for now since we're not going to require it at the moment. Could you please upload the latest dump files if you're able to?
 
Thank you for providing the other dump files. It seems like they're more fruitful than the others.

It does appear that Norton Internet Security is causing some problems here, and I would strongly suggest removing the program completely using their official removal tool. I mentioned it in my previous post as more of a hunch, since Norton has caused so many problems in the past. However, the latest dump files have confirmed my suspicions.

Rich (BB code): 
1: kd> lmvm SYMEVENT64x86
Browse full module list
start             end                 module name
fffff80f`b1650000 fffff80f`b1671000   SYMEVENT64x86 T (no symbols)           
    Loaded symbol image file: SYMEVENT64x86.SYS
    Image path: \??\C:\WINDOWS\system32\Drivers\SYMEVENT64x86.SYS
    Image name: SYMEVENT64x86.SYS
    Browse all global symbols  functions  data
    Timestamp:        Mon Oct  8 23:59:48 2018 (5BBBE164)
    CheckSum:         00026FFF
    ImageSize:        00021000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

Here's the call stack from another dump file, which isn't a Stop 0x154, however, the call stack is very similar to the one where Norton was clearly present.

Rich (BB code): 
0: kd> knL
 # Child-SP          RetAddr           Call Site
00 ffff9985`b3a52da8 fffff805`48812b69 nt!KeBugCheckEx
01 ffff9985`b3a52db0 fffff805`4880ee69 nt!KiBugCheckDispatch+0x69
02 ffff9985`b3a52ef0 fffff805`489bbd82 nt!KiPageFault+0x469 << Crash here!
03 ffff9985`b3a53080 fffff805`4888ade2 nt!ExpCheckForWorker+0x13e
04 ffff9985`b3a530e0 fffff805`48dbd149 nt!ExFreeHeapPool+0x16efd2
05 ffff9985`b3a531c0 fffff805`48762e9f nt!ExFreePool+0x9
06 ffff9985`b3a531f0 fffff805`4870393b nt!SmFpFree+0x83
07 ffff9985`b3a53220 fffff805`4876309e nt!SMKM_STORE_MGR<SM_TRAITS>::SmWorkItemFreeResource+0x2b << Store Manager functions
08 ffff9985`b3a53250 fffff805`486afb8e nt!SMKM_STORE_MGR<SM_TRAITS>::SmWorkItemFree+0x136
09 ffff9985`b3a532d0 fffff805`486afb56 nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadComplete+0x1e
0a ffff9985`b3a53300 fffff805`486a2bc8 nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadCallout+0x46
0b ffff9985`b3a53330 fffff805`486ad68f nt!KeExpandKernelStackAndCalloutInternal+0x78
0c ffff9985`b3a533a0 fffff805`48763934 nt!SMKM_STORE<SM_TRAITS>::SmStDirectRead+0xc7
0d ffff9985`b3a53470 fffff805`48763368 nt!SMKM_STORE<SM_TRAITS>::SmStWorkItemQueue+0x1ac
0e ffff9985`b3a534c0 fffff805`486ae117 nt!SMKM_STORE_MGR<SM_TRAITS>::SmIoCtxQueueWork+0xc0
0f ffff9985`b3a53550 fffff805`4870496b nt!SMKM_STORE_MGR<SM_TRAITS>::SmPageRead+0x167
10 ffff9985`b3a535c0 fffff805`486680a0 nt!SmPageRead+0x33
11 ffff9985`b3a53610 fffff805`48665b4d nt!MiIssueHardFaultIo+0x10c
12 ffff9985`b3a53660 fffff805`48732278 nt!MiIssueHardFault+0x29d
13 ffff9985`b3a53720 fffff805`4880ed5e nt!MmAccessFault+0x468
14 ffff9985`b3a538c0 fffff805`489ffcfe nt!KiPageFault+0x35e
15 ffff9985`b3a53a50 fffff805`489ffbee nt!ObpReferenceObjectByHandleWithTag+0xfe
16 ffff9985`b3a53ae0 fffff805`486b961d nt!ObReferenceObjectByHandle+0x2e
17 ffff9985`b3a53b30 fffff805`488125b5 nt!NtAssociateWaitCompletionPacket+0x5d
18 ffff9985`b3a53bd0 00007ffe`2750e014 nt!KiSystemServiceCopyEnd+0x25
19 0000005c`6cbff778 00000000`00000000 0x00007ffe`2750e014

The Store Manager directly works with page fault handling, it will compress all the pages in the system to converse as much as space as possible, which is designed to reduce the number of page faults by reducing the number of pages which need to be paged out. It also makes the page faults more efficient since the pages can be paged in and out much faster.

The last crash is another Stop 0x154.

Rich (BB code): 
UNEXPECTED_STORE_EXCEPTION (154)
The store component caught an unexpected exception.
Arguments:
Arg1: ffff888799a84000, Pointer to the store context or data manager << Some offset into SmGlobals?
Arg2: fffff98366371170, Exception information << Pointer to _EXCEPTION_POINTERS
Arg3: 0000000000000002, Reserved
Arg4: 0000000000000000, Reserved

For those interested, the second parameter is a pointer to the _EXCEPTION_POINTERS structure, which then contains the exception record and context record saved in the dump file.

Rich (BB code): 
1: kd> dt _EXCEPTION_POINTERS fffff98366371170
nt!_EXCEPTION_POINTERS
   +0x000 ExceptionRecord  : 0xfffff983`663720f8 _EXCEPTION_RECORD
   +0x008 ContextRecord    : 0xfffff983`66371930 _CONTEXT

Rich (BB code): 
1: kd> .exr 0xfffff983663720f8
ExceptionAddress: fffff800516d10d0 (nt!RtlDecompressBufferXpressLz+0x0000000000000050)
   ExceptionCode: c0000006 (In-page I/O error)
  ExceptionFlags: 00000000
NumberParameters: 3
   Parameter[0]: 0000000000000000
   Parameter[1]: 000002293d694f30
   Parameter[2]: 00000000c000000e
Inpage operation failed at 000002293d694f30, due to I/O error 00000000c000000e


Rich (BB code): 
1: kd> .cxr 0xfffff98366371930
rax=fffff800516d1080 rbx=ffffe580dd293000 rcx=ffffe580dd293000
rdx=ffffe580dd293000 rsi=0000000000000002 rdi=000002293d694f30
rip=fffff800516d10d0 rsp=fffff98366372338 rbp=000002293d694f82
 r8=000002293d694f30  r9=00000000000000a8 r10=ffffe580dd293ea0
r11=000002293d694fd8 r12=fffff983663725a8 r13=ffff88879e5f2000
r14=ffffe580dd294000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nt!RtlDecompressBufferXpressLz+0x50:
fffff800`516d10d0 418b08          mov     ecx,dword ptr [r8] ds:002b:00000229`3d694f30=????????
 
Uninstalled Norton's with the recommended tool. So far no crashes or errors on restart, shutdown, or turning on the laptop. I'll give it another day of going thru restarts, shutdowns, etc...before I'm satisfied it's trouble free. I appreciate your help it means the world to me. Will update tomorrow. Thank you!
 
When was the PNY drive installed?

Make sure that you test it.

Most of the tests can run overnight.


Run HD Tune (free version) (all drives)
HD Tune website
Post images into the thread for results on these tabs:
a) Health
b) Benchmark
c) Full error scan


Run Sea Tools for Windows
long generic test
Post an image of the test result into the thread
SeaTools (Windows) | Seagate
How to use SeaTools for Windows | Seagate Support US


Open administrative command prompt and type or copy and paste:
chkdsk /r /v
This may take hours to run so plan to run overnight.

C:\Windows\system32>chkdsk /r /v
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)

Type: Y
reboot


Run HD Sentinel: (free or trial edition)
Hard Disk Sentinel - HDD health and temperature monitoring
Hard Disk Sentinel - HDD health and temperature monitoring
For each drive post images of these tabs into the thread:
Overview tab
Temperature
SMART
Disk performance


These steps / tests can be performed overnight:
a) HD Tune full error scan
b) Sea Tools for Windows long generic test
e) Chkdsk /r /v
 
Daniel_Jack said:
Uninstalled Norton's with the recommended tool. So far no crashes or errors on restart, shutdown, or turning on the laptop. I'll give it another day of going thru restarts, shutdowns, etc...before I'm satisfied it's trouble free. I appreciate your help it means the world to me. Will update tomorrow. Thank you!
Click to expand...
That's good news so far! Let us know how it goes.
 
x BlueRobot said:
Rich (BB code): 
1: kd> .exr 0xfffff983663720f8
ExceptionAddress: fffff800516d10d0 (nt!RtlDecompressBufferXpressLz+0x0000000000000050)
   ExceptionCode: c0000006 (In-page I/O error)
  ExceptionFlags: 00000000
NumberParameters: 3
   Parameter[0]: 0000000000000000
   Parameter[1]: 000002293d694f30
   Parameter[2]: 00000000c000000e
Inpage operation failed at 000002293d694f30, due to I/O error 00000000c000000e
Click to expand...


The above clearly shows an I/O error, which only occurs on SSDs or HDDs - your internal hard drive.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top