Bluescreen (BSOD)

M

Mr ClaudeZ

Member
Hello. Recently, problems like Blue Screen Of Death and sudden restarts or even suddenly the screen went blank happened once awhile in a day. Not that I never went to see other threads on this particular issue, but , I can't really figure out what many had written. In addition, I suppose there are different causes in different computer systems. In anyway, I hope someone could help me.

Here are the information my computer manage to show when it "recovered" from it.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 18441

Additional information about the problem:
BCCode: 1000008e
BCP1: C0000005
BCP2: 82A70247
BCP3: 916D163C
BCP4: 00000000
OS Version: 6_0_6002
Service Pack: 2_0
Product: 768_1

Files that help describe the problem:
C:\WINDOWS\Minidump\Mini092810-03.dmp
C:\Users\user\AppData\Local\Temp\WER-107968-0.sysdata.xml
C:\Users\user\AppData\Local\Temp\WERF334.tmp.version.txt

Is there any solution for my case? Certainly I would appreciate anyone's useful help.
 

My Computer

System One

Hello, it's you again, haha.
Hmm, mine is Window Vista Home Premium, running under 32-bit operating system. As for OEM, I don't know what's that, but if is Original Equipment Manufactured, it is Hewlett-Packard Company is the manufacturer. It all came when I bought around one year round or two years from then. I suppose the age of the hardware should be same too.

Well, here's the attachment, hope I did it correctly. Do help me analyse this data. It looks alien to me. =/
View attachment 20791

Look forward to your reply soon.
 

My Computer

System One

LOL you got me again. Not many members do detail BSOD work. Please note after Thursday, I will be unavailable for 3 weeks. I will leave a note that others should offer help after that date.
STOP 0x0000001A: MEMORY_MANAGEMENT Usual causes: Device driver, memory, kernel


STOP 0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint in startup without having a debugger attached, Hardware incompatibility, Faulty system service, 3rd party remote control, Memory

STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility

Code: 
roduct: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18267.x86fre.vistasp2_gdr.100608-0458
Machine Name:
Kernel base = 0x82a00000 PsLoadedModuleList = 0x82b17c70
Debug session time: Mon Sep 27 18:50:01.847 2010 (GMT-4)
System Uptime: 0 days 0:00:56.877
Loading Kernel Symbols
...............................................................
.................................................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {41287, 18, 0, 0}
Probably caused by : CI.dll ( CI!I_ReloadCatalogs+d8 )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041287, The subtype of the bugcheck.
Arg2: 00000018
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
 
