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 BSODs plagueing my new system


08 Jun 2011   #1

Windows 7 Professional 64-bit
 
 
Random BSODs plagueing my new system

Hello,
I'm new here. I built my dream of a computer just a week ago and now I get random, frustrating BSODs. I have no clue why. Everything I have read about the BSODs I am getting says that it is memory related, but I have run windows memory test and memtest86 to no avail. Also, all my drivers were installed from accompanying CDs, so i didn't download a faulty driver. Any help is much appreciated.

I am running Windows 7 professional 64-bit, retail copy
It started happening about two days after building the PC and one day after installing my OS
Thank you in advance

My System SpecsSystem Spec
.

08 Jun 2011   #2

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by howerj View Post
Hello,
I'm new here. I built my dream of a computer just a week ago and now I get random, frustrating BSODs. I have no clue why. Everything I have read about the BSODs I am getting says that it is memory related, but I have run windows memory test and memtest86 to no avail. Also, all my drivers were installed from accompanying CDs, so i didn't download a faulty driver. Any help is much appreciated.

I am running Windows 7 professional 64-bit, retail copy
It started happening about two days after building the PC and one day after installing my OS
Thank you in advance

Simple your avast. Remove and replace with Microsoft Security essentials.

http://files.avast.com/files/eng/aswclear5.exe

Virus, Spyware & Malware Protection | Microsoft Security Essentials


Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\060711-12698-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Machine Name:
Kernel base = 0xfffff800`02e02000 PsLoadedModuleList = 0xfffff800`0303fe50
Debug session time: Wed Jun  8 00:46:47.880 2011 (GMT-4)
System Uptime: 0 days 0:41:48.285
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80002e75905, fffff88004163628, fffff88004162e90}

