Jump to content

BSOD after PC Upgrades. Help!

Taters_
By Taters_
in Troubleshooting
 Share
Posted

So, I just got some new upgrades for my PC, and I started getting BSOD, with the message "SYSTEM_THREAD_EXCEPTION_NOT_HANDLED" without any further info. I have only ran Windows Memory Check, no other memcheck programs, and I have already tried different GPU drivers and tutorials online. I am not sure if it is a bad RAM stick, or CPU Problem or what, I just know that the BSOD happens mostly in the middle of CS:GO competitive matches, which sucks, since it wont let me back in. I can post anymore info if needed, just let me know. Thanks!

-----------------------------------------------------------------------------------------------------------

My Specs BEFORE the upgrade

 

CPU- AMD FX-6300, 6 Cores, 3.5GHz

Cooler - Corsair H60

MotherBoard- ASUS M5A97 LE R2.0 AM3+ Socket

RAM - 8GB (2x4GB) G-Skill Sniper Series 1600Mhz DDR3

GPU- MSI GTX 760

Storage- 1 WD Blue HDDs WD10EZEX 1TB 7200RPM 64MB Cache

PSU- Corsair CX600 600W Power Supply Semi-Modular

OS- Windows 8.1 64-Bit

------------------------------------------------------------------------------------------------------------

My Specs AFTER the upgrade

 

CPU- AMD FX-8350, 8 Cores, 4.0GHz

Cooler - Corsair H60

MotherBoard- ASUS M5A97 LE R2.0 AM3+ Socket

RAM - 16GB (4x4GB) G-Skill Sniper Series 1600Mhz DDR3

GPU- MSI GTX 760

Storage- 2 WD Blue HDDs WD10EZEX 1TB 7200RPM 64MB Cache

PSU- Corsair CX600 600W Power Supply Semi-Modular

OS- Windows 8.1 64-Bit

-------------------------------------------------------------------------------------------------------------

DxDiag.txt

DxDiag.txt

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

does it show what causes the problem? It's normally listed in event viewer at the time of the crash with a critical icon.

Also try updating your chipset and Graphics drivers.

One Steam to rule them all, One Sale to find them, One Sale to bring them all and with their wallets, bind them! - r/pcmasterrace 17/01/2014

Spoiler
  • CPU: Intel Core i7 6700k
  • CPU Cooler: CM Hyper 212+ 
  • RAM: 16GB Kingston HyperX Fury 2400Mhz (2x8GB)
  • GPU: Gigabyte G1 R9 390 
  • Mobo: Asus Z170-AR
  • PSU: Antec High Current Gamer 900W 
  • Storage: 240GB intel 520 SSD (OS), Sandisk 128GB SSD(Other OS) 2x 2TB Seagate Barracuda 
  • Case: Fractal Design R4

 

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

To the OP, please follow the instructions here: http://linustechtips.com/main/topic/354634-bsod-posting-instructions-please-read/

Also @Taters_ please follow this thread to get notifications when people reply.

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

@SubTract

 

No it doesn't show the cause of the crash, and I cant seem to find it in Event viewer. I see the critical icons, but it just tells me that it was because "The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly." (Event ID 41) I cant seem to find the exact cause of the crash, maybe you could help me find it.

 

@ionbasa

 

Sorry, i'm new to LTT forums, but not the community. I have followed all of the instructions, and have the dump files, but when i try to run the PERFMON report, I get

Error:

 

An error occured while attempting to generate the report.

The operator or administrator has refused the request.

 

On the other hand, I will update some of the info that needs to be added according to the BSOD Posting Instuctions.

 

Windows 8 was originally installed on the system, and then upgraded to Windows 8.1. I have never re-installed the OS. The PC was custom built by myself.

The system is about 2 years old, with its first upgrade done only on July 8th 2015, the cause of my BSOD currently.

 

Thank you everyone for your help so far!

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

Run memtest86 a few times through. Looks to me like that is the most likely thing to be the problem. Also, to cover all bases, take out the new HDD and see if it still crashes.

 

Did you just buy more of the same memory? Or did you get a validated kit of 4, and set aside the old set. (It's not likely that they won't work together, but it is a possibility. Also one of the new sticks could be faulty.)

The first step to insanity is believing in your sanity.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

Step One: Uninstall Windows

Step Two: Realise you should have backed important stuff up and cry (this can be avoid)

Step Three: Make sure you have the right SATA mode set on yor HDD

Step Four: Reinstall Windows (or a unix based system or both)

Step Five: Drivers

