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: new bsod

30 Aug 2010   #1
colby122

Windows 7 Home Premium 64bit.
 
 
new bsod

Is Windows 7 . . .
- x64
- the original installed OS on the system? yea
- an OEM or full retail version? full retail
- [COLOR=#0072BC ! important][COLOR=#0072BC ! important]OEM[/COLOR] = came pre-installed on system? i built computer an installed everything myself[/COLOR]

- What is the age of system (hardware)? build it beginning of this year
- What is the age of OS installation (have you re-installed the OS?) jan / no


i get bsod most of the time when im watching videos on [COLOR=#0072BC ! important][COLOR=#0072BC ! important]youtube[/COLOR][/COLOR] etc and just random times when starting the computer up

-iv cleaned out my comp and checked all wires and im leaning towards it being ntoskrl.exe
being currupted and having a avalanch effect on hal.dll win32k.sys
dxgmmsl.sys and rt64win7.sys

-i tryed running Repair Install
the repair for windows 7 but id get to the point where it said where it couldnt update to the newest version
and didnt work. i also tryed the startup repair and that found nothing aswell.

- also i did a can with superantispyware as i was looking across youtube for help and came across rogue.antimalwaredoctor and that got taken care of but bsod's are still happening need help please.

thank you!


My System SpecsSystem Spec
.
30 Aug 2010   #2
JMH

Win 7 Ultimate 64-bit. SP1.
 
 

Quote   Quote: Originally Posted by colby122 View Post
Is Windows 7 . . .
- x64
- the original installed OS on the system? yea
- an OEM or full retail version? full retail
- [COLOR=#0072BC ! important][COLOR=#0072BC ! important]OEM[/COLOR] = came pre-installed on system? i built computer an installed everything myself[/COLOR]

- What is the age of system (hardware)? build it beginning of this year
- What is the age of OS installation (have you re-installed the OS?) jan / no


i get bsod most of the time when im watching videos on [COLOR=#0072BC ! important][COLOR=#0072BC ! important]youtube[/COLOR][/COLOR] etc and just random times when starting the computer up

-iv cleaned out my comp and checked all wires and im leaning towards it being ntoskrl.exe
being currupted and having a avalanch effect on hal.dll win32k.sys
dxgmmsl.sys and rt64win7.sys

-i tryed running Repair Install
the repair for windows 7 but id get to the point where it said where it couldnt update to the newest version
and didnt work. i also tryed the startup repair and that found nothing aswell.

- also i did a can with superantispyware as i was looking across youtube for help and came across rogue.antimalwaredoctor and that got taken care of but bsod's are still happening need help please.

thank you!

Hi Colby and welcome

These crashes were caused by memory corruption. The driver causing it is unknown but since your raid driver is almost two years old I would suspect that.

I would run a memory test

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.


I would also update all the drivers listed below

How To Find Drivers:
Quote:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

Let us know if you need assistance with that

Jan


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\083010-17612-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c00000 PsLoadedModuleList = 0xfffff800`02e3de50
Debug session time: Mon Aug 30 09:05:18.662 2010 (GMT-4)
System Uptime: 0 days 0:15:59.677
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff88003e1b2d0, 0, fffff80002f3e4d3, 1}


Could not read faulting driver name
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for win32k.sys - 
Probably caused by : memory_corruption

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

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: fffff88003e1b2d0, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002f3e4d3, 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 fffff80002ea80e0
 fffff88003e1b2d0 

FAULTING_IP: 
nt!PspSetContextThreadInternal+f3
fffff800`02f3e4d3 488b8d90e40000  mov     rcx,qword ptr [rbp+0E490h]

MM_INTERNAL_CODE:  1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0x50

PROCESS_NAME:  taskhost.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88003e0cc70 -- (.trap 0xfffff88003e0cc70)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=fffff88003e0ce01 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002f3e4d3 rsp=fffff88003e0ce00 rbp=fffff88003e0ce40
 r8=0000000000000023  r9=000000000000002b r10=fffff88003e0ce40
r11=0000000002cbf400 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!PspSetContextThreadInternal+0xf3:
fffff800`02f3e4d3 488b8d90e40000  mov     rcx,qword ptr [rbp+0E490h] ss:0018:fffff880`03e1b2d0=0000000000000000
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c1c91d to fffff80002c70740

STACK_TEXT:  
fffff880`03e0cb08 fffff800`02c1c91d : 00000000`00000050 fffff880`03e1b2d0 00000000`00000000 fffff880`03e0cc70 : nt!KeBugCheckEx
fffff880`03e0cb10 fffff800`02c6e82e : 00000000`00000000 fffffa80`039afb60 c1900000`4a409800 fffff880`03e0cce8 : nt! ?? ::FNODOBFM::`string'+0x428ff
fffff880`03e0cc70 fffff800`02f3e4d3 : fffff880`03e0ce98 0000007f`ffffffff 00000980`00000000 0000007f`fffffff8 : nt!KiPageFault+0x16e
fffff880`03e0ce00 fffff800`02f3dc65 : fffffa80`039afb60 00000000`00000000 fffffa80`039afb60 fffff880`03e0d270 : nt!PspSetContextThreadInternal+0xf3
fffff880`03e0d000 fffff800`02f3e323 : fffffa80`039afb60 00000000`00000000 fffffa80`05ac1060 00000000`00000000 : nt!PspInitializeThunkContext+0x1b4
fffff880`03e0da80 fffff800`02c4ed55 : fffff880`02fd3180 00000000`00000000 fffff800`02f3e200 fffffa80`039afb60 : nt!PspUserThreadStartup+0x123
fffff880`03e0dae0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartUserThread+0x16


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
3 errors : !nt (fffff80002f3e4cf-fffff80002f3e4f7)
fffff80002f3e4c0  4d  10  e8  99  f9  d0  ff  66  01  bb  c6  01  00  00  74 *b3 M......f......t.
fffff80002f3e4d0  8b  45  6c  48  8b  8d  90 *e4  00  00  48  33  cd  e8  2e  9a .ElH......H3....
...
fffff80002f3e4f0  48  8b  bd  d0  01  00  00 *33  8d  a5  a0  01  00  00  41  5d H......3......A]

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  STRIDE

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

BUCKET_ID:  X64_MEMORY_CORRUPTION_STRIDE

Followup: memory_corruption
---------
Code:
jraid.sys        fffff880`0115e000    fffff880`0117a000    0x0001c000    0x494a425b    12/18/2008 08:30:19                        
cpuz132_x64.sys        fffff880`039f3000    fffff880`039fb000    0x00008000    0x49cc0d03    3/26/2009 19:17:23                        
spldr.sys        fffff880`01675000    fffff880`0167d000    0x00008000    0x4a0858bb    5/11/2009 12:56:27                        
GEARAspiWDM.sys        fffff880`0457b000    fffff880`04588000    0x0000d000    0x4a1151c0    5/18/2009 08:17:04                        
amdxata.sys        fffff880`011a9000    fffff880`011b4000    0x0000b000    0x4a12f2eb    5/19/2009 13:56:59                        
rtkio.sys        fffff880`080c8000    fffff880`080d0000    0x00008000    0x4a3c7af9    6/20/2009 02:00:25
My System SpecsSystem Spec
30 Aug 2010   #3
CarlTR6

Windows 7 Ultimate 32 bit
 
 

Quote:
-iv cleaned out my comp and checked all wires and im leaning towards it being ntoskrl.exe
being currupted and having a avalanch effect on hal.dll win32k.sys
dxgmmsl.sys and rt64win7.sys
Just added information for you. ntoskrl.exe is a Microsoft system core file and is in all probability not the cause. Nor are hal.dll, win32k.sys, and dxgmmsl.sys likely to the cause. These are all Windows OS files. dxgmmsl.sys is a Microsoft Direct X driver. Microsoft system core files get blamed when the debug program cannot pinpoint the actual cause. Something else is corrupting memory and affecting these files.

Follow Jan's suggestions.
My System SpecsSystem Spec
.

31 Aug 2010   #4
Jonathan_King

Windows 7 Professional x64
 
 

Do run the Memtest Jan recommended. Here is a tutorial on it: RAM - Test with Memtest86+

Also, enable driver verifier. Hopefully that will flag a bad driver causing this memory corruption. Here is a tutorial for that: Driver Verifier - Enable and Disable
My System SpecsSystem Spec
31 Aug 2010   #5
jcgriff2

Windows 7 - Vista
 
 

Hi -

The Event viewer logs recorded 2,155 Live Kernel Events (0x117) beginning on 15 January 2010 and continue through 30 August 2010 -

0x117 = display driver failed to respond in the time alloted, but ultimately did recover; 0x117 is related to video.

The logs also show 376 BSODs, that began on 30 December 2009; this 1st BSOD clearly shows AVG as the probable cause -
Code:
Event[20699]:
Log Name: Application
Source: Windows Error Reporting
Date: 2009-12-30T00:20:40.000
Event ID: 1001
Description: 
Fault bucket X64_0x7E_avgldx64!operator_delete+d, type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0
Problem signature:
P1: 
P2: 
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 
Attached files:
C:\Windows\Minidump\123009-40373-01.dmp
C:\Users\Colby\AppData\Local\Temp\WER-77329-0.sysdata.xml
C:\Users\Colby\AppData\Local\Temp\WER22DB.tmp.WERInternalMetadata.xml
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_0_0_cab_0da329ae
Analysis symbol: X64_0x7E_avgldx64!operator_delete+d
Rechecking for solution: 0
Report Id: 123009-40373-01
Report Status: 0 

The system log goes back to 29 July 2010 and recorded 45 of the 376 BSODs -
Code:
0x50 (0xfffff88003e1b2d0, 0x0000000000000000, 0xfffff80002f3e4d3, 0x0000000000000001). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 083010-17612-01.
0xd1 (0x0000000000000060, 0x000000000000000a, 0x0000000000000001, 0xfffff88004118437). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 083010-25615-01.
0x1a (0x0000000000041790, 0xfffffa800223a7f0, 0x000000000000ffff, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 083010-23774-01.
0x1e (0x0000000000000000, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 083010-19656-01.
0x3b (0x00000000c0000005, 0x000000000001409a, 0xfffff88003966900, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 083010-22074-01.
0x7e (0xffffffffc0000005, 0xfffff80002cd4ef7, 0xfffff880035e7948, 0xfffff880035e71b0). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 082910-31574-01.
0x0a (0xffffffffffffffff, 0x0000000000000002, 0x0000000000000001, 0xfffff80002d080a2). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 082910-30357-01.
0x7e (0xffffffffc0000005, 0xfffff80002cb5c56, 0xfffff8800a72a598, 0xfffff8800a729e00). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 082910-20404-01.
0x0a (0xffffffffffffffff, 0x0000000000000002, 0x0000000000000001, 0xfffff80002d040a2). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 082910-19640-01.
0xd1 (0xfffffa7fb77a6198, 0x0000000000000002, 0x0000000000000000, 0xfffff880016b7649). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 082910-20467-01.
0x0a (0xfffff80802ec28f8, 0x000000000000000c, 0x0000000000000000, 0xfffff80002c98925). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 082910-19094-01.
0x7e (0xffffffffc0000005, 0xfffff88004393ce5, 0xfffff880021b96a8, 0xfffff880021b8f10). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 082910-19765-01.
0x1a (0x0000000000041284, 0x0000000076361001, 0x0000000000000000, 0xfffff70001080000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 082810-24304-01.
0x3b (0x00000000c000001d, 0xfffff88002ce7c0f, 0xfffff8800b3f3d90, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 082810-24850-01.
0x7f (0x0000000000000008, 0x0000000080050031, 0x00000000000006f8, 0xfffff80002f60715). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 082810-25911-01.
0x3b (0x00000000c0000005, 0xfffff96000109b1f, 0xfffff8800b3ad9d0, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 082810-40357-01.
0x3b (0x00000000c0000005, 0xfffff9600009010d, 0xfffff880098b0f50, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 082810-40903-01.
0x24 (0x00000000001904fb, 0xfffff880061ff148, 0xfffff880061fe9b0, 0xfffff880012ba613). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 082810-40560-01.
0x1a (0x0000000000005002, 0xfffff70001080000, 0x0000000000027dd8, 0x0802c4ebfffffffe). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 082810-18345-01.
0x3d (0xfffff88002f1b210, 0x0000000000000000, 0x0000000000000000, 0xfffff80002ccac9e). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 082810-19390-01.
0x3b (0x00000000c0000005, 0xfffff80002e0a90d, 0xfffff8800bd34c20, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 082810-18860-01.
0x1e (0xffffffffc0000005, 0xfffff80002cb03a4, 0x0000000000000000, 0xffffffffffffffff). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 082610-18813-01.
0x24 (0x00000000001904fb, 0xfffff88003354348, 0xfffff88003353bb0, 0xfffff8800123b494). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 082610-25209-01.
0xd1 (0x0000000000000000, 0x0000000000000002, 0x0000000000000008, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 082610-23618-01.
0x3b (0x00000000c0000005, 0xfffff80002c8a995, 0xfffff8800b68f120, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 082510-20810-01.
0x3b (0x00000000c0000005, 0xfffff9600009fb25, 0xfffff8800bfe51a0, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 082410-24679-01.
0x1e (0xffffffffc0000005, 0xfffff80002f99dce, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 082210-28220-01.
0x1e (0x0000000000000000, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 082210-24507-01.
0x0a (0x0000000000000028, 0x0000000000000002, 0x0000000000000000, 0xfffff80002d02518). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 082210-25459-01.
0x3b (0x00000000c0000005, 0xfffff88007742474, 0xfffff88007b89cc0, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 082210-34663-01.
0x116 (0xfffffa8006e0d4e0, 0xfffff88002c1cc48, 0x0000000000000000, 0x0000000000000002). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 081710-22214-01.
0x1e (0x0000000000000000, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 081510-20124-01.
0x1e (0xffffffffc0000005, 0xfffff80002c8556f, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 081510-19219-01.
0xbe (0xfffff960002fabe0, 0x80000001034d9021, 0xfffff88003e3c870, 0x000000000000000b). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 081510-20763-01.
0x1a (0x0000000000005100, 0xfffff6fc4002c3d0, 0x0000000000000001, 0x45f0000049e00121). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 081510-21200-01.
0x3b (0x00000000c0000005, 0xfffff80002f4bd5d, 0xfffff8800c41de30, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 081510-20404-01.
0x109 (0xa3a039d8965f465e, 0xb3b7465ee8dd6f20, 0xfffff88000d23658, 0x0000000000000001). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 081510-19593-01.
0x50 (0xfffffa7f8eb23c29, 0x0000000000000000, 0xfffff80002f2e40f, 0x0000000000000007). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 081110-21184-01.
0xd1 (0xfffff88001534c7c, 0x0000000000000002, 0x0000000000000008, 0xfffff88001534c7c). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 080410-21964-01.
0x1e (0xffffffffc0000005, 0xfffff80002cd3450, 0x0000000000000000, 0xffffffffffffffff). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 080410-19110-01.
0x50 (0xfffff87fdad747e8, 0x0000000000000000, 0xfffff88002d9b70a, 0x0000000000000005). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 080410-21871-01.
0x1a (0x0000000000041289, 0x0000000074a12001, 0x00000000000004ba, 0x4100000074a12405). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 080210-37580-01.
0x109 (0xa3a039d895d208dc, 0xb3b7465ee84edad2, 0xfffff800030ab5a0, 0x0000000000000001). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 080210-21138-01.
0x50 (0xfffff87fd9c2b4a8, 0x0000000000000000, 0xfffff80002fba64d, 0x0000000000000005). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 080210-24304-01.
0x3b (0x00000000c000001d, 0xfffff9600001f3f6, 0xfffff88005dc6ec0, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 072910-21153-01.
The BSODs began the same day as Windows 7 was installed.

I would suggest that in addition to the running memtest86+ that you run HDD diagnostics as well becuase several of the BSODs had a bugcheck = 0x24 = NTFS file system = possible HDD problems.

Start with SeaTools (for DOS) --> SeaTools | Seagate

Burn ISO to CD with ImgBurn --> The Official ImgBurn Website

Boot with SeaTools CD.

If SeaTools comes up OK, run HDD manufacturer's diagnostics --> Hard Drive Diagnostics Tools and Utilities (Storage) - TACKtech Corp.

If all hardware checks out, I would then wipe the HDD with KillDisk and reinstall Windows 7.

KillDisk --> Format HDD jcgriff2.com

Regards. . .

jcgriff2
.
My System SpecsSystem Spec
Reply

 new bsod




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