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: Frequent BSoDs


05 Sep 2010   #1

Windows 7 Professional 64-bit
 
 
Daily BSoD

I built my computer 3 weeks ago and I've been having BSoD errors when I turn on the computer in the morning.

I've ran disk check, memtest86, and all my drivers are up to date.

My OS: Windows 7 Professional 64-Bit [Full Retail]
- I bought it online and used an USB to boot
Age of System: 3 weeks
Age of OS: Installed a week ago

Any help is appreciated!

Thanks

My System SpecsSystem Spec
.

05 Sep 2010   #2

Windows 7 Professional 64-bit
 
 

Added the minidump files
My System SpecsSystem Spec
05 Sep 2010   #3

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by SpeC View Post
Added the minidump files


Spec hi and welcome

these are still pointing to memory corruption. How long did you run memtest for? did you run one stick at a time? did you try each mobo slot with known good memory?


Ken


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\minidump\090110-23758-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e67000 PsLoadedModuleList = 0xfffff800`030a4e50
Debug session time: Wed Sep  1 13:49:01.202 2010 (GMT-4)
System Uptime: 0 days 0:01:37.685
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffa8181d44140, 2, 1, fffff80002eed801}

Probably caused by : memory_corruption ( nt!MmCreateKernelStack+e6 )

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

1: 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: fffffa8181d44140, 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: fffff80002eed801, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff8000310f0e0
 fffffa8181d44140 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MmCreateKernelStack+e6
fffff800`02eed801 49891cd2        mov     qword ptr [r10+rdx*8],rbx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff88006bf9110 -- (.trap 0xfffff88006bf9110)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff6fc4003ad00 rbx=0000000000000000 rcx=000000000809c15c
rdx=00000000303a8828 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002eed801 rsp=fffff88006bf92a0 rbp=0000000000000002
 r8=fffff880075a3000  r9=0000000fffffffff r10=fffffa8000000000
r11=fffffa8001d440e0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!MmCreateKernelStack+0xe6:
fffff800`02eed801 49891cd2        mov     qword ptr [r10+rdx*8],rbx ds:fffffa81`81d44140=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ed6ca9 to fffff80002ed7740

