ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)

jasonlong

New Member
Local time
11:44 AM
Posts
4
Thread starter
Hello,
How can I solve the "ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)" BSoD? I reinstalled the Chipset and USB drivers and checked my System File via "SFC /scannow" and everything seems OK, but I got BSoD!
How can I solve it?
The analysis result is:
Code:
 ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
   
 An attempt was made to write to readonly memory.  The guilty driver is on the
 stack trace (and is typically the current instruction pointer).
 When possible, the guilty driver's name (Unicode string) is printed on
 the bugcheck screen and saved in KiBugCheckDriver.
 Arguments:
 Arg1: ffff900035b3a334, Virtual address for the attempted write.
 Arg2: 8a00000005300021, PTE contents.
 Arg3: ffffdc82017c6550, (reserved)
 Arg4: 000000000000000a, (reserved)

Full dump analysis is: Link
I executed the V2 log collector and reports is: Link

Thank you.
 

My Computer

System One

  • Operating System
    Windows 10 Pro

philc43

BSOD Analyst
MVP
Member
VIP
Local time
11:44 AM
Posts
178
Location
Cambridge, UK
Hello jasonlong,

Sorry you are having problems. Only one of the crash dump files was the error in your title. The others were different and therefore this is not a consistent crash. It could be hardware related or software drivers. There is no obvious cause.

If this happens frequently I would try running your system in safe mode for a while to make sure it does not happen in that mode. This will tend to rule out the hardware cause.

Then I would try a clean boot to see if you can eliminate the BSODs. Follow the tutorial to add items back into the boot process until you identify which one may be causing the BSOD.
 

My Computer

System One

  • Operating System
    Windows 10
    Computer type
    PC/Desktop
    Manufacturer/Model
    Self-Build
    CPU
    Intel Core i5 3570K 3.4GHz
    Motherboard
    ASUS P8Z77-V LX
    Memory
    16GB
    Graphics Card(s)
    NVidia Geforce GTX 750Ti
    Sound Card
    On-board Realtek HD Audio
    Monitor(s) Displays
    Samsung 226BW
    Hard Drives
    1TB SSD + 1TB HDD
    PSU
    Corsair TX550
    Case
    Gigabyte IF233
    Keyboard
    Microsoft wired Keyboard 600
    Mouse
    Microsoft wired Basic Optical
    Internet Speed
    900MB/s
    Browser
    MS Edge
    Antivirus
    Microsoft Defender

zbook

Active Member
Member
VIP
Local time
5:44 AM
Posts
343
The logs reported problems related to the drives including:
paging error
retried
corruption


Please perform the following steps:

1) Run: (currently this requires a Ten Forums logon to have access to the script)
Tuneup_plus_log.bat ─ Click here to go to the BSOD batch repository to download and run this batch file.


2) Open administrative command prompt and type or copy and paste:
Chkdsk /b /v

Run on all drives using the syntax: chkdsk /b /v C: or chkdsk /b /v D: or chkdsk /b /v E:

C:\WINDOWS\system32>chkdsk /b /v C:
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


This may take many hours so plan to run overnight as needed.



3) Reinstall Intel Chipset drivers

4) Download and Install: Intel driver and support assistant


5) Run HD Tune (free or trial version)
Post images for results on these tabs:
a) Health
b) Benchmark
c) Full error scan

6) Sea Tools for Windows
Post images for results of the:
long generic test


7) These steps / tests can be performed overnight:
a) HD Tune full error scan
b) Sea Tools for Windows long generic test
c) Chkdsk /b /v






Code:
------------------------
Disk & DVD/CD-ROM Drives
------------------------
      Drive: C:
 Free Space: 150.5 GB
Total Space: 249.9 GB
File System: NTFS
      Model: ST1000DM003-1CH162

      Drive: D:
 Free Space: 5.9 GB
Total Space: 300.0 GB
File System: NTFS
      Model: ST1000DM003-1CH162

      Drive: E:
 Free Space: 52.4 GB
Total Space: 403.9 GB
File System: NTFS
      Model: ST1000DM003-1CH162



Code:
Event[5715]:
  Log Name: System
  Source: disk
  Date: 2021-10-02T19:57:03.3030000Z
  Event ID: 153
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: MY-PC.MYDOMAIN.COM
  Description:
The IO operation at logical block address 0x3fc01b38 for Disk 1 (PDO name: \Device\0000008a) was retried.


Code:
Event[6651]:
  Log Name: System
  Source: disk
  Date: 2021-10-08T17:02:27.7320000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: MY-PC.MYDOMAIN.COM
  Description:
An error was detected on device \Device\Harddisk1\DR1 during a paging operation.

Event[6652]:
  Log Name: System
  Source: disk
  Date: 2021-10-08T17:02:27.7320000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: MY-PC.MYDOMAIN.COM
  Description:
