CC4 BSOD on building

[Bugs]

Hi all,

 

Hi have been dealing with this issue for nearly a year now, and have yet to find a proper resolution.

 

We bought a batch of RM NB14's last year and they have performed well, all have SSD's. We have noticed an issue with building them, Once they are building it gets past the first reboot and on the second reboot it hangs with a BSOD error driver is not equal to irq or something and the file name is tunnel.sys. For a time we found that removing all DNS and DHCP would resolve this which it did for a time but now I cant get any of them to build. I have also tried remiving the battery for a while, unplugging the CMOS battery, wiping the SSD but nothing seems to work.

 

Please help

[Danp]

Trying to remember, has it loaded the OS at that point? Are you PXEing building them?

 

I would fully expect there is the wrong driver in the build area, maybe network.

[X-13]

Trying to remember, has it loaded the OS at that point?

 

I believe so.

 

I would fully expect there is the wrong driver in the build area, maybe network.

 

If the network driver was wrong it wouldn't get this far. It'd fail before the first reboot due to not being able to connect to the server. [iIRC]

[Bugs]

Yes it goes through the OS installation, it then retrieves the drives and extracts them, it then reboots, not sure what it does here but it reboots again and its on this reboot that it always BSOD's I have checked the drive is for the NB14 and is the 2012 driver so its not very old.

 

I am PXE booting them as they don't appear to like RMR

 

what's odd is nobody else appears to have this issue.

[Danp]

I believe so.

 

 

 

If the network driver was wrong it wouldn't get this far. It'd fail before the first reboot due to not being able to connect to the server. [iIRC]

 

But, if they were booted from disk then at reboot time would be the first time it tried the network, hence me asking ;-)

@Bugs

 

Do you have the correct driver back from RM for those on the server? I know they are funny about them.

[Bugs]

yeah my line manager installed the driver pack for it, I have checked and the drivers are there and correct, surely though if the was a network driver issue I wouldn't be able to retrieve the OS?

 

I could be wrong entirely!

[Danp]

yeah my line manager installed the driver pack for it, I have checked and the drivers are there and correct, surely though if the was a network driver issue I wouldn't be able to retrieve the OS?

 

I could be wrong entirely!

 

PXE booting using one lot of drivers, but once the OS is installed it sometimes needs a different one! Not sure if that is official but it's something we found out with some odd one of machines

[X-13]

PXE booting using one lot of drivers, but once the OS is installed it sometimes needs a different one! Not sure if that is official but it's something we found out with some odd one of machines

 

IIRC, CC4 PxE boots Vista instead of Win7.

[Bugs]

OK, but I have been able to build previously, it just seems a bit random, we first thought it was a DNS issue so we removed all DNS records for that machine this worked initially but, it it isnt.

[X-13]

Have you tried restarting the RM host service? [RM service host?]

 

That usually fixes 9/10 problems with CCx core components.

[Bugs]

Yes we have restarted the RM host service, not specifically for the build issues but it made no difference

[X-13]

Yes we have restarted the RM host service, not specifically for the build issues but it made no difference

 

Best bet would be to log it with support if it's under warranty.

 

Something strange is going on...

[Bugs]

I had it logged for a while but we ended up going round in circles and not getting anywhere.

[Bugs]

OK, so I think I have narrowed it down to the SSD, I have rebuilt a previously non-working machine with a normal hard drive and its building fine. I have tried updating the firmware on one of the drives but, unfortunately it looks as if my machine has crashed so i`m going to give it an hour a reboot it if it hasnt recovered and cross my fingers it hasnt screwed the SSD

[foofighterjim]

If you have narrowed it down to HDD I do remember some time ago having Toshiba laptops that wouldn't build with AHCI enabled. We got around this by putting the hard drive into IDE mode in the BIOS. Edited June 3, 2014 by foofighterjim

[Bugs]

I had a look at that with an SSD installed the option is ghosted and I cant change it from AHCI

[Oaktech]

Try changing the HDD access mode in the bios from AHCI/SATA to IDE and see what happens...

 

Just read the last 2 posts... I'm late to the party here!

Edited June 3, 2014 by Oaktech

[foofighterjim]

What build disk are you building from? You should be using WinPE 3.1 as a minimum now (based on Windows 7 not Vista). It should only include Windows 7 build templates, if you have XP & Vista listed as well as Win 7 you are still using WinPE 2.0 wim which is Vista based and may be causing the issue.

[Bugs]

we are using WinPE2.0 but if I build an RM One with a SSD it builds no problem, so it seems to an issue with the combination of SSD and NB14

[foofighterjim]

I would say it is worth a try with WinPE 3.1 just on the off chance. The only other thing I can think of is if the NB14 and the drive are SATA 3. Is thee a way to slow the speed down to SATA 2 (either physically on the drive or through the BIOS)? The fact that it works fine in an RM One it would be worth checking what SATA type is on board for that.

[Bugs]

I have checked the SATA and the laptop and both are SATA 3 although I couldnt find official specs for the laptop, also the SSD has backwards compatibility to SATA2. I checked the BIOS on another laptop and oddly I could change the SATA mode on that machine. Edited June 3, 2014 by Bugs

[Bugs]

so I tried it in IDE mode and got the same results, so after complete trial and error I found if I pull the network cable during the first, second, and third restart it then appears to build (I have no idea why)

[jaf]

I would say this is a driver issue. As you are using WinPE 2.0 this will be using a Vista based driver for the first part of the build process for the network adapter. After it restarts the first time it then installs the devices - including the Windows 7 network driver. I think it is very likely this is causing your problems - so as has been said create a new build disk based on Win PE 3.1 and try this. Another thing to try is the box where you type in the name of the PC etc, if you click on one of the tabs at the top you can click a radio button saying choose the drivers myself (or something like that). From here choose a different driver for the network adapter and wireless adapter if relevant (might be trial and error here). If there are no other options then you need to import a more up to date driver into management console for the network adapter. You can also choose to use only RM approved drivers which might fix the problem. I hope that helps.

[Sam_Brown]

EDIT: Ok so that's been suggested already!

 

As pointed out before it's worth bearing in mind that the drivers required to build the computer are usually different to the ones windows will need once the computer has been built. I believe Win PE will use Vista Drivers and then when it's built and the O\S takes over it will be looking for Windows 7 drivers.

 

It's very possible for it to build correctly and then once Windows takes over and starts to install all the devices for it to pick up a bad driver and cause issues. The fact it's blue screening when trying to connect to the network and unplugging it from the network fixes this heavily suggests a nic driver error.

 

I've had a few cases with drivers where the drivers will appear to work absolutely fine but will cause sporadic problems over time. So just because they "work" don't assume they "work"

 

In fact I had this very issue before building a Stone laptop on RM where I had the correct driver however for some reason the particular version I was using was causing issues so removing it and re-adding an older one fixed the issue.

Edited June 6, 2014 by Sam_Brown