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 from 5mins to 30min's after start, usually just blue w/no info.

13 Jun 2015   #1
lamia1

windows 7 home
 
 
bsod from 5mins to 30min's after start, usually just blue w/no info.

this time it did give the usual bsod info about whether this is first time. No new hard or software, its happened booting from windows on ssd as well as hhd and while in safe mode. Please help!! I will be very grateful.


My System SpecsSystem Spec
.
14 Jun 2015   #2
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

Allot of important info is missing from your zip, please follow Blue Screen of Death (BSOD) Posting Instructions to grab all and upload a new report here.
My System SpecsSystem Spec
14 Jun 2015   #3
lamia1

windows 7 home
 
 
bsod proper file uploaded

thanks for responding. I apparently uploaded the wrong files. I have attached yesterdays and today's zip of the diagnostic. I was able to keep the pc up and running after the one crash yesterday so not sure what Sun's file might show. Usually it crashes every day.
My System SpecsSystem Spec
.

14 Jun 2015   #4
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

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


Loading Dump File [C:\Users\YUSSIKAT\Downloads\PHIL-PC-Sun_06_14_2015_161417_48\061315-5803-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18869.amd64fre.win7sp1_gdr.150525-0603
Machine Name:
Kernel base = 0xfffff800`03211000 PsLoadedModuleList = 0xfffff800`03458730
Debug session time: Sun Jun 14 01:49:35.651 2015 (UTC + 6:00)
System Uptime: 0 days 0:06:29.962
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff8000356d167, 2, 0, fffff800032afc22}

Probably caused by : memory_corruption

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

0: 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: fffff8000356d167, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff800032afc22, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034c2100
GetUlongFromAddress: unable to read from fffff800034c21c0
 fffff8000356d167 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
nt!RtlDispatchException+122
fffff800`032afc22 410fb60c24      movzx   ecx,byte ptr [r12]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0xA

PROCESS_NAME:  downloader.exe

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

TRAP_FRAME:  fffff88008923670 -- (.trap 0xfffff88008923670)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff80003407f68 rbx=0000000000000000 rcx=fffbf80003407f68
rdx=00000000000007ff rsi=0000000000000000 rdi=0000000000000000
rip=fffff800032896da rsp=fffff88008923800 rbp=0000000000000000
 r8=fffff80003211000  r9=0000000000000000 r10=fffffffffffffffe
r11=fffff80003404e80 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!KiCommitThreadWait+0x2aa:
fffff800`032896da 488901          mov     qword ptr [rcx],rax ds:fffbf800`03407f68=????????????????
Resetting default scope

EXCEPTION_RECORD:  fffff880089235c8 -- (.exr 0xfffff880089235c8)
ExceptionAddress: fffff800032896da (nt!KiCommitThreadWait+0x00000000000002aa)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

LAST_CONTROL_TRANSFER:  from fffff80003284e69 to fffff800032858c0

STACK_TEXT:  
fffff880`08922438 fffff800`03284e69 : 00000000`0000000a fffff800`0356d167 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`08922440 fffff800`03283ae0 : 00000000`00000000 fffff800`032b1470 00000000`00000001 00000000`00000047 : nt!KiBugCheckDispatch+0x69
fffff880`08922580 fffff800`032afc22 : fffff800`0356d167 fffff880`08922758 fffff880`089235c8 fffff800`03211000 : nt!KiPageFault+0x260
fffff880`08922710 fffff800`032c0e81 : fffff880`089235c8 fffff880`08922e20 fffff880`00000000 fffffa80`0ca3ba60 : nt!RtlDispatchException+0x122
fffff880`08922df0 fffff800`03284f42 : fffff880`089235c8 fffff800`03407f60 fffff880`08923670 fffffa80`1152dc10 : nt!KiDispatchException+0x135
fffff880`08923490 fffff800`0328384a : 00000000`00000000 fffff800`03288473 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`08923670 fffff800`032896da : fffffa80`1152db50 fffffa80`1152db50 fffffa80`00000000 fffff800`00000000 : nt!KiGeneralProtectionFault+0x10a
fffff880`08923800 fffff800`0328db63 : fffffa80`0f5b4f20 fffff800`0326d657 fffffa80`00000067 00000000`00000000 : nt!KiCommitThreadWait+0x2aa
fffff880`08923890 fffff800`0356d167 : 00000000`00000000 fffff800`03804b01 00000000`00000001 00000000`0000000f : nt!KeRemoveQueueEx+0x323
fffff880`08923950 fffff800`032717b6 : 00000000`002ea600 fffff880`08923a68 fffff880`08923a88 00000000`002c3801 : nt!IoRemoveIoCompletion+0x47
fffff880`089239e0 fffff800`03284b53 : fffffa80`1152db50 00000000`775605c0 fffff880`00000000 fffffa80`114c6120 : nt!NtWaitForWorkViaWorkerFactory+0x285
fffff880`08923ae0 00000000`774af4ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`01e3fc38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x774af4ba


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff800032857e6 - nt!KiUmsExit+a6
    [ 48:08 ]