Step Six: Decent Firewall (don't waste time with AV just remove them if you get them)

Before this run a live os from a pendrive or cd.

Current System: Tower: 32GB RAM, 2TB HDD, Quad Core i5(haswell), RX480, 128GB SSD

Future Systems: ? When I get a job I will think about it more

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

@hiyayhi

I had looked back on my Newegg purchase history, and bought the exact same kit of 8GB (4x2GB) more that i had 2 years ago. Exact same RAM. I am thinking the RAM stick may be faulty, and i will try memtest86 tomorrow

So, in conclusion I had a current 2x4GB kit, and bought another of the exact same RAM

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

@rrps700

I don't think i'm going to uninstall windows if i can try to find a simpler solution. If not, then maybe I might

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

@hiyayhi

I had looked back on my Newegg purchase history, and bought the exact same kit of 8GB (4x2GB) more that i had 2 years ago. Exact same RAM. I am thinking the RAM stick may be faulty, and i will try memtest86 tomorrow

So, in conclusion I had a current 2x4GB kit, and bought another of the exact same RAM

Ok, it should be fine. Another way to check if it the RAM, is to take out one of the new sticks, see if it crashes still, rinse and repeat with the other stick if it does. Then if it still crashing, take them both out, and see what happens. (You could also just take out the old ram altogether and run just the new ones by themselves.)

The first step to insanity is believing in your sanity.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

Step One: Uninstall Windows

Step Two: Realise you should have backed important stuff up and cry (this can be avoid)

Step Three: Make sure you have the right SATA mode set on yor HDD

Step Four: Reinstall Windows (or a unix based system or both)

Step Five: Drivers

Step Six: Decent Firewall (don't waste time with AV just remove them if you get them)

Before this run a live os from a pendrive or cd.

I'm not sure if you understand what is happening here. He upgraded HARDWARE and stuff started to fail. Why would you suspect a software problem? Uninstalling your OS is kind of a last resort thing after you have tested the hardware and have it back in the state of before the upgrade but things are still broken.

The first step to insanity is believing in your sanity.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

@hiyayhi

I agree, it's not a software problem.

I will definitely try taking out the 2 new sticks and see if i still crash, but the whole point of getting more was to go form 8GB to 16Gb, So sticking with 8GB again wouldn't be preffered. Maybe thats how it'll have to be if a stick is bad. I will definitely run memtest86 tomorrow.

 

Thank you very much!

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

@hiyayhi

I agree, it's not a software problem.

I will definitely try taking out the 2 new sticks and see if i still crash, but the whole point of getting more was to go form 8GB to 16Gb, So sticking with 8GB again wouldn't be preffered. Maybe thats how it'll have to be if a stick is bad. I will definitely run memtest86 tomorrow.

 

Thank you very much!

I was not saying you should stick with just running 8 gig, I was just saying that is another step you can take to test the sticks and see what is faulty. Whatever is found to be faulty should be RMA'd

The first step to insanity is believing in your sanity.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

I will try a memtest and stick removal tomorrow and update you guys on how things are going. I will definitly return whatever is faulty, if anything.otherwise, it may just work itself out, considering ive had no problems or BSODs today. Yet, I had quite a few BSOD's at the beggining of my PC's life and never did anything about them, and was clean from BSODs for 1 and a half years. Idk we'll see

 Thanks!

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

@ExplodingTaters could you please post the dump files for us to look at, you mention you have them. As for the Windows Performance Monitor not working, I suspect there is something wrong with your Windows installation. 

 

We can find out what those issues are, but we need the dump files. You can manually retrieve them if needed. 

 

Also, People in the thread are already mentioning re-installing windows, running memtest, etc. That only wastes your time, we don't know for certain what the BSODs are caused by until I or anyone else runs the dump files through the WIndows Debugger (WinDbg) which is apart of the Windows SDK.

 

Everyone else's suggestions is analogous to shooting fish in a barrel.

 

So here is what you should do:

  1. Post dump files by manually retrieving them
  2. Run an SFC Scannow: http://www.eightforums.com/tutorials/3047-sfc-scannow-command-run-windows-8-a.html#option2

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

Okay i am running an sfc /scannow, and here are the Dump files, this should be the correct link

https://www.dropbox.com/s/7hsrkbaj03gg330/Dump.zip?dl=0

So I ran the dump files through WinDbg.

 

 

Here are the culprits:

  • nvlddmkm.sys - An Nvidia driver component related to the GPU
  • dxgmms1.sys - A DirectX component related to graphics rendering
  • athwnx.sys - A qualcomm Atheros component related to networking or WiFi. (This actually caused 2 BSODs).
  • And a kernel panic caused by an IRQ issue (driver related) at the Windows logon screen

 

First, please update your GPU drivers from Nvidia's website. Next, check if you have any driver updates for your Atheros Qualcomm NIC, if none are available, re-install the latest available version.

 

As for the DirectX component and the kernel panic; did the SFC scan find any integrity violations? If so, were they fixed? You may need to run the command 2 or 3 times if it fails the first time. If it still finds integrity violations, please let me know. 

Windows 8 Kernel Version 9600 MP (6 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTS PersonalBuilt by: 9600.17041.amd64fre.winblue_gdr.140305-1710Machine Name:Kernel base = 0xfffff803`5fa09000 PsLoadedModuleList = 0xfffff803`5fcd32d0Debug session time: Wed May 28 17:47:26.347 2014 (UTC - 4:00)System Uptime: 5 days 1:28:00.058********************************************************************************                                                                             **                        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 itis pointing at freed memory.Arguments:Arg1: ffffe0002048c200, memory referenced.Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.Arg3: fffff8002bc52cb7, If non-zero, the instruction address which referenced the bad memory	address.Arg4: 0000000000000000, (reserved)Debugging Details:------------------Could not read faulting driver nameTRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2READ_ADDRESS: fffff8035fcc0ce0: Unable to get special pool infofffff8035fcc0ce0: Unable to get special pool infounable to get nt!MmNonPagedPoolStartunable to get nt!MmSizeOfNonPagedPoolInBytes ffffe0002048c200 FAULTING_IP: nvlddmkm+1fccb7fffff800`2bc52cb7 0fb703          movzx   eax,word ptr [rbx]MM_INTERNAL_CODE:  0CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTBUGCHECK_STR:  AVPROCESS_NAME:  SystemCURRENT_IRQL:  0TRAP_FRAME:  ffffd00064b2aca0 -- (.trap 0xffffd00064b2aca0)NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=0000000000010e00 rbx=0000000000000000 rcx=0000000000000007rdx=ffffe0002047b440 rsi=0000000000000000 rdi=0000000000000000rip=fffff8002bc52cb7 rsp=ffffd00064b2ae30 rbp=0000000000000000 r8=0000000000000001  r9=ffffe0002046c000 r10=0000000000000000r11=000000000000001c r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0         nv up ei pl zr na po ncnvlddmkm+0x1fccb7:fffff800`2bc52cb7 0fb703          movzx   eax,word ptr [rbx] ds:00000000`00000000=????Resetting default scopeLAST_CONTROL_TRANSFER:  from fffff8035fb8e0e7 to fffff8035fb5cfa0STACK_TEXT:  ffffd000`64b2aab8 fffff803`5fb8e0e7 : 00000000`00000050 ffffe000`2048c200 00000000`00000000 ffffd000`64b2aca0 : nt!KeBugCheckExffffd000`64b2aac0 fffff803`5fa709c9 : 00000000`00000000 ffffe000`21c3a040 ffffd000`64b2aca0 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x20c37ffffd000`64b2ab60 fffff803`5fb6722f : 00000000`00000000 ffffe000`2048c200 00000000`00000000 ffffd000`64b2aca0 : nt!MmAccessFault+0x7a9ffffd000`64b2aca0 fffff800`2bc52cb7 : ffffd000`64b2af68 00000000`00000004 ffffd000`64b2af70 00000000`00000004 : nt!KiPageFault+0x12fffffd000`64b2ae30 ffffd000`64b2af68 : 00000000`00000004 ffffd000`64b2af70 00000000`00000004 00000000`00454400 : nvlddmkm+0x1fccb7ffffd000`64b2ae38 00000000`00000004 : ffffd000`64b2af70 00000000`00000004 00000000`00454400 fffff800`2bc69014 : 0xffffd000`64b2af68ffffd000`64b2ae40 ffffd000`64b2af70 : 00000000`00000004 00000000`00454400 fffff800`2bc69014 ffffe000`1e42f000 : 0x4ffffd000`64b2ae48 00000000`00000004 : 00000000`00454400 fffff800`2bc69014 ffffe000`1e42f000 ffffe000`1d82e000 : 0xffffd000`64b2af70ffffd000`64b2ae50 00000000`00454400 : fffff800`2bc69014 ffffe000`1e42f000 ffffe000`1d82e000 ffffe000`1e6c8000 : 0x4ffffd000`64b2ae58 fffff800`2bc69014 : ffffe000`1e42f000 ffffe000`1d82e000 ffffe000`1e6c8000 00000000`00000001 : 0x454400ffffd000`64b2ae60 ffffe000`1e42f000 : ffffe000`1d82e000 ffffe000`1e6c8000 00000000`00000001 ffffd000`64b2af7c : nvlddmkm+0x213014ffffd000`64b2ae68 ffffe000`1d82e000 : ffffe000`1e6c8000 00000000`00000001 ffffd000`64b2af7c ffffd000`64b2af80 : 0xffffe000`1e42f000ffffd000`64b2ae70 ffffe000`1e6c8000 : 00000000`00000001 ffffd000`64b2af7c ffffd000`64b2af80 00000000`00000000 : 0xffffe000`1d82e000ffffd000`64b2ae78 00000000`00000001 : ffffd000`64b2af7c ffffd000`64b2af80 00000000`00000000 fffff800`2bc536ba : 0xffffe000`1e6c8000ffffd000`64b2ae80 ffffd000`64b2af7c : ffffd000`64b2af80 00000000`00000000 fffff800`2bc536ba ffffe000`1e42f000 : 0x1ffffd000`64b2ae88 ffffd000`64b2af80 : 00000000`00000000 fffff800`2bc536ba ffffe000`1e42f000 ffffe000`1d82e000 : 0xffffd000`64b2af7cffffd000`64b2ae90 00000000`00000000 : fffff800`2bc536ba ffffe000`1e42f000 ffffe000`1d82e000 ffffd000`64b2af90 : 0xffffd000`64b2af80STACK_COMMAND:  kbFOLLOWUP_IP: nvlddmkm+1fccb7fffff800`2bc52cb7 0fb703          movzx   eax,word ptr [rbx]SYMBOL_STACK_INDEX:  4SYMBOL_NAME:  nvlddmkm+1fccb7FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: nvlddmkmIMAGE_NAME:  nvlddmkm.sysDEBUG_FLR_IMAGE_TIMESTAMP:  537a8efcFAILURE_BUCKET_ID:  X64_AV_nvlddmkm+1fccb7BUCKET_ID:  X64_AV_nvlddmkm+1fccb7Followup: MachineOwner 
Windows 8 Kernel Version 9600 MP (8 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTS PersonalBuilt by: 9600.17736.amd64fre.winblue_r9.150322-1500Machine Name:Kernel base = 0xfffff800`62475000 PsLoadedModuleList = 0xfffff800`6274e850Debug session time: Wed Jul  8 17:43:39.555 2015 (UTC - 4:00)System Uptime: 0 days 0:25:35.260********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)This is a very common bugcheck.  Usually the exception address pinpointsthe driver/function that caused the problem.  Always note this addressas well as the link date of the driver/image that contains this address.Some common problems are exception code 0x80000003.  This means a hardcoded breakpoint or assertion was hit, but this system was booted/NODEBUG.  This is not supposed to happen as developers should never havehardcoded breakpoints in retail code, but ...If this happens, make sure a debugger gets connected, and thesystem is booted /DEBUG.  This will let us see why this breakpoint ishappening.Arguments:Arg1: ffffffffc0000005, The exception code that was not handledArg2: fffff8006255f7a0, The address that the exception occurred atArg3: ffffd0002041b518, Exception Record AddressArg4: ffffd0002041ad20, Context Record AddressDebugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".FAULTING_IP: nt!KxWaitForLockOwnerShipWithIrql+14fffff800`6255f7a0 48890a          mov     qword ptr [rdx],rcxEXCEPTION_RECORD:  ffffd0002041b518 -- (.exr 0xffffd0002041b518)ExceptionAddress: fffff8006255f7a0 (nt!KxWaitForLockOwnerShipWithIrql+0x0000000000000014)   ExceptionCode: c0000005 (Access violation)  ExceptionFlags: 00000000NumberParameters: 2   Parameter[0]: 0000000000000000   Parameter[1]: ffffffffffffffffAttempt to read from address ffffffffffffffffCONTEXT:  ffffd0002041ad20 -- (.cxr 0xffffd0002041ad20)rax=0000000000000080 rbx=0000000000000000 rcx=ffffd0002041b808rdx=5528800000000000 rsi=fffff800627d0420 rdi=ffffd0002041b808rip=fffff8006255f7a0 rsp=ffffd0002041b750 rbp=fffffa800c5d0c00 r8=0000000000000000  r9=0000000000000000 r10=0000000000e0b260r11=0000000000000001 r12=0000058000000000 r13=0000000000000000r14=000000000c5d0c00 r15=0000000000000000iopl=0         nv up ei pl zr na po nccs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246nt!KxWaitForLockOwnerShipWithIrql+0x14:fffff800`6255f7a0 48890a          mov     qword ptr [rdx],rcx ds:002b:55288000`00000000=????????????????Resetting default scopeCUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTPROCESS_NAME:  SystemCURRENT_IRQL:  2ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".EXCEPTION_PARAMETER1:  0000000000000000EXCEPTION_PARAMETER2:  ffffffffffffffffREAD_ADDRESS: fffff8006273c240: Unable to get special pool infofffff8006273c240: Unable to get special pool infounable to get nt!MmNonPagedPoolStartunable to get nt!MmSizeOfNonPagedPoolInBytes ffffffffffffffff FOLLOWUP_IP: dxgmms1!VidMmProcessAsyncOperation+1afffff800`c8e81042 8b05f86dfeff    mov     eax,dword ptr [dxgmms1!Microsoft_Windows_DxgKrnlEnableBits (fffff800`c8e67e40)]BUGCHECK_STR:  AVLAST_CONTROL_TRANSFER:  from fffff80062657724 to fffff8006255f7a0STACK_TEXT:  ffffd000`2041b750 fffff800`62657724 : ffffd000`dfd40180 fffff800`00000010 00000000`00000001 fffff800`00000402 : nt!KxWaitForLockOwnerShipWithIrql+0x14ffffd000`2041b780 fffff800`6260e0b0 : fffffa80`00e0b260 ffffd000`2041b838 fffffa80`0c5d0c00 fffff800`6260d189 : nt!KiAcquireQueuedSpinLockInstrumented+0x68ffffd000`2041b7d0 fffff800`624e54c1 : 00000000`0004b0a1 fffffa80`00e0b260 fffffa80`00000000 00000000`00000005 : nt! ?? ::FNODOBFM::`string'+0x37ef0ffffd000`2041b860 fffff800`624e526c : 00000000`00000000 ffffe000`88146230 00000000`00080000 00000000`00080000 : nt!MiDeleteLockedTransitionPte+0xb1ffffd000`2041b8c0 fffff800`6281e00b : ffffe000`88146230 00000000`00002000 ffffe000`00002001 00000000`00000000 : nt!MiDeleteSegmentPages+0x1c0ffffd000`2041b950 fffff800`624bbf69 : 00000000`00000002 ffffd000`2041b9c0 ffffe000`8612cb20 00000000`00000000 : nt!MiSegmentDelete+0x57ffffd000`2041b990 fffff800`628a2944 : 00000000`00000000 00000000`00000000 ffffe000`8612cb20 ffffc000`7beec660 : nt!MiCheckControlArea+0x1bdffffd000`2041b9f0 fffff800`624c801f : 00000000`00000000 ffffe000`86a26160 ffffc000`7beec690 fffff800`62727340 : nt!ObpRemoveObjectRoutine+0x64ffffd000`2041ba50 fffff800`c8e81042 : ffffe000`86a26160 ffffe000`8afe7340 00000000`00000000 fffff800`62727340 : nt!ObfDereferenceObject+0x8fffffd000`2041ba90 fffff800`625226bc : fffff800`cab62860 ffffe000`8afe7480 ffffe000`88850620 00000000`00000005 : dxgmms1!VidMmProcessAsyncOperation+0x1affffd000`2041bad0 fffff800`6257536c : ffffe000`8a52b880 ffffe000`8afe7340 00000000`00000080 ffffe000`8afe7340 : nt!ExpWorkerThread+0x28cffffd000`2041bb80 fffff800`625cc2c6 : ffffd000`dfcbb180 ffffe000`8afe7340 ffffe000`8a52b880 ffffe000`8601b180 : nt!PspSystemThreadStartup+0x58ffffd000`2041bbe0 00000000`00000000 : ffffd000`2041c000 ffffd000`20415000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16SYMBOL_STACK_INDEX:  9SYMBOL_NAME:  dxgmms1!VidMmProcessAsyncOperation+1aFOLLOWUP_NAME:  MachineOwnerMODULE_NAME: dxgmms1IMAGE_NAME:  dxgmms1.sysDEBUG_FLR_IMAGE_TIMESTAMP:  54505506STACK_COMMAND:  .cxr 0xffffd0002041ad20 ; kbFAILURE_BUCKET_ID:  X64_AV_dxgmms1!VidMmProcessAsyncOperation+1aBUCKET_ID:  X64_AV_dxgmms1!VidMmProcessAsyncOperation+1aFollowup: MachineOwner 
Windows 8 Kernel Version 9600 MP (6 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTS PersonalBuilt by: 9600.17238.amd64fre.winblue_gdr.140723-2018Machine Name:Kernel base = 0xfffff803`49086000 PsLoadedModuleList = 0xfffff803`49350350Debug session time: Sat Sep 27 18:09:56.745 2014 (UTC - 4:00)System Uptime: 0 days 9:04:24.449********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)An attempt was made to access a pageable (or completely invalid) address at aninterrupt request level (IRQL) that is too high.  This is usuallycaused by drivers using improper addresses.If kernel debugger is available get stack backtrace.Arguments:Arg1: ffffd00201ba0000, memory referencedArg2: 0000000000000002, IRQLArg3: 0000000000000000, value 0 = read operation, 1 = write operationArg4: fffff801ba3000b7, address which referenced memoryDebugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2READ_ADDRESS: fffff8034933dd60: Unable to get special pool infofffff8034933dd60: Unable to get special pool infounable to get nt!MmNonPagedPoolStartunable to get nt!MmSizeOfNonPagedPoolInBytes ffffd00201ba0000 CURRENT_IRQL:  2FAULTING_IP: athwnx+2290b7fffff801`ba3000b7 f3a4            rep movs byte ptr [rdi],byte ptr [rsi]CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTBUGCHECK_STR:  AVPROCESS_NAME:  javaw.exeTRAP_FRAME:  ffffd001fee23ef0 -- (.trap 0xffffd001fee23ef0)NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=000000000000c0a5 rbx=0000000000000000 rcx=00000000000016b3rdx=000000000000000d rsi=0000000000000000 rdi=0000000000000000rip=fffff801ba3000b7 rsp=ffffd001fee24080 rbp=ffffd001fee24b19 r8=000000000000c0bd  r9=ffffe0018a6e5400 r10=0000000000000000r11=fffff6fb780064d8 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0         nv up ei ng nz na po ncathwnx+0x2290b7:fffff801`ba3000b7 f3a4            rep movs byte ptr [rdi],byte ptr [rsi]Resetting default scopeLAST_CONTROL_TRANSFER:  from fffff803491e57e9 to fffff803491d9ca0STACK_TEXT:  ffffd001`fee23da8 fffff803`491e57e9 : 00000000`0000000a ffffd002`01ba0000 00000000`00000002 00000000`00000000 : nt!KeBugCheckExffffd001`fee23db0 fffff803`491e403a : 00000000`00000000 00000000`00001fff ffffe001`88dc8800 ffffd001`fee23ef0 : nt!KiBugCheckDispatch+0x69ffffd001`fee23ef0 fffff801`ba3000b7 : ffffe001`8a6e5458 ffffe001`0000000d ffffe001`0000c0bd ffffd001`fee243c8 : nt!KiPageFault+0x23affffd001`fee24080 ffffe001`8a6e5458 : ffffe001`0000000d ffffe001`0000c0bd ffffd001`fee243c8 00000000`00000018 : athwnx+0x2290b7ffffd001`fee24088 ffffe001`0000000d : ffffe001`0000c0bd ffffd001`fee243c8 00000000`00000018 00000000`00000000 : 0xffffe001`8a6e5458ffffd001`fee24090 ffffe001`0000c0bd : ffffd001`fee243c8 00000000`00000018 00000000`00000000 00000000`00000080 : 0xffffe001`0000000dffffd001`fee24098 ffffd001`fee243c8 : 00000000`00000018 00000000`00000000 00000000`00000080 00000000`00000000 : 0xffffe001`0000c0bdffffd001`fee240a0 00000000`00000018 : 00000000`00000000 00000000`00000080 00000000`00000000 0000ea21`ba308e00 : 0xffffd001`fee243c8ffffd001`fee240a8 00000000`00000000 : 00000000`00000080 00000000`00000000 0000ea21`ba308e00 0000c0b3`0000c0a5 : 0x18STACK_COMMAND:  kbFOLLOWUP_IP: athwnx+2290b7fffff801`ba3000b7 f3a4            rep movs byte ptr [rdi],byte ptr [rsi]SYMBOL_STACK_INDEX:  3SYMBOL_NAME:  athwnx+2290b7FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: athwnxIMAGE_NAME:  athwnx.sysDEBUG_FLR_IMAGE_TIMESTAMP:  51591bd5FAILURE_BUCKET_ID:  X64_AV_athwnx+2290b7BUCKET_ID:  X64_AV_athwnx+2290b7Followup: MachineOwner 
Windows 8 Kernel Version 9600 MP (6 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTS PersonalBuilt by: 9600.17238.amd64fre.winblue_gdr.140723-2018Machine Name:Kernel base = 0xfffff802`20a88000 PsLoadedModuleList = 0xfffff802`20d52350Debug session time: Mon Sep 29 18:29:17.265 2014 (UTC - 4:00)System Uptime: 2 days 0:17:56.967********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)An attempt was made to access a pageable (or completely invalid) address at aninterrupt request level (IRQL) that is too high.  This is usuallycaused by drivers using improper addresses.If kernel debugger is available get stack backtrace.Arguments:Arg1: ffffd00023120000, memory referencedArg2: 0000000000000002, IRQLArg3: 0000000000000000, value 0 = read operation, 1 = write operationArg4: fffff8019f63b0b7, address which referenced memoryDebugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2READ_ADDRESS: fffff80220d3fd60: Unable to get special pool infofffff80220d3fd60: Unable to get special pool infounable to get nt!MmNonPagedPoolStartunable to get nt!MmSizeOfNonPagedPoolInBytes ffffd00023120000 CURRENT_IRQL:  2FAULTING_IP: athwnx+2290b7fffff801`9f63b0b7 f3a4            rep movs byte ptr [rdi],byte ptr [rsi]CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTBUGCHECK_STR:  AVPROCESS_NAME:  SystemTRAP_FRAME:  ffffd00020da6e60 -- (.trap 0xffffd00020da6e60)NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=0000000000002f0e rbx=0000000000000000 rcx=00000000000002a0rdx=000000000000000a rsi=0000000000000000 rdi=0000000000000000rip=fffff8019f63b0b7 rsp=ffffd00020da6ff0 rbp=ffffd00020da7a89 r8=0000000000002f26  r9=ffffe00181fc7de0 r10=0000000000000000r11=fffff6fb78006078 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0         nv up ei ng nz na po ncathwnx+0x2290b7:fffff801`9f63b0b7 f3a4            rep movs byte ptr [rdi],byte ptr [rsi]Resetting default scopeLAST_CONTROL_TRANSFER:  from fffff80220be77e9 to fffff80220bdbca0STACK_TEXT:  ffffd000`20da6d18 fffff802`20be77e9 : 00000000`0000000a ffffd000`23120000 00000000`00000002 00000000`00000000 : nt!KeBugCheckExffffd000`20da6d20 fffff802`20be603a : 00000000`00000000 00000000`00001fff ffffe001`81fc7d00 ffffd000`20da6e60 : nt!KiBugCheckDispatch+0x69ffffd000`20da6e60 fffff801`9f63b0b7 : ffffe001`81fc7e38 ffffe001`0000000a ffffe001`00002f26 ffffd000`20da7338 : nt!KiPageFault+0x23affffd000`20da6ff0 ffffe001`81fc7e38 : ffffe001`0000000a ffffe001`00002f26 ffffd000`20da7338 ffffe001`00000018 : athwnx+0x2290b7ffffd000`20da6ff8 ffffe001`0000000a : ffffe001`00002f26 ffffd000`20da7338 ffffe001`00000018 00000000`00000000 : 0xffffe001`81fc7e38ffffd000`20da7000 ffffe001`00002f26 : ffffd000`20da7338 ffffe001`00000018 00000000`00000000 ffffe001`7f4fa680 : 0xffffe001`0000000affffd000`20da7008 ffffd000`20da7338 : ffffe001`00000018 00000000`00000000 ffffe001`7f4fa680 fffff801`9f669abe : 0xffffe001`00002f26ffffd000`20da7010 ffffe001`00000018 : 00000000`00000000 ffffe001`7f4fa680 fffff801`9f669abe 0000fc9f`80ae3e00 : 0xffffd000`20da7338ffffd000`20da7018 00000000`00000000 : ffffe001`7f4fa680 fffff801`9f669abe 0000fc9f`80ae3e00 00002f1c`00002f0e : 0xffffe001`00000018STACK_COMMAND:  kbFOLLOWUP_IP: athwnx+2290b7fffff801`9f63b0b7 f3a4            rep movs byte ptr [rdi],byte ptr [rsi]SYMBOL_STACK_INDEX:  3SYMBOL_NAME:  athwnx+2290b7FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: athwnxIMAGE_NAME:  athwnx.sysDEBUG_FLR_IMAGE_TIMESTAMP:  51591bd5FAILURE_BUCKET_ID:  X64_AV_athwnx+2290b7BUCKET_ID:  X64_AV_athwnx+2290b7Followup: MachineOwner 
Windows 8 Kernel Version 9600 MP (6 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTS PersonalBuilt by: 9600.17328.amd64fre.winblue_r3.140827-1500Machine Name:Kernel base = 0xfffff801`0868b000 PsLoadedModuleList = 0xfffff801`08961370Debug session time: Sat Dec  6 13:37:08.109 2014 (UTC - 4:00)System Uptime: 0 days 0:00:26.799********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************IRQL_GT_ZERO_AT_SYSTEM_SERVICE (4a)Returning to usermode from a system call at an IRQL > PASSIVE_LEVEL.Arguments:Arg1: 00007ffe11ab13aa, Address of system function (system call routine)Arg2: 0000000000000002, Current IRQLArg3: 0000000000000000, 0Arg4: ffffd000fb9dab00, 0Debugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2PROCESS_NAME:  LogonUI.exeBUGCHECK_STR:  RAISED_IRQL_FAULTFAULTING_IP: +000007ffe`11ab13aa ??              ???CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTCURRENT_IRQL:  2LAST_CONTROL_TRANSFER:  from fffff801087e5ce9 to fffff801087da1a0STACK_TEXT:  ffffd000`fb9da938 fffff801`087e5ce9 : 00000000`0000004a 00007ffe`11ab13aa 00000000`00000002 00000000`00000000 : nt!KeBugCheckExffffd000`fb9da940 fffff801`087e5c06 : ffffe000`dd2ab080 ffffe000`dd2ab080 0000001d`f1ccf340 0000001d`f0b9cc40 : nt!KiBugCheckDispatch+0x69ffffd000`fb9daa80 00007ffe`11ab13aa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x24b0000001d`f0a8e908 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7ffe`11ab13aaSTACK_COMMAND:  kbFOLLOWUP_IP: nt!KiSystemServiceExit+24bfffff801`087e5c06 4883ec50        sub     rsp,50hSYMBOL_STACK_INDEX:  2SYMBOL_NAME:  nt!KiSystemServiceExit+24bFOLLOWUP_NAME:  MachineOwnerMODULE_NAME: ntIMAGE_NAME:  ntkrnlmp.exeDEBUG_FLR_IMAGE_TIMESTAMP:  53fe6f2eFAILURE_BUCKET_ID:  X64_RAISED_IRQL_FAULT_LogonUI.exe_nt!KiSystemServiceExit+24bBUCKET_ID:  X64_RAISED_IRQL_FAULT_LogonUI.exe_nt!KiSystemServiceExit+24bFollowup: MachineOwner 

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

So I ran the dump files through WinDbg.

 

 

Here are the culprits:

  • nvlddmkm.sys - An Nvidia driver component related to the GPU
  • dxgmms1.sys - A DirectX component related to graphics rendering
  • athwnx.sys - A qualcomm Atheros component related to networking or WiFi. (This actually caused 2 BSODs).
  • And a kernel panic caused by an IRQ issue (driver related) at the Windows logon screen

 

First, please update your GPU drivers from Nvidia's website. Next, check if you have any driver updates for your Atheros Qualcomm NIC, if none are available, re-install the latest available version.

 

As for the DirectX component and the kernel panic; did the SFC scan find any integrity violations? If so, were they fixed? You may need to run the command 2 or 3 times if it fails the first time. If it still finds integrity violations, please let me know. 

The kernel panic and the Atheros issue are probably related. It's probably trying to take up an IRQ assigned to another device.

 

Atheros drivers are generally junk so it doesn't surprise me.

Windows 8 Kernel Version 9600 MP (6 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTS PersonalBuilt by: 9600.17041.amd64fre.winblue_gdr.140305-1710Machine Name:Kernel base = 0xfffff803`5fa09000 PsLoadedModuleList = 0xfffff803`5fcd32d0Debug session time: Wed May 28 17:47:26.347 2014 (UTC - 4:00)System Uptime: 5 days 1:28:00.058********************************************************************************                                                                             **                        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 itis pointing at freed memory.Arguments:Arg1: ffffe0002048c200, memory referenced.Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.Arg3: fffff8002bc52cb7, If non-zero, the instruction address which referenced the bad memory	address.Arg4: 0000000000000000, (reserved)Debugging Details:------------------Could not read faulting driver nameTRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2READ_ADDRESS: fffff8035fcc0ce0: Unable to get special pool infofffff8035fcc0ce0: Unable to get special pool infounable to get nt!MmNonPagedPoolStartunable to get nt!MmSizeOfNonPagedPoolInBytes ffffe0002048c200 FAULTING_IP: nvlddmkm+1fccb7fffff800`2bc52cb7 0fb703          movzx   eax,word ptr [rbx]MM_INTERNAL_CODE:  0CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTBUGCHECK_STR:  AVPROCESS_NAME:  SystemCURRENT_IRQL:  0TRAP_FRAME:  ffffd00064b2aca0 -- (.trap 0xffffd00064b2aca0)NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=0000000000010e00 rbx=0000000000000000 rcx=0000000000000007rdx=ffffe0002047b440 rsi=0000000000000000 rdi=0000000000000000rip=fffff8002bc52cb7 rsp=ffffd00064b2ae30 rbp=0000000000000000 r8=0000000000000001  r9=ffffe0002046c000 r10=0000000000000000r11=000000000000001c r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0         nv up ei pl zr na po ncnvlddmkm+0x1fccb7:fffff800`2bc52cb7 0fb703          movzx   eax,word ptr [rbx] ds:00000000`00000000=????Resetting default scopeLAST_CONTROL_TRANSFER:  from fffff8035fb8e0e7 to fffff8035fb5cfa0STACK_TEXT:  ffffd000`64b2aab8 fffff803`5fb8e0e7 : 00000000`00000050 ffffe000`2048c200 00000000`00000000 ffffd000`64b2aca0 : nt!KeBugCheckExffffd000`64b2aac0 fffff803`5fa709c9 : 00000000`00000000 ffffe000`21c3a040 ffffd000`64b2aca0 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x20c37ffffd000`64b2ab60 fffff803`5fb6722f : 00000000`00000000 ffffe000`2048c200 00000000`00000000 ffffd000`64b2aca0 : nt!MmAccessFault+0x7a9ffffd000`64b2aca0 fffff800`2bc52cb7 : ffffd000`64b2af68 00000000`00000004 ffffd000`64b2af70 00000000`00000004 : nt!KiPageFault+0x12fffffd000`64b2ae30 ffffd000`64b2af68 : 00000000`00000004 ffffd000`64b2af70 00000000`00000004 00000000`00454400 : nvlddmkm+0x1fccb7ffffd000`64b2ae38 00000000`00000004 : ffffd000`64b2af70 00000000`00000004 00000000`00454400 fffff800`2bc69014 : 0xffffd000`64b2af68ffffd000`64b2ae40 ffffd000`64b2af70 : 00000000`00000004 00000000`00454400 fffff800`2bc69014 ffffe000`1e42f000 : 0x4ffffd000`64b2ae48 00000000`00000004 : 00000000`00454400 fffff800`2bc69014 ffffe000`1e42f000 ffffe000`1d82e000 : 0xffffd000`64b2af70ffffd000`64b2ae50 00000000`00454400 : fffff800`2bc69014 ffffe000`1e42f000 ffffe000`1d82e000 ffffe000`1e6c8000 : 0x4ffffd000`64b2ae58 fffff800`2bc69014 : ffffe000`1e42f000 ffffe000`1d82e000 ffffe000`1e6c8000 00000000`00000001 : 0x454400ffffd000`64b2ae60 ffffe000`1e42f000 : ffffe000`1d82e000 ffffe000`1e6c8000 00000000`00000001 ffffd000`64b2af7c : nvlddmkm+0x213014ffffd000`64b2ae68 ffffe000`1d82e000 : ffffe000`1e6c8000 00000000`00000001 ffffd000`64b2af7c ffffd000`64b2af80 : 0xffffe000`1e42f000ffffd000`64b2ae70 ffffe000`1e6c8000 : 00000000`00000001 ffffd000`64b2af7c ffffd000`64b2af80 00000000`00000000 : 0xffffe000`1d82e000ffffd000`64b2ae78 00000000`00000001 : ffffd000`64b2af7c ffffd000`64b2af80 00000000`00000000 fffff800`2bc536ba : 0xffffe000`1e6c8000ffffd000`64b2ae80 ffffd000`64b2af7c : ffffd000`64b2af80 00000000`00000000 fffff800`2bc536ba ffffe000`1e42f000 : 0x1ffffd000`64b2ae88 ffffd000`64b2af80 : 00000000`00000000 fffff800`2bc536ba ffffe000`1e42f000 ffffe000`1d82e000 : 0xffffd000`64b2af7cffffd000`64b2ae90 00000000`00000000 : fffff800`2bc536ba ffffe000`1e42f000 ffffe000`1d82e000 ffffd000`64b2af90 : 0xffffd000`64b2af80STACK_COMMAND:  kbFOLLOWUP_IP: nvlddmkm+1fccb7fffff800`2bc52cb7 0fb703          movzx   eax,word ptr [rbx]SYMBOL_STACK_INDEX:  4SYMBOL_NAME:  nvlddmkm+1fccb7FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: nvlddmkmIMAGE_NAME:  nvlddmkm.sysDEBUG_FLR_IMAGE_TIMESTAMP:  537a8efcFAILURE_BUCKET_ID:  X64_AV_nvlddmkm+1fccb7BUCKET_ID:  X64_AV_nvlddmkm+1fccb7Followup: MachineOwner 
Windows 8 Kernel Version 9600 MP (8 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTS PersonalBuilt by: 9600.17736.amd64fre.winblue_r9.150322-1500Machine Name:Kernel base = 0xfffff800`62475000 PsLoadedModuleList = 0xfffff800`6274e850Debug session time: Wed Jul  8 17:43:39.555 2015 (UTC - 4:00)System Uptime: 0 days 0:25:35.260********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)This is a very common bugcheck.  Usually the exception address pinpointsthe driver/function that caused the problem.  Always note this addressas well as the link date of the driver/image that contains this address.Some common problems are exception code 0x80000003.  This means a hardcoded breakpoint or assertion was hit, but this system was booted/NODEBUG.  This is not supposed to happen as developers should never havehardcoded breakpoints in retail code, but ...If this happens, make sure a debugger gets connected, and thesystem is booted /DEBUG.  This will let us see why this breakpoint ishappening.Arguments:Arg1: ffffffffc0000005, The exception code that was not handledArg2: fffff8006255f7a0, The address that the exception occurred atArg3: ffffd0002041b518, Exception Record AddressArg4: ffffd0002041ad20, Context Record AddressDebugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".FAULTING_IP: nt!KxWaitForLockOwnerShipWithIrql+14fffff800`6255f7a0 48890a          mov     qword ptr [rdx],rcxEXCEPTION_RECORD:  ffffd0002041b518 -- (.exr 0xffffd0002041b518)ExceptionAddress: fffff8006255f7a0 (nt!KxWaitForLockOwnerShipWithIrql+0x0000000000000014)   ExceptionCode: c0000005 (Access violation)  ExceptionFlags: 00000000NumberParameters: 2   Parameter[0]: 0000000000000000   Parameter[1]: ffffffffffffffffAttempt to read from address ffffffffffffffffCONTEXT:  ffffd0002041ad20 -- (.cxr 0xffffd0002041ad20)rax=0000000000000080 rbx=0000000000000000 rcx=ffffd0002041b808rdx=5528800000000000 rsi=fffff800627d0420 rdi=ffffd0002041b808rip=fffff8006255f7a0 rsp=ffffd0002041b750 rbp=fffffa800c5d0c00 r8=0000000000000000  r9=0000000000000000 r10=0000000000e0b260r11=0000000000000001 r12=0000058000000000 r13=0000000000000000r14=000000000c5d0c00 r15=0000000000000000iopl=0         nv up ei pl zr na po nccs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246nt!KxWaitForLockOwnerShipWithIrql+0x14:fffff800`6255f7a0 48890a          mov     qword ptr [rdx],rcx ds:002b:55288000`00000000=????????????????Resetting default scopeCUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTPROCESS_NAME:  SystemCURRENT_IRQL:  2ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".EXCEPTION_PARAMETER1:  0000000000000000EXCEPTION_PARAMETER2:  ffffffffffffffffREAD_ADDRESS: fffff8006273c240: Unable to get special pool infofffff8006273c240: Unable to get special pool infounable to get nt!MmNonPagedPoolStartunable to get nt!MmSizeOfNonPagedPoolInBytes ffffffffffffffff FOLLOWUP_IP: dxgmms1!VidMmProcessAsyncOperation+1afffff800`c8e81042 8b05f86dfeff    mov     eax,dword ptr [dxgmms1!Microsoft_Windows_DxgKrnlEnableBits (fffff800`c8e67e40)]BUGCHECK_STR:  AVLAST_CONTROL_TRANSFER:  from fffff80062657724 to fffff8006255f7a0STACK_TEXT:  ffffd000`2041b750 fffff800`62657724 : ffffd000`dfd40180 fffff800`00000010 00000000`00000001 fffff800`00000402 : nt!KxWaitForLockOwnerShipWithIrql+0x14ffffd000`2041b780 fffff800`6260e0b0 : fffffa80`00e0b260 ffffd000`2041b838 fffffa80`0c5d0c00 fffff800`6260d189 : nt!KiAcquireQueuedSpinLockInstrumented+0x68ffffd000`2041b7d0 fffff800`624e54c1 : 00000000`0004b0a1 fffffa80`00e0b260 fffffa80`00000000 00000000`00000005 : nt! ?? ::FNODOBFM::`string'+0x37ef0ffffd000`2041b860 fffff800`624e526c : 00000000`00000000 ffffe000`88146230 00000000`00080000 00000000`00080000 : nt!MiDeleteLockedTransitionPte+0xb1ffffd000`2041b8c0 fffff800`6281e00b : ffffe000`88146230 00000000`00002000 ffffe000`00002001 00000000`00000000 : nt!MiDeleteSegmentPages+0x1c0ffffd000`2041b950 fffff800`624bbf69 : 00000000`00000002 ffffd000`2041b9c0 ffffe000`8612cb20 00000000`00000000 : nt!MiSegmentDelete+0x57ffffd000`2041b990 fffff800`628a2944 : 00000000`00000000 00000000`00000000 ffffe000`8612cb20 ffffc000`7beec660 : nt!MiCheckControlArea+0x1bdffffd000`2041b9f0 fffff800`624c801f : 00000000`00000000 ffffe000`86a26160 ffffc000`7beec690 fffff800`62727340 : nt!ObpRemoveObjectRoutine+0x64ffffd000`2041ba50 fffff800`c8e81042 : ffffe000`86a26160 ffffe000`8afe7340 00000000`00000000 fffff800`62727340 : nt!ObfDereferenceObject+0x8fffffd000`2041ba90 fffff800`625226bc : fffff800`cab62860 ffffe000`8afe7480 ffffe000`88850620 00000000`00000005 : dxgmms1!VidMmProcessAsyncOperation+0x1affffd000`2041bad0 fffff800`6257536c : ffffe000`8a52b880 ffffe000`8afe7340 00000000`00000080 ffffe000`8afe7340 : nt!ExpWorkerThread+0x28cffffd000`2041bb80 fffff800`625cc2c6 : ffffd000`dfcbb180 ffffe000`8afe7340 ffffe000`8a52b880 ffffe000`8601b180 : nt!PspSystemThreadStartup+0x58ffffd000`2041bbe0 00000000`00000000 : ffffd000`2041c000 ffffd000`20415000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16SYMBOL_STACK_INDEX:  9SYMBOL_NAME:  dxgmms1!VidMmProcessAsyncOperation+1aFOLLOWUP_NAME:  MachineOwnerMODULE_NAME: dxgmms1IMAGE_NAME:  dxgmms1.sysDEBUG_FLR_IMAGE_TIMESTAMP:  54505506STACK_COMMAND:  .cxr 0xffffd0002041ad20 ; kbFAILURE_BUCKET_ID:  X64_AV_dxgmms1!VidMmProcessAsyncOperation+1aBUCKET_ID:  X64_AV_dxgmms1!VidMmProcessAsyncOperation+1aFollowup: MachineOwner 
Windows 8 Kernel Version 9600 MP (6 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTS PersonalBuilt by: 9600.17238.amd64fre.winblue_gdr.140723-2018Machine Name:Kernel base = 0xfffff803`49086000 PsLoadedModuleList = 0xfffff803`49350350Debug session time: Sat Sep 27 18:09:56.745 2014 (UTC - 4:00)System Uptime: 0 days 9:04:24.449********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)An attempt was made to access a pageable (or completely invalid) address at aninterrupt request level (IRQL) that is too high.  This is usuallycaused by drivers using improper addresses.If kernel debugger is available get stack backtrace.Arguments:Arg1: ffffd00201ba0000, memory referencedArg2: 0000000000000002, IRQLArg3: 0000000000000000, value 0 = read operation, 1 = write operationArg4: fffff801ba3000b7, address which referenced memoryDebugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2READ_ADDRESS: fffff8034933dd60: Unable to get special pool infofffff8034933dd60: Unable to get special pool infounable to get nt!MmNonPagedPoolStartunable to get nt!MmSizeOfNonPagedPoolInBytes ffffd00201ba0000 CURRENT_IRQL:  2FAULTING_IP: athwnx+2290b7fffff801`ba3000b7 f3a4            rep movs byte ptr [rdi],byte ptr [rsi]CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTBUGCHECK_STR:  AVPROCESS_NAME:  javaw.exeTRAP_FRAME:  ffffd001fee23ef0 -- (.trap 0xffffd001fee23ef0)NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=000000000000c0a5 rbx=0000000000000000 rcx=00000000000016b3rdx=000000000000000d rsi=0000000000000000 rdi=0000000000000000rip=fffff801ba3000b7 rsp=ffffd001fee24080 rbp=ffffd001fee24b19 r8=000000000000c0bd  r9=ffffe0018a6e5400 r10=0000000000000000r11=fffff6fb780064d8 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0         nv up ei ng nz na po ncathwnx+0x2290b7:fffff801`ba3000b7 f3a4            rep movs byte ptr [rdi],byte ptr [rsi]Resetting default scopeLAST_CONTROL_TRANSFER:  from fffff803491e57e9 to fffff803491d9ca0STACK_TEXT:  ffffd001`fee23da8 fffff803`491e57e9 : 00000000`0000000a ffffd002`01ba0000 00000000`00000002 00000000`00000000 : nt!KeBugCheckExffffd001`fee23db0 fffff803`491e403a : 00000000`00000000 00000000`00001fff ffffe001`88dc8800 ffffd001`fee23ef0 : nt!KiBugCheckDispatch+0x69ffffd001`fee23ef0 fffff801`ba3000b7 : ffffe001`8a6e5458 ffffe001`0000000d ffffe001`0000c0bd ffffd001`fee243c8 : nt!KiPageFault+0x23affffd001`fee24080 ffffe001`8a6e5458 : ffffe001`0000000d ffffe001`0000c0bd ffffd001`fee243c8 00000000`00000018 : athwnx+0x2290b7ffffd001`fee24088 ffffe001`0000000d : ffffe001`0000c0bd ffffd001`fee243c8 00000000`00000018 00000000`00000000 : 0xffffe001`8a6e5458ffffd001`fee24090 ffffe001`0000c0bd : ffffd001`fee243c8 00000000`00000018 00000000`00000000 00000000`00000080 : 0xffffe001`0000000dffffd001`fee24098 ffffd001`fee243c8 : 00000000`00000018 00000000`00000000 00000000`00000080 00000000`00000000 : 0xffffe001`0000c0bdffffd001`fee240a0 00000000`00000018 : 00000000`00000000 00000000`00000080 00000000`00000000 0000ea21`ba308e00 : 0xffffd001`fee243c8ffffd001`fee240a8 00000000`00000000 : 00000000`00000080 00000000`00000000 0000ea21`ba308e00 0000c0b3`0000c0a5 : 0x18STACK_COMMAND:  kbFOLLOWUP_IP: athwnx+2290b7fffff801`ba3000b7 f3a4            rep movs byte ptr [rdi],byte ptr [rsi]SYMBOL_STACK_INDEX:  3SYMBOL_NAME:  athwnx+2290b7FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: athwnxIMAGE_NAME:  athwnx.sysDEBUG_FLR_IMAGE_TIMESTAMP:  51591bd5FAILURE_BUCKET_ID:  X64_AV_athwnx+2290b7BUCKET_ID:  X64_AV_athwnx+2290b7Followup: MachineOwner 
Windows 8 Kernel Version 9600 MP (6 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTS PersonalBuilt by: 9600.17238.amd64fre.winblue_gdr.140723-2018Machine Name:Kernel base = 0xfffff802`20a88000 PsLoadedModuleList = 0xfffff802`20d52350Debug session time: Mon Sep 29 18:29:17.265 2014 (UTC - 4:00)System Uptime: 2 days 0:17:56.967********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)An attempt was made to access a pageable (or completely invalid) address at aninterrupt request level (IRQL) that is too high.  This is usuallycaused by drivers using improper addresses.If kernel debugger is available get stack backtrace.Arguments:Arg1: ffffd00023120000, memory referencedArg2: 0000000000000002, IRQLArg3: 0000000000000000, value 0 = read operation, 1 = write operationArg4: fffff8019f63b0b7, address which referenced memoryDebugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2READ_ADDRESS: fffff80220d3fd60: Unable to get special pool infofffff80220d3fd60: Unable to get special pool infounable to get nt!MmNonPagedPoolStartunable to get nt!MmSizeOfNonPagedPoolInBytes ffffd00023120000 CURRENT_IRQL:  2FAULTING_IP: athwnx+2290b7fffff801`9f63b0b7 f3a4            rep movs byte ptr [rdi],byte ptr [rsi]CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTBUGCHECK_STR:  AVPROCESS_NAME:  SystemTRAP_FRAME:  ffffd00020da6e60 -- (.trap 0xffffd00020da6e60)NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=0000000000002f0e rbx=0000000000000000 rcx=00000000000002a0rdx=000000000000000a rsi=0000000000000000 rdi=0000000000000000rip=fffff8019f63b0b7 rsp=ffffd00020da6ff0 rbp=ffffd00020da7a89 r8=0000000000002f26  r9=ffffe00181fc7de0 r10=0000000000000000r11=fffff6fb78006078 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0         nv up ei ng nz na po ncathwnx+0x2290b7:fffff801`9f63b0b7 f3a4            rep movs byte ptr [rdi],byte ptr [rsi]Resetting default scopeLAST_CONTROL_TRANSFER:  from fffff80220be77e9 to fffff80220bdbca0STACK_TEXT:  ffffd000`20da6d18 fffff802`20be77e9 : 00000000`0000000a ffffd000`23120000 00000000`00000002 00000000`00000000 : nt!KeBugCheckExffffd000`20da6d20 fffff802`20be603a : 00000000`00000000 00000000`00001fff ffffe001`81fc7d00 ffffd000`20da6e60 : nt!KiBugCheckDispatch+0x69ffffd000`20da6e60 fffff801`9f63b0b7 : ffffe001`81fc7e38 ffffe001`0000000a ffffe001`00002f26 ffffd000`20da7338 : nt!KiPageFault+0x23affffd000`20da6ff0 ffffe001`81fc7e38 : ffffe001`0000000a ffffe001`00002f26 ffffd000`20da7338 ffffe001`00000018 : athwnx+0x2290b7ffffd000`20da6ff8 ffffe001`0000000a : ffffe001`00002f26 ffffd000`20da7338 ffffe001`00000018 00000000`00000000 : 0xffffe001`81fc7e38ffffd000`20da7000 ffffe001`00002f26 : ffffd000`20da7338 ffffe001`00000018 00000000`00000000 ffffe001`7f4fa680 : 0xffffe001`0000000affffd000`20da7008 ffffd000`20da7338 : ffffe001`00000018 00000000`00000000 ffffe001`7f4fa680 fffff801`9f669abe : 0xffffe001`00002f26ffffd000`20da7010 ffffe001`00000018 : 00000000`00000000 ffffe001`7f4fa680 fffff801`9f669abe 0000fc9f`80ae3e00 : 0xffffd000`20da7338ffffd000`20da7018 00000000`00000000 : ffffe001`7f4fa680 fffff801`9f669abe 0000fc9f`80ae3e00 00002f1c`00002f0e : 0xffffe001`00000018STACK_COMMAND:  kbFOLLOWUP_IP: athwnx+2290b7fffff801`9f63b0b7 f3a4            rep movs byte ptr [rdi],byte ptr [rsi]SYMBOL_STACK_INDEX:  3SYMBOL_NAME:  athwnx+2290b7FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: athwnxIMAGE_NAME:  athwnx.sysDEBUG_FLR_IMAGE_TIMESTAMP:  51591bd5FAILURE_BUCKET_ID:  X64_AV_athwnx+2290b7BUCKET_ID:  X64_AV_athwnx+2290b7Followup: MachineOwner 
Windows 8 Kernel Version 9600 MP (6 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTS PersonalBuilt by: 9600.17328.amd64fre.winblue_r3.140827-1500Machine Name:Kernel base = 0xfffff801`0868b000 PsLoadedModuleList = 0xfffff801`08961370Debug session time: Sat Dec  6 13:37:08.109 2014 (UTC - 4:00)System Uptime: 0 days 0:00:26.799********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************IRQL_GT_ZERO_AT_SYSTEM_SERVICE (4a)Returning to usermode from a system call at an IRQL > PASSIVE_LEVEL.Arguments:Arg1: 00007ffe11ab13aa, Address of system function (system call routine)Arg2: 0000000000000002, Current IRQLArg3: 0000000000000000, 0Arg4: ffffd000fb9dab00, 0Debugging Details:------------------TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2PROCESS_NAME:  LogonUI.exeBUGCHECK_STR:  RAISED_IRQL_FAULTFAULTING_IP: +000007ffe`11ab13aa ??              ???CUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULTCURRENT_IRQL:  2LAST_CONTROL_TRANSFER:  from fffff801087e5ce9 to fffff801087da1a0STACK_TEXT:  ffffd000`fb9da938 fffff801`087e5ce9 : 00000000`0000004a 00007ffe`11ab13aa 00000000`00000002 00000000`00000000 : nt!KeBugCheckExffffd000`fb9da940 fffff801`087e5c06 : ffffe000`dd2ab080 ffffe000`dd2ab080 0000001d`f1ccf340 0000001d`f0b9cc40 : nt!KiBugCheckDispatch+0x69ffffd000`fb9daa80 00007ffe`11ab13aa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x24b0000001d`f0a8e908 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7ffe`11ab13aaSTACK_COMMAND:  kbFOLLOWUP_IP: nt!KiSystemServiceExit+24bfffff801`087e5c06 4883ec50        sub     rsp,50hSYMBOL_STACK_INDEX:  2SYMBOL_NAME:  nt!KiSystemServiceExit+24bFOLLOWUP_NAME:  MachineOwnerMODULE_NAME: ntIMAGE_NAME:  ntkrnlmp.exeDEBUG_FLR_IMAGE_TIMESTAMP:  53fe6f2eFAILURE_BUCKET_ID:  X64_RAISED_IRQL_FAULT_LogonUI.exe_nt!KiSystemServiceExit+24bBUCKET_ID:  X64_RAISED_IRQL_FAULT_LogonUI.exe_nt!KiSystemServiceExit+24bFollowup: MachineOwner 

The New Machine: Intel 11700K / Strix Z590-A WIFI II / Patriot Viper Steel 4400MHz 2x8GB / Gigabyte RTX 3080 Gaming OC w/ Bykski WB / x4 1TB SSDs (x2 M.2, x2 2.5) / Corsair 5000D Airflow White / EVGA G6 1000W / Custom Loop CPU & GPU

 

The Rainbow X58: i7 975 Extreme Edition @4.2GHz, Asus Sabertooth X58, 6x2GB Mushkin Redline DDR3-1600 @2000MHz, SP 256GB Gen3 M.2 w/ Sabrent M.2 to PCI-E, Inno3D GTX 580 x2 SLI w/ Heatkiller waterblocks, Custom loop in NZXT Phantom White, Corsair XR7 360 rad hanging off the rear end, 360 slim rad up top. RGB everywhere.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

 

-snip-

 

Shooting at fish in a barrel hey?

 

I said graphics drivers

as well as chip set.... >.>

 

Not saying your wrong but it's amazing what you can fairly safely assume without a dump file.

 

I'd say more like reaching for your lightswitch in your dark bedroom than shooting at fish in a barrel.

Also re-installing might be extreme but it likely would have solved the issue.

 

still don't necessarily disagree with you though.

 

 

I'm not sure if you understand what is happening here. He upgraded HARDWARE and stuff started to fail. Why would you suspect a software problem? Uninstalling your OS is kind of a last resort thing after you have tested the hardware and have it back in the state of before the upgrade but things are still broken.

 

You would assume it was a software problem because he changed the hardware but didn't change the software. Putting new hardware with an existing OS drive often causes software problems.

 

@Taters_ I would suggest for drivers uninstall your current drivers and go back a few revisions in the geforce drivers. There seem to be a few issues with the latest drivers.

 

As for your wifi drivers go and download the drivers for the device name written on the box rather than the device windows assumes it is. Windows is fairly terrible at correctly identifying wireless cards. It often loads the wrong driver.

 

 

If it comes to it windows 10 comes out 19 days so you can do the upgrade then and It will hopefully solve any remaining problems.

One Steam to rule them all, One Sale to find them, One Sale to bring them all and with their wallets, bind them! - r/pcmasterrace 17/01/2014

Spoiler
  • CPU: Intel Core i7 6700k
  • CPU Cooler: CM Hyper 212+ 
  • RAM: 16GB Kingston HyperX Fury 2400Mhz (2x8GB)
  • GPU: Gigabyte G1 R9 390 
  • Mobo: Asus Z170-AR
  • PSU: Antec High Current Gamer 900W 
  • Storage: 240GB intel 520 SSD (OS), Sandisk 128GB SSD(Other OS) 2x 2TB Seagate Barracuda 
  • Case: Fractal Design R4

 

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

-snip-

 

You would assume it was a software problem because he changed the hardware but didn't change the software. Putting new hardware with an existing OS drive often causes software problems.

 

-snip-

Why would you assume it to be a software problem without first testing the new hardware for faults? That seems like it is complicating things an extra step for what could be no reason.

 

Edit- Maybe you just have a different way of looking at it, I check hardware first because that is what has given me trouble in my experience, you check software first.

The first step to insanity is believing in your sanity.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

If windows is booting then the bsod appears after then configuration issue with windows than the hardware if bsoding on boot then you need to follow my earlier advice to a tee. If the RAM shows on the post screen it is likely a windows issue with detecting the new ram. To be clear I do understand HARDWARE I am a computer science student on track to get a 1-2

Current System: Tower: 32GB RAM, 2TB HDD, Quad Core i5(haswell), RX480, 128GB SSD

Future Systems: ? When I get a job I will think about it more

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

 @SubTract @ionbasa I will rollback Nvidia drivers a few versions, as after i updated to the latest version i once again saw a BSOD. However, I have/had not gotten any BSODs yesterday, and today. I will also run the SFC scan a few more times. but as for the message i had gotten on the first scan, it seemed it didn't repair all of the files it found corrupted. 

 

Here is what the administrator command prompt told me throughout the first scan-

 

C:\Windows\system32>sfc /scannow

 

Beginning System scan. This process will take some time

 

Beginning verification phase of system scan.

Verification 100% complete

 

Windows Resource protection found corrupt files but was unable to fix some

of them. Details are included in the CBS.log windir\logs\CBS\CBS.log. For

example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not

supported in offline servicing scenarios.

 

C:\Windows\system32>_

 

But then i checked out CBS.log, and at the end of the log it said that all files found corrupt in this logged scan were fixed. Does that mean it did fix them?

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

 

Shooting at fish in a barrel hey?

 

I said graphics drivers

as well as chip set.... >.>

 

Not saying your wrong but it's amazing what you can fairly safely assume without a dump file.

 

I'd say more like reaching for your lightswitch in your dark bedroom than shooting at fish in a barrel.

Also re-installing might be extreme but it likely would have solved the issue.

 

still don't necessarily disagree with you though.

 

 

 

You would assume it was a software problem because he changed the hardware but didn't change the software. Putting new hardware with an existing OS drive often causes software problems.

 

@Taters_ I would suggest for drivers uninstall your current drivers and go back a few revisions in the geforce drivers. There seem to be a few issues with the latest drivers.

 

As for your wifi drivers go and download the drivers for the device name written on the box rather than the device windows assumes it is. Windows is fairly terrible at correctly identifying wireless cards. It often loads the wrong driver.

 

 

If it comes to it windows 10 comes out 19 days so you can do the upgrade then and It will hopefully solve any remaining problems.

You can't fairly assume anything without a dump file. You just guessed right for the GPU driver, and the buck stops there. 

 

As to Windows not reporting the proper WiFi device: It actually does report the proper device. It reports the chipset name, not necessarily the brand name, and well, there are only a handful of wireless chipset manufacturers on the market (Atheros, Broadcom, Intel, and Realtek). Here is a fun fact: The chipset information is actually part of the firmware as a Hardware ID. Windows merely reads the Device ID and represents the device under Device Manager based on the type of device it is (USB, GPU, network, etc). The name given to a device actually comes from the driver that is installed, and isn't assigned by Windows.

 

Even then, he shouldn't be updating the drivers from the brand name he bought. He should be updating his driver based on the wireless chipset in his device. Which is more of a pain in the backside since Atheros doesn't publish 1st part drivers, but you can find a good chunk of them here: https://www.atheros.cz/

 

Why would you assume it to be a software problem without first testing the new hardware for faults? That seems like it is complicating things an extra step for what could be no reason.

 

Edit- Maybe you just have a different way of looking at it, I check hardware first because that is what has given me trouble in my experience, you check software first.

Software and hardware go hand in hand.

 

If windows is booting then the bsod appears after then configuration issue with windows than the hardware if bsoding on boot then you need to follow my earlier advice to a tee. If the RAM shows on the post screen it is likely a windows issue with detecting the new ram. To be clear I do understand HARDWARE I am a computer science student on track to get a 1-2

I think we debunked your RAM hypothesis already from the dump file output, just saying, maybe take a moment to actually look at the WinDbg output I put up for reference. 

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

 @SubTract @ionbasa I will rollback Nvidia drivers a few versions, as after i updated to the latest version i once again saw a BSOD. However, I have/had not gotten any BSODs yesterday, and today. I will also run the SFC scan a few more times. but as for the message i had gotten on the first scan, it seemed it didn't repair all of the files it found corrupted. 

 

Here is what the administrator command prompt told me throughout the first scan-

 

C:\Windows\system32>sfc /scannow

 

Beginning System scan. This process will take some time

 

Beginning verification phase of system scan.

Verification 100% complete

 

Windows Resource protection found corrupt files but was unable to fix some

of them. Details are included in the CBS.log windir\logs\CBS\CBS.log. For

example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not

supported in offline servicing scenarios.

 

C:\Windows\system32>_

 

But then i checked out CBS.log, and at the end of the log it said that all files found corrupt in this logged scan were fixed. Does that mean it did fix them?

Can you run it one more time? Have you followed my previous advice and updated your drivers?

▶ Learn from yesterday, live for today, hope for tomorrow. The important thing is not to stop questioning. - Einstein◀

Please remember to mark a thread as solved if your issue has been fixed, it helps other who may stumble across the thread at a later point in time.

Link to comment
Share on other sites
Link to post
Share on other sites
Posted

Currently running another SFC scan, and will rollback Nvidia drivers in a sec. Also how would i find/update my Atheros Qualcomm NIC Driver(s)?

Link to comment
Share on other sites
Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing Troubleshooting

×