Windows 7: Constant BSOD

jkm1687 · 08 Jan 2013

Hello so ive been getting different bsods for about a week now and could really use some help. Ive tried a reformat, messing with drivers and even changed my power supply but still keep getting them about once a day atleast. Below is a minidump i beleive i did it right. i will post another after it happens again but any advice on the issue would be appreciated,

Thanks so much

koolkat77 · 08 Jan 2013

Welcome to SevenForums.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8800c366a28, 0, fffff96000142a82, 1}


Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!PostMessageExtended+292 )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff8800c366a28, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff96000142a82, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000001, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030fc100
GetUlongFromAddress: unable to read from fffff800030fc1c0
 fffff8800c366a28 Nonpaged pool

FAULTING_IP: 
win32k!PostMessageExtended+292
fffff960`00142a82 488b8c24b8000000 mov     rcx,qword ptr [rsp+0B8h]

MM_INTERNAL_CODE:  1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  firefox.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff8800c2e67e0 -- (.trap 0xfffff8800c2e67e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff900c06651e8 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff96000142a82 rsp=fffff8800c2e6970 rbp=0000000000000000
 r8=000000000000c1ac  r9=0000000000000000 r10=fffffa8009dddf80
r11=fffff900c2641ce0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
win32k!PostMessageExtended+0x292:
fffff960`00142a82 488b8c24b8000000 mov     rcx,qword ptr [rsp+0B8h] ss:0018:fffff880`0c2e6a28=206e180100000000
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e5cad4 to fffff80002eccfc0

STACK_TEXT:  
fffff880`0c2e6678 fffff800`02e5cad4 : 00000000`00000050 fffff880`0c366a28 00000000`00000000 fffff880`0c2e67e0 : nt!KeBugCheckEx
fffff880`0c2e6680 fffff800`02ecb0ee : 00000000`00000000 fffff880`0c366a28 fffffa80`0b1d4b00 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x45212
fffff880`0c2e67e0 fffff960`00142a82 : 00000000`00000000 00000000`00000000 fffff880`009ea180 fffffa80`0b1d4c58 : nt!KiPageFault+0x16e
fffff880`0c2e6970 fffff960`00142d61 : fffff900`c2641ce0 00000000`0000c1ac 00000000`74b62450 00000000`01186e20 : win32k!PostMessageExtended+0x292
fffff880`0c2e6a10 fffff960`001427b9 : 00000000`00000000 00000000`01186e20 00000000`0001028e fffff880`0c2e6af8 : win32k!PostMessageCheckIL+0x1c9
fffff880`0c2e6a80 fffff800`02ecc253 : fffffa80`0b1d4b50 fffff880`0c2e6b60 00000000`00000000 00000000`00000020 : win32k!NtUserPostMessage+0xed
fffff880`0c2e6ae0 00000000`74bafeca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0137e478 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74bafeca


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!PostMessageExtended+292
fffff960`00142a82 488b8c24b8000000 mov     rcx,qword ptr [rsp+0B8h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  win32k!PostMessageExtended+292

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  50ad9b54

FAILURE_BUCKET_ID:  X64_0x50_win32k!PostMessageExtended+292

BUCKET_ID:  X64_0x50_win32k!PostMessageExtended+292

Followup: MachineOwner
---------

Code:

STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA   

Usual causes:  Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus,  Device driver, NTFS corruption, BIOS

Hard to say anything with one .dmp file. But seeing it's usual causes...
If you are overclocking any hardware, STOP. Reset any changed values back to default.

Upload a screenshot of your hard disk using CrystalDiskInfo:

Make a hard drive test from the hard drive manufacturers website:

Hard Drive Diagnostic Procedure

Run Disk Check on your hard disk for file system errors and bad sectors on it:

Disk Check

Hard drive test both short and long with:

SeaTools for Windows

Also the DOS version of:

SeaTools for DOS
SeaTools for DOS tutorial

Perform a System File Check:

Click on the start
Type CMD on Search
Left click and Run as Administrator
Type SFC /scannow

Full tutorial here:

SFC /SCANNOW Command - System File Checker

Reduce items at start-up. Nothing except anti-virus is required:

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

RAM - Test with Memtest86+

Quote:

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.

Information

Errors are sometimes found after 8 passes.

Tip

Do this test overnight, before going to bed.

Let us know the results.

jkm1687 · 08 Jan 2013

Thanks for the reply,

Ive uploaded a screenshot with crystal disk
Ran Disk Check came up fine
Ran a System file check came up fine

I cant run any of the other harddrive tests because i dont have a optical drive, Tonight im gunna run the ram test and will let ya know the results tommorow. Also next bsod i get ill post the minidump again, may be a day or 2.

koolkat77 · 08 Jan 2013

Looks OK.

Thanks.

jkm1687 · 08 Jan 2013

any tips on how to get memtest to run off my usb stick, i installed the installer on it and it wont boot when i choose boot usb it still loads windows and when i go to the boot menu it doesnt show the usb drive. any tips or advice would be sweet

Britton30 · 08 Jan 2013

It won't work by putting the installer on the flash drive. you have to use the installer to install it to the flash.

Quote: Originally Posted by jonathanking

1. Download the latest version of the "Auto-installer for USB Key (Win 9x/2k/xp/7)" from this link: Memtest86+ - Advanced Memory Diagnostic Tool

2. Plug in an empty USB key drive. Size is no concern, as the actual files take up 180 KB of space.

3. Go into the .zip folder you downloaded, and double-click on the .exe file inside.

4. Follow the setup utility. To reduce the risk of problems, it is advised to format the drive.
Attachment 92455

Tip, click the Attachment to see what you should see.
You may have to enter your one-time boot menu and select the USB stick manually.

jkm1687 · 08 Jan 2013

Thanks for the reply, I figured out how to run memtest so ill let that run tonight, Here is the latest dump file from tonights bluescreen aswell. Ill post memtest results in the morning,

koolkat77 · 08 Jan 2013

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050031, 406f8, fffff80003084401}

Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000406f8
Arg4: fffff80003084401

Debugging Details:
------------------


BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80003084569 to fffff80003084fc0

STACK_TEXT:  
fffff880`009f0ce8 fffff800`03084569 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000406f8 : nt!KeBugCheckEx
fffff880`009f0cf0 fffff800`03082a32 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`009f0e30 fffff800`03084401 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
00000000`0000002b 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x1a6


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiDoubleFaultAbort+b2
fffff800`03082a32 90              nop

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiDoubleFaultAbort+b2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  503f82be

FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

Followup: MachineOwner
---------

Doesn't say much but there are lot of Nvidia drivers & Direct X errors.

Code:

fffff880`02706a08  fffff880`04408077 dxgmms1!VidSchDdiNotifyInterruptWorker+0xef
fffff880`02706a58  fffff880`04407f76 dxgmms1!VidSchDdiNotifyInterrupt+0x9e
fffff880`02706a88  fffff880`044e013f dxgkrnl!DxgNotifyInterruptCB+0x83
fffff880`02706ab8  fffff880`0590dae5*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
 nvlddmkm+0xb4ae5
fffff880`02706ad8  fffff800`03379ed4 nt!ObpIncrementHandleCountEx+0x414
fffff880`02706ae0  fffff880`0590da8b nvlddmkm+0xb4a8b
fffff880`02706af8  fffff880`0440e691 dxgmms1!VidSchiUpdateCurrentIsrFrameTime+0x95
fffff880`02706b28  fffff880`044083f1 dxgmms1!VidSchiProcessIsrVSync+0xc9
fffff880`02706b48  fffff880`0590dd2d nvlddmkm+0xb4d2d
fffff880`02706b68  fffff880`0440e691 dxgmms1!VidSchiUpdateCurrentIsrFrameTime+0x95
fffff880`02706b98  fffff880`044083f1 dxgmms1!VidSchiProcessIsrVSync+0xc9
fffff880`02706bb8  fffff880`04408077 dxgmms1!VidSchDdiNotifyInterruptWorker+0xef
fffff880`02706bd8  fffff880`0590dc40 nvlddmkm+0xb4c40
fffff880`02706c08  fffff880`04407f76 dxgmms1!VidSchDdiNotifyInterrupt+0x9e
fffff880`02706c38  fffff880`044e013f dxgkrnl!DxgNotifyInterruptCB+0x83
fffff880`02706c68  fffff880`0590dae5 nvlddmkm+0xb4ae5
fffff880`02706c90  fffff880`0590da8b nvlddmkm+0xb4a8b
fffff880`02706cf8  fffff880`0590dd2d nvlddmkm+0xb4d2d
fffff880`02706d20  fffff880`0590dcc6 nvlddmkm+0xb4cc6
fffff880`02706d88  fffff880`0590dc40 nvlddmkm+0xb4c40
fffff880`02706d90  fffff880`0590dcc6 nvlddmkm+0xb4cc6
fffff880`02706db8  fffff880`05949fd7 nvlddmkm+0xf0fd7
fffff880`02706de0  fffff880`05949d72 nvlddmkm+0xf0d72
fffff880`02706e58  fffff880`044083f1 dxgmms1!VidSchiProcessIsrVSync+0xc9
fffff880`02706ea8  fffff880`0590dd2d nvlddmkm+0xb4d2d
fffff880`02706ed8  fffff880`0440c095 dxgmms1!VidSchiUpdateContextRunningTimeAtISR+0x45
fffff880`02706f18  fffff880`0440866b dxgmms1!VidSchiProcessIsrCompletedPacket+0x1eb
fffff880`02706fa8  fffff880`04408172 dxgmms1!VidSchDdiNotifyInterruptWorker+0x1ea
fffff880`02706ff8  fffff880`04407f76 dxgmms1!VidSchDdiNotifyInterrupt+0x9e
fffff880`02707028  fffff880`044e013f dxgkrnl!DxgNotifyInterruptCB+0x83
fffff880`02707058  fffff880`0590dae5 nvlddmkm+0xb4ae5
fffff880`02707080  fffff880`0590da8b nvlddmkm+0xb4a8b
fffff880`027070e8  fffff880`0590dd2d nvlddmkm+0xb4d2d
fffff880`02707110  fffff880`0590dcc6 nvlddmkm+0xb4cc6
fffff880`02707178  fffff880`0590dc40 nvlddmkm+0xb4c40
fffff880`027071a8  fffff880`0593ea9b nvlddmkm+0xe5a9b
fffff880`027071d0  fffff880`0593e7dd nvlddmkm+0xe57dd
fffff880`02707260  fffff880`0593e7dd nvlddmkm+0xe57dd
fffff880`02707298  fffff880`05adb5ca nvlddmkm+0x2825ca
fffff880`02707308  fffff880`0593e605 nvlddmkm+0xe5605
fffff880`02707348  fffff880`0590d655 nvlddmkm+0xb4655
fffff880`02707398  fffff880`044577a8 HDAudBus!HDABusWmiLogETW+0x248
fffff880`02707468  fffff880`0444a4b6 HDAudBus!HdaController::Isr+0x596
fffff880`027074a8  fffff800`03087ef2 nt!KiDispatchInterrupt+0x12
fffff880`027074e0  fffff800`0308ee85 nt!KiIpiInterrupt+0x135
fffff880`02707528  fffff800`03601552 hal!HalpRequestIpiSpecifyVector+0x41
fffff880`02707558  fffff800`030a3be3 nt!KiIpiSendRequest+0x2d3
fffff880`027075f8  fffff800`03006000 nt!KiSelectNextThread <PERF> (nt+0x0)
fffff880`02707618  fffff800`03059f9f nt!KiIpiSendPacket+0x4f
nt!B_TREE<_SM_PAGE_KEY,SMKM_STORE_MGR<SM_TRAITS>::SMKM_FRONTEND_ENTRY,4096,B_TREE_DUMMY_NODE_POOL>::BTreeSearchResultDeref
fffff880`02707678  fffff800`03059d3d nt!KeFlushProcessWriteBuffers+0x61
fffff880`02707690  fffff800`0308ee85 nt!KiIpiInterrupt+0x135
fffff880`02707698  fffff800`03088243 nt!SwapContext_PatchXSave+0xa3
fffff880`027076e8  fffff800`0338987b nt!ExpQuerySystemInformation+0x259
fffff880`02707708  fffff880`05c6063e nvlddmkm+0x40763e

Here are the usual causes of this bug check:

Code:

STOP 0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP

Usual causes:  Memory corruption, Hardware (memory in particular), Overclocking failure, Installing a faulty or mismatched hardware (especially memory) or a failure after installing it, 3rd party firewall, Device drivers, SCSI/network/BIOS updates needed, Improperly seated cards, Incompatible storage devices, Overclocking, Virus scanner, Backup tool, Bad motherboard, Missing Service Pack

We'll see what we can do after the results from memtest.

jkm1687 · 08 Jan 2013

heres another blue screen that just popped up

koolkat77 · 08 Jan 2013

Proceed with memtest please.

Windows 7: Constant BSOD

Constant BSOD problems?