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: Bsod

22 Nov 2011   #1

windows 7 ultimate x64
Months and Months of BSODs PLEASE HELP

I built a new computer back in July. Everything came over from my old stable tower except for a new motherboard, new CPU new RAM, and 2 new tv tuner cards.

Components from previous stable computer include hard drives, video card, chassis, PSU, bluray drive.

I'm using the motherboards onboard SATA for hard drives and bluray drive. Also using motherboard's onboard network jack, audio.

The OS hard drive was formatted and then I installed a fresh install of Windows 7 Ultimate x64.

I've run MemTest 86 a few times for 3 or 4 passes each time and never got any errors. However for what it is worth my gut is still telling me this might be a RAM problem.

Hope you all help! Know in advance that I really really appreciate it!

My crash dumps are attached.

My System SpecsSystem Spec
28 Mar 2012   #2

windows 7 ultimate x64

Please I still have this problem and I've been VERY patient on this form waiting for a response. Please excuse my BUMP...
My System SpecsSystem Spec
28 Mar 2012   #3

Windows 7 Ultimate x86

You did state that you attached the necessary crash info but I don't see any. That might be the main reason nobody answered.
Please create those jcgriff2 files after this tut:
and attach them to the first post so we could take a look

My System SpecsSystem Spec

03 Apr 2012   #4

windows 7 ultimate x64

OK just attached the dump file Zip. Thanks for the help!
My System SpecsSystem Spec
03 Apr 2012   #5

Windows 7 Home Premium 64 Bit

Security Software (this is just to check that you have it and it is working properly; nothing needs to be done with this at this time):
msmpeng.exe	c:\program files\microsoft security client\antimalware\msmpeng.exe	952	8	200	1380	3/21/2012 7:27 PM	3.0.8402.0	12.48 KB (12,784 bytes)	4/27/2011 5:21 PM
nissrv.exe	c:\program files\microsoft security client\antimalware\nissrv.exe	3856	8	200	1380	3/21/2012 7:28 PM	3.0.8402.0	281.52 KB (288,272 bytes)	4/27/2011 5:21 PM
msseces.exe	c:\program files\microsoft security client\msseces.exe	3004	8	200	1380	3/21/2012 7:28 PM	2.1.1116.0	1.37 MB (1,436,736 bytes)	6/15/2011 2:35 PM

Possible out of date driver:
amdsbs	fffff880`00e00000	fffff880`00e47000	Fri Mar 20 12:36:03 2009 (49c3e213)	0003938a		amdsbs.sys
amdsbs.sys can probably be found for your motherboard at the manufacturer's support site. Please fill in your system specs. System Info - See Your System Specs is an excellent guide to fill in the system specs.

  1. Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\Kingston\BSODDmpFiles\cesiumdeth\Windows_NT6_BSOD_jcgriff2\031912-28282-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache* Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330 Machine Name: Kernel base = 0xfffff800`0324c000 PsLoadedModuleList = 0xfffff800`03490650 Debug session time: Mon Mar 19 15:13:29.841 2012 (UTC - 6:00) System Uptime: 1 days 23:33:54.605 Loading Kernel Symbols ............................................................... ................................................................ ....................................... Loading User Symbols Loading unloaded module list ...... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {80, 2, 1, fffff800032d212f} Probably caused by : ntkrnlmp.exe ( nt!KeAcquireInStackQueuedSpinLock+5f ) Followup: MachineOwner --------- 5: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: 0000000000000080, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000001, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff800032d212f, address which referenced memory Debugging Details: ------------------ WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800034fa100 0000000000000080 CURRENT_IRQL: 2 FAULTING_IP: nt!KeAcquireInStackQueuedSpinLock+5f fffff800`032d212f 488717 xchg rdx,qword ptr [rdi] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System TRAP_FRAME: fffff880033d1890 -- (.trap 0xfffff880033d1890) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000002 rbx=0000000000000000 rcx=0000000000000000 rdx=fffff880033d1aa0 rsi=0000000000000000 rdi=0000000000000000 rip=fffff800032d212f rsp=fffff880033d1a20 rbp=fffffa800fdc2450 r8=fffff880033d1aa0 r9=0000000000000002 r10=0000000000000000 r11=0000058000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz ac pe nc nt!KeAcquireInStackQueuedSpinLock+0x5f: fffff800`032d212f 488717 xchg rdx,qword ptr [rdi] ds:00000000`00000000=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff800032c82e9 to fffff800032c8d40 STACK_TEXT: fffff880`033d1748 fffff800`032c82e9 : 00000000`0000000a 00000000`00000080 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx fffff880`033d1750 fffff800`032c6f60 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69 fffff880`033d1890 fffff800`032d212f : 00000000`00080000 fffff880`03288180 fffffa80`00000000 fffff8a0`0bd0e400 : nt!KiPageFault+0x260 fffff880`033d1a20 fffff800`0337f47e : fffffa80`0fdc2450 00000000`00000000 00000000`00000000 fffff800`032d9b9c : nt!KeAcquireInStackQueuedSpinLock+0x5f fffff880`033d1a70 fffff800`03334931 : 80118210`800a8202 00000000`00000000 80118210`800a8202 fffff800`033f6fbd : nt!MiReleaseConfirmedPageFileSpace+0x5e fffff880`033d1af0 fffff800`0356721f : fffffa80`136130c0 00000000`00000000 00000000`0008c081 fffffa80`0efb7f10 : nt! ?? ::FNODOBFM::`string'+0x2b2cd fffff880`033d1bc0 fffff800`0331591d : fffffa80`136130c8 00000000`00000001 00000000`00000000 00000000`00000631 : nt!MiSegmentDelete+0x7b fffff880`033d1c00 fffff800`03315b95 : 00000000`00000000 00000000`00000080 fffffa80`0ca7b040 fffffa80`00000012 : nt!MiProcessDereferenceList+0x131 fffff880`033d1cc0 fffff800`03562f7a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiDereferenceSegmentThread+0x10d fffff880`033d1d40 fffff800`032b99c6 : fffff880`03164180 fffffa80`0cb6db60 fffff880`0316f040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`033d1d80 00000000`00000000 : fffff880`033d2000 fffff880`033cc000 fffff880`033d17f0 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: nt!KeAcquireInStackQueuedSpinLock+5f fffff800`032d212f 488717 xchg rdx,qword ptr [rdi] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: nt!KeAcquireInStackQueuedSpinLock+5f FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4ec79dd2 FAILURE_BUCKET_ID: X64_0xA_nt!KeAcquireInStackQueuedSpinLock+5f BUCKET_ID: X64_0xA_nt!KeAcquireInStackQueuedSpinLock+5f Followup: MachineOwner ---------
  1. Possible causes are Memory problems... Corrupted hard disk file system... Corrupted System Files... BIOS... Lack of Windows updates... Antivirus Software... Backup... Hardware...
You have a variety of different errors, and the one error analysis above in the code has a possible cause of hardware. A wide variety of errors also indicates hardware.

You also have:
  Log Name: System
  Source: Ntfs
  Date: 2012-03-27T03:01:52.918
  Event ID: 55
  Task: N/A
  Level: Error
  Opcode: N/A
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DJW-SERVER
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume \Device\HarddiskVolume4.

  • 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.

  • 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. This means you should run Memtest86+ for at least seven passes and preferably more. 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


Thread Tools

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 21:03.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App