New
#1
BSOD when surfing the web with Google Chrome
Hi, I recently got BSOD when surfing the web casually. I've been getting BSOD three times now and I went here to seven forum too see if anyone could help me. I'll upload the dumpfiles.
Hi, I recently got BSOD when surfing the web casually. I've been getting BSOD three times now and I went here to seven forum too see if anyone could help me. I'll upload the dumpfiles.
Point toward memory management and memory corruption.
Memtest86+
Run Memtest86+ for at least 8-10 passes. It may take up to 20 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold. How to Test and Diagnose RAM Issues with Memtest86+
NotePay close attention to part 3 of the tutorial in order to rule the faulty RAM stick out.
TipDo this test overnight.
BSOD BUGCHECK SUMMARY
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {403, fffff680000a3338, e0100001bcc1a867, fffff680001f4bca} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+3211c ) Followup: MachineOwner ---------Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 4E, {99, 1ded66, 7, 1} Probably caused by : memory_corruption ( nt!MiBadShareCount+4c ) Followup: MachineOwner ---------Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1A, {41284, 6c0a001, 63d6, fffff70001080000} Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4ad3 ) Followup: MachineOwner ---------