hey guys.
having recent problems with my windows 7 OS.
I'm getting BSOD on startups. This started recently and occurs during idle or viewing videos. I've tried WhoCrashed and found out it might be my nvidia drivers for my mobo, but i've updated them and still crashes. any help?
I'm running windows 7 32bit
Not sure how else I can explain my problems. I've attached the dump files; hopefully you guys can figure it out for me. Thanks bunches
These crashes were mainly caused by memory corruption/exception (probably a driver).
Please run these two tests to verify your memory and find which driver is causing the problem.
If you are overclocking anything reset to default before running these tests.
In other words STOP!!!
Memtest.
RAM - Test with Memtest86+*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool
*Boot from the CD, and leave it running for at least 5 or 6 passes.
Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.
Test the sticks individually, and if you find a good one, test it in all slots.
Any errors are indicative of a memory problem.
If a known good stick fails in a motherboard slot it is probably the slot.
Driver verifier
Using Driver Verifier to identify issues with Windows drivers for advanced usersUsing Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.
So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).
Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Special Pool", "Force Pending I/O Requests" and "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).
Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.
If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
We dont encourage the use of Blue Screen View, or Who crashed because they both erroneously blame OS files when thee actual cause may be something else.. Please follow JMH'S instructions .
thanks. i will try swapping memory sticks and see how it goes
Hi, I'm still having the same problems. sometimes its memory_management and sometimes its irql_not_less.....
i've RMA my ram and bought new corsair memory.
still having same problems. it bsod on startup right away. also, sometimes when i boot up, the computer does nothing. i have to shutdown/boot up several times before it "startsup"
i've bought 4 sticks of 2gb DDr ram and it've memtested each one. each test was ran for 1 pass. one gives me 4 errors
the current setup with 2 sticks ran for 2 hours with no errors
i was running the minidump files and it BSOD again. this time was Bad_pool_header. FYI, i was in safemode too
another one
the driver is mismanaging PTE
Last edited by 5t341th; 07 Mar 2012 at 01:40.
The files you uploaded contained a lot of corruption. Your crashes have NTFS in the stack, which may suggest that corruption is due to hard disk errors or a faulty hard disk.
- Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log
- Use HD Diagnostic to find your hard disk manufacturer and the diagnostic tools provided by the manufacturer. If you have a Samsung drive, use the Seagate SeaTools and run the short and long tests for the drive.
i've ran the disk check and also the hd diagnostic with seagate tools.
i've been doing a bit of reading and it might be the video card driver
heres my latest dump files. please help me diagnose this!! ive been without my desktop for months
i've also ran driver verifier and it crashed displaying usbohci.sys
could that be the culprit?
Possible out of date drivers:giveio.sysCode:giveio 8e24e000 8e24e680 Wed Apr 03 20:33:25 1996 (316334f5) 00003355 giveio.sys NCREMOTEPCI 94b8b000 94b8e180 Mon Sep 11 14:47:38 2006 (4505cb6a) 0000d72a NCREMOTEPCI.SYS SSPORT a20c2000 a20c9000 Tue Nov 21 21:41:42 2006 (4563d506) 000109dd SSPORT.sys nvm62x32 94107000 9415bc80 Fri Oct 17 15:00:39 2008 (48f8fcf7) 000610af nvm62x32.sys Epfwndis 94169000 94174000 Thu May 14 07:12:03 2009 (4a0c18a3) 0000a084 Epfwndis.sys epfw 9052b000 9054e000 Thu May 14 07:12:05 2009 (4a0c18a5) 000287ac epfw.sys epfwwfp 9075d000 9076b000 Thu May 14 07:12:05 2009 (4a0c18a5) 0000a08d epfwwfp.sys eamon 9043e000 904fa000 Thu May 14 07:30:44 2009 (4a0c1d04) 0002889f eamon.sys ehdrv 8e344000 8e361000 Thu May 14 07:31:56 2009 (4a0c1d4c) 000232c6 ehdrv.sys GEARAspiWDM 94bf3000 94bf8280 Mon May 18 06:16:53 2009 (4a1151b5) 00008fb0 GEARAspiWDM.sys
NCREMOTEPCI.SYS
SSPORT.sys
nvm62x32.sys
Epfwndis.sys
epfw.sys
epfwwfp.sys
eamon.sys
ehdrv.sys
GEARAspiWDM.sys
Code:
- Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\Kingston\BSODDmpFiles\5t341th\Windows_NT6_BSOD_jcgriff2\030912-32484-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505 Machine Name: Kernel base = 0x84855000 PsLoadedModuleList = 0x84995230 Debug session time: Fri Mar 9 01:17:19.903 2012 (UTC - 7:00) System Uptime: 0 days 0:08:25.450 Loading Kernel Symbols ............................................................... ................................................................ ..................................... Loading User Symbols Loading unloaded module list ..... 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_PTE_MISUSE (da) The stack trace identifies the guilty driver. Arguments: Arg1: 00000504, Type of error. Arg2: c0259404 Arg3: 00000001 Arg4: 00016501 Debugging Details: ------------------ Unable to load image \SystemRoot\system32\DRIVERS\eamon.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for eamon.sys *** ERROR: Module load completed but symbols could not be loaded for eamon.sys CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xDA PROCESS_NAME: setup.exe CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from 848d11e2 to 848f111f STACK_TEXT: a587b84c 848d11e2 84993440 00000001 00000000 nt!MiReplenishBitMap+0x235 a587b8a4 848db9a2 84993440 c02089e8 00000001 nt!MiInsertCachedPte+0x1f8 a587b8d4 848c4d6b 00000001 8d5a7732 8b819a60 nt!MiReleaseSystemPtes+0x50 a587b974 848e9e4b a3a00000 01440020 00000000 nt!MmCopyToCachedPage+0x697 a587ba08 848eec51 875a3008 01440020 a587ba58 nt!CcMapAndCopyInToCache+0x1f0 a587ba60 8dd98bd0 8b5cce60 a587bb68 00010000 nt!CcCopyWrite+0x1d9 a587bb8c 8dcbffec 8b5cce60 a587ba8c 00010000 Ntfs!NtfsCopyWriteA+0x248 a587bbc0 8dcc01bb 00000004 00000000 8752b0a4 fltmgr!FltpPerformFastIoCall+0x22e a587bbec 8dcd2dcf 0087bc10 904f4ebc a587bca4 fltmgr!FltpPassThroughFastIo+0x7d a587bc30 90443bed 8b5cce60 a587bcac 00010000 fltmgr!FltpFastIoWrite+0x163 WARNING: Stack unwind information not available. Following frames may be wrong. a587bc64 84a6f41d 8b5cce60 a587bcac 00010000 eamon+0x5bed a587bd08 8488a85a 89376b80 000001f4 00000000 nt!NtWriteFile+0x342 a587bd08 776d7094 89376b80 000001f4 00000000 nt!KiFastCallEntry+0x12a 0030e134 00000000 00000000 00000000 00000000 0x776d7094 STACK_COMMAND: kb FOLLOWUP_IP: eamon+5bed 90443bed ?? ??? SYMBOL_STACK_INDEX: a SYMBOL_NAME: eamon+5bed FOLLOWUP_NAME: MachineOwner MODULE_NAME: eamon IMAGE_NAME: eamon.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a0c1d04 FAILURE_BUCKET_ID: 0xDA_eamon+5bed BUCKET_ID: 0xDA_eamon+5bed Followup: MachineOwner ---------
- Loading Dump File [D:\Kingston\BSODDmpFiles\5t341th\Windows_NT6_BSOD_jcgriff2\030912-31296-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505 Machine Name: Kernel base = 0x8483c000 PsLoadedModuleList = 0x8497c230 Debug session time: Fri Mar 9 01:08:09.812 2012 (UTC - 7:00) System Uptime: 0 days 0:00:18.406 Loading Kernel Symbols ............................................................... .............................................. Loading User Symbols 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_PTE_MISUSE (da) The stack trace identifies the guilty driver. Arguments: Arg1: 00000500, Type of error. Arg2: c024f400 Arg3: 00000008 Arg4: 00013d00 Debugging Details: ------------------ CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xDA PROCESS_NAME: System CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from 84899b45 to 848d811f STACK_TEXT: 92f28ae4 84899b45 8497a440 00000008 00000001 nt!MiReplenishBitMap+0x235 92f28b28 848a6f04 8497a440 00000001 872f9fc8 nt!MiEmptyPteBins+0xdc 92f28b7c 8e1e79e5 89141cc0 00000000 00000001 nt!MmMapLockedPagesSpecifyCache+0x1c7 92f28b9c 8e1ee3b9 89141cc0 00000000 872f9fc8 rdyboost!SmMapMdl+0x23 92f28bb4 8e1d9bcc 872f9fc8 00000002 883e1838 rdyboost!SmFpAllocate+0x1b 92f28bdc 8e1e4eee 883faca4 00000329 00000001 rdyboost!SMKM_STORE<SMD_TRAITS>::SmStMapRegion+0x68 92f28c28 8e1e57f3 00000329 92f28cec 891c25d0 rdyboost!ST_STORE<SMD_TRAITS>::StDmpSinglePageRetrieve+0xde 92f28d10 8e1e6d1a 872f9478 891c25d0 891c25d0 rdyboost!ST_STORE<SMD_TRAITS>::StDmPageRetrieve+0x103 92f28d28 8e1e6f14 872f9430 891c25d0 00000000 rdyboost!ST_STORE<SMD_TRAITS>::StWorkItemProcess+0x4a 92f28d50 84a2446a 00000000 ba336f17 00000000 rdyboost!SMKM_STORE<SMD_TRAITS>::SmStWorker+0xfe 92f28d90 848c5989 8e1e6e16 872f9430 00000000 nt!PspSystemThreadStartup+0x9e 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19 STACK_COMMAND: kb FOLLOWUP_IP: rdyboost!SmMapMdl+23 8e1e79e5 5d pop ebp SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: rdyboost!SmMapMdl+23 FOLLOWUP_NAME: MachineOwner MODULE_NAME: rdyboost IMAGE_NAME: rdyboost.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ce78e17 FAILURE_BUCKET_ID: 0xDA_rdyboost!SmMapMdl+23 BUCKET_ID: 0xDA_rdyboost!SmMapMdl+23 Followup: MachineOwner ---------
- Loading Dump File [D:\Kingston\BSODDmpFiles\5t341th\Windows_NT6_BSOD_jcgriff2\030812-34640-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505 Machine Name: Kernel base = 0x84842000 PsLoadedModuleList = 0x84982230 Debug session time: Fri Mar 9 00:53:06.286 2012 (UTC - 7:00) System Uptime: 0 days 0:01:41.833 Loading Kernel Symbols ............................................................... ................................................................ .................................... Loading User Symbols Loading unloaded module list ..... 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* BAD_POOL_HEADER (19) The pool is already corrupt at the time of the current request. This may or may not be due to the caller. The internal pool links must be walked to figure out a possible cause of the problem, and then special pool applied to the suspect tags or the driver verifier to a suspect driver. Arguments: Arg1: 00000020, a pool block header size is corrupt. Arg2: 88d7c530, The pool entry we were looking for within the page. Arg3: 88d7c780, The next pool entry. Arg4: 184a0005, (reserved) Debugging Details: ------------------ BUGCHECK_STR: 0x19_20 POOL_ADDRESS: GetPointerFromAddress: unable to read from 849a1828 Unable to read MiSystemVaType memory at 84981d80 88d7c530 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: csrss.exe CURRENT_IRQL: 1 LAST_CONTROL_TRANSFER: from 848d190b to 8495ac4e STACK_TEXT: 84363a0c 848d190b 88d7c538 00000000 8aa7b620 nt!ExFreePoolWithTag+0x1b2 84363a28 84a0cab8 88d7c538 84363a84 848b058e nt!IopFreeIrp+0x65 84363a34 848b058e 88d7c578 84363a60 84363a6c nt!IopUserCompletion+0x11 84363a84 8489dd4d 00000000 00000000 00000000 nt!KiDeliverApc+0x160 84363ac8 8489cbc3 8aa78458 8aa7b620 8aa7b71c nt!KiSwapThread+0x24e 84363af0 84898c29 8aa7b620 8aa7b6e0 00000000 nt!KiCommitThreadWait+0x1df 84363c68 959fe50e 00000002 88de81f8 00000001 nt!KeWaitForMultipleObjects+0x535 84363cc0 95975a17 00000001 88de81f8 9597eb3e win32k!xxxMsgWaitForMultipleObjects+0xe9 84363d04 9597d7c1 88de81f8 00000001 95b82bc0 win32k!xxxDesktopThread+0x1b6 84363d18 95a33c45 00000004 0024fb04 84363d34 win32k!xxxCreateSystemThreads+0x54 84363d28 8487785a 00000004 0024fb44 77057094 win32k!NtUserCallNoParam+0x1b 84363d28 77057094 00000004 0024fb44 77057094 nt!KiFastCallEntry+0x12a WARNING: Frame IP not in any known module. Following frames may be wrong. 0024fb44 00000000 00000000 00000000 00000000 0x77057094 STACK_COMMAND: kb FOLLOWUP_IP: win32k!xxxMsgWaitForMultipleObjects+e9 959fe50e 8945e4 mov dword ptr [ebp-1Ch],eax SYMBOL_STACK_INDEX: 7 SYMBOL_NAME: win32k!xxxMsgWaitForMultipleObjects+e9 FOLLOWUP_NAME: MachineOwner MODULE_NAME: win32k IMAGE_NAME: win32k.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ecdc722 FAILURE_BUCKET_ID: 0x19_20_win32k!xxxMsgWaitForMultipleObjects+e9 BUCKET_ID: 0x19_20_win32k!xxxMsgWaitForMultipleObjects+e9 Followup: MachineOwner ---------
- Never seen this crash before... Research suggests this is a driver caused crash. Yours is pointing to your ESET antivirus software... ESET normally does not cause crashes, so I suspect something else at work here.
- Same type of crash. This one indicated ReadyBoost. Are you using a ReadyBoost enabled flash drive?
- Possible cause is drivers... You do have a number of outdated drivers listed above.
ESET normally does not cause crashes, but yours is outdated. Can you install the latest version? That may help with your crashes.
You also have a network adapter driver that is out of date. nvm62x32.sys We see a lot of blue screen crashes related to out of date network adapter drivers.
Additionally, try updating as many of the above listed possible out of date drivers as you can. If the device that requires an outdated driver is not required for using your computer, remove it. See if this improves stability.
so i get fed up with the crashes and am installing a fresh install of windows 7 64bit.
was installing it and after the second restart, the install crashed with a blue screen. I'm so annoyed with the crashes. I just want to build a new computer setup.
the crashes are related to
"the driver is mismanaging system PTEs"
also, if i use my new gtx550 video card, on computer startup, the screen stays black and monitor blinks.
if i use my older 9800gt video card, it displays the screen fine. what could be the problem here?
Quote