STACK_TEXT:  
fffff880`06bf8fc8 fffff800`02ed6ca9 : 00000000`0000000a fffffa81`81d44140 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`06bf8fd0 fffff800`02ed5920 : fffff880`06bf9390 fffffa80`06cf4b61 fffffa80`04f33100 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`06bf9110 fffff800`02eed801 : 00000000`00000001 fffffa80`04f33184 fffffa80`0467cb00 fffffa80`04f33180 : nt!KiPageFault+0x260
fffff880`06bf92a0 fffff800`02ee6fc4 : fffffa80`063ec170 fffffa80`06cf4b60 fffffa80`06054540 fffff8a0`026a4140 : nt!MmCreateKernelStack+0xe6
fffff880`06bf9380 fffff880`01210b69 : fffff880`01212534 fffff880`06bf9498 00000000`0001f000 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0x244
fffff880`06bf9460 fffff880`01210036 : fffffa80`0461daf0 00000000`00000000 fffff8a0`026a4140 fffff880`01071160 : Ntfs!NtfsMultipleAsync+0xa9
fffff880`06bf94d0 fffff880`01213526 : fffffa80`06054540 fffffa80`06794c10 fffff8a0`026a4140 fffff8a0`026a4010 : Ntfs!NtfsNonCachedIo+0x216
fffff880`06bf9650 fffff880`01215f78 : fffffa80`06054540 fffffa80`06794c10 fffff880`06bf9800 fffffa80`0468cc01 : Ntfs!NtfsCommonRead+0x7a6
fffff880`06bf97f0 fffff880`0107223f : fffffa80`06794fb0 fffffa80`06794c10 fffffa80`0468cc30 00000000`00000000 : Ntfs!NtfsFsdRead+0x1b8
fffff880`06bf98a0 fffff880`010706df : fffffa80`0466cde0 fffffa80`06794c10 fffffa80`0466cd00 fffffa80`06794c10 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`06bf9930 fffff800`02ec91f2 : fffffa80`06794c30 fffffa80`068dfa20 00000000`00000403 00000008`0000001f : fltmgr!FltpDispatch+0xcf
fffff880`06bf9990 fffff800`03177947 : fffffa80`06611600 fffffa80`06611600 fffffa80`0638d4d1 fffffa80`06e5ba90 : nt!IoPageRead+0x252
fffff880`06bf9a20 fffff800`03177a41 : fffffa80`06ed7eb0 fffffa80`06cf4b60 fffff880`06bf9b40 00000000`00000005 : nt!MiPfExecuteReadList+0xff
fffff880`06bf9a80 fffff800`02e89a67 : fffffa80`06ed7eb0 00000000`00000000 00000000`00000000 fffff800`0307c5a0 : nt!MmPrefetchForCacheManager+0xb5
fffff880`06bf9ad0 fffff800`02ecb576 : fffffa80`068dfa20 fffffa80`06cf4b00 fffff880`000000a8 fffff880`03e52734 : nt!CcPerformReadAhead+0x2f3
fffff880`06bf9c00 fffff800`02ee4961 : fffffa80`036e43d0 fffff800`02ecb358 fffff800`030de150 00000000`00000002 : nt!CcWorkerThread+0x21e
fffff880`06bf9cb0 fffff800`0317bc06 : 00000000`0805e0ef fffffa80`06cf4b60 00000000`00000080 fffffa80`036cd040 : nt!ExpWorkerThread+0x111
fffff880`06bf9d40 fffff800`02eb5c26 : fffff880`009e9180 fffffa80`06cf4b60 fffffa80`06ce0600 00000000`00000212 : nt!PspSystemThreadStartup+0x5a
fffff880`06bf9d80 00000000`00000000 : fffff880`06bfa000 fffff880`06bf4000 fffff880`06bf99f0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MmCreateKernelStack+e6
fffff800`02eed801 49891cd2        mov     qword ptr [r10+rdx*8],rbx

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MmCreateKernelStack+e6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MmCreateKernelStack+e6

BUCKET_ID:  X64_0xA_nt!MmCreateKernelStack+e6

Followup: MachineOwner
---------
My System SpecsSystem Spec
.


05 Sep 2010   #4

Windows 7 Professional 64-bit
 
 

I ran the memtest86 once (took around an hour) but I've read that I should leave it for 5-10 passes. I plan on running it overnight tonight.

Overnight, I'll test both sticks of RAM. If I don't get any errors, should I still test one stick at a time, and each motherboard slot?

Thanks for the post!
My System SpecsSystem Spec
06 Sep 2010   #5

Windows 7 - Vista
 
 

Hi -

One of the 5 dumps named F-Secure as the probable cause -
Code:
fsvista.sys  Tue Mar 18 02:37:07 2008 (47DF6313) - F-Secure Vista Support Driver - Products & Store - Buy F-Secure products against viruses and malware to protect you computer and your valuable content
fsdfw.sys    Wed Jul 08 04:11:48 2009 (4A5454C4) - F-Secure Distributed Firewall Driver - Products & Store - Buy F-Secure products against viruses and malware to protect you computer and your valuable content
fsgk.sys     Sun Jul 18 05:06:56 2010 (4C42C430) - F-Secure Gatekeeper - Products & Store - Buy F-Secure products against viruses and malware to protect you computer and your valuable content
Remove F-Secure --> View Support Knowledge Base Article

Reboot upon completion

Install MSE --> http://www.microsoft.com/security_essentials/

Another had bugcheck = 0x24 = NTFS File System = possible HDD issue

Run HDD diagnostics -

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.

2 others - bugcheck = 0x1a = memory management error. Memtes86+ good idea to run as well.

Other bugcheck = 0xa = driver attempted to access pageable memory (or bad memory) at a time it should not have (IRQL too high). Run Driver Verifier after all above steps completed.

Driver Verifier -- Driver Verifier - jcgriff2.com

