Looks good now. Perhaps noscript is enabled on your browser? It had me puzzled as well until I realized I needed it disabled for this site.
As for the crashes, unfortunately it's looking like the crashes are occurring too late. It appears a driver is corrupting pool memory. We'll need
Driver Verifier enabled. Follow instructions on setting it up, restart, get it to crash the system some, and then send us the resulting crashdumps. If it causes a boot loop, merely enter Safe Mode by tapping F8 key before Windows logo appears at startup, and then disable Driver Verifier there by going back into it and selecting
Delete existing settings. Restart afterwards.
Btw, it may be best - in order to avoid potentially false positives - to do a rundown of all your drivers and update any that needs updating, prior to doing the Driver Verifier thing. If you have a custom system (it looks like you do), go to each part's manufacturer website and download the appropriate updated driver there. Do this for each part in your system. Who knows, this may fix the problem itself!