Random BSOD app/data--- wer sysdata.xml

This originally had x32 processor and has been changed to x64 a couple of days ago. I have ran suggested scan because the BSOD is rather random. After a fresh install of Windows Ultimate x64 I have installed all suggested updates from what I can see however still get this BSOD. Racking my brain now, is there a solution other than any hardware replacement?

Thank you in advance!!

We need more information, it seems an unidentified driver is causing pool corruption.

Please enable Driver Verifier following these instructions.

Driver Verifier - Enable and Disable

Thank you for the quick reply,
Before recieving your response, I read this morning, that the BSOD could be caused by my browser. I was running firefox for x32, so I changed over to Waterfox for x64. Thus far, I haven't had any BSOD today. I'm not sure if that was the fix, sooo, about 10 minutes ago, I also followed your instructions to begin verifier, just in case.

Crossing Fingers!!!
Thanks again!!!

Ok, so after switching my browser and starting the verifier as suggested yesturday, I still got 2 BSOD. I copied their information for both times, and also did another dm log. Is there anything else that I can provide you, to better see the problem?

Thanks in advance,

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: c1
BCP1: FFFFF9801CA9CE70
BCP2: FFFFF9801CA9C185
BCP3: 0000000000574198
BCP4: 0000000000000032
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\032114-34226-01.dmp
C:\Users\tenacity\AppData\Local\Temp\WER-142148-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt


-------------------------------------------------------------------------------------
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033

Additional information about the problem:
BCCode: c1
BCP1: FFFFF98012E22C60
BCP2: FFFFF98012E22A05
BCP3: 0000000000BF03A0
BCP4: 0000000000000032
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\032114-30232-01.dmp
C:\Users\tenacity\AppData\Local\Temp\WER-13912855-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

There appears to be memory corruption, can you please run memtest86 for at least 8 passes?

RAM - Test with Memtest86+

Your Realtek Network Interface Controller seems to be causing problems.

Can you download the Windows 7 driver from here.

Realtek

Code:

Probably caused by : Rtnic64.sys ( Rtnic64+395f )

Code:

fffff880`049de000 fffff880`049f0000   Rtnic64  T (no symbols)           
    Loaded symbol image file: Rtnic64.sys
    Image path: \SystemRoot\system32\DRIVERS\Rtnic64.sys
    Image name: Rtnic64.sys
    Timestamp:        Thu Jul 23 15:03:10 2009 (4A686D9E)
    CheckSum:         0000FDB9
    ImageSize:        00012000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

I've always believed in the saying. If it ain't broke, don't fix it. So unless you get problems I would go around messing with the BIOS.

Gotcha, Thanks! I'll get back to you tomorrow in regards to BSOD. So far so good though.

Thanks again!!!

After running memtest86 as suggested, I believe you have helped me solve this crazy BSOD. 1st I ran test with all RAM. Between 47%-63% of each pass I received approx. 100 errors each pass. Then I removed all Ram running test with one stick at a time. Found the culprit that was spawning all the errors and for the 1st time,,, threw something to do with a computer,,, into the trash.. lol! Also put the other 2 sticks in and ran the test again, to make sure there was no compatibility problem. Will keep computer on through the night to watch for BSOD. But I really think this is the end of my immediate concerns.

Thank you again ,
Tenacity

That's excellent news :)
If the problem has been solved don't forget to mark the thread as solved.
Any more problems let me know :)