An error was detected on device \Device\Harddisk1\DR1 during a paging operation.

Event[6653]:
  Log Name: System
  Source: disk
  Date: 2021-10-08T17:02:27.7320000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: MY-PC.MYDOMAIN.COM
  Description:
An error was detected on device \Device\Harddisk1\DR1 during a paging operation.

Event[6654]:
  Log Name: System
  Source: disk
  Date: 2021-10-08T17:02:27.9160000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: MY-PC.MYDOMAIN.COM
  Description:
An error was detected on device \Device\Harddisk1\DR1 during a paging operation.

Event[6655]:
  Log Name: System
  Source: disk
  Date: 2021-10-08T17:02:27.9160000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: MY-PC.MYDOMAIN.COM
  Description:
An error was detected on device \Device\Harddisk1\DR1 during a paging operation.

Event[6656]:
  Log Name: System
  Source: disk
  Date: 2021-10-08T17:02:27.9320000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: MY-PC.MYDOMAIN.COM
  Description:
An error was detected on device \Device\Harddisk1\DR1 during a paging operation.

Event[6657]:
  Log Name: System
  Source: disk
  Date: 2021-10-08T17:02:27.9320000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: MY-PC.MYDOMAIN.COM
  Description:
An error was detected on device \Device\Harddisk1\DR1 during a paging operation.

Event[6658]:
  Log Name: System
  Source: disk
  Date: 2021-10-08T17:02:27.9320000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: MY-PC.MYDOMAIN.COM
  Description:
An error was detected on device \Device\Harddisk1\DR1 during a paging operation.

Event[6659]:
  Log Name: System
  Source: disk
  Date: 2021-10-08T17:02:27.9320000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: MY-PC.MYDOMAIN.COM
  Description:
An error was detected on device \Device\Harddisk1\DR1 during a paging operation.

Event[6660]:
  Log Name: System
  Source: disk
  Date: 2021-10-08T17:02:27.9320000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: MY-PC.MYDOMAIN.COM
  Description:
An error was detected on device \Device\Harddisk1\DR1 during a paging operation.

Event[6661]:
  Log Name: System
  Source: disk
  Date: 2021-10-08T17:02:27.9320000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: MY-PC.MYDOMAIN.COM
  Description:
An error was detected on device \Device\Harddisk1\DR1 during a paging operation.

Event[6662]:
  Log Name: System
  Source: disk
  Date: 2021-10-08T17:02:27.9480000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: MY-PC.MYDOMAIN.COM
  Description:
An error was detected on device \Device\Harddisk1\DR1 during a paging operation.

Event[6663]:
  Log Name: System
  Source: disk
  Date: 2021-10-08T17:02:27.9480000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: MY-PC.MYDOMAIN.COM
  Description:
An error was detected on device \Device\Harddisk1\DR1 during a paging operation.

Event[6664]:
  Log Name: System
  Source: disk
  Date: 2021-10-08T17:02:27.9480000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: MY-PC.MYDOMAIN.COM
  Description:
An error was detected on device \Device\Harddisk1\DR1 during a paging operation.

Event[6665]:
  Log Name: System
  Source: disk
  Date: 2021-10-08T17:02:27.9480000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: MY-PC.MYDOMAIN.COM
  Description:
An error was detected on device \Device\Harddisk1\DR1 during a paging operation.

Event[6666]:
  Log Name: System
  Source: disk
  Date: 2021-10-08T17:02:27.9480000Z
  Event ID: 51
  Task: N/A
  Level: Warning
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: MY-PC.MYDOMAIN.COM
  Description:
An error was detected on device \Device\Harddisk1\DR1 during a paging operation.



Code:
Event[6543]:
  Log Name: System
  Source: Ntfs
  Date: 2021-10-08T16:41:06.0150000Z
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: MY-PC.MYDOMAIN.COM
  Description:
A corruption was discovered in the file system structure on volume F:.

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


Code:
Stage 1: Examining basic file system structure ...
Some clusters occupied by attribute of type 0x80 and instance tag 0x1
in file 0x4369 is already in use.
Deleting corrupt attribute record (0x80, "")
from file record segment 0x4369.
"chkdsk /scan" is aborting due to self-healing command failure: 0xc0000102
"chkdsk /f" will be required to repair the volume.




Code:
Event[741]:
  Log Name: System
  Source: Volsnap
  Date: 2021-09-12T14:08:31.6520000Z
  Event ID: 14
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: MY-PC.MYDOMAIN.COM
  Description:
The shadow copies of volume H: were aborted because of an IO failure on volume H:.



Code:
Event[7105]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-PnP
  Date: 2021-10-10T09:00:46.9920000Z
  Event ID: 219
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: MY-PC.MYDOMAIN.COM
  Description:
