New
#1
BSOD any time. Ie waching film, surfing or playing game
As i worte in topic, BSOD any time.
Cant understand .bmp files... =)
Please help.
As i worte in topic, BSOD any time.
Cant understand .bmp files... =)
Please help.
Welcome
Please upload your msinfo32.nfo file. To get this:
- Click on the Start
- Type msinfo32 into the Search programs and files box
- When it opens, go to File, Save
- Save as msinfo32.nfo and save in a place you will remember
- Let it finish the process of gathering and saving the system info
- Right click the .nfo file, click send to compressed (zipped) folder
- Upload the .zip file here.
Here you go.
Got an other blue screes doing as you wrote =)
Hmm, is this a new computer?
I've taken a quick look at the dumps, what I can suggest right now is:
Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.STOP 0x00000109: CRITICAL_STRUCTURE_CORRUPTION
Usual causes: Device driver, Breakpoint set with no debugger attached,
Hardware (Memory in particular)
STOP 0x0000001A: MEMORY_MANAGEMENT
Usual causes: Device driver, memory, kernel
→ RAM - Test with Memtest86+
→ Guide to using Memtest86+ - Geeks to Go Forums
Analysis:
Code:Use !analyze -v to get detailed debugging information. BugCheck 1A, {8887, fffffa8001848a80, fffffa8001802d60, 105} Probably caused by : hardware_ram ( ZEROED_PAGE_CORRUPTED )Code:BugCheck 109, {a3a039d8a2a2160c, b3b7465ef51ff416, fffff880014e9bbc, 1} *** WARNING: Unable to verify timestamp for win32k.sys *** ERROR: Module load completed but symbols could not be loaded for win32k.sys Probably caused by : memory_corruptionCode:MODULE_NAME: memory_corruption IMAGE_NAME: memory_corruption FOLLOWUP_NAME: memory_corruption DEBUG_FLR_IMAGE_TIMESTAMP: 0 MEMORY_CORRUPTOR: ONE_BIT FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT Followup: memory_corruption