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: recurring BSOD, errors: 0x00000024 and 0x00000003B

27 Apr 2013   #21

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1

Appdata\Local\Temp is a protected operating system file under C: Users\Username ... hidden by default. So the OP is to first go to folder options,then unhide protected OS files (which is against system recommendations, may be heavy for noobs) and then delete it?

What I wanted to know is how you identified it as a problem?

My System SpecsSystem Spec
27 Apr 2013   #22

Windows 7 Ultimate 32-Bit & Windows 7 Ultimate 64-Bit

There shouldn't be any ?? in front of C:\ if there is a ? in front then there is an issue there.

But if he wants he could leave it there. Is dmp files point to

*                                                                                                                                           *
*                        Bugcheck Analysis                                                                                           *
*                                                                                                                                           *

An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arg1: 0000000000000040, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002ade0d8, address which referenced memory

Debugging Details:

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d07100
GetUlongFromAddress: unable to read from fffff80002d071c0
 0000000000000040 Nonpaged pool


fffff800`02ade0d8 f0480fba6b4000  lock bts qword ptr [rbx+40h],0



PROCESS_NAME:  svchost.exe
fffff880`019a2c08 8bf8            mov     edi,eax


SYMBOL_NAME:  NETIO!NsiGetAllParametersEx+258

FOLLOWUP_NAME:  MachineOwner




FAILURE_BUCKET_ID:  X64_0xA_NETIO!NsiGetAllParametersEx+258

BUCKET_ID:  X64_0xA_NETIO!NsiGetAllParametersEx+258

Followup: MachineOwner
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

An exception happened while executing a system service routine.
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002dd7074, Address of the instruction which caused the bugcheck
Arg3: fffff88007b4bdc0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

Debugging Details:

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

fffff800`02dd7074 0000            add     byte ptr [rax],al

CONTEXT:  fffff88007b4bdc0 -- (.cxr 0xfffff88007b4bdc0)
rax=0000000000000005 rbx=fffff88007b4c9c0 rcx=0000000000000001
rdx=fffff88007b4c8b0 rsi=0000000000000000 rdi=fffff8a00147d650
rip=fffff80002dd7074 rsp=fffff88007b4c7a0 rbp=0000000000000000
 r8=0000000000000000  r9=fffff8a00147d680 r10=0000000000000000
r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
r14=0000000000000001 r15=fffffa800acd3060
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
fffff800`02dd7074 0000            add     byte ptr [rax],al ds:002b:00000000`00000005=??
Resetting default scope


PROCESS_NAME:  spoolsv.exe


fffff800`02dd7074 0000            add     byte ptr [rax],al

LAST_CONTROL_TRANSFER:  from fffff80002dd6abc to fffff80002dd7074

fffff880`07b4c7a0 fffff800`02dd6abc : fffffa80`00000001 fffff880`07b4c8b0 fffffa80`0acd3060 fffff8a0`0147d680 : nt!ObpIncrementHandleCountEx+0x34
fffff880`07b4c860 fffff800`02dc87a9 : 00000000`00000001 fffff8a0`0147d680 00000000`00000000 fffff800`02deb800 : nt!ObpCreateHandle+0x19c
fffff880`07b4c970 fffff800`02db79d4 : fffff880`07b4cca0 00000000`00020002 fffff8a0`0147d680 00000000`00020002 : nt!ObOpenObjectByPointerWithTag+0x109
fffff880`07b4cb90 fffff800`02adae93 : fffffa80`0c297060 fffffa80`00020002 00000000`00000000 00000000`02ece7a8 : nt!NtOpenProcessTokenEx+0x114
fffff880`07b4cc20 00000000`772022da : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`02ece478 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x772022da

fffff800`02dd7074 0000            add     byte ptr [rax],al


SYMBOL_NAME:  nt!ObpIncrementHandleCountEx+34

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware


STACK_COMMAND:  .cxr 0xfffff88007b4bdc0 ; kb

MODULE_NAME: hardware



Followup: MachineOwner
My System SpecsSystem Spec
27 Apr 2013   #23

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64 Bit SP 1

Please read it.
Note File I/O functions in the Windows API convert "/" to "\" as part of converting the name to an NT-style name, except when using the "\\?\" prefix as detailed in the following sections.
The Windows API has many functions that also have Unicode versions to permit an extended-length path for a maximum total path length of 32,767 characters. This type of path is composed of components separated by backslashes, each up to the value returned in the lpMaximumComponentLength parameter of the GetVolumeInformation function (this value is commonly 255 characters). To specify an extended-length path, use the "\\?\" prefix. For example, "\\?\D:\very long path".
Note The maximum path of 32,767 characters is approximate, because the "\\?\" prefix may be expanded to a longer string by the system at run time, and this expansion applies to the total length.
The "\\?\" prefix can also be used with paths constructed according to the universal naming convention (UNC). To specify such a path using UNC, use the "\\?\UNC\" prefix. For example, "\\?\UNC\server\share", where "server" is the name of the computer and "share" is the name of the shared folder. These prefixes are not used as part of the path itself. They indicate that the path should be passed to the system with minimal modification, which means that you cannot use forward slashes to represent path separators, or a period to represent the current directory, or double dots to represent the parent directory. Because you cannot use the "\\?\" prefix with a relative path, relative paths are always limited to a total of MAX_PATH characters.
There is no need to perform any Unicode normalization on path and file name strings for use by the Windows file I/O API functions because the file system treats path and file names as an opaque sequence of WCHARs. Any normalization that your application requires should be performed with this in mind, external of any calls to related Windows file I/O API functions.
When using an API to create a directory, the specified path cannot be so long that you cannot append an 8.3 file name (that is, the directory name cannot exceed MAX_PATH minus 12).
The shell and the file system have different requirements. It is possible to create a path with the Windows API that the shell user interface is not able to interpret properly.

There are two main categories of namespace conventions used in the Windows APIs, commonly referred to as NT namespaces and the Win32 namespaces. The NT namespace was designed to be the lowest level namespace on which other subsystems and namespaces could exist, including the Win32 subsystem and, by extension, the Win32 namespaces. POSIX is another example of a subsystem in Windows that is built on top of the NT namespace. Early versions of Windows also defined several predefined, or reserved, names for certain special devices such as communications (serial and parallel) ports and the default display console as part of what is now called the NT device namespace, and are still supported in current versions of Windows for backward compatibility.
Win32 File Namespaces

The Win32 namespace prefixing and conventions are summarized in this section and the following section, with descriptions of how they are used. Note that these examples are intended for use with the Windows API functions and do not all necessarily work with Windows shell applications such as Windows Explorer. For this reason there is a wider range of possible paths than is usually available from Windows shell applications, and Windows applications that take advantage of this can be developed using these namespace conventions.
For file I/O, the "\\?\" prefix to a path string tells the Windows APIs to disable all string parsing and to send the string that follows it straight to the file system. For example, if the file system supports large paths and file names, you can exceed the MAX_PATH limits that are otherwise enforced by the Windows APIs. For more information about the normal maximum path limitation, see the previous section Maximum Path Length Limitation.
Because it turns off automatic expansion of the path string, the "\\?\" prefix also allows the use of ".." and "." in the path names, which can be useful if you are attempting to perform operations on a file with these otherwise reserved relative path specifiers as part of the fully qualified path.
Many but not all file I/O APIs support "\\?\"; you should look at the reference topic for each API to be sure.
Source: Naming Files, Paths, and Namespaces
It appears to be not an issue, but a long path.
My System SpecsSystem Spec

27 Apr 2013   #24

Windows 7 Professional 64bit

finally regained access after a series of BSOD's... I'll try to uninstall (delete?) the files as indicated by VistaKing.

yes, i tried several memory tests, as indicated on first page... maybe file still from them?

anyways, i'll post my progress as I try your indications. guys, you are really patient thanks a million!
My System SpecsSystem Spec
27 Apr 2013   #25

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium x86 Service Pack 1 - Linux Mint Mate 14 x64

AVG is a known cause of BSODs with Windows 7, please remove the program with the official AVG Removal Tool and then install these free and proven alternatives which work with Windows 7:

Install and perform full scans with:
information   Information
Remember to install the free version of Malwarebytes not the free trail; untick the free trial box during installation. MSE is the most lightweight and compatible with the Windows 7 operating system

You can also view this thread for a complete free and lightweight security protection combination:

Sorry saw that I already suggested to install MSE in my first post, I'm not sure if you have done it yet or not.

3: kd> lmvm SynTP
start             end                 module name
fffff880`05c01000 fffff880`05c77000   SynTP    T (no symbols)           
    Loaded symbol image file: SynTP.sys
    Image path: SynTP.sys
    Image name: SynTP.sys
    Timestamp:        Thu Oct 18 05:56:11 2012 (507F8BEB)
    CheckSum:         00072CBB
    ImageSize:        00076000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Your Synaptic Touch Pad Driver may be causing a few problems, please update it from here:
3: kd> lmvm igdkmd64 
start             end                 module name
fffff880`04c04000 fffff880`057c1d60   igdkmd64 T (no symbols)           
    Loaded symbol image file: igdkmd64.sys
    Image path: igdkmd64.sys
    Image name: igdkmd64.sys
    Timestamp:        Tue Jan 10 22:28:09 2012 (4F0CBB79)
    CheckSum:         00BC541D
    ImageSize:        00BBDD60
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Your onboard Intel Graphics driver may also be contributing, please update the driver from here:
My System SpecsSystem Spec
29 Apr 2013   #26

Windows 7 Professional 64bit

Hi guys,

sorry, couldn't get to it earlier... so, now I have:
- updated intel graphics driver
- updated touchpad driver
- installed microsoft security essentials & malwarebytes
- removed AVG (hopefully no traces of it left)
- scanned the SSD with the intel SSD toolbox, no errors found

here is a few screen captures and the SF diagnostics... now let's see if the machine behaves stable for more than short stints. i'll report back.

thanks for your help !

My System SpecsSystem Spec
29 Apr 2013   #27

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium x86 Service Pack 1 - Linux Mint Mate 14 x64

Welcome, and thanks for the update, leave this thread open for a few days.
My System SpecsSystem Spec
29 Apr 2013   #28

Windows 7 Professional 64bit

so, I was optimistic... the ungrateful box promptly threw a 0x000001e at us

here are the SF diagnostics, if you still feel it's worth trying

My System SpecsSystem Spec
30 Apr 2013   #29

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium x86 Service Pack 1 - Linux Mint Mate 14 x64

Your Intel Rapid Storage driver seems to be causing some issues, there is one known stable driver which works with Windows 7, and this is dated as 6/11/2012, with the version number of - RAID: Intel® Rapid Storage Technology Driver for Intel Desktop Boards

3: kd> lmvm iaStor
start             end                 module name
fffff880`01235000 fffff880`015d9000   iaStor   T (no symbols)           
    Loaded symbol image file: iaStor.sys
    Image path: iaStor.sys
    Image name: iaStor.sys
    Timestamp:        Wed May 30 21:40:40 2012 (4FC685C8)
    CheckSum:         00091790
    ImageSize:        003A4000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
My System SpecsSystem Spec
30 Apr 2013   #30

Windows 7 Professional 64bit


I updated this driver and the process ran fine to the end. However, once i go to device manager to see the version of driver installed I get the same dated 5/30/2012 (not 6/11/2012). This although the driver I downloaded from the intel page and installed is apparently dated as you say (june).

As far as I know the version number is the relevant piece of info, the date could be different. Correct?


My System SpecsSystem Spec

 recurring BSOD, errors: 0x00000024 and 0x00000003B

Thread Tools

Similar help and support threads for2: recurring BSOD, errors: 0x00000024 and 0x00000003B
Thread Forum
BSOD Errors: 0x0000001E - 0x000000C1 - 0x00000024 And so on BSOD Help and Support
BSOD at random, errors 0x0000001e, 0x00000024, 0x0000003b, 0x00000050 BSOD Help and Support
Recurring BSODs with various STOP errors BSOD Help and Support
BSOD 0x00000003b BSOD Help and Support
BSOD 0x00000003b BSOD Help and Support
Recurring warnings and errors(event viewer) General Discussion

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 10:11 AM.
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