The driver \Driver\MEIx64 failed to load for the device PCI\VEN_8086&DEV_8C3A&SUBSYS_1C3A1458&REV_04\3&11583659&0&B0.
 
Last edited:

My Computer

System One

  • Operating System
    Windows 10

jasonlong

New Member
Local time
11:44 AM
Posts
4
Thread starter
Hello,
Thank you so much for your reply.
I can't find "Tuneup_plus_log.bat" file and as I said, I reinstalled the Chipset and USB drivers.
I did Check Disk as you said:
Code:
C:\>chkdsk /v /b C:

Checking file system on C:
The type of the file system is NTFS.

A disk check has been scheduled.
Windows will now check the disk.                        

Stage 1: Examining basic file system structure ...
  367616 file records processed.                                                        
File verification completed.
 Phase duration (File record verification): 6.89 seconds.
  3577 large file records processed.                                  
 Phase duration (Orphan file record recovery): 0.00 milliseconds.
  0 bad file records processed.                                    
 Phase duration (Bad file record checking): 0.70 milliseconds.

Stage 2: Examining file name linkage ...
  4122 reparse records processed.                                      
  501932 index entries processed.                                                      
Index verification completed.
 Phase duration (Index verification): 1.12 minutes.
  0 unindexed files scanned.                                        
 Phase duration (Orphan reconnection): 294.86 milliseconds.
  0 unindexed files recovered to lost and found.                    
 Phase duration (Orphan recovery to lost and found): 1.09 seconds.
  4122 reparse records processed.                                      
 Phase duration (Reparse point and Object ID verification): 9.69 milliseconds.

Stage 3: Examining security descriptors ...
Cleaning up 1632 unused index entries from index $SII of file 0x9.
Cleaning up 1632 unused index entries from index $SDH of file 0x9.
Cleaning up 1632 unused security descriptors.
Security descriptor verification completed.
 Phase duration (Security descriptor verification): 47.83 milliseconds.
  67159 data files processed.                                          
 Phase duration (Data attribute verification): 0.73 milliseconds.
CHKDSK is verifying Usn Journal...
The USN Journal length 0x59e53db0 in file 0x24 is less the
largest USN encountered, 0x59e53e50, plus eight in file 0x3ece2.
Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...
  367600 files processed.                                                              
File data verification completed.
 Phase duration (User file recovery): 24.53 minutes.

Stage 5: Looking for bad, free clusters ...
  40840298 free clusters processed.                                                      
Free space verification is complete.
 Phase duration (Free space recovery): 0.00 milliseconds.

Windows has made corrections to the file system.
No further action is required.

 255947775 KB total disk space.
  91971668 KB in 293343 files.
    168788 KB in 67160 indexes.
         0 KB in bad sectors.
    446123 KB in use by the system.
     65536 KB occupied by the log file.
 163361196 KB available on disk.

      4096 bytes in each allocation unit.
  63986943 total allocation units on disk.
  40840299 allocation units available on disk.
Total duration: 25.79 minutes (1547732 ms).