BUGCHECK_STR:  0x1a_41287
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
CURRENT_IRQL:  0
TRAP_FRAME:  8dcfff84 -- (.trap 0xffffffff8dcfff84)
ErrCode = 00000000
eax=00000000 ebx=0000000e ecx=0000000f edx=00000000 esi=870f9d78 edi=9922e400
eip=82c3df49 esp=8dcffff8 ebp=8dd00038 iopl=0         nv up ei ng nz ac pe cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00210297
nt!CcMapData+0xaf:
82c3df49 8a17            mov     dl,byte ptr [edi]          ds:0023:9922e400=??
Resetting default scope
LAST_CONTROL_TRANSFER:  from 82a4ddd4 to 82a9838d
STACK_TEXT:  
8dd00038 8b09a574 86fe7ec0 8dd00070 00000400 nt!CcMapData+0xaf
8dd00060 8b09a674 8790e008 86d306e8 055ae400 Ntfs!NtfsMapStream+0x4a
8dd000dc 8b08fd7b 8790e008 86fc40d8 9ae367c0 Ntfs!NtfsReadMftRecord+0x7d
8dd00188 8b092c75 8790e008 9bfa7ea8 9bfa7d08 Ntfs!NtfsRetrieveOtherFileName+0xea
8dd00388 8b0938f6 8790e008 87a489f8 86fc40d8 Ntfs!NtfsQueryDirectory+0xc03
8dd003bc 8b093a3c 8790e008 9bfa7ea8 06d49ee1 Ntfs!NtfsCommonDirectoryControl+0x21c
8dd00424 82a449c6 86fc4020 87a489f8 87a489f8 Ntfs!NtfsFsdDirectoryControl+0xf4
8dd0043c 8a9d1ba7 86d31020 87a489f8 00000000 nt!IofCallDriver+0x63
8dd00460 8a9d1d64 8dd00480 86d31020 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x251
8dd00498 82a449c6 86d31020 87a489f8 87a489f8 fltmgr!FltpDispatch+0xc2
8dd004b0 82c467a3 8dd00524 8dd005c8 82c08d65 nt!IofCallDriver+0x63
8dd004d0 82c08dc0 86d31020 879d7028 00000001 nt!IopSynchronousServiceTail+0x1d9
8dd004f0 82a4ac7a 80001df0 00000000 00000000 nt!NtQueryDirectoryFile+0x5b
8dd004f0 82a493bd 80001df0 00000000 00000000 nt!KiFastCallEntry+0x12a
8dd00594 8a930df4 80001df0 00000000 00000000 nt!ZwQueryDirectoryFile+0x11
8dd00670 8a93105f 8dd006cc 8dd088ad 8dd0080c CI!I_ReloadCatalogs+0xd8
8dd006bc 8a931302 8dd00834 00000000 00000001 CI!I_FindFileOrHeaderHashInCatalogs+0xc1
8dd006e4 8a92deaf 8dd00834 00000001 00000001 CI!MinCrypK_FindPageHashesInCatalog+0x21
8dd00744 8a92e2bf 877cf3e0 8dd00834 8dd00794 CI!CipGetPageHashesForFile+0x9b
8dd007dc 8a92e903 877cf3e0 9b2c0000 00001000 CI!CipValidatePageHash+0xeb
8dd0084c 82b9afb5 877cf3e0 9b2c0000 00001000 CI!CiValidateImageHeader+0x143
8dd00868 82b9ae20 877cf3e0 9b2c0000 00001000 nt!SeValidateImageHeader+0x4d
8dd008dc 82c31191 877cf3e0 87a414b8 00000002 nt!MiValidateImageHeader+0x171
8dd009f8 82c31a86 8dd00a4c 0000000d 8dd00a9c nt!MmCreateSection+0x763
8dd00a6c 82bba060 8dd00adc 0000000d 8dd00a9c nt!NtCreateSection+0x177
8dd00ae4 82bb9c74 8dd00be0 8b957468 8dd00b20 nt!PfSnGetSectionObject+0x1a4
8dd00b78 82b46290 00d00be0 00000001 00000001 nt!PfSnPrefetchSections+0x1d3
8dd00bc8 82a449c6 8dd00bb0 ffffffff 0000000c nt!PfSnBootWorker+0x205
00000000 00000000 00000000 00000000 00000000 nt!IofCallDriver+0x63

Code: 
icrosoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp1_relevent%20information[1].zip\Windows_NT6_BSOD_jcgriff2\Mini092810-03.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 Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18267.x86fre.vistasp2_gdr.100608-0458
Machine Name:
Kernel base = 0x82a34000 PsLoadedModuleList = 0x82b4bc70
Debug session time: Tue Sep 28 04:05:44.352 2010 (GMT-4)
System Uptime: 0 days 0:02:52.366
Loading Kernel Symbols
...............................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 82a70247, 916d163c, 0}
Probably caused by : ntkrpamp.exe ( nt!FsFilterCtrlInit+2c )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 82a70247, The address that the exception occurred at
Arg3: 916d163c, Trap Frame
Arg4: 00000000

