New
#1
Odd BSOD behaviour
Hello everyone, and I hope you are all doing well.
My laptop has recently been subjected to a few BSODs. The first one was about a few weeks ago. The BSODs typically involved the screen going a pink fuzzy texture (graphics messing up), and restarting. It started showing the blue screen more recently. Sometimes, the computer would start up very slowly, so I decided to open task manager. The ram occasionally decreased from ~6GB to ~1.5 GB (RAM reserved), but it would be quickly rectified upon restarting again.
Blue screen typically stated (IRQL NOT LESS OR EQUAL).
I upgraded to Windows 10 yesterday (from Windows 7 Home Premium), and received another BSOD screen just there. This time it stated (KMODE EXCEPTION NOT HANDLED).
I also ran whocrashed (not sure if it helps), and it said
On Thu 06/08/2015 06:35:47 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80344E7F765, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Thank you for your time, and I hope to hear back soon.
Gerald