M mseilerrr New member Joined May 23, 2014 Posts 3 May 26, 2014 #1 Hey I'm back! Sorry! It was okay for a while, but now I'm having the same problem for a different reason. My computer also makes this weird buzzing sound. I haven't changed anything or installed anything new. Windows 8.1 x64, came pre-installed Hardware is 6 months old No OS resinstall Laptop model # 20246 View attachment 8106
Hey I'm back! Sorry! It was okay for a while, but now I'm having the same problem for a different reason. My computer also makes this weird buzzing sound. I haven't changed anything or installed anything new. Windows 8.1 x64, came pre-installed Hardware is 6 months old No OS resinstall Laptop model # 20246 View attachment 8106
P Patrick Sysnative Staff Joined Jun 7, 2012 Posts 4,618 May 26, 2014 #2 Hi, We have two consistent bug checks: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) This indicates that a system thread generated an exception which the error handler did not catch. Code: BugCheck 1000007E, {ffffffffc0000005, 0, ffffd00022cd4818, ffffd00022cd4020} The 1st parameter of the bug check is 0xc0000005 which indicates an access violation occurred. Code: 0: kd> k Child-SP RetAddr Call Site ffffd000`22cd4a58 fffff800`49d3f25e 0x0 ffffd000`22cd4a60 fffff802`802ee220 rtwlanu+0xde25e ffffd000`22cd4a68 00000000`00000001 nt!PiUEventUsermodeEventQueueLock ffffd000`22cd4a70 ffffe000`5555bb80 0x1 ffffd000`22cd4a78 fffff802`802ae59e 0xffffe000`5555bb80 ffffd000`22cd4a80 fffff802`8006cadb nt!ExFreePoolWithTag+0x2be ffffd000`22cd4b50 fffff802`800e8794 nt!ExpWorkerThread+0x293 ffffd000`22cd4c00 fffff802`801735c6 nt!PspSystemThreadStartup+0x58 ffffd000`22cd4c60 00000000`00000000 nt!KiStartSystemThread+0x16 rtwlanu.sys is the Realtek RTLxxxxx Wireless USB 2.0 Adapter driver. There's something 3rd party causing NETBIOS conflicts. PAGE_FAULT_IN_NONPAGED_AREA (50) This indicates that invalid system memory has been referenced. Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM). Another common cause is the installation of a faulty system service. Antivirus software can also trigger this error, as can a corrupted NTFS volume. Code: 2: kd> k Child-SP RetAddr Call Site ffffd000`9e186618 fffff802`9378724a nt!KeBugCheckEx ffffd000`9e186620 fffff802`936699c9 nt! ?? ::FNODOBFM::`string'+0x20d9a ffffd000`9e1866c0 fffff802`9376022f nt!MmAccessFault+0x7a9 ffffd000`9e186800 fffff801`ec738970 nt!KiPageFault+0x12f ffffd000`9e186990 00000000`00008401 rtwlanu+0xdc970 ffffd000`9e186998 00000000`00000000 0x8401 Same here as well, seems to have called into a pagefault. Remove and replace avast! with Windows 8's built-in Windows Defender for temporary troubleshooting purposes: avast! removal - avast! Uninstall Utility | Download aswClear for avast! Removal Windows Defender (how to turn on after removal) - Windows Defender - Turn On or Off in Windows 8 Regards, Patrick
Hi, We have two consistent bug checks: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) This indicates that a system thread generated an exception which the error handler did not catch. Code: BugCheck 1000007E, {ffffffffc0000005, 0, ffffd00022cd4818, ffffd00022cd4020} The 1st parameter of the bug check is 0xc0000005 which indicates an access violation occurred. Code: 0: kd> k Child-SP RetAddr Call Site ffffd000`22cd4a58 fffff800`49d3f25e 0x0 ffffd000`22cd4a60 fffff802`802ee220 rtwlanu+0xde25e ffffd000`22cd4a68 00000000`00000001 nt!PiUEventUsermodeEventQueueLock ffffd000`22cd4a70 ffffe000`5555bb80 0x1 ffffd000`22cd4a78 fffff802`802ae59e 0xffffe000`5555bb80 ffffd000`22cd4a80 fffff802`8006cadb nt!ExFreePoolWithTag+0x2be ffffd000`22cd4b50 fffff802`800e8794 nt!ExpWorkerThread+0x293 ffffd000`22cd4c00 fffff802`801735c6 nt!PspSystemThreadStartup+0x58 ffffd000`22cd4c60 00000000`00000000 nt!KiStartSystemThread+0x16 rtwlanu.sys is the Realtek RTLxxxxx Wireless USB 2.0 Adapter driver. There's something 3rd party causing NETBIOS conflicts. PAGE_FAULT_IN_NONPAGED_AREA (50) This indicates that invalid system memory has been referenced. Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM). Another common cause is the installation of a faulty system service. Antivirus software can also trigger this error, as can a corrupted NTFS volume. Code: 2: kd> k Child-SP RetAddr Call Site ffffd000`9e186618 fffff802`9378724a nt!KeBugCheckEx ffffd000`9e186620 fffff802`936699c9 nt! ?? ::FNODOBFM::`string'+0x20d9a ffffd000`9e1866c0 fffff802`9376022f nt!MmAccessFault+0x7a9 ffffd000`9e186800 fffff801`ec738970 nt!KiPageFault+0x12f ffffd000`9e186990 00000000`00008401 rtwlanu+0xdc970 ffffd000`9e186998 00000000`00000000 0x8401 Same here as well, seems to have called into a pagefault. Remove and replace avast! with Windows 8's built-in Windows Defender for temporary troubleshooting purposes: avast! removal - avast! Uninstall Utility | Download aswClear for avast! Removal Windows Defender (how to turn on after removal) - Windows Defender - Turn On or Off in Windows 8 Regards, Patrick