Outdated Drivers
Code: 
PS2.sys      Mon Dec 12 20:26:59 2005 
secdrv.SYS   Wed Sep 13 09:18:32 2006 
nvraid.sys   Tue Oct 03 20:25:15 2006 
peauth.sys   Mon Oct 23 04:55:32 2006 
crcdisk.sys  Thu Nov 02 04:52:27 2006 
spldr.sys    Thu Jun 21 20:29:17 2007 
nvstor32.sys Fri Dec 07 18:27:08 2007 
nvlddmkm.sys Thu Jan 10 09:15:12 2008 
processr.sys Sat Jan 19 00:27:20 2008 
Fs_Rec.SYS   Sat Jan 19 00:27:57 2008 
cdfs.sys     Sat Jan 19 00:28:02 2008 
Msfs.SYS     Sat Jan 19 00:28:08 2008 
bowser.sys   Sat Jan 19 00:28:26 2008 
luafv.sys    Sat Jan 19 00:30:35 2008 
msisadrv.sys Sat Jan 19 00:32:51 2008 
mssmbios.sys Sat Jan 19 00:32:55 2008 
fileinfo.sys Sat Jan 19 00:34:27 2008 
Dxapi.sys    Sat Jan 19 00:36:12 2008 
Beep.SYS     Sat Jan 19 00:49:10 2008 
Null.SYS     Sat Jan 19 00:49:12 2008 
mountmgr.sys Sat Jan 19 00:49:13 2008 
mouclass.sys Sat Jan 19 00:49:14 2008 
kbdclass.sys Sat Jan 19 00:49:14 2008 
i8042prt.sys Sat Jan 19 00:49:17 2008 
swenum.sys   Sat Jan 19 00:49:20 2008 
volmgr.sys   Sat Jan 19 00:49:51 2008 
vga.sys      Sat Jan 19 00:52:06 2008 
VIDEOPRT.SYS Sat Jan 19 00:52:10 2008 
WDFLDR.SYS   Sat Jan 19 00:52:19 2008 
monitor.sys  Sat Jan 19 00:52:19 2008 
Wdf01000.sys Sat Jan 19 00:52:21 2008 
WMILIB.SYS   Sat Jan 19 00:53:08 2008 
drmkaud.sys  Sat Jan 19 00:53:16 2008 
USBD.SYS     Sat Jan 19 00:53:17 2008 
usbccgp.sys  Sat Jan 19 00:53:29 2008 
umbus.sys    Sat Jan 19 00:53:40 2008 
mpsdrv.sys   Sat Jan 19 00:54:45 2008 
rspndr.sys   Sat Jan 19 00:55:03 2008 
lltdio.sys   Sat Jan 19 00:55:03 2008 
tunmp.sys    Sat Jan 19 00:55:40 2008 
netbios.sys  Sat Jan 19 00:55:45 2008 
nsiproxy.sys Sat Jan 19 00:55:50 2008 
ndistapi.sys Sat Jan 19 00:56:24 2008 
NDProxy.SYS  Sat Jan 19 00:56:28 2008 
wanarp.sys   Sat Jan 19 00:56:31 2008 
rasacd.sys   Sat Jan 19 00:56:31 2008 
rasl2tp.sys  Sat Jan 19 00:56:33 2008 
raspptp.sys  Sat Jan 19 00:56:34 2008 
TDI.SYS      Sat Jan 19 00:57:10 2008 
modem.sys    Sat Jan 19 00:57:16 2008 
RDPCDD.sys   Sat Jan 19 01:01:08 2008 
rdpencdd.sys Sat Jan 19 01:01:09 2008 
TSDDD.dll    Sat Jan 19 01:01:09 2008 
drmk.sys     Sat Jan 19 01:53:02 2008 
BOOTVID.dll  Sat Jan 19 02:27:15 2008 
RTKVHDA.sys  Thu Jul 03 04:58:00 2008

Your reports have indicated 3 separate error codes, as shown above. All 3 have drivers as a possible cause, 2 show memory; I will concentrate on those areas.

The reports that you have submitted reveal clues to the cause of your problem. They do not give a definitive answer. The more reports that we receive the more clues are made available improving our chances of finding a solution to your problem. You may have to experience several more BSODs until the final answer is discovered.

If overclocking restore normal settings

SFC /scannow
System Files - SFC Command
Download memtest86 and test RAM
www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
Update outdated listed drivers. If I have inadvertently listed any Microsoft Drivers, they can be ignored. If the list is extensive I have included a driver verifier test so that you can determine which drivers need immediate attention.

Enable the Driver Verifier
www.sevenforums.com/crash-lockup-debug-how/65331-using-driver-verifier-identify-issues-drivers.html
Scan with your Anti Virus

How to Find Drivers
search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone - will help you search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- - if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- The most common drivers are listed on this page: http://www.carrona.org/dvrref.html
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html
To remove any left over driver remnants, especially from graphics cards, use driver sweeper
www.guru3d.com/category/driversweeper/

