Solved BSOD when doing anything, error 0x0000001a

altobi · Mar 8, 2012

Hi, this is my first time here.
Over the last year or so i've had many problems with my PC. The main problem is that the computer just shuts off or gets a BSOD. about 2-3 months ago i found out that my PSU (tegan 1300w) isnt doing well so i sendt it back (RMA) and got a new one (corsair hx1200). The computer was stable for 2-3 weeks then it started again. This time alot worse then ever.

The last hardware changed before the PSU was the GPUs (2x asus gtx 560) and a motherboard (Asus rampage extreme 3).

Now here's the last BSOD error code.
0x0000001a (0x0000000000041790, 0xfffffa8008596020, 0x000000000000ffff, 0x0000000000000000).

The computer often shuts off after 5-6 seconds when turning it on first time every day (happens on cold start only). but sometimes it does not, but rather alot of problems on the OS.

I really need help! I can't do this by my own anymore.

writhziden · Mar 8, 2012

These types of faults usually indicate hardware issues. I would do the following to check the hardware:

If you are overclocking any hardware, please stop.
Monitor temperatures during the following tests.

Use the following programs to monitor the temperatures.
- Real Temp is a good CPU temperature monitor.
- Speccy - System Information - Free Download will monitor all hardware temperatures.
- HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
- Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
- Run http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).

If you swap any memory components, follow these steps for ESD safety:
1. Shut down and turn off your computer.
2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working.
Once these steps have been followed, it is safe to remove and replace components within your computer.

altobi · Mar 9, 2012

Thanks for the reply

Thanks for replying.

Here's some results:

Hardware Temp: everything seems to be ok (see attached files)
FurMark: VGA Stress Test: very stable and no errors
Video Memory Test: 15 errors (see attached files)
CPU test: no errors (done it before too, without errors)

Thats how far i've come. Tell me if you get anything from this.

Thank you again

writhziden · Mar 9, 2012

Your graphics card memory is throwing errors...

I also see an out of date driver:

Code:

iaStor	fffff880`0127f000	fffff880`0139b000	Thu Jun 04 19:53:40 2009 (4a287aa4)	000640d7		iaStor.sys

Update using the Intel® Driver Update Utility

Try updating/re-installing your graphics card drivers using the following method (they may be up to date already, but they could be corrupted and need re-installing):

Re-install or install the latest drivers for your display card. Your current drivers may be corrupt and/or outdated. Use the following method to re-install the drivers.

Download the latest drivers for your display card(s)
Click Start Menu
Right Click My Computer/Computer
Click Manage
Click Device Manager from the list on the left
Expand Display adapters
Do the following for each adapter (in case you have multiple display cards)
- Right click the adapter
- Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
- Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
Restart your computer after uninstalling drivers for all display cards
Install the latest driver for the display cards once Windows starts

Alternatively:

Login as an adminstrative user
Download the latest drivers for your display card(s)
Click Start Menu
Click Control Panel
Click Hardware and Sound
Click Device Manager (the last link under Devices and Printers)
Expand Display adapters
Do the following for each adapter (in case you have multiple display cards)
- Right click the adapter
- Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
- Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
Restart your computer after uninstalling drivers for all display cards
Install the latest driver for the display cards once Windows starts

Also, install all Windows updates.

Run the graphics card memory test again for at least 7 passes once the graphics driver has been re-installed.

altobi · Mar 9, 2012

I've updated the graphic card driver many times. I also ran a new windows install 1-2months ago. all the drivers should be up to date. What driver do you see that is not up to date?

I can also add to the information. You asked about OC.
My system is not overclocked, but before i changed the PSU i had an error when booting the system (after it shuts off) which tells me that overcloking failed. This problem also happen 2-3 times after i changed the PSU.

Thank you again

writhziden · Mar 9, 2012

iaStor.sys is dated Thu Jun 04 19:53:40 2009 which is pre-Windows 7. May or may not need updating (I believe there is a newer version, but I could be wrong), but you should check the intel update utility just in case.

altobi · Mar 9, 2012

New BSOD :/

One more crash (BSOD)

writhziden · Mar 9, 2012

Problem devices:

Code:

Photosmart B110 series	ROOT\IMAGE\0000	This device is disabled.
Photosmart B110 series	ROOT\MULTIFUNCTION\0000	This device is disabled.

Antivirus software:

Code:

avfwsvc.exe	c:\program files (x86)\avira\antivir desktop\avfwsvc.exe	1716	8	200	1380	09.03.2012 20:45	12.1.0.15	601,95 kB (616*400 byte)	05.02.2012 17:13
avgnt.exe	c:\program files (x86)\avira\antivir desktop\avgnt.exe	4820	8	200	1380	09.03.2012 20:46	12.1.0.17	252,45 kB (258*512 byte)	05.02.2012 17:13
avguard.exe	c:\program files (x86)\avira\antivir desktop\avguard.exe	1740	8	200	1380	09.03.2012 20:45	12.1.0.18	107,45 kB (110*032 byte)	05.02.2012 17:13
avmailc.exe	c:\program files (x86)\avira\antivir desktop\avmailc.exe	2884	8	200	1380	09.03.2012 20:45	12.1.1.20	334,45 kB (342*480 byte)	05.02.2012 17:13
avshadow.exe	c:\program files (x86)\avira\antivir desktop\avshadow.exe	2852	8	200	1380	09.03.2012 20:45	12.1.0.10	242,95 kB (248*784 byte)	05.02.2012 17:13
avwebgrd.exe	c:\program files (x86)\avira\antivir desktop\avwebgrd.exe	2904	8	200	1380	09.03.2012 20:45	12.1.6.17	452,95 kB (463*824 byte)	05.02.2012 17:13
sched.exe	c:\program files (x86)\avira\antivir desktop\sched.exe	1548	8	200	1380	09.03.2012 20:45	12.1.0.18	84,20 kB (86*224 byte)	05.02.2012 17:13

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\altobi\Windows_NT6_BSOD_jcgriff2\030812-22276-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`03416000 PsLoadedModuleList = 0xfffff800`03653e70
Debug session time: Thu Mar  8 10:47:51.629 2012 (UTC - 7:00)
System Uptime: 0 days 4:35:41.644
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa8008596020, ffff, 0}

Probably caused by : win32k.sys ( win32k!SURFACE::bDeleteSurface+3c8 )

Followup: MachineOwner
---------

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa8008596020
Arg3: 000000000000ffff
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800034f9efe to fffff800034865c0

STACK_TEXT:  
fffff880`0b927428 fffff800`034f9efe : 00000000`0000001a 00000000`00041790 fffffa80`08596020 00000000`0000ffff : nt!KeBugCheckEx
fffff880`0b927430 fffff800`034c7fba : 00000000`00000000 00000000`05cdefff fffffa80`00000000 fffffa80`00000000 : nt! ?? ::FNODOBFM::`string'+0x338c6
fffff880`0b9275f0 fffff800`03485813 : ffffffff`ffffffff fffff880`0b9278b0 fffff880`0b927918 00000000`00008000 : nt!NtFreeVirtualMemory+0x5ca
fffff880`0b9276e0 fffff800`03481db0 : fffff960`001065a8 00000000`00000001 00000000`00000000 fffff900`c0b43cd0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`0b927878 fffff960`001065a8 : 00000000`00000001 00000000`00000000 fffff900`c0b43cd0 00000000`00000001 : nt!KiServiceLinkage
fffff880`0b927880 fffff960`0010e8c1 : 00000000`00000000 00000000`00000001 fffff900`c0b43cd0 fffff900`00000000 : win32k!SURFACE::bDeleteSurface+0x3c8
fffff880`0b9279d0 fffff960`00105ddc : 00000000`00001598 00000000`00000000 fffff900`c2995960 00000000`00000000 : win32k!NtGdiCloseProcess+0x2c9
fffff880`0b927a30 fffff960`00105523 : fffffa80`0ce58a00 00000000`00000001 fffffa80`0ed31060 fffffa80`0f9b64e0 : win32k!GdiProcessCallout+0x200
fffff880`0b927ab0 fffff800`037686bd : fffffa80`0ce58a30 00000000`00000000 00000000`00000000 fffffa80`0ed31060 : win32k!W32pProcessCallout+0x6b
fffff880`0b927ae0 fffff800`0374035b : 00000000`c0000005 00000000`00000001 fffffa80`0f9b6400 00000000`00000000 : nt!PspExitThread+0x561
fffff880`0b927ba0 fffff800`03485813 : fffffa80`0f9b64e0 00000000`c0000005 00000000`00000001 fffffa80`0ed31060 : nt!NtTerminateProcess+0x25b
fffff880`0b927c20 00000000`77aaf97a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0020dbd8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77aaf97a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!SURFACE::bDeleteSurface+3c8
fffff960`001065a8 e9b0010000      jmp     win32k!SURFACE::bDeleteSurface+0x57d (fffff960`0010675d)

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  win32k!SURFACE::bDeleteSurface+3c8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4f10fe35

FAILURE_BUCKET_ID:  X64_0x1a_41790_win32k!SURFACE::bDeleteSurface+3c8

BUCKET_ID:  X64_0x1a_41790_win32k!SURFACE::bDeleteSurface+3c8

Followup: MachineOwner
---------

The most recent crash was from March 8, 2012. It does not look like your most recent crash was recorded.

I suspect there is an issue with your graphics card based on the memory faults and you having already updated the driver many times. When you updated, did you delete the old driver software completely by putting a check in the box before hitting OK in the dialog that shows up after clicking uninstall?

Have you uninstalled all AMD software through the Start Menu -> Control panel -> Uninstall a program -> AMD Catalyst Install Manager or did you only install the drivers and not the software that can come with them.

altobi · Mar 9, 2012

Yes, i have done all that.

The last crash was also MEMORY_MANAGEMENT crash with the same error codes.

Could the crash be caused by the RAM i have installed?
i've lendt out one of the RAM pieces before, can it be the problem?
When i lendt it out i took out the rest of the RAM set tho (i have 2 RAM sets, 3x 2GB corsair + 3x 2GB corsair, same type and part number)

zigzag3143 · Mar 9, 2012

altobi said:
Yes, i have done all that.

The last crash was also MEMORY_MANAGEMENT crash with the same error codes.

Could the crash be caused by the RAM i have installed?
i've lendt out one of the RAM pieces before, can it be the problem?
When i lendt it out i took out the rest of the RAM set tho (i have 2 RAM sets, 3x 2GB corsair + 3x 2GB corsair, same type and part number)

Win 7 is very sensitive about ram. Even exact make and model is sometimes not enough. The only way to assure compatibility is to buy all the ram in a single package.

altobi · Mar 9, 2012

Well, i'll have to troubleshoot the RAM tomorrow after work then. Getting to late for me now.

Thank you for keeping up with me today, you'll hear from me tomorrow.

zigzag3143 · Mar 9, 2012

altobi said:
Well, i'll have to troubleshoot the RAM tomorrow after work then. Getting to late for me now.

Thank you for keeping up with me today, you'll hear from me tomorrow.

Good luck and yell if you need help

altobi · Mar 12, 2012

Hi again guys.
2 days since i took out one set of the installed RAM (the set that i thought had the problem)
and no BSOD or any windows crash yet.

Should I wait a cuple more days before sending them back (RMA)?

Thanks

writhziden · Mar 12, 2012

I would suggest that you wait at least twice as long as it usually takes for you to get a crash. To guarantee the system is stable, 1-3 weeks of doing your normal routine is recommended, and the longer, the better.

altobi · Mar 12, 2012

Alright, I'll wait

altobi · Mar 14, 2012

The problem was the RAM. Thanks everyone for the help

writhziden · Mar 14, 2012

You're very welcome. We were glad to help, and we are happy it was resolved with the RAM removal.

missleah · Oct 22, 2014

Solution

I also had this exact same BSOD and it was also the RAM that was bad. Just wanted to throw that out there.

Solved BSOD when doing anything, error 0x0000001a

New member

My Computer

Closed by request.

My Computer

New member

My Computer

Closed by request.

My Computer

New member

My Computer

Closed by request.

My Computer

New member

My Computer

Closed by request.

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

Closed by request.

My Computer

New member

My Computer

New member

My Computer

Closed by request.

My Computer

New member

My Computer

Similar threads