Purbeckfossil 17:33 07 Feb 14

OK – Here goes. I have had 7 BSOD occurrences in 7 days. Following various tips I have loaded windbg.exe and have had a look at the dumps but couldn’t see anything that looked obvious.

General consensus is that memory or drivers could be the most likely cause.

My desktop has 2x2GB memory blocks so I took one out, created a MEMTEST86 boot CD and ran it several times. One test passed and the others failed with type6 errors. I then replaced the memory block with the other and the test ran A-OK for 5 passes.

So, I left the machine as it was and it was fine for several days. So, as I wanted to put a graphics card in I decided to go ahead and bung in the Geforce 8400 GS card with driver downloaded from web.

As the desktop had been running on on-board ATI, I deleted the ATI Catalyst Manager.

Machine still OK but maybe 2 days later, I got a message that SM Bus driver was missing. It appeared that removing the ATI software had caused this so I re-installed it from the Foxconn Motherboard driver CD.

THEN, maybe a day later I get another BSOD after 5 clear days. I still had only the one memory block in. The dump created this time MEMORY.DMP at 117,508KB whereas all the other dumps were miniMMDDYY-nn.dmp files.

I can’t pretend to be an IT specialist but with this log of events, could it possibly be that re-installing the ATI Catalyst Manager caused the BSOD

I have the last minidump and the latest MEMORY.DMP zipped but there does not seem to be anywhere I can attach these files

Any comments would be enormously helpful in trying to resolve this.

  Fruit Bat /\0/\ 18:01 07 Feb 14

Blue screen viewer makes life easier when trying to solve this sort of problem. download and run it (its free).

then tell us what it shows about the BSOD you have had.

  Purbeckfossil 11:14 08 Feb 14

Thanks for quick response. I have set-up Blue Screen Viewer and the latest dump shows the following on the top of the screen

Mini020814-01.dmp 07/02/2014 18:22:02 KERNELMODEEXCEPTIONNOTHANDLED 0x1000008e 0xc0000005 0xbf85a83a 0xb11ddac4 0x00000000 win32k.sys win32k.sys+5a90e Multi-User Win32 Driver Microsoft® Windows® Operating System Microsoft Corporation 5.1.2600.6473 (xpspsp3qfe.131030-0418) 32-bit win32k.sys+5a83a win32k.sys+5a90e win32k.sys+e0a4b win32k.sys+e0f43 C:\WINDOWS\Minidump\Mini020814-01.dmp 1 15 2600 65,536 08/02/2014 10:18:40

followed by these two entries that are highlighted in pink on the bottom section:

ntkrnlpa.exe ntkrnlpa.exe+5b145 0x804d7000 0x806d0680 0x001f9680 0x51d4d90e 04/07/2013 02:08:14 Microsoft® Windows® Operating System NT Kernel & System 5.1.2600.6419 (xpspsp3qfe.130704-0421) Microsoft Corporation C:\WINDOWS\system32\ntkrnlpa.exe

win32k.sys win32k.sys+5a90e 0xbf800000 0xbf9cac00 0x001cac00 0x52706e3f 30/10/2013 02:26:07 Microsoft® Windows® Operating System Multi-User Win32 Driver 5.1.2600.6473 (xpspsp3qfe.131030-0418) Microsoft Corporation C:\WINDOWS\system32\win32k.sys

I have found updated chipset drivers for the Foxconn motherboard and also a new BIOS zip file.

So, I was thinking the following:

  1. REBOOT in safe mode and run CHKDSK /F from command prompt.
  2. Install chipset drivers
  3. Install new BIOS

Is this the way to go?


  Fruit Bat /\0/\ 12:44 08 Feb 14

1 and 2 yes

3 NO - never mess with the BIOS unless absolutely necessary - a bad BIOS flash can render the machine totally unusable.

In your case this is a windows / driver problem, possibly caused by HDD becoming corrupt in places.

This thread is now locked and can not be replied to.

Surface Pro (2017) vs Surface Pro 4

Where HTML5 is headed next

MacBook Pro v Surface Pro 5