After performing all of the above, post back with any new BSOD reports, or indicate that the attempted repairs were successful.
If any links do not work, if clicked, please copy and paste to browser address bar.
These reports are not definitive but merely point the way to a solution. It is very important to remember that the dump reports only give clues as to the problem and although it is very easy to analyze only one or two, usually more are needed. If you experience additional BSOD after installing a current version of the driver in question, be sure to post so that we can use the additional information to assist you in preventing the BSOD's
 
Last edited:

My Computer

System One

  • Manufacturer/Model
    Dell XPS420
    Memory
    6 gig
    Graphics Card(s)
    ATI Radeon HD3650 256 MB
    Sound Card
    Intergrated 7.1 Channel Audio
    Monitor(s) Displays
    Dell SP2009W 20 inch Flat Panel w Webcam
    Hard Drives
    640 gb
    Cooling
    Fan
    Keyboard
    Dell USB
    Mouse
    Dell USB 4 button optical
    Other Info
    DSL provided by ATT
Yeah, certainly not many members do detail BSOD work. Although it's slow for me to realise there is this "BSOD squad" under your name, I suppose you are another expert in this area too =D.
Okay, getting back to the topic. Everything seems complicated, however I will try my best to follow every information you gave. If I would to have any problem in the process of doing it, I will let post again in this thread to inform you.
Hope you can get back into business soon and once again, thank you.
 

My Computer

System One

eh mr richard. can u help me too?

Problem Event Name: BlueScreen
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 18441

Additional information about the problem:
BCCode: 1000008e
BCP1: C0000005
BCP2: 90A8A1CF
BCP3: C3ED1B38
BCP4: 00000000
OS Version: 6_0_6002
Service Pack: 2_0
Product: 768_1
 

My Computer

System One

My Computer

System One

  • Manufacturer/Model
    Dell XPS420
    Memory
    6 gig
    Graphics Card(s)
    ATI Radeon HD3650 256 MB
    Sound Card
    Intergrated 7.1 Channel Audio
    Monitor(s) Displays
    Dell SP2009W 20 inch Flat Panel w Webcam
    Hard Drives
    640 gb
    Cooling
    Fan
    Keyboard
    Dell USB
    Mouse
    Dell USB 4 button optical
    Other Info
    DSL provided by ATT
Hi richc46, sorry for the late updates. It's was unbelievable. I guessed it was miracle. The thing is that my computer is fixed ; no sign of BSOD, no sudden restarts and black-out. However, the weird thing is that despite following as you instructed, i was sort of like half way through, but the computer is fixed.
The process is like this, I did the memtest on my computer (but I did with all my rams), then strangely there was no signs of errors or problems. Oh, before this, I also installed the malwarebytes' Anti-malware, which helps me to fixed some errors when I first run it. But there is still seldom sudden restarts occuring after that. Then out of no great solution left, I went to take out my rams, then put it back, all back to the same position. Then after this, my computer did not experience anymore problem. Weird huh?
I guess that's all of this problem i faced, it's solved! (in a unusual way). Anyway, if you have extra time to spare, could you list out some reason why my computer recovered?
I would like to thank you again for your useful information which helped me in solving my problem, thank you.
 

My Computer

System One

One or more ram sticks had to be reset. Good job in following instructions and getting it up and running.
 

My Computer

System One

  • Manufacturer/Model
    Dell XPS420
    Memory
    6 gig
    Graphics Card(s)
    ATI Radeon HD3650 256 MB
    Sound Card
    Intergrated 7.1 Channel Audio
    Monitor(s) Displays
    Dell SP2009W 20 inch Flat Panel w Webcam
    Hard Drives
    640 gb
    Cooling
    Fan
    Keyboard
    Dell USB
    Mouse
    Dell USB 4 button optical
    Other Info
    DSL provided by ATT
Glad that I got you up and running Take care.
 

My Computer

System One

  • Manufacturer/Model
    Dell XPS420
    Memory
    6 gig
    Graphics Card(s)
    ATI Radeon HD3650 256 MB
    Sound Card
    Intergrated 7.1 Channel Audio
    Monitor(s) Displays
    Dell SP2009W 20 inch Flat Panel w Webcam
    Hard Drives
    640 gb
    Cooling
    Fan
    Keyboard
    Dell USB
    Mouse
    Dell USB 4 button optical
    Other Info
    DSL provided by ATT
You must log in or register to reply here.
Back
Top