Internal Info:
00 9c 05 00 41 80 05 00 5b 20 0a 00 00 00 00 00  ....A...[ ......
44 01 00 00 d6 0e 00 00 00 00 00 00 00 00 00 00  D...............

Windows has finished checking your disk.
Please wait while your computer restarts.

And:
Code:
C:\>chkdsk /v /b D:
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
  128000 file records processed.
File verification completed.
 Phase duration (File record verification): 1.66 seconds.
  2 large file records processed.
 Phase duration (Orphan file record recovery): 0.00 milliseconds.
  0 bad file records processed.
 Phase duration (Bad file record checking): 0.22 milliseconds.

Stage 2: Examining file name linkage ...
  768 reparse records processed.
  148856 index entries processed.
Index verification completed.
 Phase duration (Index verification): 1.02 minutes.
  0 unindexed files scanned.
 Phase duration (Orphan reconnection): 26.66 milliseconds.
  0 unindexed files recovered to lost and found.
 Phase duration (Orphan recovery to lost and found): 1.65 milliseconds.
  768 reparse records processed.
 Phase duration (Reparse point and Object ID verification): 3.69 milliseconds.

Stage 3: Examining security descriptors ...
Cleaning up 143 unused index entries from index $SII of file 9.
Cleaning up 143 unused index entries from index $SDH of file 9.
Cleaning up 143 unused security descriptors.
Security descriptor verification completed.
 Phase duration (Security descriptor verification): 33.69 milliseconds.
  10428 data files processed.
 Phase duration (Data attribute verification): 1.31 milliseconds.

Stage 4: Looking for bad clusters in user file data ...
  127984 files processed.
File data verification completed.
 Phase duration (User file recovery): 3.61 hours.

Stage 5: Looking for bad, free clusters ...
  1503055 free clusters processed.
Free space verification is complete.
 Phase duration (Free space recovery): 0.00 milliseconds.

Windows has scanned the file system and found no problems.
No further action is required.

 307199999 KB total disk space.
 300929956 KB in 117435 files.
     54436 KB in 10430 indexes.
         0 KB in bad sectors.
    203383 KB in use by the system.
     65536 KB occupied by the log file.
   6012224 KB available on disk.

      4096 bytes in each allocation unit.
  76799999 total allocation units on disk.
   1503056 allocation units available on disk.
Total duration: 3.63 hours (13082166 ms).

And:
Code:
C:\>chkdsk /v /b E:
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
  84992 file records processed.
File verification completed.
 Phase duration (File record verification): 640.10 milliseconds.
  1 large file records processed.
 Phase duration (Orphan file record recovery): 0.00 milliseconds.
  0 bad file records processed.
 Phase duration (Bad file record checking): 0.18 milliseconds.

Stage 2: Examining file name linkage ...
  813 reparse records processed.
  85720 index entries processed.
Index verification completed.
 Phase duration (Index verification): 967.78 milliseconds.
  0 unindexed files scanned.
 Phase duration (Orphan reconnection): 6.53 milliseconds.
  0 unindexed files recovered to lost and found.
 Phase duration (Orphan recovery to lost and found): 1.08 milliseconds.
  813 reparse records processed.
 Phase duration (Reparse point and Object ID verification): 3.24 milliseconds.

Stage 3: Examining security descriptors ...
Cleaning up 36 unused index entries from index $SII of file 9.
Cleaning up 36 unused index entries from index $SDH of file 9.
Cleaning up 36 unused security descriptors.
Security descriptor verification completed.
 Phase duration (Security descriptor verification): 10.40 milliseconds.
  364 data files processed.
 Phase duration (Data attribute verification): 0.75 milliseconds.

Stage 4: Looking for bad clusters in user file data ...
  84976 files processed.
File data verification completed.
 Phase duration (User file recovery): 45.26 minutes.

Stage 5: Looking for bad, free clusters ...
  13440786 free clusters processed.
Free space verification is complete.
 Phase duration (Free space recovery): 0.00 milliseconds.

Windows has scanned the file system and found no problems.
No further action is required.

 413560831 KB total disk space.
 359631272 KB in 4898 files.
      2820 KB in 366 indexes.
         0 KB in bad sectors.
    163591 KB in use by the system.
     65536 KB occupied by the log file.
  53763148 KB available on disk.

      4096 bytes in each allocation unit.
 103390207 total allocation units on disk.
  13440787 allocation units available on disk.
Total duration: 45.29 minutes (2717421 ms).

And the HD Tune result is:
Capture-1.PNG


Capture-2.PNG


Capture-3.PNG


Any idea?

Thank you.
 

My Computer

System One

  • Operating System
    Windows 10 Pro

zbook

Active Member
Member
VIP
Local time
5:44 AM
Posts
343
If you can logon to Ten Forums then these scripts should be available:



When available post HD Tune results for each drive.

Please use the scroll bar on the right as necessary so that all of the Health results are viewable.

For any BSOD post a new V2.
 

My Computer

System One

  • Operating System
    Windows 10

jasonlong

New Member
Local time
11:44 AM
Posts
4
Thread starter
If you can logon to Ten Forums then these scripts should be available:



When available post HD Tune results for each drive.

Please use the scroll bar on the right as necessary so that all of the Health results are viewable.

For any BSOD post a new V2.

Hello,
Thank you so much for your reply.
I just have one drive and the health result is:

Capture-4.PNG
 

My Computer

System One

  • Operating System
    Windows 10 Pro

zbook

Active Member
Member
VIP
Local time
5:44 AM
Posts
343
Run Hard Disk Sentinel (free or trial version)

Post images for results on these tabs:

Overview
Temperature
SMART



When available please post Sea Tools results.

Open administrative command prompt and copy and paste:
sfc /scannow
dism /online /cleanup-image /restorehealth
wmic recoveros set autoreboot = false
wmic recoveros set debuginfotype = 7
wmic recoveros get autoreboot
wmic recoveros get debuginfotype
wmic computersystem where name="%computername%" set automaticmanagedpagefile=true
wmic computersystem where name="%computername%" get automaticmanagedpagefile
bcdedit /enum {badmemory}


Post images of the commands with results using one drive, drop box, or google drive into this thread.


Update the progress with the Intel chipset drivers and the Intel driver and support assistant.

Upload a new V2.
 
Last edited:

My Computer

System One

  • Operating System
    Windows 10
Top