Unable to load image \SystemRoot\System32\Drivers\aswSP.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswSP.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswSP.SYS
Probably caused by : aswSP.SYS ( aswSP+102c4 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002e75905, The address that the exception occurred at
Arg3: fffff88004163628, Exception Record Address
Arg4: fffff88004162e90, Context Record Address

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!ExpInterlockedPopEntrySListFault16+0
fffff800`02e75905 498b08          mov     rcx,qword ptr [r8]

EXCEPTION_RECORD:  fffff88004163628 -- (.exr 0xfffff88004163628)
ExceptionAddress: fffff80002e75905 (nt!ExpInterlockedPopEntrySListFault16)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff88004162e90 -- (.cxr 0xfffff88004162e90)
rax=0000000968460003 rbx=0000000000000001 rcx=fffffa8006a358a0
rdx=e16d655302080001 rsi=fffff880030a4180 rdi=fffffa8006a358a0
rip=fffff80002e75905 rsp=fffff88004163860 rbp=fffff88004163ca8
 r8=e16d655302080000  r9=0000000000000000 r10=fffffa8006a358a0
r11=fffff88004163a48 r12=0000000000000000 r13=fffffa8006a239f0
r14=0000000000000000 r15=fffff88004163970
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
nt!ExpInterlockedPopEntrySListFault16:
fffff800`02e75905 498b08          mov     rcx,qword ptr [r8] ds:002b:e16d6553`02080000=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030aa0e0
 ffffffffffffffff 

FOLLOWUP_IP: 
aswSP+102c4
fffff880`03dbc2c4 ??              ???

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff8000316f900 to fffff80002e75905

STACK_TEXT:  
fffff880`04163860 fffff800`0316f900 : fffffa80`00000000 fffffa80`07252c20 00000000`00000000 fffff880`01084600 : nt!ExpInterlockedPopEntrySListFault16
fffff880`04163870 fffff800`03176527 : 00000000`000007ff 00000000`00000001 fffffa80`09669900 fffff880`04163938 : nt!ObOpenObjectByName+0x70
fffff880`04163920 fffff800`0318f378 : fffff880`04163c90 fffff8a0`00100080 fffff8a0`092940e0 fffff880`04163c98 : nt!IopCreateFile+0x2b7
fffff880`041639c0 fffff800`02e71953 : fffffa80`06a12040 00000000`00000000 fffffa80`07528040 fffff800`03187164 : nt!NtOpenFile+0x58
fffff880`04163a50 fffff800`02e6def0 : fffff880`03dbc2c4 fffff880`02f68fc0 00000000`00000000 fffff880`00000000 : nt!KiSystemServiceCopyEnd+0x13
fffff880`04163c58 fffff880`03dbc2c4 : fffff880`02f68fc0 00000000`00000000 fffff880`00000000 00000000`00000000 : nt!KiServiceLinkage
fffff880`04163c60 fffff880`02f68fc0 : 00000000`00000000 fffff880`00000000 00000000`00000000 fffff880`00000001 : aswSP+0x102c4
fffff880`04163c68 00000000`00000000 : fffff880`00000000 00000000`00000000 fffff880`00000001 fffff800`00000060 : 0xfffff880`02f68fc0


SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  aswSP+102c4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: aswSP

IMAGE_NAME:  aswSP.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4dc929b6

STACK_COMMAND:  .cxr 0xfffff88004162e90 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_aswSP+102c4

BUCKET_ID:  X64_0x7E_aswSP+102c4

Followup: MachineOwner
---------
My System SpecsSystem Spec
08 Jun 2011   #3

Windows 7 Professional 64-bit
 
 
Fixed

Wow! Totally figured out what the problem was. My blu-ray player's software is known for glitching out with my model. Someone with the same exact model had the exact same different BSODs. The model is Samsung SH-B123L BR. If you have this problem, uninstall the Cyberlink software and your problem will go away
My System SpecsSystem Spec
.


08 Jun 2011   #4

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by howerj View Post
Wow! Totally figured out what the problem was. My blu-ray player's software is known for glitching out with my model. Someone with the same exact model had the exact same different BSODs. The model is Samsung SH-B123L BR. If you have this problem, uninstall the Cyberlink software and your problem will go away

Not what the crash log says

Unable to load image \SystemRoot\System32\Drivers\aswSP.SYS, Win32 error 0n2 *** WARNING: Unable to verify timestamp for aswSP.SYS *** ERROR: Module load completed but symbols could not be loaded for aswSP.SYS Probably caused by : aswSP.SYS ( aswSP+102c4 )
My System SpecsSystem Spec
08 Jun 2011   #5

Windows 7 Professional 64-bit
 
 

Quote   Quote: Originally Posted by zigzag3143 View Post
Quote   Quote: Originally Posted by howerj View Post
Wow! Totally figured out what the problem was. My blu-ray player's software is known for glitching out with my model. Someone with the same exact model had the exact same different BSODs. The model is Samsung SH-B123L BR. If you have this problem, uninstall the Cyberlink software and your problem will go away

Not what the crash log says

Unable to load image \SystemRoot\System32\Drivers\aswSP.SYS, Win32 error 0n2 *** WARNING: Unable to verify timestamp for aswSP.SYS *** ERROR: Module load completed but symbols could not be loaded for aswSP.SYS Probably caused by : aswSP.SYS ( aswSP+102c4 )
I did both. I uninstalled Avast!, installed security essentials, and uninstalled the Cyberlink software. I will keep you posted if it BSODs again.
My System SpecsSystem Spec
08 Jun 2011   #6

Windows 7 Professional 64-bit
 
 
BSOD again

I received another BSOD and ran another report. I did uninstall Avast!
This one was a:
DRIVER_IRQL_NOT_LESS_OR_EQUAL
My System SpecsSystem Spec
08 Jun 2011   #7

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by howerj View Post
I received another BSOD and ran another report. I did uninstall Avast!
This one was a:
DRIVER_IRQL_NOT_LESS_OR_EQUAL

Newest one related to memory corruption Please run a system file check andrun memtest


Run a system file check to verify and repair your system files.
To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW

Read here for more information SFC /SCANNOW Command - System File Checker


Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.

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.

Let us know the results from the report at the end.



Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\060811-12105-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Machine Name:
Kernel base = 0xfffff800`02e1d000 PsLoadedModuleList = 0xfffff800`0305ae50
Debug session time: Wed Jun  8 05:52:55.942 2011 (GMT-4)
System Uptime: 0 days 0:09:30.002
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, 2, 0, fffff880052fe6b1}

*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880052fe6b1, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c50e0
 0000000000000000 

CURRENT_IRQL:  2

FAULTING_IP: 
usbhub!USBHUB_TriggerCallBacks+11
fffff880`052fe6b1 813848554220    cmp     dword ptr [rax],20425548h

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff80000b9c1b0 -- (.trap 0xfffff80000b9c1b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffffa80081c9050
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880052fe6b1 rsp=fffff80000b9c340 rbp=0000000000000004
 r8=0000000000000000  r9=0000000000000000 r10=f3db7a03fcf6c080
r11=fffff80000b9c430 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
usbhub!USBHUB_TriggerCallBacks+0x11:
fffff880`052fe6b1 813848554220    cmp     dword ptr [rax],20425548h ds:7bb4:00000000`00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e8cc69 to fffff80002e8d700

STACK_TEXT:  
fffff800`00b9c068 fffff800`02e8cc69 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff800`00b9c070 fffff800`02e8b8e0 : fffff880`0198b3c8 fffffa80`081c9050 00000000`00000028 0000057f`f8bb9fd8 : nt!KiBugCheckDispatch+0x69
fffff800`00b9c1b0 fffff880`052fe6b1 : fffff880`01987bb4 00000000`0007c0c8 fffff880`01987bb4 00000000`00000160 : nt!KiPageFault+0x260
fffff800`00b9c340 fffff880`052d8a67 : fffff800`030920c0 00000000`00000000 00000000`ffffffff fffff880`04406628 : usbhub!USBHUB_TriggerCallBacks+0x11
fffff800`00b9c370 fffff880`052d8ac1 : 00000000`00000004 fffff880`0441654a 00000000`00000001 fffffa80`07527050 : usbhub!UsbhTrapFatal_Dbg+0x13
fffff800`00b9c3b0 fffff880`052f0fd4 : fffffa80`081e1050 fffff880`0440af79 fffffa80`0825db08 00000000`00000000 : usbhub!FdoExt+0x35
fffff800`00b9c3f0 fffff800`02e785af : 00000000`00000000 00000000`00000004 00000000`00000001 fffffa80`07a58878 : usbhub!UsbhDmTimer+0x24
fffff800`00b9c460 fffff800`02e992ae : 00000000`00000002 fffff800`00b9c660 00000000`00000000 00000000`00000001 : nt!IopTimerDispatch+0x132
fffff800`00b9c570 fffff800`02e98de6 : fffff880`02d95960 00000000`00008eba 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`02e994ce : 00000001`53bf7978 fffff800`00b9cc58 00000000`00008eba fffff800`0300b9c8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`02e98cc7 : 00000000`6e3eb5c8 00000000`00008eba 00000000`6e3eb58a 00000000`000000ba : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`02e95eea : fffff800`03007e80 fffff800`03015c40 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !usbhub
    fffff880052fe38a - usbhub!UsbhInitGlobal+112
    [ d2:d0 ]
1 error : !usbhub (fffff880052fe38a)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BIT

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BIT

Followup: memory_corruption
---------
My System SpecsSystem Spec
Reply

 Random BSODs plagueing my new system




Thread Tools



Similar help and support threads for2: Random BSODs plagueing my new system
Thread Forum
Solved Random BSODs for 2 days, system has been stable for 2+ yrs BSOD Help and Support
Solved Random BSODs on new system BSOD Help and Support
Random BSODS daily, new system BSOD Help and Support
Solved Multiple random BSODs on new system,cannot install Win XP BSOD Help and Support
Unknown Random BSODs- Freshly recovered system BSOD Help and Support
Random BSODs when system is Idle. BSOD Help and Support
Solved Constant Random BSODs on a 5 days old system 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 12:25 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33