New
#31
Okay that's great, thanks a lot guys. I'll get a hard drive ordered and give it a while to see if the problems are fixed, then I'll come back and mark this as solved!
Okay that's great, thanks a lot guys. I'll get a hard drive ordered and give it a while to see if the problems are fixed, then I'll come back and mark this as solved!
Hey there, I received my new Hard Drive today and as I was in the middle of Downloading my data onto it, I had another crash. I got a Chrome.exe - Application error and had to shut it down. Is there anything else you think it could be?
In Chrome please try disabling hardware acceleration if it is turned on
- In the right upper corner click on Attachment 380046
- In the menu choose 'settings'
- In the settings scroll down and click 'Show advanced settings'
- Scroll all the way down to the bottom.
- Under the part 'System' you can find 'Use hardware acceleration when available'
- If it is checked, uncheck it
Hardware acceleration uses the hardware to execute functionality faster then with software.
I suspect this may be a problem if it is enabled.
Okay that's done, I'll give it some time and get back to you with some more info if there's another problem, thanks.
No luck, just had another BSOD now, but no minidump file was created, any other ideas?
Please search 'services.msc' and search for a service called "Windows Error Reporting Service"
Make sure the startup type is manual.
Please make sure the page file is at least the size of your physical memory
Virtual Memory Paging File - Change
Just had another BSOD, but a different one this time, it may have been because I changed the dump file to a Kernel dump, to see if that would create one (it didn't).
The BSOD read like this:
KERNEL_DATA_INPAGE_ERROR
Technical Information:
Stop: 0x0000007A (0xFFFFF6FC4000ADE0, 0xFFFFFFFFC000000E, 0x0000000066817860, 0xFFFFF880015BCBA0)
rdyboost.sys - Address FFFFF880015BCBA0 base at FFFFF88001590000, Datestamp 4ce7982e
The startup type was already manual, and I'm pretty sure the page file is big enough.
No, it's the new Hard Drive. Is it possible that it's my SSD Drive?