Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.



Windows 7: BSOD at random times error 0x0000001e

17 Oct 2011   #1

Windows 7 Home Premium x64
 
 
BSOD at random times error 0x0000001e

Hello, first off i want to say thank you for viewing this thread, secondly i believe the error code was 0x0000001e (if not im sorry i uploaded as instructions of everything) I ran Memtest for atleast 10 hours and no errors what so ever. I have had problems with my Desktop ever since i did a driver scanner and then messed up my whole system i believe, i switched my computer cases from the default to a HAF922 coolmaster, upgraded my gtx260 to a gtx 580 with a 1000watt psu, and have had a BSOD randomly since I have done all this and I'm not sure what it is, I've tried everything to figure it out so now im going to ask the experts to please help!!! thank you!!


Windows 7 . - x86 (32-bit) or x64 ? Home premium x64 - the original installed OS on the system? Vista - an OEM or full retail version? OEM - What is the age of system (hardware)? no older then 2-3 years? its an Asus essentio cg5290-bp007 (upgtaded psu(1000watt MUSHKIN) and graphics card(gtx 580)) - What is the age of OS installation (have you re-installed the OS?) No, Just upgraded it when windows 7 came out (was a free upgrade to Windows 7 from asus for purchasing their Essentio desktop

I just want to thank everyone who will be able to help me because it will mean alot to me!! thank you so much

My System SpecsSystem Spec
.

17 Oct 2011   #2

Windows 8.1 Pro x64
 
 

Arctosa.sys, a driver used by your Razer Arctosa device is the cause, please update this driver
Razer Support
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Unable to load image \SystemRoot\system32\drivers\Arctosa.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Arctosa.sys
*** ERROR: Module load completed but symbols could not be loaded for Arctosa.sys
Probably caused by : Arctosa.sys ( Arctosa+11db )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+0
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800030db5fe to fffff800030e3c10

STACK_TEXT:  
fffff880`031fcc28 fffff800`030db5fe : 00000000`00000000 fffff800`0326e340 fffff880`031fd430 fffff800`0310f830 : nt!KeBugCheck
fffff880`031fcc30 fffff800`0310f4fd : fffff800`032ed71c fffff800`0322ac30 fffff800`03067000 fffff880`031fd390 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`031fcc60 fffff800`0310e2d5 : fffff800`0322e0fc fffff880`031fccd8 fffff880`031fd390 fffff800`03067000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`031fcc90 fffff800`031115c6 : fffff880`031fd390 fffff880`031fd430 00000000`00000001 00000000`00000008 : nt!RtlDispatchException+0x415
fffff880`031fd370 fffff800`0309e70a : 00000000`00000007 fffff880`042d70a4 fffffa80`093dc608 fffff880`042c6f99 : nt!RtlRaiseStatus+0x4e
fffff880`031fd910 fffff880`08c0e1db : fffffa80`096f48f0 fffff800`00000000 fffffa80`094e1c60 fffffa80`094e1e00 : nt! ?? ::FNODOBFM::`string'+0xf5a9
fffff880`031fd990 fffffa80`096f48f0 : fffff800`00000000 fffffa80`094e1c60 fffffa80`094e1e00 fffffa80`00000000 : Arctosa+0x11db
fffff880`031fd998 fffff800`00000000 : fffffa80`094e1c60 fffffa80`094e1e00 fffffa80`00000000 fffffa80`096f4a40 : 0xfffffa80`096f48f0
fffff880`031fd9a0 fffffa80`094e1c60 : fffffa80`094e1e00 fffffa80`00000000 fffffa80`096f4a40 00000000`00000000 : 0xfffff800`00000000
fffff880`031fd9a8 fffffa80`094e1e00 : fffffa80`00000000 fffffa80`096f4a40 00000000`00000000 ffff0280`00000090 : 0xfffffa80`094e1c60
fffff880`031fd9b0 fffffa80`00000000 : fffffa80`096f4a40 00000000`00000000 ffff0280`00000090 fffffa80`00000008 : 0xfffffa80`094e1e00
fffff880`031fd9b8 fffffa80`096f4a40 : 00000000`00000000 ffff0280`00000090 fffffa80`00000008 fffffa80`0960baa0 : 0xfffffa80`00000000
fffff880`031fd9c0 00000000`00000000 : ffff0280`00000090 fffffa80`00000008 fffffa80`0960baa0 00000000`00000000 : 0xfffffa80`096f4a40


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Arctosa+11db
fffff880`08c0e1db ??              ???

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  Arctosa+11db

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Arctosa

IMAGE_NAME:  Arctosa.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  48ca1eac

FAILURE_BUCKET_ID:  X64_0x1E_Arctosa+11db

BUCKET_ID:  X64_0x1E_Arctosa+11db

Followup: MachineOwner
---------
My System SpecsSystem Spec
17 Oct 2011   #3

Windows 7 Home Premium x64
 
 

Thank you so much for your fast reply I will go and search for the driver for this, thank you so much! hopefully no more bsod! +rep for you
My System SpecsSystem Spec
.


Reply

 BSOD at random times error 0x0000001e





Thread Tools



Similar help and support threads for2: BSOD at random times error 0x0000001e
Thread Forum
Solved It Seems I'm getting a Random BSOD error 0x0000001e BSOD Help and Support
Random BSOD error 0x0000001e BSOD Help and Support
BSOD many times in a day, error 0x0000001E BSOD Help and Support
Random BSOD, error 0x0000001e BSOD Help and Support
BSOD serveral times a day, error 0x0000001e BSOD Help and Support
Random BSOD error 0x0000001e BSOD Help and Support
Random BSOD's, error 0x0000001e BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 11:20 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33