STOP: 0x000000BE an attempt was made to write to read-only memory

Several issues here, I'm expecting it to be a long battle. The Latest STOP error recieved is:
STOP: 0x000000B (0xFFFFF88000080F70, 0x000000000EC0121, 0xFFFF880009A8C30, 0x000000000000000B)

This occurred after a boot disk chkdsk of the primary partition (C:).

Earlier that day a PAGE_FAULT_IN_NON_PAGED_AREA was also received.
Ntfs.sys

STOP: 0x00000050 (0xFFFFF8800368540, 0x0000000000000000, 0xFFFFF88012EFAFD, 0x0000000000000000)

Ntfs.sys - address FFFFF880012EFAFD base at FFFF8800124D000, Datestamp 4a5bc14f

I have tried a few things with UBCD, chkdsk, and driver updates. Just ready to start somewhere new.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

"Rylet" wrote in message news:29843875-61da-4657-a865-3a6f99452c84...
 
The STOP 50 error is a common result of a rootkit virus - have you run any
decent scanners over the drive from an external boot?
 
 
 
--
Noel
 
 

Noel Paton | Nil Carborundum Illegitemi | CrashFixPC
Noel Paton
Nil Carborundum Illegitemi -
No, I don't work for Microsoft!
http://www.crashfixpc.co.uk

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Yes I have run a virus scan both localy and sandbox style from a computer that I know is not infected via a USB SATA cable. No virus' found. Also, I ran memtest86+ all night last night. 13 passes with zero errors.

After trying to play some WoW two more stop errors were thrown today.

dxgmms1.sys STOP: 0x0000007E (0xFFFFFFFFC000005, 0xFFFFF88003F898C7,0xFFFFF88013C696D8, 0xFFFFF88013C68F40) Date stamp 4a5bc578

after shutting down and waiting a few min, durring restart:
fwpkclnt.sys
an attempt was made to write to read-only memory

