Ok system service exception error blue screen

Attachment 233848Attachment 233849


My DM log and V2 log

Hello debgram,

Unfortunately the mini-dump file was empty. There appears to be a memory.dmp file so I wonder if you could share it via OneDrive. The file itself is too big to zip and post in the thread.

Code:

Crash dump found at C:\WINDOWS\MEMORY.DMP
Creation date: 05/15/2019 16:16:49
Size on disk: 1195 MB

Do I zip it and share on OneDrive? I don't have memory.dmp the folder is minidump and it won't let me access it

philc43 said:

Hello debgram,

Unfortunately the mini-dump file was empty. There appears to be a memory.dmp file so I wonder if you could share it via OneDrive. The file itself is too big to zip and post in the thread.

Code:

Crash dump found at C:\WINDOWS\MEMORY.DMP
Creation date: 05/15/2019 16:16:49
Size on disk: 1195 MB

debgram said:

Do I zip it and share on OneDrive?

That would be great!

Microsoft services

philc43 said:

That would be great!

I have been using Rapport for years and never had a blue screen.

Ztruker said:

The dump files shows a problem with RapportCerberus64_1930247.sys.

Code:

ffff830c`23dde5a8  fffff800`8cf7359f*** ERROR: Module load completed but symbols could not be loaded for RapportCerberus64_1930247.sys
 RapportCerberus64_1930247+0x8359f

Found a similar error here: Blue Screen Error and the solution was to uninstall Rapport.

It shows in your installed list: Rapport 3.5.1930.243 Trusteer 20190115

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /restorehealth
4) wmic recoveros set autoreboot = false
5) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

6) chkdsk /r /v
This may take hours to run so plan to run overnight.
Run on all drives using the syntax: chkdsk /r /v C: or chkdsk /r /v D: changing the drive letter to the applicable drive.

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


7) Use the information in this link to find the chkdsk report in the event viewer. Copy and paste into notepad > save to desktop > post into the thread using one drive or drop box share link:
Read Chkdsk Log in Event Viewer in Windows 10 Windows 10 Performance Maintenance Tutorials
Read Chkdsk Log in Event Viewer in Windows 10


8) For any BSOD:

a) run the V2 log collector to collect new log files

b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
> if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive

Code:

Event[1544]:
  Log Name: System
  Source: Ntfs
  Date: 2019-05-15T16:24:04.023
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DEBBIE-PC
  Description: 
A corruption was discovered in the file system structure on volume ??.

The Master File Table (MFT) contains a corrupted file record.  The file reference number is 0x8e0000000001ae.  The name of the file is "<unable to determine file name>".

Code:

Event[1538]:
  Log Name: System
  Source: Ntfs
  Date: 2019-05-15T16:18:03.108
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DEBBIE-PC
  Description: 
A corruption was discovered in the file system structure on volume ??.

The Master File Table (MFT) contains a corrupted file record.  The file reference number is 0x8e0000000001ae.  The name of the file is "<unable to determine file name>".

Code:

Event[1536]:
  Log Name: System
  Source: Ntfs
  Date: 2019-05-15T16:17:44.615
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DEBBIE-PC
  Description: 
A corruption was discovered in the file system structure on volume ??.

The Master File Table (MFT) contains a corrupted file record.  The file reference number is 0x8e0000000001ae.  The name of the file is "<unable to determine file name>".

Code:

Event[1500]:
  Log Name: System
  Source: Ntfs
  Date: 2019-05-15T16:16:28.572
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DEBBIE-PC
  Description: 
A corruption was discovered in the file system structure on volume D:.

The exact nature of the corruption is unknown.  The file system structures need to be scanned online.

It had something to do with security on my bank account. I did however, look and my bank isn't listed anymore as one of the banks using it.

Ztruker said:

That may be, I'm just reporting what I saw in the dump.

What is it used for?