Random BSOD during browser

Martin Dendev · 09 Dec 2012

Hi,

It's not my pc, so don't look at the specs.

My brothers computer crashed when he started the browser.

Crash report in attachment. It's just the .dmp file from C:\Windows\Minidump, since the SF Diagnostic Tool didn't work. The folder on the desktop stayed empty.

Thanks in advance!
Martin

koolkat77 · 09 Dec 2012

Please upload your msinfo32.nfo file. To get this: Start Menu -> 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.

Please upload your msinfo32.txt file. To get this: Start Menu -> Type msinfo32 into the Search programs and files box -> When it opens, go to File, Export -> Save as msinfo32.txt and save in a place you will remember -> Let it finish the process of gathering and saving the system info -> Right click the .txt file, click send to compressed (zipped) folder -> Upload the .zip file here.

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

RAM - Test with Memtest86+

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

Errors are sometimes found after 8 passes.

Do this test overnight, before going to bed.

Code:

STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !win32k
    95e67000-95e67038  57 bytes - win32k!itrp_SetRoundValues+95
	[ 8e 5a eb 06 66 c7 40 24:c1 57 8b 3d 04 21 00 96 ]
    95e6703a-95e670cb  146 bytes - win32k!itrp_SetRoundValues+cf (+0x3a)
	[ eb 23 0f bf 50 26 83 c2:00 00 00 2b ce 8b 35 00 ]
    95e670cd-95e670df  19 bytes - win32k!itrp_SetRoundValues+15d (+0x93)
	[ 04 04 04 03 90 90 90 90:21 00 96 8b 15 f8 20 00 ]
    95e670e1-95e67118  56 bytes - win32k!itrp_SetElementPtr+b (+0x14)
	[ 57 8b 3d 04 21 00 96 8b:f9 02 83 f9 01 73 14 a1 ]
    95e6711a-95e67160  71 bytes - win32k!itrp_SetElementPtr+44 (+0x39)
	[ 00 00 00 2b ce 8b 35 00:96 10 11 00 00 5f 8b e5 ]
    95e67163-95e6718d  43 bytes - win32k!itrp_SetElementPtr+8d (+0x49)
	[ 00 00 5e c3 89 35 e8 20:5b 5f 8b e5 5d c3 a1 50 ]
    95e6718f-95e671b9  43 bytes - win32k!itrp_SetElementPtr+b9 (+0x2c)
	[ 90 43 71 e6 95 55 71 e6:00 00 00 00 c3 90 90 90 ]
    95e671bb-95e671c4  10 bytes - win32k!itrp_MINDEX+16 (+0x2c)
	[ 38 8b ca 2b cf c1 f9 02:0d 04 21 00 96 75 2e 8b ]
    95e671c6-95e67257  146 bytes - win32k!itrp_MINDEX+21 (+0x0b)
	[ 73 14 a1 50 21 00 96 c7:00 00 0f b7 72 10 8b 15 ]
    95e67259-95e67263  11 bytes - win32k!itrp_MINDEX+b5 (+0x93)
	[ 00 5f 8b e5 5d c3 90 90:96 83 e8 04 3b df a3 f8 ]
    95e67265-95e6729d  57 bytes - win32k!itrp_FLIPOFF+1 (+0x0c)
	[ c1 8b 0d 04 21 00 96 c6:30 75 0e 8b 81 30 01 00 ]
    95e6729f-95e672a5  7 bytes - win32k!itrp_ALIGNRP+26 (+0x3a)
	[ 96 75 2e 8b 91 30 01:74 66 f6 81 70 01 00 ]
    95e672a7-95e67347  161 bytes - win32k!itrp_ALIGNRP+2e (+0x08)
	[ 00 0f b7 72 10 8b 15 0c:02 74 5d 66 8b 0d 66 21 ]
    95e67349-95e673f4  172 bytes - win32k!itrp_ALIGNRP+d1 (+0xa2)
	[ 81 30 01 00 00 0f b7 50:e5 5d c3 90 90 90 90 90 ]
    95e673f6-95e67408  19 bytes - win32k!itrp_ALIGNRP+17e (+0xad)
	[ 4d f4 ff 15 2c 21 00 96:06 5e c1 f8 02 83 f8 02 ]
    95e6740a-95e67412  9 bytes - win32k!itrp_ALIGNRP+192 (+0x14)
	[ 96 83 2d 1c 21 00 96 01:a1 50 21 00 96 c3 83 ea ]
    95e67414-95e67423  16 bytes - win32k!itrp_ALIGNRP+19c (+0x0a)
	[ 11 ff ff ff 8b 45 f0 5f:15 f8 20 00 96 8b 02 83 ]
    95e67425-95e67427  3 bytes - win32k!itrp_ALIGNRP+1ad (+0x11)
	[ 00 00 5b:96 75 36 ]
    95e67429-95e6743f  23 bytes - win32k!itrp_ALIGNRP+1b1 (+0x04)
	[ e5 5d c3 90 90 90 90 90:12 83 2d 58 21 00 96 01 ]
    95e67441-95e67449  9 bytes - win32k!itrp_RTHG+10 (+0x18)
	[ 00 66 89 56 1c 66 83 3d:96 07 11 00 00 c3 3b 0d ]
    95e6744d-95e6747f  51 bytes - win32k!itrp_RTHG+1c (+0x0c)
	[ 00 8b c1 74 1b 8b 0d 04:73 0b c7 05 4c 21 00 96 ]
    95e67481-95e674a5  37 bytes - win32k!itrp_RTHG+50 (+0x34)
	[ 96 00 00 5e c3 90 90 90:00 01 57 bb ff ff fe ef ]
    95e674a7-95e674ad  7 bytes - win32k!itrp_RoundToHalfGrid+1c (+0x26)
	[ d0 33 d1 7d 14 85 c9:4e 44 8b 46 4c 3b c8 ]
    95e674af-95e674d0  34 bytes - win32k!itrp_RoundToHalfGrid+24 (+0x08)
	[ 10 33 c0 85 c9 0f 9e c0:06 f7 d8 3b c8 75 3c 8b ]
    95e674d2-95e67519  72 bytes - win32k!itrp_JROF+c (+0x23)
	[ 96 8b c2 2b 06 5e c1 f8:00 00 0f b7 4e 6c 51 50 ]
    95e6751b-95e67545  43 bytes - win32k!itrp_JROF+55 (+0x49)
	[ 0b c7 05 4c 21 00 96 07:0f 8b 46 18 8b 0e 23 c3 ]
    95e67547-95e67556  16 bytes - win32k!vSetClearTypeState__FONTCONTEXT+1 (+0x2c)
	[ ff 55 8b ec 53 56 8b 75:ca 2b 0e 5e c1 f9 02 83 ]
    95e67558-95e6755f  8 bytes - win32k!vSetClearTypeState__FONTCONTEXT+12 (+0x11)
	[ 00 80 66 f7 82 f8 00 00:96 10 11 00 00 a1 50 21 ]
    95e67561-95e67569  9 bytes - win32k!vSetClearTypeState__FONTCONTEXT+1b (+0x09)
	[ 00 01 57 bb ff ff fe ef:96 c3 83 ea 04 89 15 f8 ]
    95e6756b-95e67585  27 bytes - win32k!vSetClearTypeState__FONTCONTEXT+25 (+0x0a)
	[ 00 00 02 74 62 f6 46 64:96 8b 12 89 15 0c 21 00 ]
    95e67587-95e67595  15 bytes - win32k!vSetClearTypeState__FONTCONTEXT+41 (+0x1c)
	[ 4e 44 8b 46 4c 3b c8 74:0d 48 67 00 96 57 8b 38 ]
    95e67597-95e675fb  101 bytes - win32k!vSetClearTypeState__FONTCONTEXT+51 (+0x10)
	[ 8e a0 00 00 00 83 b9 98:06 39 58 58 74 7b ff 48 ]
    95e675fd-95e6768b  143 bytes - win32k!vSetClearTypeState__FONTCONTEXT+b7 (+0x66)
	[ 46 18 8b 0e 23 c3 0b c7:40 10 3b cb 8b 16 89 5a ]
    95e6768d-95e6769a  14 bytes - win32k!PFEOBJ::vFreepfdg+33 (+0x90)
	[ a4 ff 95 75 12 ff 70 04:00 8b 35 18 53 00 96 8b ]
    95e6769d-95e676a7  11 bytes - win32k!PFEOBJ::vFreepfdg+43 (+0x10)
	[ 8b 06 89 58 0c eb 54 66:3d ff bb 00 00 77 73 c7 ]
    95e676a9-95e676b0  8 bytes - win32k!PFEOBJ::vFreepfdg+4f (+0x0c)
	[ 80 74 4c 39 99 6c 06 00:00 00 6a 57 e8 fa 07 08 ]
    95e676b2-95e67778  199 bytes - win32k!PFEOBJ::vFreepfdg+58 (+0x09)
	[ 74 44 8b 48 14 80 79 2c:83 7d 20 00 75 26 83 fb ]
    95e6777a-95e67789  16 bytes - win32k!xxxBroadcastMessage+18 (+0xc8)
	[ fc ff ff 3d ff bb 00 00:00 8b 4d 08 81 e1 ff ff ]
    95e6778b-95e677bb  49 bytes - win32k!xxxBroadcastMessage+29 (+0x11)
	[ 6a 57 e8 5a 08 08 00 83:85 7e 04 74 1e ff 36 ff ]
    95e677bd-95e67871  181 bytes - win32k!xxxBroadcastMessage+5b (+0x32)
	[ 00 8b 45 08 85 c0 0f 85:83 c4 0c 83 65 e4 00 8b ]
    95e67873-95e678ee  124 bytes - win32k!xxxBroadcastMessage+111 (+0xb6)
	[ 76 08 8d 4d 08 51 ff 75:70 38 e8 b0 d0 07 00 8b ]
    95e678f0-95e67940  81 bytes - win32k!xxxBroadcastMessage+184 (+0x7d)
	[ ff 75 d0 ff 15 24 b0 fd:33 c9 39 4d e0 74 0a f6 ]
    95e67942-95e6794e  13 bytes - win32k!xxxBroadcastMessage+1d6 (+0x52)
	[ b0 50 e8 21 94 06 00 e9:18 2b c1 0f 84 23 01 00 ]
    95e67950-95e67989  58 bytes - win32k!xxxBroadcastMessage+1e4 (+0x0e)
	[ 6a 02 ff 70 38 e8 10 d1:00 00 48 74 71 48 74 51 ]
    95e6798b-95e67999  15 bytes - win32k!xxxBroadcastMessage+21f (+0x3b)
	[ 8b f0 85 f6 0f 84 ce 01:00 ff 75 20 ff 73 08 ff ]
    95e6799b-95e679a6  12 bytes - win32k!xxxBroadcastMessage+22f (+0x10)
	[ 3f ff ff 3d 9c 02 00 00:75 10 52 56 e8 c3 fb 08 ]
    95e679a9-95e679cd  37 bytes - win32k!xxxBroadcastMessage+23d (+0x0e)
	[ 8b 46 64 0f b7 40 04 8b:ff 75 20 ff 73 08 ff 73 ]
    95e679cf-95e679ec  30 bytes - win32k!xxxBroadcastMessage+263 (+0x26)
	[ 00 33 c9 39 4d e0 74 0a:ff 75 20 ff 75 14 ff 75 ]
    95e679ee-95e67a02  21 bytes - win32k!xxxBroadcastMessage+282 (+0x1f)
	[ 11 03 00 00 75 15 f6 46:1b 77 86 39 4d 14 74 18 ]
    95e67a04-95e67a56  83 bytes - win32k!xxxBroadcastMessage+298 (+0x16)
	[ 84 5a 01 00 00 a1 18 53:b7 c0 89 45 1c 66 85 c0 ]
WARNING: !chkimg output was truncated to 50 lines. Invoke !chkimg without '-lo [num_lines]' to view  entire output.
3999 errors : !win32k (95e67000-95e67fff)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE_4096

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE_4096

BUCKET_ID:  MEMORY_CORRUPTION_LARGE_4096

Followup: memory_corruption
---------