STOP: 0c000000BE ( 0xFFFFF880001EF3388 //rest of paramaters lost because computer restarted)

Let me know if the AVG Free scans are not enough and or the next step, or if there is any info that you need! Thanks! -Ry

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

"Rylet" wrote in message news:5291bf3d-c1f6-41d9-a45b-018b19477b37...
> Yes I have run a virus scan both localy and sandbox style from a computer
> that I know is not infected via a USB SATA cable. No virus' found. Also, I
> ran memtest86+ all night last night. 13 passes with zero errors.
>
> After trying to play some WoW two more stop errors were thrown today.
>
> dxgmms1.sys STOP: 0x0000007E (0xFFFFFFFFC000005,
> 0xFFFFF88003F898C7,0xFFFFF88013C696D8, 0xFFFFF88013C68F40) Date stamp
> 4a5bc578
>
> after shutting down and waiting a few min, durring restart:
> fwpkclnt.sys
> an attempt was made to write to read-only memory
>
> STOP: 0c000000BE ( 0xFFFFF880001EF3388 //rest of paramaters lost because
> computer restarted)
>
> Let me know if the AVG Free scans are not enough and or the next step, or
> if there is any info that you need! Thanks! -Ry
>
 
AVG should be OK - it's not the best, but it's good enough for most things.
Try running MalwareBytes Anti-Malware over the disk - it will probably find
some to complain about - do a local scan, so it can scan the registry as
well.
 
Have you ever had Zone Alarm installed on that machine? Which firewall are
you currently using?
 
The variety of errors you are getting is very suggestive of a hardware
failure - How old is the machine?
For a while, a huge number of machines were using faulty capacitors, so if
it's from that era, it's worth opening the box and looking at the caps to
see if any look like they're leaking, or the end is doming.
 
--
Noel
 
 

Noel Paton | Nil Carborundum Illegitemi | CrashFixPC
Noel Paton
Nil Carborundum Illegitemi -
No, I don't work for Microsoft!
http://www.crashfixpc.co.uk

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Trying things again...  Trying things wastes time and leads to frustration!

What things did you try with UBCD, chdksk and driver updates?

If you made the UBCD yourself (or did you borrow it), you have a genuine bootable XP installation CD, right?

Does your computer boot okay and you see these messages sometime or does your computer no longer boot?

AVG scans are mediocre.  I personally gave up on AVG years ago.

 

Perform some scans for malicious software, then fix any remaining issues:

Download, install, update and do a full scan with these free malware detection programs:

 

Malwarebytes (MBAM):  http://malwarebytes.org/

SUPERAntiSpyware: (SAS):  http://www.superantispyware.com/

 

They can be uninstalled later if desired.

 

WoW is comupter intensive - does your system meet the minuimum requirements for playing Wow?

Does your computer work okay if you are not playing Wow?

Sometimes systems are not quite up to WoW and things work great until folk start gaming and then things go downhill (while gaming).  As players get more into it they play more often and more intensely and then the number of problems also increase (naturally).

f you are not sure if your computer meets the minimum requirements for Wow or just want another set of eyeballs on your configuration, do this:

Click Start, Run and in the box enter:

msinfo32

Click OK, and when the System Summary info appears, click Edit, Select All, Copy and then paste the information back here.

There will be some personal information (like System Name and User Name), and whatever appears to be private information to you, just delete it from the pasted information.

For video driver information, expand the Components, click Display, click Edit, Select All, Copy and then paste the information here as well.

 


 

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

With UBCD, yes (tried both chkdsk and driver updates). Yes is was self made. And yes I have a genuine bootable Windows 7 DVD. 

The computer usually boots fine. The only time it does not (boot fine) is when a blue screen has just previously been thrown and I'm trying to get back to the OS.

 

The Blue screen's occur both wile playing WoW and general computer use like listening to music and browsing the internet. However, the occurances are much more frequent when trying to play WoW. The computer is fairly new, I built it for my roommate about a year and a half ago. I'm sure it's above the minimum requirements for most games, not just WoW. WoW is actually less "computer intensive" then other games previously played on this computer (i.e. SPORE).

Thank you for the software suggestions. I pulled the HDD out and ran scans with both softwares from a different computer. The drive is back in the computer it is supposed to be now and I'm running the scans locally before trying to get another blue screen (by playing WoW). 

Here is some of the system and display info you requested. I will post results of the scans and/or my next blue screen. Thanks for all the help!

-Ry

OS Name Microsoft Windows 7 Professional

Version 6.1.7600 Build 7600

Other OS Description Not Available

OS Manufacturer Microsoft Corporation

System Name USER-PC

System Manufacturer System manufacturer

System Model System Product Name

System Type x64-based PC

Processor AMD Athlon(tm) 64 X2 Dual Core Processor 6400+, 3209 Mhz, 2 Core(s), 2 Logical Processor(s)

BIOS Version/Date American Megatrends Inc. 1406, 11/21/2008

SMBIOS Version 2.5

Windows Directory C:\Windows

System Directory C:\Windows\system32

Boot Device \Device\HarddiskVolume1

Locale United States

Hardware Abstraction Layer Version = "6.1.7600.16385"

User Name User-PC\User

Time Zone Eastern Daylight Time

Installed Physical Memory (RAM) 2.00 GB

Total Physical Memory 2.00 GB

Available Physical Memory 945 MB

Total Virtual Memory 4.00 GB

Available Virtual Memory 2.58 GB

Page File Space 2.00 GB

Page File C:\pagefile.sys

 

Video Info

NameNVIDIA GeForce 9800 GT

PNP Device IDPCI\VEN_10DE&DEV_0614&SUBSYS_829D1043&REV_A2\4&2ACE1B05&0&0010

Adapter TypeGeForce 9800 GT, NVIDIA compatible

Adapter DescriptionNVIDIA GeForce 9800 GT

Adapter RAM512.00 MB (536,870,912 bytes)

Installed Driversnvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um

Driver Version8.17.11.9745

INF Fileoem8.inf (Section003 section)

Color PlanesNot Available

Color Table Entries4294967296

Resolution1680 x 1050 x 59 hertz

Bits/Pixel32

Memory Address0xFD000000-0xFDFFFFFF

Memory Address0xD0000000-0xDFFFFFFF

Memory Address0xFA000000-0xFE6FFFFF

I/O Port0x00009800-0x0000987F

IRQ ChannelIRQ 18

I/O Port0x000003B0-0x000003BB

I/O Port0x000003C0-0x000003DF

Memory Address0xA0000-0xBFFFF

Driverc:\windows\system32\drivers\nvlddmkm.sys (8.17.11.9745, 13.17 MB (13,807,976 bytes), 4/3/2010 10:55 PM)



P.S. Sorry bout the format, kinda hard to read...

 

 


 

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Well, I do not feel qualified with resolving BSOD in Windows 7 yet but I will be happy to at least look at your BSOD info and see what I can see.  I do not have a feel for doing crash dump analysis on Windows 7 yet (XP crash dumps I can understand) or I would get you to send me some of the crash dumps and I would be able to point you in a better direction.

Download BlueScreenView from here:

 

http://www.nirsoft.net/utils/blue_screen_view.html

Unzip and run it (it does not install anything) and let it finish scanning all your dump files.  Select the most recent dump files by clicking them and holding down the Ctrl key to select multiples files.  

Try to select just the most recent ones that relate to your issue - maybe 5-10 crash dumps.

Click File, Save Selected Items and save the information from the crash dumps to a text file on your desktop called BSOD.txt.  Open BSOD.txt with a text editor, copy all the text and paste it into your next reply.

See if there is some kind of repeatable pattern in your BSOD informations from BSV...

Thanks for the msinfo32 info, I don't see anything jumping out at me.  

It does not sound like malicious software (these BSODs), but I just like to reduce the number of variables in my favor when troublehooting.  If we don't know what it is, we'll know what it's not.

Have you check the NVIDIA WWW page to see if there is a later video driver for Windows 7?  I would do it for you, but can't right now.

 

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Noel, 

Zone Alarm has never been run on the machine. I opened the tower and took a look at the caps, they look okay to me but I didn't feel like taking the board out of the tower to get the closer inspection just yet... heh. Also, currently just using windows firewall.

 

I have double and triple checked my drivers. And I'm pretty sure I'm subscribed to my graphics card newsletter by now... 

10 Most Recent BlueScreenView Crash Reports:

==================================================

Dump File         : 053010-37565-01.dmp

Crash Time        : 5/30/2010 9:38:25 PM

Bug Check String  : PAGE_FAULT_IN_NONPAGED_AREA

Bug Check Code    : 0x00000050

Parameter 1       : ffffffff`fffffffc

Parameter 2       : 00000000`00000000

Parameter 3       : fffff800`02db3750

Parameter 4       : 00000000`00000000

Caused By Driver  : dxgkrnl.sys

Caused By Address : dxgkrnl.sys+2333

File Description  : 

Product Name      : 

Company           : 

File Version      : 

Processor         : x64

Computer Name     : 

Full Path         : C:\Windows\Minidump\053010-37565-01.dmp

Processors Count  : 2

Major Version     : 15

Minor Version     : 7600

==================================================

 

==================================================

Dump File         : 052910-36863-01.dmp

Crash Time        : 5/29/2010 10:32:22 PM

Bug Check String  : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Bug Check Code    : 0x1000007e

Parameter 1       : ffffffff`c0000005

Parameter 2       : fffff880`03f898c7

Parameter 3       : fffff880`13c696d8

Parameter 4       : fffff880`13c68f40

Caused By Driver  : hal.dll

Caused By Address : hal.dll+f64c

File Description  : 

Product Name      : 

Company           : 

File Version      : 

Processor         : x64

Computer Name     : 

Full Path         : C:\Windows\Minidump\052910-36863-01.dmp

Processors Count  : 2

Major Version     : 15

Minor Version     : 7600

==================================================

 

==================================================

Dump File         : 052910-37580-01.dmp

Crash Time        : 5/29/2010 3:14:43 PM

Bug Check String  : NTFS_FILE_SYSTEM

Bug Check Code    : 0x00000024

Parameter 1       : 00000000`001904fb

Parameter 2       : fffff880`02fc5918

Parameter 3       : fffff880`02fc5180

Parameter 4       : fffff800`02acb4e6

Caused By Driver  : Ntfs.sys

Caused By Address : Ntfs.sys+213d8

File Description  : 

Product Name      : 

Company           : 

File Version      : 

Processor         : x64

Computer Name     : 

Full Path         : C:\Windows\Minidump\052910-37580-01.dmp

Processors Count  : 2

Major Version     : 15

Minor Version     : 7600

==================================================

 

==================================================

Dump File         : 052810-24070-01.dmp

Crash Time        : 5/28/2010 11:35:17 PM

Bug Check String  : PAGE_FAULT_IN_NONPAGED_AREA

Bug Check Code    : 0x00000050

Parameter 1       : fffff880`077d4050

Parameter 2       : 00000000`00000000

Parameter 3       : fffff800`02bbd98c

Parameter 4       : 00000000`00000000

Caused By Driver  : dxgkrnl.sys

Caused By Address : dxgkrnl.sys+307f

File Description  : 

Product Name      : 

Company           : 

File Version      : 

Processor         : x64

Computer Name     : 

Full Path         : C:\Windows\Minidump\052810-24070-01.dmp

Processors Count  : 2

Major Version     : 15

Minor Version     : 7600

==================================================

 

==================================================

Dump File         : 052810-22885-01.dmp

Crash Time        : 5/28/2010 6:58:44 PM

Bug Check String  : PAGE_FAULT_IN_NONPAGED_AREA

Bug Check Code    : 0x00000050

Parameter 1       : fffff880`03685040

Parameter 2       : 00000000`00000000

Parameter 3       : fffff880`012efafd

Parameter 4       : 00000000`00000000

Caused By Driver  : ntoskrnl.exe

Caused By Address : ntoskrnl.exe+70600

File Description  : NT Kernel & System

Product Name      : Microsoft® Windows® Operating System

Company           : Microsoft Corporation

File Version      : 6.1.7600.16539 (win7_gdr.100226-1909)

Processor         : x64

Computer Name     : 

Full Path         : C:\Windows\Minidump\052810-22885-01.dmp

Processors Count  : 2

Major Version     : 15

Minor Version     : 7600

==================================================

 

==================================================

Dump File         : 052810-28750-01.dmp

Crash Time        : 5/28/2010 5:50:44 PM

Bug Check String  : ATTEMPTED_WRITE_TO_READONLY_MEMORY

Bug Check Code    : 0x000000be

Parameter 1       : fffff880`02a94ff4

Parameter 2       : 00000000`7ad32121

Parameter 3       : fffff880`02c35720

Parameter 4       : 00000000`0000000b

Caused By Driver  : athrx.sys

Caused By Address : athrx.sys+7cff4

File Description  : 

Product Name      : 

Company           : 

File Version      : 

Processor         : x64

Computer Name     : 

Full Path         : C:\Windows\Minidump\052810-28750-01.dmp

Processors Count  : 2

Major Version     : 15

Minor Version     : 7600

==================================================

 

==================================================

Dump File         : 052810-26410-01.dmp

Crash Time        : 5/28/2010 5:03:25 PM

Bug Check String  : PAGE_FAULT_IN_NONPAGED_AREA

Bug Check Code    : 0x00000050

Parameter 1       : fffff880`06c41fa0

Parameter 2       : 00000000`00000000

Parameter 3       : fffff880`03f710a1

Parameter 4       : 00000000`00000000

Caused By Driver  : nvlddmkm.sys

Caused By Address : nvlddmkm.sys+7606f0

File Description  : 

Product Name      : 

Company           : 

File Version      : 

Processor         : x64

Computer Name     : 

Full Path         : C:\Windows\Minidump\052810-26410-01.dmp

Processors Count  : 2

Major Version     : 15

Minor Version     : 7600

==================================================

 

==================================================

Dump File         : 052710-27612-01.dmp

Crash Time        : 5/27/2010 7:58:49 PM

Bug Check String  : ATTEMPTED_WRITE_TO_READONLY_MEMORY

Bug Check Code    : 0x000000be

Parameter 1       : fffff880`01afd9b0

Parameter 2       : 80000000`02ed0121

Parameter 3       : fffff880`02c1f800

Parameter 4       : 00000000`0000000b

Caused By Driver  : hal.dll

Caused By Address : hal.dll+f64c

File Description  : 

Product Name      : 

Company           : 

File Version      : 

Processor         : x64

Computer Name     : 

Full Path         : C:\Windows\Minidump\052710-27612-01.dmp

Processors Count  : 2

Major Version     : 15

Minor Version     : 7600

==================================================

 

==================================================

Dump File         : 052610-24944-01.dmp

Crash Time        : 5/26/2010 8:59:37 PM

Bug Check String  : MEMORY_MANAGEMENT

Bug Check Code    : 0x0000001a

Parameter 1       : 00000000`00005003

Parameter 2       : fffff781`c0000000

Parameter 3       : 00000000`00004a57

Parameter 4       : fffff8a0`02e59009

Caused By Driver  : nvlddmkm.sys

Caused By Address : nvlddmkm.sys+1be63f

File Description  : 

Product Name      : 

Company           : 

File Version      : 

Processor         : x64

Computer Name     : 

Full Path         : C:\Windows\Minidump\052610-24944-01.dmp

Processors Count  : 2

Major Version     : 15

Minor Version     : 7600

==================================================

 

==================================================

Dump File         : 052610-27877-01.dmp

Crash Time        : 5/26/2010 7:56:02 PM

Bug Check String  : PAGE_FAULT_IN_NONPAGED_AREA

Bug Check Code    : 0x00000050

Parameter 1       : fffff880`08ecffa0

Parameter 2       : 00000000`00000001

Parameter 3       : fffff880`019b66c4

Parameter 4       : 00000000`00000002

Caused By Driver  : ntoskrnl.exe

Caused By Address : ntoskrnl.exe+70600

File Description  : NT Kernel & System

Product Name      : Microsoft® Windows® Operating System

Company           : Microsoft Corporation

File Version      : 6.1.7600.16539 (win7_gdr.100226-1909)

Processor         : x64

Computer Name     : 

Full Path         : C:\Windows\Minidump\052610-27877-01.dmp

Processors Count  : 2

Major Version     : 15

Minor Version     : 7600

==================================================

 

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

"Rylet" wrote in message news:ffe04542-c486-486f-8809-a9bed81248ec...
> Noel,
>
> Zone Alarm has never been run on the machine. I opened the tower and took
> a look at the caps, they look okay to me but I didn't feel like taking the
> board out of the tower to get the closer inspection just yet... heh. Also,
> currently just using windows firewall.
>
>
>
 
 
OK - thanks for the info
 
A number of those errors are the 0x00000050 fault that I was concerned
about - which is often the result of an infection with rootkit.
http://support.microsoft.com/kb/903251
or having bad video drivers
http://support.microsoft.com/kb/329293
or bad/incorrect RAM
http://support.microsoft.com/kb/315335
http://support.microsoft.com/kb/171003 - for Win2k/NT, but the same idea
applies
 
IIRC, you've already run MemTest? if not pleas download if from
www.memtest.org and run it for a few hours to check the RAM.
You have 2GB Ram installed - are the sticks identical (i.e. bought as a
matched pair/threesome), or from different batches or manufacturers?
Sometimes while the testers work fine, they don't pick up on slight
mismatches between sticks of RAM, and Windows is getting more and more
sensitive to this - with the result that you get unpredictable STOP errors.
The only way to test is to take one of the sticks out, and try to repro the
error, rinse and repeat :)
 
