Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Plague of Blue Screen Errors: Vista & Win 7 Trial SP1


  • Please log in to reply

#1
DoubleTapDesign

DoubleTapDesign

    New Member

  • Member
  • Pip
  • 9 posts
Hello! I have been having some issues with my HP machine for the past few weeks, and have tried various fixes to no avail. I am at the end of my rope on this one, and would truly appreciate some guidance! Here are some details:

Computer came with Vista factory installed - ran fine for a few years, started getting blue screen errors - tried various fixes, nothing worked.

I ran:
memtest86 - overnight, multiple passes no errors
MBAM - nothing detected
HP Hardware diagnostics - no errors
chkdsk - no errors
seatools - no errors
enabled driver verifier, ran fine for a few hours eventually crashing to one of the same blue screens as before.


I updated every driver i possibly could - nothing. I tried to restore the computer to factory conditions using the rescue discs I had created (and used before without issue) - nothing. Still blue screen, more frequently now.

Frustrated, I installed Ubuntu 11.10 - this runs fine without error - I am even using it right now to type this. Because all of the tests passed without error, and I can Ubuntu just fine, I figured it may not be a hardware problem, so I ran DBAN (default settings) on my drive for about 8 hours (500GiB SATA Drive) to be sure it was clean, and then attempted to reinstall windows using a windows 7 SP1 trial disc instead of my rescue discs because I figured it was time to upgrade anyways.

Windows 7 installed just fine, But BAM! Blue screens again. I updated drivers, installed all available updates, but nothing works. it just kills itself. As of this moment, I am running Ubuntu 11.10 on one partition, and I have a very broken windows 7 install on another. I could boot into windows last night without too much trouble, although it crashed frequently. This morning however, it will not boot at all!

edit* I will add, that on top of the windows 7 install I did install Google chrome,Nvidia Control panel(to update drivers), Adobe Illustrator, Dreamweaver and Fireworks CS5.

I would love to just be done with it and move onto ubuntu until I can purchase a new machine, but I rely upon the Adobe Master Suite for work, and I cannot get it to work in WINE, so I will need to continue using windows, if only for those applications. I have attached all of the minidump files from the windows side, and I can make some sense of them, but would love to have some guidance from the pros! Please help me! Thanks in advance!

Attached Files


Edited by DoubleTapDesign, 09 February 2012 - 11:05 AM.

  • 0

Advertisements


#2
jcgriff2

jcgriff2

    Member

  • Expert
  • 92 posts
  • MVP
Hi -

What Windows 7 trial disc did you use?

Was it this one - http://technet.micro...center/cc442495

If not, wipe HDD again and install W7 Enterprise.



Or, you can see if updating these drivers helps:
[font=lucida console]
nvstor.sys      Fri Mar 19 16:51:52 2010 (4BA3E3E8) - NVIDIA nForce
nvm62x32.sys    Fri Oct 17 17:00:39 2008 (48F8FCF7)
nvstor32.sys    Mon Jun 22 18:19:03 2009 (4A400357)
nvmf6232.sys    Thu Jul 30 19:47:55 2009 (4A72312B)

nvlddmkm.sys    Thu May 14 16:32:27 2009 (4A0C7FDB) - NVIDIA video

VSTCNXT3.SYS    Wed Oct 15 20:29:13 2008 (48F68AD9) - Conexant SoftK56 Modem Driver
VSTBS23.SYS     Wed Oct 15 20:30:15 2008 (48F68B17)
VSTDPV3.SYS     Wed Oct 15 20:32:04 2008 (48F68B84)
HSXHWBS2.sys    Fri Feb 13 15:58:27 2009 (4995DEF3)
HSX_DP.sys      Fri Feb 13 15:56:27 2009 (4995DE7B)
HSX_CNXT.sys    Fri Feb 13 15:57:25 2009 (4995DEB5)
XAudio32.sys    Wed Apr 29 14:20:55 2009 (49F89A87)
mdmxsdk.sys     Mon Jun 19 17:26:59 2006 (449716A3)
[/font]

http://sysnative.com/drivers/driver.php?id=nvstor.sys
http://sysnative.com/drivers/driver.php?id=nvm62x32.sys
http://sysnative.com/drivers/driver.php?id=nvstor32.sys
http://sysnative.com/drivers/driver.php?id=nvmf6232.sys

http://sysnative.com/drivers/driver.php?id=nvlddmkm.sys

