Overclock.net › Forums › Graphics Cards › AMD/ATI › Black screen, looping sound and other problems
New Posts  All Forums:Forum Nav:

Black screen, looping sound and other problems - Page 2

post #11 of 14
Quote:
Originally Posted by MoReece View Post

Further update: I did a refresh of Windows 8 (removes all desktop software, but keeps files). The amount of BSOD's I get seems to have reduced, but they're still not gone. Reinstalled Assassin's Creed: Revelations (since it got removed during the refresh), and after a while it now crashes to desktop with the simple message "acrsp.exe has stopped working". Not sure if it's related to my original problem.

I ran dskchk, memory diagnostics and everything I could think of. Only thing that's left to do is swap out my RAM (although tests didn't return any errors) and then reinstall Windows. Pretty sure it's not my GPU, so this topic is probably in the wrong forum by now...

Can you post the error codes on the BSODs that you are getting? You'll need to head over to the even viewer and find the crashes there. That might suggest why your computer is crashing.
Combat 1.1
(16 items)
 
PAIN
(11 items)
 
 
CPUMotherboardGraphicsRAM
Intel Core i7 3930K P9X79 PRO GIGABYTE G1 Gaming GeForce GTX 970 Samsung  
RAMHard DriveHard DriveOptical Drive
Samsung  Crucial M4 64GB SSD Seagate Barracuda 1TB ASUS 24x DVD Burner 
CoolingOSOSMonitor
NH-D14 Windows 7 Ultamite 64 bit Arch Linux ASUS VW246H Glossy Black 24" HDMI Widescreen LC... 
KeyboardPowerCaseMouse
Logitech Combo mk520 Seasonic X Series 650W NXT Phantom 410 Logitech Combo mk520 
CPUMotherboardGraphicsRAM
Intel Core i7 2600K P8Z68-V PRO GEN3 NVIDIA GeForce GTX 560 Ti  Samsung  
RAMHard DriveHard DriveCooling
Samsung  Seagate Barracuda HDD Crucial M4 SSD Corsair H80 
OSPowerCase
Windows 7 Enterprise Seasonic M12II 750w Plexiglass 
  hide details  
Reply
Combat 1.1
(16 items)
 
PAIN
(11 items)
 
 
CPUMotherboardGraphicsRAM
Intel Core i7 3930K P9X79 PRO GIGABYTE G1 Gaming GeForce GTX 970 Samsung  
RAMHard DriveHard DriveOptical Drive
Samsung  Crucial M4 64GB SSD Seagate Barracuda 1TB ASUS 24x DVD Burner 
CoolingOSOSMonitor
NH-D14 Windows 7 Ultamite 64 bit Arch Linux ASUS VW246H Glossy Black 24" HDMI Widescreen LC... 
KeyboardPowerCaseMouse
Logitech Combo mk520 Seasonic X Series 650W NXT Phantom 410 Logitech Combo mk520 
CPUMotherboardGraphicsRAM
Intel Core i7 2600K P8Z68-V PRO GEN3 NVIDIA GeForce GTX 560 Ti  Samsung  
RAMHard DriveHard DriveCooling
Samsung  Seagate Barracuda HDD Crucial M4 SSD Corsair H80 
OSPowerCase
Windows 7 Enterprise Seasonic M12II 750w Plexiglass 
  hide details  
Reply
post #12 of 14
Thread Starter 
Well, there's a bunch of them. Here are some from a week ago, as analysed by WhoCrashed.
Quote:
On Tue 30/07/2013 20:51:00 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\073013-10623-01.dmp
This was probably caused by the following module: hal.dll (hal+0x17325)
Bugcheck code: 0xA (0xFFFFF800BDF507FE, 0x2, 0x1, 0xFFFFF800BE093228)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Tue 30/07/2013 20:51:00 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFFF800BDF507FE, 0x2, 0x1, 0xFFFFF800BE093228)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 30/07/2013 17:22:02 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\073013-15756-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x8A389)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800B9AA6389, 0xFFFFF88007360988, 0xFFFFF880073601C0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 29/07/2013 21:14:29 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\072913-11029-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR



On Mon 29/07/2013 20:32:43 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\072913-9703-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0xC000021A (0xFFFFF8A00165D730, 0x0, 0x0, 0x0)
Error: STATUS_SYSTEM_PROCESS_TERMINATED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This means that an error has occurred in a crucial user-mode subsystem.
There is a possibility this problem was caused by a virus or other malware.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 29/07/2013 20:29:57 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\072913-15022-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x5A440)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF8035B31D620, 0xFFFFFA8009B8A400, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 29/07/2013 20:29:33 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\072913-15022-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR

Yesterday, I did a full reinstall of Windows 8, but to no avail. BSOD's and restarts keep coming, only this time it's always something with ntsokrnl.exe or ntkrnlmp.exe. After the reinstall, sfc /scannow didn't find any corrupt files anymore, which it always did (and couldn't repair) before.
post #13 of 14
Doing a quick google search I came across these links explaining the errors you are getting.

STATUS_SYSTEM

IQRL
Combat 1.1
(16 items)
 
PAIN
(11 items)
 
 
CPUMotherboardGraphicsRAM
Intel Core i7 3930K P9X79 PRO GIGABYTE G1 Gaming GeForce GTX 970 Samsung  
RAMHard DriveHard DriveOptical Drive
Samsung  Crucial M4 64GB SSD Seagate Barracuda 1TB ASUS 24x DVD Burner 
CoolingOSOSMonitor
NH-D14 Windows 7 Ultamite 64 bit Arch Linux ASUS VW246H Glossy Black 24" HDMI Widescreen LC... 
KeyboardPowerCaseMouse
Logitech Combo mk520 Seasonic X Series 650W NXT Phantom 410 Logitech Combo mk520 
CPUMotherboardGraphicsRAM
Intel Core i7 2600K P8Z68-V PRO GEN3 NVIDIA GeForce GTX 560 Ti  Samsung  
RAMHard DriveHard DriveCooling
Samsung  Seagate Barracuda HDD Crucial M4 SSD Corsair H80 
OSPowerCase
Windows 7 Enterprise Seasonic M12II 750w Plexiglass 
  hide details  
Reply
Combat 1.1
(16 items)
 
PAIN
(11 items)
 
 
CPUMotherboardGraphicsRAM
Intel Core i7 3930K P9X79 PRO GIGABYTE G1 Gaming GeForce GTX 970 Samsung  
RAMHard DriveHard DriveOptical Drive
Samsung  Crucial M4 64GB SSD Seagate Barracuda 1TB ASUS 24x DVD Burner 
CoolingOSOSMonitor
NH-D14 Windows 7 Ultamite 64 bit Arch Linux ASUS VW246H Glossy Black 24" HDMI Widescreen LC... 
KeyboardPowerCaseMouse
Logitech Combo mk520 Seasonic X Series 650W NXT Phantom 410 Logitech Combo mk520 
CPUMotherboardGraphicsRAM
Intel Core i7 2600K P8Z68-V PRO GEN3 NVIDIA GeForce GTX 560 Ti  Samsung  
RAMHard DriveHard DriveCooling
Samsung  Seagate Barracuda HDD Crucial M4 SSD Corsair H80 
OSPowerCase
Windows 7 Enterprise Seasonic M12II 750w Plexiglass 
  hide details  
Reply
post #14 of 14
Thread Starter 
I seem to have solved the constant crashing that started to occur after I removed the BIOS battery: I switched out the motherboard. Despite being extra careful, maybe there was a bit of static electricity that ruined something? Haven't had the time to play Assassin's Creed and see if my original problem is resolved, but with a new motherboard and Windows reinstalled from scratch, I can't see why that problem would pop up again.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: AMD/ATI
Overclock.net › Forums › Graphics Cards › AMD/ATI › Black screen, looping sound and other problems