1 error : !nt (fffff800032857e6)

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

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_memory_corruption_one_bit

FAILURE_ID_HASH:  {2dbb898e-c425-bad1-90fe-71c78117521f}

Followup: memory_corruption
---------
Code:
Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\YUSSIKAT\Downloads\PHIL-PC-Sun_06_14_2015_161417_48\060915-8829-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18839.amd64fre.win7sp1_gdr.150427-0707
Machine Name:
Kernel base = 0xfffff800`0325c000 PsLoadedModuleList = 0xfffff800`034a3730
Debug session time: Tue Jun  9 06:22:55.469 2015 (UTC + 6:00)
System Uptime: 0 days 0:22:00.780
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {411, fffff6fc40024770, 1aa000033ac80860, ffbff6fc40024771}

Probably caused by : memory_corruption

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000000411, The subtype of the bugcheck.
Arg2: fffff6fc40024770
Arg3: 1aa000033ac80860
Arg4: ffbff6fc40024771

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


BUGCHECK_STR:  0x1a_411

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

TRAP_FRAME:  fffff88008a99290 -- (.trap 0xfffff88008a99290)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000005 rbx=0000000000000000 rcx=fffff8a00361b000
rdx=fffffa80101c9978 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880048eebe3 rsp=fffff88008a99420 rbp=fffff8a002727c30
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=fffff88008a98f80 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
dxgkrnl!DXGCONTEXT::Present+0x362b:
fffff880`048eebe3 4c8dadc0000000  lea     r13,[rbp+0C0h]
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800032ad2ad to fffff800032d08c0

STACK_TEXT:  
fffff880`08a98f38 fffff800`032ad2ad : 00000000`0000001a 00000000`00000411 fffff6fc`40024770 1aa00003`3ac80860 : nt!KeBugCheckEx
fffff880`08a98f40 fffff800`03301c61 : 1aa00003`3ac80860 fffff6fc`40024770 0000007f`fffffff8 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x6051
fffff880`08a98f90 fffff800`032ee61f : 00000000`00000000 1ba00003`3ad80860 00000000`00000000 fffff800`03510540 : nt!MiResolveTransitionFault+0x381
fffff880`08a99020 fffff800`032de5bb : fffffa80`11b25b50 fffff880`08a99200 fffffa80`11b25b50 fffff880`08a99280 : nt!MiDispatchFault+0x95f
fffff880`08a99130 fffff800`032ce9ee : 00000000`00000008 fffff880`048eebe3 fffffa80`00000000 00000000`00000000 : nt!MmAccessFault+0xe1b
fffff880`08a99290 fffff880`048eebe3 : 00000000`00000000 00000000`00000000 fffff8a0`40000880 fffff880`00000000 : nt!KiPageFault+0x16e
fffff880`08a99420 fffff880`048eafaf : fffff8a0`40000880 fffff8a0`00000780 fffff880`08a99780 fffff880`08a997b0 : dxgkrnl!DXGCONTEXT::Present+0x362b
fffff880`08a99740 fffff960`001dacb8 : fffffa80`11b25b50 00000000`002bd238 fffff8a0`016b0530 fffff8a0`00000010 : dxgkrnl!DxgkPresent+0x543
fffff880`08a99ab0 fffff800`032cfb53 : fffffa80`11b25b50 00000000`025bfb20 000007fe`00000000 fffffa80`11b2b270 : win32k!NtGdiDdDDIPresent+0x18
fffff880`08a99ae0 000007fe`fe09145a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`025bec48 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`fe09145a


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff800032d0016 - nt!KiExceptionDispatch+196
    [ 0c:4c ]
    fffff800032d0106 - nt!KiUmsFastReturnToUser+46 (+0xf0)
    [ 83:87 ]
    fffff800032d011e - nt!KiUmsFastReturnToUser+5e (+0x18)
    [ fc:7c ]
    fffff800032d0186 - nt!KiUmsFastReturnToUser+c6 (+0x68)
    [ 45:05 ]
    fffff800032d028e - nt!KiUmsRestoreUch+e (+0x108)
    [ 48:68 ]
    fffff800032d030e - nt!KiUmsTrapEntry+4e (+0x80)
    [ 29:69 ]
    fffff800032d031e - nt!KiUmsTrapEntry+5e (+0x10)
    [ 44:04 ]
    fffff800032d03de - nt!KiUmsTrapEntry+11e (+0xc0)
    [ 00:06 ]
    fffff800032d04ee - nt!KiUmsCallEntry+2e (+0x110)
    [ e0:a0 ]
    fffff800032d05a6 - nt!KiUmsCallEntry+e6 (+0xb8)
    [ c4:84 ]
    fffff800032d0616 - nt!KiUmsCallEntryContinue+56 (+0x70)
    [ 00:04 ]
    fffff800032d0d57 - nt!KiRestoreDebugRegisterState+57 (+0x741)
    [ d9:f9 ]