Windbg Logs
--> http://jcgriff2.com/dbug_logs/_99-db..._jcgriff2_.txt
--> http://jcgriff2.com/dbug_logs/_99-db...riff2_.txt.zip

Regards. . .

jcgriff2

`

BSOD BUGCHECK SUMMARY
Code:
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Sep  5 13:46:21.193 2010 (GMT-4)
System Uptime: 0 days 0:10:49.336
*** WARNING: Unable to verify timestamp for fsgk.sys
*** ERROR: Module load completed but symbols could not be loaded for fsgk.sys
Probably caused by : fsgk.sys ( fsgk+d060 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  fssm32.exe
Bugcheck code 00000050
Arguments fffff820`01d09268 00000000`00000000 fffff880`064d0060 00000000`00000005
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Sep  1 14:07:27.517 2010 (GMT-4)
System Uptime: 0 days 0:07:52.626
Probably caused by : Ntfs.sys ( Ntfs!NtfsExpandHashTable+75 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
BUGCHECK_STR:  0x24
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`097bf678 fffff880`097beee0 fffff880`0130b535
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Sep  1 13:56:19.996 2010 (GMT-4)
System Uptime: 0 days 0:02:30.105
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33906 )
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  avgchsva.exe
Bugcheck code 0000001A
Arguments 00000000`00041790 fffffa80`021bef80 00000000`0000ffff 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Sep  1 13:50:33.434 2010 (GMT-4)
System Uptime: 0 days 0:00:49.917
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33906 )
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  avgemc.exe
Bugcheck code 0000001A
Arguments 00000000`00041790 fffffa80`021a7a00 00000000`0000ffff 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Sep  1 13:49:01.202 2010 (GMT-4)
System Uptime: 0 days 0:01:37.685
Probably caused by : memory_corruption ( nt!MmCreateKernelStack+e6 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
Bugcheck code 0000000A
Arguments fffffa81`81d44140 00000000`00000002 00000000`00000001 fffff800`02eed801
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
 
by jcgriff2     
 
        J. C. Griffith, Microsoft MVP 
 
 https://mvp.support.microsoft.com/profile/Griffith 
 
 www.jcgriff2.com 
 
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
My System SpecsSystem Spec
06 Sep 2010   #6

Windows 7 Professional 64-bit
 
 

Just ran Memtest86 overnight for 9 hours and after 12 passes, 0 errors found. (Both sticks of RAM)

jcgriff2, I'll try your list of suggestions and post the results after.

Thanks for your input!
My System SpecsSystem Spec
07 Sep 2010   #7

Windows 7 Professional 64-bit
 
 

- F-Secure program removed
- MSE Installed
- Ran SeaTools CD
- Short Test: Passed
- Long Test: Passed
- I couldn't run the Samsung Hard Drive Diagnostics Tool because the program wasn't Compatible with a 64-bit OS
- Ran Memtest86+
- 12 Passes, 0 errors

As for the Driver Verifier, I'm going to wait until tomorrow and see if I get any errors or BSoDs before I run it

Thanks for the advice!
My System SpecsSystem Spec
07 Sep 2010   #8

Windows 7 - Vista
 
 

Hi -

Looks good so far.

Driver Verifier will be the final test on the software side. If it flags a 3rd party driver it will BSOD your system.

Good Luck to you. Thank you for posting back.

Regards. . .

jcgriff2

`
My System SpecsSystem Spec
07 Sep 2010   #9

Windows 7 Professional 64-bit
 
 

When I tried turning on my computer this morning, I got a BSoD. When I tried to restart my computer, I kept getting more BSoD.

I'll upload the new mini dump files and run the verifier.

Thanks!
My System SpecsSystem Spec
08 Sep 2010   #10

Windows 7 - Vista
 
 

Hi -

6 BSODs; 5 different bugchecks -
Code:
BugCheck 50, {fffffa0005a63cf8, 1, fffff800022adc56, 7}
BugCheck 24, {1904fb, fffff88008420718, fffff8800841ff80, fffff88001308c27}
BugCheck 1A, {41790, fffffa8001bbfbb0, ffff, 0}
BugCheck 50, {fffffa0006ab2958, 0, fffff8000319248e, 7}
BugCheck 3B, {80000003, fffff8800415a446, fffff88004bec210, 0}
BugCheck 50, {fffff82001d1e080, 0, fffff80002ef7ca0, 5}
(3) 0x50 = invalid memory referenced

0x24 = NTFS File system = potential HDD issue

0x1a = memory management error

0x3b (0x80000003,,,) = System service threw an exception; exception = 0x80000003 = invalid arguments; probable cause = NVIDIA

None of the dumps were VERIFIER_ENABLED. I don't see any drivers out of place here at this time. Back to hardware tests again - RAM and HDD diagnostics -

Frequent BSoDs


Windbg Logs
--> http://jcgriff2.com/dbug_logs/_99-db..._jcgriff2_.txt
--> http://jcgriff2.com/dbug_logs/_99-db...riff2_.txt.zip

Regards. . .

jcgriff2

`

BSOD BUGCHECK SUMMARY
Code:
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Sep  7 12:34:46.587 2010 (GMT-4)
System Uptime: 0 days 0:01:12.477
Probably caused by : ntkrnlmp.exe ( nt!RtlDeleteNoSplay+2a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  explorer.exe
Bugcheck code 00000050
Arguments fffffa00`05a63cf8 00000000`00000001 fffff800`022adc56 00000000`00000007
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Sep  7 12:32:55.190 2010 (GMT-4)
System Uptime: 0 days 0:01:22.673
Probably caused by : Ntfs.sys ( Ntfs!NtfsFindPrefixHashEntry+1fe )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  MsMpEng.exe
BUGCHECK_STR:  0x24
Bugcheck code 00000024
Arguments 00000000`001904fb fffff880`08420718 fffff880`0841ff80 fffff880`01308c27
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Sep  7 12:30:54.820 2010 (GMT-4)
System Uptime: 0 days 0:04:26.928
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+33906 )
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
Bugcheck code 0000001A
Arguments 00000000`00041790 fffffa80`01bbfbb0 00000000`0000ffff 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Sep  7 12:25:51.743 2010 (GMT-4)
System Uptime: 0 days 0:02:50.851
Probably caused by : ntkrnlmp.exe ( nt!ObpCloseHandleTableEntry+3e )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  svchost.exe
Bugcheck code 00000050
Arguments fffffa00`06ab2958 00000000`00000000 fffff800`0319248e 00000000`00000007
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Sep  7 12:22:23.369 2010 (GMT-4)
System Uptime: 0 days 0:00:23.852
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : memory_corruption
DEFAULT_BUCKET_ID:  CODE_CORRUPTION
BUGCHECK_STR:  0x3B
PROCESS_NAME:  csrss.exe
Bugcheck code 0000003B
Arguments 00000000`80000003 fffff880`0415a446 fffff880`04bec210 00000000`00000000
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Sep  7 12:20:14.732 2010 (GMT-4)
System Uptime: 0 days 0:01:03.215
Probably caused by : fileinfo.sys ( fileinfo!FIStreamGetNext+5b )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  svchost.exe
Bugcheck code 00000050
Arguments fffff820`01d1e080 00000000`00000000 fffff800`02ef7ca0 00000000`00000005
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
 
by jcgriff2     
 
      J. C. Griffith, Microsoft MVP 
 
 https://mvp.support.microsoft.com/profile/Griffith 
 
 www.jcgriff2.com 
 
ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии
My System SpecsSystem Spec
Reply

 Frequent BSoDs




Thread Tools



Similar help and support threads for2: Frequent BSoDs
Thread Forum
Frequent BSODs Win 7 x64 BSOD Help and Support
Solved Frequent BSODs BSOD Help and Support
Frequent BSODs BSOD Help and Support
Very frequent BSODs BSOD Help and Support
Bsods becoming frequent BSOD Help and Support
Frequent BSODs BSOD Help and Support
Frequent BSODs 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 06:28 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