HTH
 
 
--
Noel
 
 

Noel Paton | Nil Carborundum Illegitemi | CrashFixPC
Noel Paton
Nil Carborundum Illegitemi -
No, I don't work for Microsoft!
http://www.crashfixpc.co.uk

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Yes you read correctly, I ran memtest86+ two nights ago with 13 passes and zero errors. Something to mention about the memtest though, as soon as I pressed [Esc] to abort the 14th test and reboot to the OS, a bluescreen was received. I can not remember which one it was but if I had to guess... I think it was the "An attempt was made to write to read-only memory." After a restart, the OS loaded fine.

The 2 sticks of RAM are identical, bought as a matched pair. Because RAM is usually the case, I have already tried pulling one out and running memtest. I have also tried the RAM in a different computer altogether. It tested fine in that tower two... :-/. If there is a different test/results from a different test anyone would like to see, please let me know.

Should I try the "fix it" procedures in your previous links Noel? Even though they are for a different operating system then Windows 7?
(i.e. http://support.microsoft.com/kb/903251)

While both sticks of RAM were in this morning another blue screen was thrown after just 25 min of WoW play.

==================================================
Dump File         : 053110-35880-01.dmp
Crash Time        : 5/31/2010 8:56:39 AM
Bug Check String  : NTFS_FILE_SYSTEM
Bug Check Code    : 0x00000024
Parameter 1       : 00000000`001904fb
Parameter 2       : fffff880`07b8e3b8
Parameter 3       : fffff880`07b8dc20
Parameter 4       : fffff880`0121ac4a
Caused By Driver  : Ntfs.sys
Caused By Address : Ntfs.sys+8c4a
File Description  : 
Product Name      : 
Company           : 
File Version      : 
Processor         : x64
Computer Name     : 
Full Path         : C:\Windows\Minidump\053110-35880-01.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 7600
==================================================

//Side note: I have not been able to repro any of the errors while Notplaying WoW. As soon as I get one that occurs during more common computer use it shall be posted. Thanks!

-Ry

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

"Rylet" wrote in message news:c3c3f552-a2b2-4469-955a-e2850708fac5...
 
> Should I try the "fix it" procedures in your previous links Noel? Even
> though they are for a different operating system then Windows 7?
> (i.e. http://support.microsoft.com/kb/903251)
>
 
Definitely NOT! - those fixits are for use in particular circumstances, and
yours meet non of them.
 
Hmmm - the fact that you can't get the system to fail unless you are running
WoW leads to an inevitable thought - that it's WoW itself causing the
problem (or at least most of it)
You need to check out the WoW forums, and see if anyone there has similar
problems (and then post back here with the answer!<g\>)
 
NTFS.sys is one of the major files controlling access to the HD - have you
run a CHKDSK? how about running the disk manufacturer's test utility over
the drive/disk??
 
 
--
Noel
 
 

Noel Paton | Nil Carborundum Illegitemi | CrashFixPC
Noel Paton
Nil Carborundum Illegitemi -
No, I don't work for Microsoft!
http://www.crashfixpc.co.uk

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

 
 

Question Info


Last updated December 14, 2021 Views 44,565 Applies to: