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 error please help

01 Mar 2010   #1
pragnesh89

Windows 7 Professional 32 Bit
 
 
BSOD error please help

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033
Additional information about the problem:
BCCode: 4e
BCP1: 00000007
BCP2: 00000004
BCP3: 00000001
BCP4: 00000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\022310-43071-01.dmp
C:\Users\Praggy\AppData\Local\Temp\WER-83756-0.sysdata.xml
Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

5th time
Additional information about the problem:
BCCode: 19
BCP1: 00000003
BCP2: 82B41918
BCP3: 1FCD2428
BCP4: 0FFE06F2
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1


I actually got this error about a week ago but only once. But in the last 3 hours, I have had about 5. I get a blue screen and my laptop restarts.

Somebody please help.

I am using a Dell Inspiron E1505 with windows 7.

I'm trying to attach a system scan but the files 8md exceeding the alloted 2 mb.


My System SpecsSystem Spec
.
01 Mar 2010   #2
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by pragnesh89 View Post
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033
Additional information about the problem:
BCCode: 4e
BCP1: 00000007
BCP2: 00000004
BCP3: 00000001
BCP4: 00000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
Files that help describe the problem:
C:\Windows\Minidump\022310-43071-01.dmp
C:\Users\Praggy\AppData\Local\Temp\WER-83756-0.sysdata.xml
Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

5th time
Additional information about the problem:
BCCode: 19
BCP1: 00000003
BCP2: 82B41918
BCP3: 1FCD2428
BCP4: 0FFE06F2
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1


I actually got this error about a week ago but only once. But in the last 3 hours, I have had about 5. I get a blue screen and my laptop restarts.

Somebody please help.

I am using a Dell Inspiron E1505 with windows 7.

I'm trying to attach a system scan but the files 8md exceeding the alloted 2 mb.
Hi and welcome

I have exactly the same computer.

You have several different causes. In 4 of the six BSOD's it was your AVG. in the other two a win 7 file. You also have some really old drivers dating from as far back as 2004. You must have upgraded and not clean installed.

I would upgrade all the old drivers (truth be told I would do a clean install)
uninstall AVG
run a system file check
type cmd in search>right click and run as admin>sfc /scannow

If you are overclocking stop

For some reason your version numbers do not correspond to the MS ones. I wonder where you got the image and if there were any "updates" applied that were not released from MS

Let us know as you may have to run other things


Ken

Code:
030110-31465-01.dmp    3/1/2010 6:52:40 PM    BAD_POOL_HEADER    0x00000019    0x00000003    0x82b41918    0x1fcd2428    0x0ffe06f2    ntkrnlpa.exe    ntkrnlpa.exe+120232        32-bit    
030110-21824-01.dmp    3/1/2010 6:32:26 PM    DRIVER_IRQL_NOT_LESS_OR_EQUAL    0x000000d1    0xea5b9878    0x00000002    0x00000000    0x8e4cc588    avgtdix.sys    avgtdix.sys+588        32-bit    
030110-23462-01.dmp    3/1/2010 6:27:10 PM    DRIVER_IRQL_NOT_LESS_OR_EQUAL    0x000000d1    0x6d6f6365    0x00000002    0x00000000    0x8e2ea588    avgtdix.sys    avgtdix.sys+588        32-bit    
030110-23540-01.dmp    3/1/2010 8:19:00 PM    IRQL_NOT_LESS_OR_EQUAL    0x0000000a    0xa8bdbec3    0x00000002    0x00000001    0x82a570d9    ntkrnlpa.exe    ntkrnlpa.exe+4685b        32-bit    
030110-23322-01.dmp    3/1/2010 6:13:48 PM    KERNEL_MODE_EXCEPTION_NOT_HANDLED    0x1000008e    0xc0000005    0x82c83511    0x9e6d78f0    0x00000000    ntkrnlpa.exe    ntkrnlpa.exe+232511        32-bit    
030110-32495-01.dmp    3/1/2010 7:36:48 PM    KERNEL_MODE_EXCEPTION_NOT_HANDLED    0x1000008e    0xc0000005    0x82c87511    0x9d4eb8f0    0x00000000    ntkrnlpa.exe    ntkrnlpa.exe+232511        32-bit    
022310-43071-01.dmp    2/23/2010 11:13:26 PM    PFN_LIST_CORRUPT    0x0000004e    0x00000007    0x00000004    0x00000001    0x00000000    ntkrnlpa.exe    ntkrnlpa.exe+91bec        32-bit
ANCIENT DRIVERS THAT NEED UPDATING
Code:
DellBIOS.Sys        0x9d396000    0x9d397400    0x00001400    0x42efd9ec    8/2/2005 3:39:08 PM                        
mdmxsdk.sys        0x9aca4000    0x9aca7100    0x00003100    0x4344688d    10/5/2005 6:58:05 PM                        
HSX_CNXT.sys        0x8d818000    0x8d8ce000    0x000b6000    0x438fa5f5    12/1/2005 8:40:05 PM                        
HSXHWAZL.sys        0x8ccaf000    0x8cce9000    0x0003a000    0x438fa5fa    12/1/2005 8:40:10 PM                        
HSX_DPV.sys        0x8cce9000    0x8cde0000    0x000f7000    0x438fa624    12/1/2005 8:40:52 PM                        
DRVMCDB.SYS        0x835dc000    0x835f1fe0    0x00015fe0    0x44c11aef    7/21/2006 1:20:31 PM                        
PxHelp20.sys        0x835f2000    0x835fab40    0x00008b40    0x44c5634d    7/24/2006 7:18:21 PM                        
DLARTL_M.SYS        0x8ce32000    0x8ce37320    0x00005320    0x44dcbf84    8/11/2006 12:33:56 PM                        
DRVNDDM.SYS        0x8d93d000    0x8d947600    0x0000a600    0x44dcc6db    8/11/2006 1:05:15 PM                        
DLAIFS_M.SYS        0x8d949000    0x8d960d20    0x00017d20    0x44e61fc3    8/18/2006 3:14:59 PM                        
DLAPoolM.SYS        0x8d966000    0x8d967dc0    0x00001dc0    0x44e61fc5    8/18/2006 3:15:01 PM                        
DLAUDF_M.SYS        0x8d9a6000    0x8d9bc340    0x00016340    0x44e61fd0    8/18/2006 3:15:12 PM                        
DLAUDFAM.SYS        0x8d990000    0x8d9a56c0    0x000156c0    0x44e61fe2    8/18/2006 3:15:30 PM                        
DLABOIOM.SYS        0x8d989000    0x8d98f3e0    0x000063e0    0x44e61fee    8/18/2006 3:15:42 PM                        
DLABMFSM.SYS        0x8d982000    0x8d988e20    0x00006e20    0x44e61ff3    8/18/2006 3:15:47 PM                        
DLAOPIOM.SYS        0x8d961000    0x8d965aa0    0x00004aa0    0x44e62014    8/18/2006 3:16:20 PM                        
DLADResM.SYS        0x8d948000    0x8d9489c0    0x000009c0    0x44e62041    8/18/2006 3:17:05 PM                        
secdrv.SYS        0x9ad3f000    0x9ad49000    0x0000a000    0x45080528    9/13/2006 8:18:32 AM                        
SynTP.sys        0x8f776000    0x8f7a0100    0x0002a100    0x454fe2b6    11/6/2006 8:34:46 PM                        
rixdptsk.sys        0x8f70d000    0x8f75e000    0x00051000    0x455a6ed7    11/14/2006 8:35:19 PM                        
bcm4sbxp.sys        0x8f6b7000    0x8f6c8000    0x00011000    0x4562f047    11/21/2006 7:25:43 AM                        
dne2000.sys        0x8f7d2000    0x8f7efb80    0x0001db80    0x45b70804    1/24/2007 2:17:24 AM                        
CVPNDRVA.sys        0x9ac14000    0x9aca4000    0x00090000    0x469bb176    7/16/2007 12:57:10 PM                        
NETw4v32.sys        0x8f423000    0x8f652000    0x0022f000    0x46fa5ab2    9/26/2007 8:12:18 AM                        
atikmdag.sys        0x8ee0b000    0x8f3f3000    0x005e8000    0x493450ba    12/1/2008 4:01:46 PM
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Minidump\030110-21824-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Machine Name:
Kernel base = 0x82a56000 PsLoadedModuleList = 0x82b9e810
Debug session time: Mon Mar  1 18:31:24.938 2010 (GMT-5)
System Uptime: 0 days 0:04:45.278
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
................................................................
............................................
Loading User Symbols
Loading unloaded module list
.......
Unable to load image \SystemRoot\System32\Drivers\avgtdix.sys, Win32 error 0n2
*** ERROR: Module load completed but symbols could not be loaded for avgtdix.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {ea5b9878, 2, 0, 8e4cc588}

Unable to load image \SystemRoot\system32\DRIVERS\avgfwd6x.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for avgfwd6x.sys
*** ERROR: Module load completed but symbols could not be loaded for avgfwd6x.sys
Unable to load image \SystemRoot\system32\DRIVERS\dne2000.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dne2000.sys
*** ERROR: Module load completed but symbols could not be loaded for dne2000.sys
Unable to load image \SystemRoot\system32\DRIVERS\NETw4v32.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NETw4v32.sys
*** ERROR: Module load completed but symbols could not be loaded for NETw4v32.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: nt!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
Probably caused by : avgtdix.sys ( avgtdix+588 )

Followup: MachineOwner
---------
My System SpecsSystem Spec
01 Mar 2010   #3
pragnesh89

Windows 7 Professional 32 Bit
 
 

That dell bios.sys is the latest one they have. Dell hasn't updated for e1505 since 2007. Regarding the other ones, I can't quite understand. Can you be a little more specific please, like telling me the names of these drivers so I can look it up.

P.S. I haven't had BSOD for the past 2 hours. Good news
My System SpecsSystem Spec
.

02 Mar 2010   #4
pragnesh89

Windows 7 Professional 32 Bit
 
 

Ok. So, I reinstalled the Dell BIOS last night, and I haven't had a crash since. Let's see how it goes.
My System SpecsSystem Spec
02 Mar 2010   #5
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by pragnesh89 View Post
That dell bios.sys is the latest one they have. Dell hasn't updated for e1505 since 2007. Regarding the other ones, I can't quite understand. Can you be a little more specific please, like telling me the names of these drivers so I can look it up.

P.S. I haven't had BSOD for the past 2 hours. Good news
sure lets take the second one in the list. clip the name and google it. You will find that it is for this. Mdmxsdk.sys driver. you can then go to the mfr and find the updated driver for it.

let me know if you need help

Ken
My System SpecsSystem Spec
02 Mar 2010   #6
pragnesh89

Windows 7 Professional 32 Bit
 
 

Hey, I searched for it and I found this link.

Download Mdmxsdk.sys

The version on this site is 1.0.2.002. How do I find out the version on my system? Please help
My System SpecsSystem Spec
Reply

 BSOD error please help




Thread Tools




Similar help and support threads
Thread Forum
BSOD error when computer goes to sleep. Unable to get error codes.
Recently I restored my computer to windows 7 after using Windows 8 for a short period of time provided by my university. I don't think the story as to why I went back is very necessary so I'll skip it and get onto my problem. Upon returning to Win7, I began to get some errors, namely my computer...
BSOD Help and Support
BSOD Memory Management Error, didn't catch error code.
Hello again, BSOD Forum, I've been free of frequent BSODs since earlier this year. Recently I must have installed some software or something else must have gone wrong, because the blue screens are back. Here is what happened earlier this year, in case anyone needs any further context: ...
BSOD Help and Support
Random BSOD stop error 0x0000001E, hardware error?
Hello, A few days ago I got a random BSOD with the 0x0..1E stop error. Now my computer will rarely boot and when it does it still randomly gets the same BSOD. I once got a 1D stop error but its mostly 1E that keeps happening. I run Windows 7 Professional 64-bit and this time I used a Windows DVD...
BSOD Help and Support
BSOD error.. Restarts, but power button stays on, graphics card error?
Hey guys, i want to thank you ahead of time for helping me. This BSOD is a pain in the butt. Intel Pentium 2.8GHZ RAM 3.5 32 bit OS Intel GG965 Express Chipset Family I have already reinstalled the operating system multiple times, i think its a faulty graphics card, but i want to be...
BSOD Help and Support
BSOD. error Custom built computer. error unknown between 0 or 1077...
Well I built this computer in september of 2011 everything was running great no problems at all until today. I left it on and went to the store came back and BSOD. My computer restarted before I could write down any information "Error code" system restore said it was a "unknown error" which...
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 23:48.
Twitter Facebook Google+ Seven Forums iOS App Seven Forums Android App