Vembutech :
Hi,
When a bugcheck of 0x19 with a code of 22 would generally mean the problem is with the device driver.
Try to free the same memory location twice. Even though the first one works correctly, the second one might have a chance to get failed because it is not owned by the driver anymore and causes a bug check.
Most of the time you have to actually look at the memory.dmp file and to figure out what driver had did this. You might have to enable special tracking to find out with driver verifier also.
You can also get this with certain malware attacks. (scan with malwarebytes to fix)
Hope this information helps..!!!
Thanks for the info. I restarted and logged in with another user and received a dump file that was much smaller. I took a look at it, and it mentioned possible problems with halmacpi.dll, IDSvix86.sys, and ntkrnlpa.exe (for some reason I didn't get these the first time).
It looks like IDSvix86.sys is used by Symantec AV. I took a look at the Symantec client, and it was complaining about certain errors. I decided to uninstall Symantec and re-install. It's installing now. I'll try that out, make sure Symantec is running okay, and see how it goes.