New PC, developed BSOD issues within first couple days


  1. R4VEN
    Posts : 4
    Windows 7 x64 Home Premium (SP1)
       New #1

    New PC, developed BSOD issues within first couple days


    Hey all,

    I've just recently finished a new build and I have been getting, as far as I can tell, random BSOD errors. The first OS on my machine was Windows 7 (which was getting BSODs from time to time), so I upgraded to Windows 10 to see if that would change anything. If I recall correctly, I didn't have any errors whatsoever during that period. Eventually I went back to Windows 7 due to personal preferences, and the BSOD errors came back with it.

    From the research myself and my roommates have done so far, we think it might be a hard drive related issue, though potentially it could be related to RAM as well. Any help would greatly appreciated!
      My Computer
    Quote Quote

  3. Boozad
    Posts : 6,741
    W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
       New #2

    The single dump in your logs is a 0x1A which is usually down to a device driver or RAM, unfortunately the dump is partially corrupt and there's not a lot I can read from it. The one thing that is showing looks like it's pointing to your GPU.
    Code:
    BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

LAST_CONTROL_TRANSFER:  from fffff800030fba40 to fffff8000308a5c0

STACK_TEXT:  
fffff880`21d7bf98 fffff800`030fba40 : 00000000`0000001a 00000000`00041790 fffffa80`05fff910 00000000`0000ffff : nt!KeBugCheckEx
fffff880`21d7bfa0 fffff800`03077a3f : fffffa80`00000000 00000000`5b3dffff 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x338c4
fffff880`21d7c160 fffff800`03089853 : ffffffff`ffffffff fffff8a0`1288b6d8 fffff8a0`1288b700 00000000`00008000 : nt!NtFreeVirtualMemory+0x61f
fffff880`21d7c260 fffff800`03085e10 : fffff880`0414062e fffff8a0`155083d0 fffffa80`12330b10 fffffa80`11e5c010 : nt!KiSystemServiceCopyEnd+0x13
fffff880`21d7c3f8 fffff880`0414062e : fffff8a0`155083d0 fffffa80`12330b10 fffffa80`11e5c010 fffff8a0`1288b6d0 : nt!KiServiceLinkage
fffff880`21d7c400 fffff880`0412bc93 : fffffa80`0d5ca000 fffff8a0`0b406da0 00000000`00000001 fffffa80`0d5ca000 : dxgmms1!VIDMM_PROCESS_HEAP::Free+0xa2
fffff880`21d7c430 fffff880`04126637 : fffffa80`1339b690 00000000`00000001 fffff8a0`155083d0 00000000`00000001 : dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+0x11b
fffff880`21d7c4e0 fffff880`0410cecc : fffff880`00000000 fffffa80`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x19b
fffff880`21d7c5b0 fffff880`0404dccc : 00000000`00000000 fffff8a0`14fcd000 fffff8a0`14fcd000 00000000`00000001 : dxgmms1!VidMmCloseAllocation+0x44
fffff880`21d7c5e0 fffff880`0404d65f : fffff8a0`14fcd000 fffff8a0`14fce300 fffff8a0`00000000 00000000`00000799 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x248
fffff880`21d7c6d0 fffff880`0404d8e1 : fffff8a0`14fcd000 fffff8a0`14fcd000 00000000`00000001 00000000`00000000 : dxgkrnl!DXGDEVICE::ProcessTerminationList+0xa3
fffff880`21d7c720 fffff880`04051aec : 00000000`00000000 fffff880`21d7cb60 fffff8a0`03201700 fffff880`040183af : dxgkrnl!DXGDEVICE::TerminateAllocations+0xb9
fffff880`21d7c770 fffff880`04054285 : fffff8a0`14fcd000 fffff880`21d7c850 00000000`4b677800 00000000`00000701 : dxgkrnl!DXGDEVICE::DestroyAllocation+0x44c
fffff880`21d7c800 fffff960`0024b816 : 00000000`00000000 fffffa80`1326c6c0 00000000`00000020 00000000`750261b8 : dxgkrnl!DxgkDestroyAllocation+0xa9d
fffff880`21d7cab0 fffff800`03089853 : fffffa80`1326c6c0 00000000`000009e8 00000000`00000000 fffffa80`121c9a20 : win32k!NtGdiDdDDIDestroyAllocation+0x12
fffff880`21d7cae0 00000000`7504146a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`19dbe098 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7504146a
    Your nVidia driver looks up to date, so follow the GPU stress test below. This is partial guesswork here don't forget given the single dump is corrupt.

    Run Furmark to stress test your GPU. Video Card - Stress Test with Furmark

       Note
    Run Furmark for around 30 minutes.

       Warning
    Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them, if the temperature continues to rise steadily once it has reached 80°C be prepared to stop the test so as to not damage your GPU.
      My Computer
    Quote Quote

  4. R4VEN
    Posts : 4
    Windows 7 x64 Home Premium (SP1)
    Thread Starter
       New #3

    Hey Boozad!

    Thanks for the response. I ran Furmark for 30 minutes, GPU temp didn't go over 70 and there were no artifacts that I could see. Is there a way for me to convert the log to a format that's supported in the upload tool, or is that file not necessary? I've also attached a picture of a previous BSOD (in other words not the most recent one, so they may be different issues at this point). I don't know if it helps, but on the restart after most of the BSOD occurrences, instead of booting to Windows I get a black screen that says "Reboot and select proper boot device or insert boot media in selected boot device."

    Thanks again!
      My Computer
    Quote Quote

  6. Boozad
    Posts : 6,741
    W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
       New #4

    Can you run the DM Log Collector again to grab the latest dump please and attach it to you next post. A 0x7A could be down to a number of things.

    Run SeaTools to check the integrity of your HDD (Do not use on an SSD). SeaTools for DOS and Windows - How to Use

    Run chkdsk. Disk Check

    When booted into Windows open an elevated command prompt, type in sfc /scannow and hit enter.
      My Computer
    Quote Quote

  7. R4VEN
    Posts : 4
    Windows 7 x64 Home Premium (SP1)
    Thread Starter
       New #5

    Hey Boozad,

    I ran all of the tests available in SeaTools and the HDD passed them all. Disk check and scan also didn't turn up anything suspicious. I've attached another zip from the log collector to this message, thanks again for your time!
      My Computer
    Quote Quote

  8. Boozad
    Posts : 6,741
    W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
       New #6

    The last dump in the logs is dated the 20th which I believe I've already looked over. Can you post up new logs following any subsequent BSODs.
      My Computer
    Quote Quote

  10. R4VEN
    Posts : 4
    Windows 7 x64 Home Premium (SP1)
    Thread Starter
       New #7

    Hey gang, back again

    Still having issues here, just haven't been using the PC much due to my current schedule. To comment on Boozad's previous post, I wasn't able to produce another BSOD in a timely manner. Now however they seem to be more frequent. Some more symptoms I've discovered that may or may not be related:

    -Computer seems to BSOD when several things are going on. Game, 10+ tabs in Chrome, +1-2 other lighter programs
    -Computer powers back on after shutdown. Typically just once.
    -Computer will resume out of sleep mode without being provoked
    -Just recently, computer now errors out when launching some applications. My stored Chrome data like logins and whatnot has been forgotten

    I've run the DM Log Collector after my most recent BSOD and attached it here.

    Thanks again in advance guys, really appreciate any and all feedback here.
    -R4VEN
      My Computer
    Quote Quote

 

  Related Discussions
BSOD every couple of days or so
in BSOD Help and Support

Howdy! First post here. Have had this problem since acquiring this PC a couple years ago. Get BSOD occasionally, sometimes every couple of days up to a twice a day. Doesn't seem to be associated with any type of pattern. Just random BSOD crashes. Often crashes when logged in, but not in use. ...
As far as I can tell there is nothing in common with any of my BSOD's I have been getting one or two over the last few days. Thank you so much for any help, Rich
this is a brand new pc which i bought about a month ago: intel ivybridge i5-3550 corsair cmx8gx3m2a1333c9 4gb x 2 intel dh77eb board asus gtx560 550w PSU windows 7 prof 64 - original. every couple of days i would get a bluescreen. then when rebooting i would get a couple more. then i will...
BSOD Random last couple of days
in BSOD Help and Support

Another Page fault in non page area blue screen. I've had all hardware installed for many months with no issues. Granted the computer is 5 years old.. you never know. Can't really explain why this is going on the last couple of days. Using InDesign, have Outlook open along with Firefox. Don't...
A couple BSOD in the last few days.
in BSOD Help and Support

I believe two of them happened while playing Bad Company 2, and one happened while sitting at my desktop. I ran a Memtest for 2 passes (Became impatient :P) and it came up with no errors. Tried stressing out my video card, got up to 100c over 15 minutes with no errors. My computer is a about...
Our Sites
Site Links
About 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 18:57.
Find Us