12 errors : !nt (fffff800032d0016-fffff800032d0d57)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  LARGE

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE

BUCKET_ID:  X64_MEMORY_CORRUPTION_LARGE

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_memory_corruption_large

FAILURE_ID_HASH:  {6332b0e4-cf0e-2392-6ba8-f96ca91b7f36}

Followup: memory_corruption
---------
Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.
Quote:
The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
3. Test the next stick of RAM (stick #2) in the next motherboard slot.
*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.
information   Information
Errors are sometimes found after 8 passes.

Tip   Tip
Memtest should be done overnight.
My System SpecsSystem Spec
Reply

 bsod from 5mins to 30min's after start, usually just blue w/no info.




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Windows theme changes to basic while streaming-recording after 30min
Recently, I started streaming some games and recording it to disk. Windows has been flicking into Windows Basic theme after about 30min. How can I set windows to *not* change theme regardless of situation? I honestly couldn't care if windows claims my memory is low (my video card has 3GB and I have...
Themes and Styles
BSOD once a day after 30min of start up then doesnt at all
Hi guys, Im really stumped I have had tried a lot of things to get rid of this BSOD but nothing is working for me. I recently updated my new pc with some new hardware below: Corsair Vengeance 12GB (3x4GB) DDR3 PC3-12800C9 1600MHz Tri MSI GeForce GTX 680 Twin Frozr 2048MB x Usall...
BSOD Help and Support
BLUE SCREEN with the all the info you need on a zip file! thx in adva
Guys i am FED UP !!! :( :mad: with this blue screens i have on Windows 7 ... never i got them on XP .. anyway it happens when i play games .. like silkroad online and Leaque of LEgends .. i have updated my video driver cards and sound ... and i am still getting all those differend kind of BOSD...
BSOD Help and Support
BSOD Crash After startup about 5mins after.
Hey, I hope i can get this issue resolved. Basic Info: OS: Windows 7 Home premium x64 Its the original OS that came with the system ALREADY installed. Its about 2 months Old. I haven't reinstalled It at all. (Don't Have a CD) Also attached DXDIAG.txt
BSOD Help and Support
BSOD every 30min - 1hr :(
Started a couple weeks back, but its happening much too frequently. Happens when I'm browsing the net (but thats most of my computer time) - doesn't matter which browser. I did a fresh install of Windows 7 x64 today, but the same issue persists. Software installed:after reinstalling windows: Zone...
BSOD Help and Support
Need info on blue screen message
Could someone please tell me why I recieved the following problem message Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7600.2.0.0.768.3 Locale ID: 1033 Additional information about the problem: BCCode: 3b BCP1: 00000000C000001D BCP2: FFFFF88000000000 ...
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 17:20.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App