http://sysnative.com/drivers/driver.php?id=VSTCNXT3.SYS
http://sysnative.com/drivers/driver.php?id=VSTBS23.SYS
http://sysnative.com/drivers/driver.php?id=VSTDPV3.SYS

http://sysnative.com/drivers/driver.php?id=HSXHWBS2.sys
http://sysnative.com/drivers/driver.php?id=HSX_DP.sys
http://sysnative.com/drivers/driver.php?id=HSX_CNXT.sys
http://sysnative.com/drivers/driver.php?id=XAudio32.sys
http://sysnative.com/drivers/driver.php?id=mdmxsdk.sys



Regards. . .

jcgriff2


`



BSOD SUMMARY
[font=lucida console]
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\020812-26052-01.dmp]
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Debug session time: Wed Feb  8 20:41:35.500 2012 (GMT-5)
System Uptime: 0 days 0:00:20.436
Probably caused by : ntkrpamp.exe ( nt!KiSystemFatalException+f )
BUGCHECK_STR:  0x7f_d
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  audiodg.exe
FAILURE_BUCKET_ID:  0x7f_d_nt!KiSystemFatalException+f
Bugcheck code 0000007F
Arguments 0000000d 00000000 00000000 00000000
BiosVersion = 5.21 
BiosReleaseDate = 11/02/2007
SystemManufacturer = HP-Pavilion
SystemProductName = KC746AA-ABA a6333w
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\020812-23337-01.dmp]
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Debug session time: Wed Feb  8 21:18:53.789 2012 (GMT-5)
System Uptime: 0 days 0:30:56.724
BugCheck D1, {1, ff, 1, 86911d4b}
Probably caused by : ntkrpamp.exe ( nt!KiTrap0E+2cf )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  iexplore.exe
FAILURE_BUCKET_ID:  0xD1_nt!KiTrap0E+2cf
Bugcheck code 000000D1
Arguments 00000001 000000ff 00000001 86911d4b
BiosVersion = 5.21 
BiosReleaseDate = 11/02/2007
SystemManufacturer = HP-Pavilion
SystemProductName = KC746AA-ABA a6333w
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\020812-20716-01.dmp]
Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505
Debug session time: Wed Feb  8 23:03:49.111 2012 (GMT-5)
System Uptime: 0 days 0:10:19.736
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for win32k.sys - 
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID:  0x50_win32k!CLIPOBJ_bEnum+37c0
Bugcheck code 00000050
Arguments ffffffec 00000001 91b0b9a5 00000000
BiosVersion = 5.21 
BiosReleaseDate = 11/02/2007
SystemManufacturer = HP-Pavilion
SystemProductName = KC746AA-ABA a6333w
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\020812-33165-01.dmp]
Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505
Debug session time: Wed Feb  8 22:13:28.882 2012 (GMT-5)
System Uptime: 0 days 0:19:08.817
Probably caused by : memory_corruption ( nt!MiLockProtoPoolPage+19 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  msiexec.exe
FAILURE_BUCKET_ID:  0xA_nt!MiLockProtoPoolPage+19
Bugcheck code 0000000A
Arguments c078a1c8 00000000 00000000 828491b7
BiosVersion = 5.21 
BiosReleaseDate = 11/02/2007
SystemManufacturer = HP-Pavilion
SystemProductName = KC746AA-ABA a6333w
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\020812-19687-01.dmp]
Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505
Debug session time: Wed Feb  8 22:51:21.403 2012 (GMT-5)
System Uptime: 0 days 0:27:11.338
BugCheck D1, {c89d9a07, 2, 1, 8f565c6a}
*** WARNING: Unable to verify timestamp for nvmf6232.sys
*** ERROR: Module load completed but symbols could not be loaded for nvmf6232.sys
Probably caused by : nvmf6232.sys ( nvmf6232+4c6a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  0xD1_nvmf6232+4c6a
Bugcheck code 000000D1
Arguments c89d9a07 00000002 00000001 8f565c6a
BiosVersion = 5.21 
BiosReleaseDate = 11/02/2007
SystemManufacturer = HP-Pavilion
SystemProductName = KC746AA-ABA a6333w
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\020812-17924-01.dmp]
Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505
Debug session time: Wed Feb  8 22:52:50.865 2012 (GMT-5)
System Uptime: 0 days 0:00:46.800
BugCheck D1, {0, ff, 1, 86a74d4a}
Probably caused by : ntkrpamp.exe ( nt!KiTrap0E+2cf )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  0xD1_nt!KiTrap0E+2cf
Bugcheck code 000000D1
Arguments 00000000 000000ff 00000001 86a74d4a
BiosVersion = 5.21 
BiosReleaseDate = 11/02/2007
SystemManufacturer = HP-Pavilion
SystemProductName = KC746AA-ABA a6333w
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\020812-25022-01.dmp]
Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505
Debug session time: Wed Feb  8 23:52:31.539 2012 (GMT-5)
System Uptime: 0 days 0:02:55.164
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  iexplore.exe
Bugcheck code 00000050
Arguments 00615640 00000000 75abcb6d 00000008
BiosVersion = 5.21 
BiosReleaseDate = 11/02/2007
SystemManufacturer = HP-Pavilion
SystemProductName = KC746AA-ABA a6333w
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\020812-23571-01.dmp]
Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505
Debug session time: Wed Feb  8 23:48:54.802 2012 (GMT-5)
System Uptime: 0 days 0:09:56.737
BugCheck D1, {15, 2, 1, 92e34c6a}
*** WARNING: Unable to verify timestamp for nvmf6232.sys
*** ERROR: Module load completed but symbols could not be loaded for nvmf6232.sys
Probably caused by : nvmf6232.sys ( nvmf6232+4c6a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  0xD1_nvmf6232+4c6a
Bugcheck code 000000D1
Arguments 00000015 00000002 00000001 92e34c6a
BiosVersion = 5.21 
BiosReleaseDate = 11/02/2007
SystemManufacturer = HP-Pavilion
SystemProductName = KC746AA-ABA a6333w
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\020812-18548-01.dmp]
Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505
Debug session time: Wed Feb  8 23:37:51.852 2012 (GMT-5)
System Uptime: 0 days 0:04:31.788
Probably caused by : fileinfo.sys ( fileinfo!FIStreamGet+36 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x8E
PROCESS_NAME:  SearchIndexer.
FAILURE_BUCKET_ID:  0x8E_fileinfo!FIStreamGet+36
Bugcheck code 1000008E
Arguments c0000005 828338e7 9c3d87c8 00000000
BiosVersion = 5.21 
BiosReleaseDate = 11/02/2007
SystemManufacturer = HP-Pavilion
SystemProductName = KC746AA-ABA a6333w
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\020812-29359-01.dmp]
Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505
Debug session time: Wed Feb  8 23:30:06.463 2012 (GMT-5)
System Uptime: 0 days 0:23:54.399
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000
BugCheck D1, {62, 4, 0, 8fb244f7}
Probably caused by : ntkrpamp.exe ( nt!PoIdle+524 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  0xD1_nt!PoIdle+524
Bugcheck code 000000D1
Arguments 00000062 00000004 00000000 8fb244f7
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
  J. C. Griffith, Microsoft MVP (jcgriff2)       
   https://mvp.support.microsoft.com/profile/Griffith  
จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ

  • 1

#3
DoubleTapDesign

DoubleTapDesign

    New Member

  • Topic Starter
  • Member
  • Pip
  • 9 posts
Thanks a million for the fast reply and resources! I will update all of those drivers, and I will also burn off the version you suggested right away, and report back. Thanks again!

Edit* I used the trial version found here: http://www.softpedia...Windows-7.shtml

Edit* Hello again! I formatted the HDD and installed using the enterprise .ISO and all seems well thus far. There was an issue installing a couple of the windows updates, but other than that it seems fine. I am running Verifier at the moment, and will install a few CS5 trials and play around a bit to see what happens. Thanks again!

Edit* System froze - no blue screen - attempting to install Google Chrome. CS5 Installs went fine.

Edited by DoubleTapDesign, 09 February 2012 - 03:57 PM.

  • 0

#4
DoubleTapDesign

DoubleTapDesign

    New Member

  • Topic Starter
  • Member
  • Pip
  • 9 posts
Hello again! I was able to use the system for a while, but after being AFK for about 30 mins, I returned and found there had been another Blue Screen O' Death! I have attached the dump - there is a reference to a bugcheck code (totally new to bluescreenview, but trying to learn) , and looking up the code I found references to bad RAM - I did run memtest86 overnight with no errors before running DBAN and starting again, but I have not tested each stick individually due to my success at running Ubuntu 11.10 for days on end with no problems.

At this point should I even worry about testing each stick by itself? I have 2 1Gig sticks, and 2 512MB Sticks, both came factory installed and I have not modified a single aspect of the hardware, other than the addition of peripherals - none of which have been connected yet to this install.

Thanks for all of your help thus far - It's running stable enough with Enterprise for me to get a bit of work done, MUCH better than things have been the past few weeks.

Attached Files


  • 0

#5
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
I help on a number of threads and it is not practical for me to download files.

If you wish me to have a look I am more than prepared to do so, but please download this and send me a copy and paste of the actual results.
http://www.resplendence.com/downloads

DOWNLOAD Who Crashed please.


  • 1

#6
DoubleTapDesign

DoubleTapDesign

    New Member

  • Topic Starter
  • Member
  • Pip
  • 9 posts
Hello! Thanks for the reply! Here are the results of analysis from WhoCrashed - it detected more dumps than were showing in the minidump folder, i rebooted and now I can see there were more than one! I can paste the contents of the dump files from bluescreenview if that will help too - thanks for your help!

computer name: HESH-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: AuthenticAMD AMD Athlon™ 64 X2 Dual Core Processor 4800+ AMD586, level: 15
2 logical processors, active mask: 3
RAM: 3085410304 total
VM: 2147352576, free: 1968156672



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Fri 2/10/2012 12:24:13 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020912-21060-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x467EB)
Bugcheck code: 0xA (0xFFFFFFFFFF18C5F4, 0x0, 0x0, 0xFFFFFFFF828B15E3)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoftฎ Windowsฎ Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 2/10/2012 12:24:13 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!Kei386EoiHelper+0x29B3)
Bugcheck code: 0xA (0xFFFFFFFFFF18C5F4, 0x0, 0x0, 0xFFFFFFFF828B15E3)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ntkrpamp.exe .
Google query: ntkrpamp.exe IRQL_NOT_LESS_OR_EQUAL




On Thu 2/9/2012 11:24:49 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020912-23072-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x858E3)
Bugcheck code: 0x1A (0x41287, 0x20646162, 0x0, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoftฎ Windowsฎ Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 2/9/2012 9:08:38 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020912-15615-01.dmp
This was probably caused by the following module: hal.sys (hal+0x590F)
Bugcheck code: 0xC9 (0xC, 0xFFFFFFFF8791B4F0, 0xFFFFFFFF8D9FCF68, 0x0)
Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION
Bug check description: This is the bug check code for all Driver Verifier
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hal.sys .
Google query: hal.sys DRIVER_VERIFIER_IOMANAGER_VIOLATION




On Thu 2/9/2012 8:08:53 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020912-21715-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x46F2B)
Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoftฎ Windowsฎ Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 2/9/2012 7:58:09 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020912-27128-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x858E3)
Bugcheck code: 0x50 (0xFFFFFFFFC0540200, 0x0, 0xFFFFFFFF828A6DCA, 0x9)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoftฎ Windowsฎ Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 2/9/2012 7:51:11 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020912-22261-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x858E3)
Bugcheck code: 0xBE (0xFFFFFFFFA6BAF090, 0xFFFFFFFFA9FEF121, 0xFFFFFFFF81E17394, 0xB)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoftฎ Windowsฎ Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 2/9/2012 7:46:50 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\020912-14991-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCD10)
Bugcheck code: 0x101 (0x61, 0x0, 0xFFFFFFFF807C6120, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoftฎ Windowsฎ Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
  • 0

#7
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
In view of the fact that you were experiencing problems with Vista and are now having problems with Windows 7, it is important that we attempt to separate the two.

Lets start please, unless you KNOW the answer for certain by verifying that the computer can run Windows 7.
As it ran Vista the answer is more than likely YES
However go here please and check.
http://www.microsoft...us/default.aspx
unless I say you already have.


I believe that HP Pavilion 6333w came with the two Igb sticks and the two 512 sticks, am I correct please.
If so and despite it running on Ubuntu and you running Memtest please take out the two 512 sticks and run it with the 2 Igb sticks, one stick in each channel.
See how it is then please.
If still experiencing crashes, please run it with I of the 1Gb sticks and one of the 512 sticks populating ONLY ONE CHANNEL
If still a problem please change the 1Gb in use and test and if still a problem please change the 512 in use.
If you then reach a situation whefre it does NOT crash, replace the ram that IS IN USE, with the sticks that are NOT in use, ONE at a time please.

NB read your post 4 now. - not modified
  • 1

#8
DoubleTapDesign

DoubleTapDesign

    New Member

  • Topic Starter
  • Member
  • Pip
  • 9 posts
I ran the advisor, and it identified a driver - the Nvidia graphics driver - as being in need of update. I had already updated it to the recommended version, but for some reason it is not being reflected at all in the system. I have just updated the driver, and will start to test the RAM as suggested - thanks!

Edit* Other than the single issue regarding the Nvidia driver, everything else was fine according to the advisor.

Edit* Running on just the Single Gig RAM (x2) at the moment - attempted to duplicate the conditions prior to the last crash (installing google chrome while listening to an .MP3 with 2 tabs open in IE 9) and I was able to install Chrome just fine this time, and my tunes are still running - no crashes just yet. I will Load up a graphics editor and lay around for a bit to see what happens. Thanks again!

Edited by DoubleTapDesign, 09 February 2012 - 08:08 PM.

  • 0

#9
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
You are welcome I am signing off as it is 0212 and I am in the UK
Back about 1800hrs.


Nvidia drivers are mostly these days - simple to install and you no longer need to uninstall before you install an update driver.
HOWEVER you do still need to uninstall ancilliary Nvidia utilities downloaded BEFORE you install the driver.
If you go back and look at the instructions on the Nvidia site you will see what I mean.

Sorry about missing at first the details of the ram and the model of HP , however did spot it and edited my post.

I will check when I return to see how you are going.

NB re the ram if all Ok as it is, you need to test with ONE of the 1Gb and ONE of the 512.
If you go dual channel you must balance it.
It is all about getting four pieces of card and labelling them
ONE - I GB
TWO 1Gb
THREE 512
FOUR 512.

Sorry if that sounds insulting, but if you do NOT do that or similar, you will soon forget which has been in which slot with which other stick.
YOU simply then on the pieces of card endorse as you test eg. 1 with 3 OK.
etc.
The only trick then is to make sure the stick goes back on the correct piece of card.

Good night.
  • 1

#10
DoubleTapDesign

DoubleTapDesign

    New Member

  • Topic Starter
  • Member
  • Pip
  • 9 posts
Not insulting at all! I totally understand - and that is exactly what I did - made sure to note which slot each came from. We are working with a lot of variables here, so I wanted to make sure all my tests are as well documented as I can make them. My ultimate goal is to not only fix my system without replacing it if I have to, but to learn as much as possible in the process. The more I "learn to fish" so-to-speak, the more I can help others, and contribute to communities such as this :) Thanks again! Sleep well!
  • 0

#11
DoubleTapDesign

DoubleTapDesign

    New Member

  • Topic Starter
  • Member
  • Pip
  • 9 posts
Hello again! after pulling the 2x512MB RAM sticks and running all night, I came downstairs this morning and the computer was still up and running just fine. I will be putting it through some paces today, I have a few design projects to catch up on, so I will see how it holds up - seems stable thus far! Thanks again!
  • 0

#12
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
You are welcome.
All the more so because you are so clearly appreciative.
A few people do not even bother to reply or say thank you.

All the best and come back of course whenever you wish.
  • 0

#13
DoubleTapDesign

DoubleTapDesign

    New Member

  • Topic Starter
  • Member
  • Pip
  • 9 posts
I can't see how someone could take another's help for granted, how selfish and assuming. Not only do I appreciate it whole-heartedly, but my entire family thanks you for the help! Without a working windows install I cannot do my work, I am self-employed and rely upon quite a few windows-only applications. It has been almost 3 weeks since I have been able to collect on any of my invoices due to non-completion of the work, and boy do we need it! I have been happily working on everything without a hitch all day so far! Once again, THANKS A MILLION!
  • 0

#14
DoubleTapDesign

DoubleTapDesign

    New Member

  • Topic Starter
  • Member
  • Pip
  • 9 posts
Well, I think it is safe to call this one solved! I haven't encountered a single issue, and the pc has been running and updating just fine - even when I am listening to music, running multiple tabs in 2 or more browsers and using Illustrator, Fireworks and various other apps simultaneously. Thanks again - you really saved my hide on this one! Woohoo!
  • 0

#15
Macboatmaster

Macboatmaster

    7k

  • Member
  • PipPipPipPipPipPipPipPip
  • 7,237 posts
Thanks for posting the final result.

If you are thinking of increasing the ram to take account of the lost 1Gb in the two 512Mb. The best advice is to match exactly the 2 1Gb sticks that are in.
Then run with 4 Gb albeit 32 bit windows will only actually see approx 3.5Gb
Or you can of course wait and decide in the light of future plans.

http://msdn.microsof...imits_windows_7


  • 1






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP