Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Random BSOD problems, unknown causes.

22 Mar 2012   #11
writhziden

Windows 7 Home Premium 64 Bit
 
 

Problem Devices:
Code:
Belkin High-Speed Mode Wireless G USB Network Adapter	USB\VID_050D&PID_7051\8057	The drivers for this device are not installed.

Security Software:
Code:
msmpeng.exe	c:\program files\microsoft security client\antimalware\msmpeng.exe	844	8	200	1380	22/03/2012 00:36	3.0.8402.0	12.48 KB (12,784 bytes)	27/04/2011 17:21
nissrv.exe	c:\program files\microsoft security client\antimalware\nissrv.exe	1200	8	200	1380	22/03/2012 00:37	3.0.8402.0	281.52 KB (288,272 bytes)	27/04/2011 17:21
msseces.exe	c:\program files\microsoft security client\msseces.exe	2392	8	200	1380	22/03/2012 00:37	2.1.1116.0	1.37 MB (1,436,736 bytes)	15/06/2011 14:35

Possible out of date driver:
Code:
ssadadb	fffff880`04e08000	fffff880`04e17000	Wed Jan 14 14:27:20 2009 (496e58b8)	0000debb		ssadadb.sys
ssadadb.sys


Code:
  1. Loading Dump File [D:\Kingston\BSODDmpFiles\phosphorus2500\Windows_NT6_BSOD_jcgriff2\032212-26254-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (3 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330 Machine Name: Kernel base = 0xfffff800`02c1a000 PsLoadedModuleList = 0xfffff800`02e5e650 Debug session time: Thu Mar 22 01:31:55.648 2012 (UTC - 6:00) System Uptime: 0 days 0:17:39.256 Loading Kernel Symbols ............................................................... ................................................................ ..................................... Loading User Symbols Loading unloaded module list .... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff80002f8c3b1, fffff88008096ab0, 0} Probably caused by : ntkrnlmp.exe ( nt!ObpWaitForMultipleObjects+186 ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff80002f8c3b1, Address of the instruction which caused the bugcheck Arg3: fffff88008096ab0, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: nt!ObpWaitForMultipleObjects+186 fffff800`02f8c3b1 488b4a20 mov rcx,qword ptr [rdx+20h] CONTEXT: fffff88008096ab0 -- (.cxr 0xfffff88008096ab0) rax=00000000000000a8 rbx=fffff8a0020295c0 rcx=fffff80002c1a000 rdx=0000000000000000 rsi=000000000000000e rdi=fffffa800a12eb90 rip=fffff80002f8c3b1 rsp=fffff88008097490 rbp=fffff88008097ca0 r8=0000000000000008 r9=fffff8a003b84000 r10=fffffa800a135060 r11=fffffffffffffd80 r12=fffff88008097a08 r13=fffff8a0039ebbd0 r14=000000000000000d r15=0000000000000010 iopl=0 nv up ei pl nz na pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202 nt!ObpWaitForMultipleObjects+0x186: fffff800`02f8c3b1 488b4a20 mov rcx,qword ptr [rdx+20h] ds:002b:00000000`00000020=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: Ventrilo.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80002f8c3b1 STACK_TEXT: fffff880`08097490 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObpWaitForMultipleObjects+0x186 FOLLOWUP_IP: nt!ObpWaitForMultipleObjects+186 fffff800`02f8c3b1 488b4a20 mov rcx,qword ptr [rdx+20h] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!ObpWaitForMultipleObjects+186 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4ec79dd2 STACK_COMMAND: .cxr 0xfffff88008096ab0 ; kb FAILURE_BUCKET_ID: X64_0x3B_nt!ObpWaitForMultipleObjects+186 BUCKET_ID: X64_0x3B_nt!ObpWaitForMultipleObjects+186 Followup: MachineOwner ---------
  2. Loading Dump File [D:\Kingston\BSODDmpFiles\phosphorus2500\Windows_NT6_BSOD_jcgriff2\032212-29421-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (3 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330 Machine Name: Kernel base = 0xfffff800`02c0a000 PsLoadedModuleList = 0xfffff800`02e4e650 Debug session time: Thu Mar 22 01:13:10.897 2012 (UTC - 6:00) System Uptime: 0 days 1:27:42.504 Loading Kernel Symbols ............................................................... ................................................................ .................................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff8800fd9cd42, fffff8800a6349e0, 0} Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_LINEAR_POOL::FindAdjacentBlocksOnFreeList+26 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff8800fd9cd42, Address of the instruction which caused the bugcheck Arg3: fffff8800a6349e0, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: dxgmms1!VIDMM_LINEAR_POOL::FindAdjacentBlocksOnFreeList+26 fffff880`0fd9cd42 488b5b08 mov rbx,qword ptr [rbx+8] CONTEXT: fffff8800a6349e0 -- (.cxr 0xfffff8800a6349e0) rax=fffffa8003e2e108 rbx=0000000000000000 rcx=fffffa80091a8f00 rdx=ffffffffffffffd0 rsi=fffff8a00a8a5500 rdi=fffffa80068e49a0 rip=fffff8800fd9cd42 rsp=fffff8800a6353c8 rbp=fffffa80091a8f00 r8=fffff8800a635438 r9=fffff8800a635440 r10=fffffa8003fe6d48 r11=fffffa80091a8f40 r12=0000000000000000 r13=fffff8a002fbfbd0 r14=0000000000000000 r15=fffff8a0024aec90 iopl=0 nv up ei pl nz ac po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010216 dxgmms1!VIDMM_LINEAR_POOL::FindAdjacentBlocksOnFreeList+0x26: fffff880`0fd9cd42 488b5b08 mov rbx,qword ptr [rbx+8] ds:002b:00000000`00000008=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: FirefallClient CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff8800fd9cd42 STACK_TEXT: fffff880`0a6353c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_LINEAR_POOL::FindAdjacentBlocksOnFreeList+0x26 FOLLOWUP_IP: dxgmms1!VIDMM_LINEAR_POOL::FindAdjacentBlocksOnFreeList+26 fffff880`0fd9cd42 488b5b08 mov rbx,qword ptr [rbx+8] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: dxgmms1!VIDMM_LINEAR_POOL::FindAdjacentBlocksOnFreeList+26 FOLLOWUP_NAME: MachineOwner MODULE_NAME: dxgmms1 IMAGE_NAME: dxgmms1.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4ce799c1 STACK_COMMAND: .cxr 0xfffff8800a6349e0 ; kb FAILURE_BUCKET_ID: X64_0x3B_dxgmms1!VIDMM_LINEAR_POOL::FindAdjacentBlocksOnFreeList+26 BUCKET_ID: X64_0x3B_dxgmms1!VIDMM_LINEAR_POOL::FindAdjacentBlocksOnFreeList+26 Followup: MachineOwner ---------
  3. Loading Dump File [D:\Kingston\BSODDmpFiles\phosphorus2500\Windows_NT6_BSOD_jcgriff2\032112-18844-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (3 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16917.amd64fre.win7_gdr.111118-2330 Machine Name: Kernel base = 0xfffff800`02c06000 PsLoadedModuleList = 0xfffff800`02e42e70 Debug session time: Wed Mar 21 18:11:30.482 2012 (UTC - 6:00) System Uptime: 0 days 0:00:12.370 Loading Kernel Symbols .................................................. Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 6B, {ffffffffc0000428, 3, 0, 0} Probably caused by : ntkrnlmp.exe ( nt!PspLocateSystemDll+13e ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PROCESS1_INITIALIZATION_FAILED (6b) Arguments: Arg1: ffffffffc0000428, Indicates the NT status code that caused the failure. Arg2: 0000000000000003, (reserved) Arg3: 0000000000000000 Arg4: 0000000000000000 Debugging Details: ------------------ CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x6B PROCESS_NAME: System CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff800030bab2e to fffff80002c76540 STACK_TEXT: fffff880`009a9928 fffff800`030bab2e : 00000000`0000006b ffffffff`c0000428 00000000`00000003 00000000`00000000 : nt!KeBugCheckEx fffff880`009a9930 fffff800`030bae09 : 00000000`002a0028 00000000`00000001 00000000`00000001 fffff8a0`001edc60 : nt!PspLocateSystemDll+0x13e fffff880`009a9a00 fffff800`031a3abd : fffff800`008127f0 00000000`00000002 00000000`00000000 fffff800`02defe80 : nt!PsLocateSystemDlls+0x69 fffff880`009a9a40 fffff800`031a6c6c : 00000000`00000000 00000000`00000010 ffffffff`80000028 fffff800`008127f0 : nt!IoInitSystem+0x85d fffff880`009a9b40 fffff800`030f7f59 : 00000000`00000000 fffffa80`039e5b60 00000000`00000080 fffffa80`039e5040 : nt!Phase1InitializationDiscard+0x129c fffff880`009a9d10 fffff800`02f15726 : 00000000`00000000 00000000`00000080 00000000`00000000 fffff800`02c54ab9 : nt!Phase1Initialization+0x9 fffff880`009a9d40 fffff800`02c54ac6 : fffff800`02defe80 fffffa80`039e5b60 fffff800`02dfdc40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`009a9d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: nt!PspLocateSystemDll+13e fffff800`030bab2e cc int 3 SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!PspLocateSystemDll+13e FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4ec7a284 FAILURE_BUCKET_ID: X64_0x6B_nt!PspLocateSystemDll+13e BUCKET_ID: X64_0x6B_nt!PspLocateSystemDll+13e Followup: MachineOwner ---------
  1. Possible caused by Ventrilo.exe.
  2. DirectX/Graphics Card problems...
  3. Quote:
    Any part of the disk subsystem can cause the PROCESS1_INITIALIZATION_FAILED bug check, including bad disks, bad or incorrect cables, mixing different ATA-type devices on the same chain, or drives that are not available becuase of hardware regeneration.
    This bug check can also be caused by a missing file from the boot partition or by a driver file that a user accidentally disabled in the Drivers tab.
    from Bug Check 0x6B: PROCESS1_INITIALIZATION_FAILED

Thanks to Dave76 for help understanding possible causes.


We will start with the common problems first (see bold possible causes). Do the following steps and test by doing your normal routine after each step to see if stability increases (the memory tests you can run concurrently as they will not increase stability unless you are forced to move modules around). Post back your results after each step, and if you get a blue screen crash, upload the files again and await further instructions after we are able to analyze the crash.

If you can do your normal routine for a few weeks without a crash, and your crashes are usually more frequent than that, then the problem is likely solved.
  • If you are overclocking any hardware, please stop.

  • 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.
    For any drives that do not give the message:
    Windows has checked the file system and found no problems
    run disk check again as above. In other words, if it says:
    Windows has made corrections to the file system
    after running the disk check, run the disk check again.

  • Run the short and long tests of SeaTools.

  • Try re-installing DirectX using the Download: DirectX Redist (June 2010) - Microsoft Download Center - Download Details and see how the system responds.

    Follow the steps for Diagnosing basic problems with DirectX. To re-install your display card drivers as outlined in the DirectX link, use the following steps.
    1. Download the latest drivers for your display card(s)
    2. Click Start Menu
    3. Right Click My Computer/Computer
    4. Click Manage
    5. Click Device Manager from the list on the left
    6. Expand Display adapters
    7. Do the following for each adapter (in case you have multiple display cards)
      • Right click the adapter
      • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
      • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
    8. Restart your computer after uninstalling drivers for all display cards
    9. Install the latest driver for the display cards once Windows starts

    Alternatively:
    1. Login as an adminstrative user
    2. Download the latest drivers for your display card(s)
    3. Click Start Menu
    4. Click Control Panel
    5. Click Hardware and Sound
    6. Click Device Manager (the last link under Devices and Printers)
    7. Expand Display adapters
    8. Do the following for each adapter (in case you have multiple display cards)
      • Right click the adapter
      • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
      • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
    9. Restart your computer after uninstalling drivers for all display cards
    10. Install the latest driver for the display cards once Windows starts

  • Monitor temperatures during the following tests.
    Use the following programs to monitor the temperatures.
  • Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

    If you swap any memory components, follow these steps for ESD safety:
    1. Shut down and turn off your computer.
    2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
    3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
    4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
    Once these steps have been followed, it is safe to remove and replace components within your computer.



My System SpecsSystem Spec
.
23 Mar 2012   #12
phosphorus2500

Windows Professional x64
 
 

Thank you all for the help you've given me so far but after yesterday and today I have removed a stick of RAM and done further testing and it appears that one of the sticks may be faulty which was the cause of the BSoD's as I have had none since yesterday now. I will do further testing to see, but thank you all
My System SpecsSystem Spec
23 Mar 2012   #13
writhziden

Windows 7 Home Premium 64 Bit
 
 

No problem. Keep us updated on how the system responds over the next few days. Good troubleshooting step!
My System SpecsSystem Spec
.

24 Mar 2012   #14
phosphorus2500

Windows Professional x64
 
 

Sorry for the late reply, and I dont know if we should mark it as solved or not yet.

Over the past couple of days I've been moving around the RAM to see if its a faulty stick or slot I have, I've ran the computer for a substantial amount of time in the suspected good slot with both RAM sticks and its been fine, anytime I put something in the bad slot, it bluescreens after running for a while... BUT since then I've also had random blackouts from my computer, freezing crashes and all sorts. I know its not a BSoD but my computer definitely seems to be going the way of the dodo and I dont know why =/
My System SpecsSystem Spec
24 Mar 2012   #15
writhziden

Windows 7 Home Premium 64 Bit
 
 

It's possible if you have a bad slot, you may also have a bad board...

Just to make sure I understand, you say you get these other strange occurrences when you have the RAM in the suspected good slot? Does it matter which module is in the slot, or do both cause the same erratic behavior?
My System SpecsSystem Spec
24 Mar 2012   #16
phosphorus2500

Windows Professional x64
 
 

I have looked into new motherboards to upgrade to but I dont have enough money and wont have for a while to make the suspected fix to the problems I'm having.

But the problems do seem to be incredibly random and tempermental so its difficult to try and gauge when they happen as over the past couple of days I've been switching the RAM about a lot to keep testing things and seeing what works, but yes the erratic behaviour and crashes seem to happen with either stick in the suspected good slot.
My System SpecsSystem Spec
24 Mar 2012   #17
writhziden

Windows 7 Home Premium 64 Bit
 
 

You might consider the option to Clean Install Windows 7 and see if it is indeed hardware and not Windows related. I suspect there is a bad slot since the tests indicate it, but the erratic behavior could possibly be Windows related.

Backup any important files before doing the clean install if you go that route.
My System SpecsSystem Spec
Reply

 Random BSOD problems, unknown causes.




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Random BSOD problems in the past 2 days. Random errors at random times
Three days ago my water cooling failed (got up to 77C while gaming is when I noticed the problem as my CPU should not go over 62C). I decided to install an aftermarket heatsink instead of a new water cooling system ,and add a few more fans just to make sure my whole motherboard was getting plenty...
BSOD Help and Support
Unknown and random BSOD
This BSOD occurred in my absence so I don't know how it happened and all that. Here are my SF Diagnostic Tool files.
BSOD Help and Support
Random BSOD's, unknown cause
Hello. i'm getting random bsod's lately. sometimes with the computer locked, once in a game (warzone 2100), once while browsing and once while typing in fastboot (android phone developing). So my bsod's aren't specific on an application. can someone help me? thanks i rarely can see the blue...
BSOD Help and Support
BSOD Problems with yet unknown cause
Hi everybody I'm getting much "BAD_POOL_HEADER" or "PAGEFAULT_IN_NONPAGED_AREA" BSODs lately and I have no clue what causes them. After some research I've stumbled upon this promising community and I hope that you guys can help me out =) I've attached the zip-Folder from the diagnostic tool....
BSOD Help and Support
BSOD, unknown problems...files attached
Hi, my new computer has had only a few random blue screens in its short life. Recently I got two within a week, so I think there may be a problem... Here is a log of the most recent event... Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7601.2.1.0.768.3 Locale...
BSOD Help and Support
BSOD Unknown problems...
http://icons.sevenforumscdn.com/images/styles/window7/statusicon/user_online.gif http://www.sevenforums.com/images/styles/window7/buttons/reputation.gif http://www.sevenforums.com/images/styles/window7/buttons/report.gif ...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 20:51.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App